Showing posts with label Frame Relay. Show all posts
Showing posts with label Frame Relay. Show all posts

Wednesday, July 24, 2013

Frame Relay - Address Mapping

Address Mapping in Frame Relay Circuits

A router needs a method to map a DLCI to an IP address, similar to the way ARP maps a MAC address to an IP address.  This is accomplished in two ways:

  1. Inverse ARP - 
    • Default config for Frame Relay
    • provider uses LMI to send a list of DLCIs to the local router, and the local router sends Inverse ARP requests to all other DLCIs, asking for their IP address.  All DLCIs respond with IP address.  
    • If you have multiple DLCIs, your interface becomes a multipoint interface, however - Inverse ARP does not work with subinterfaces
  2. Static Mapping
    • Complete control, but more config
    • Assign IP addresses to DLCIs
    • R1(config-if)#frame-relay map ip 192.168.5.2 503 broadcast 

Frame Relay - NBMA, Split-horizon and Subinterfaces

A little more info regarding frame relay circuits:

Frame Relay is a NBMA (Non-broadcast Multi Access) network, meaning that it does not allow broadcast traffic between devices.  This will cause a problem if you use distance-vector routing protocols such as RIP, because the split-horizon loop avoidance mechanism will prevent updates from going back out the interface on which they came.  In a hub-and-spoke configuration, the spoke offices will not get updates about each other.

To avoid the split-horizon issues created in this instance, one could disable split-horizon and rely on the other loop-avoidance mechanisms (not recommended) or use subinterfaces.

Subinterfaces are logical interfaces attached to a single physical interface.  The router sees and treats them as separate interfaces, however.

Multipoint subinterfaces do not solve the split-horizon issues and are essentially useless in Fream Relay circuits.  They simply add multipoint interfaces to a logical interface, recreating all the same issues as a physical subinterface.  Meh...

Point-to-point subinterfaces allow a single, physical interface to hold multiple ports.  They are created using a "dot" - instead of Serial 0/0 we now have Serial 0/0.10.  Each subinterface can connect a PVC of its own, and the router treats each like a different port.




Tuesday, July 23, 2013

Frame Relay 101

It does seem to be a little silly to be reviewing Frame Relay in such depth for the 640-802 CCNA exam, but I suppose that's one of the reasons Cisco is retiring the exam and old guys like me are cramming to get this taken.  Anyhow...

Frame Relay is a technology that is packet-switched instead of cell-switched like ATM.  The fundamentals are that each router on either end of the Frame Relay circuit connects to the provider network, and there is a virtual circuit inside the provider network that makes those routers think they are directly connected.  Doing a traceroute from one end of the virtual circuit to another shows only one hop, even though there are undoubtedly several devices within the provider network the packet traverses.

The 3 Major Designs are:
  1. Hub and Spoke - all branch offices connect to a central site.  The main benefit is cost savings, while the main sacrifices are redundancy and tandem switching (routing all traffic through the main hub)
  2. Partial Mesh - key sites have multiple virtual circuit connections
  3. Full Mesh - all sites connected to every other site, which is expensive.
 PVC (permanent virtual circuit) is an always-on virtual circuit, no set up time

SVC (switched virtual circuit) is an on-demand virtual circuit

LMI (Local Management Interface) is the language used for the provider to send status info about the state of the virtual circuit to the router

DLCI - because serial interfaces have no MAC address, they use a Data Link Connection Identifier to determine which interface with which to communicate.  DLCI numbers are locally significant in that, when traffic is destined for a remote IP address, it goes out a local DLCI instead of heading to a destination DLCI like in the case of using a MAC address. 

CIR (Committed Information Rate) is the minimum speed the provider promises to you at all times.  Each PVC has its own CIR, and anything over that minimum rate is marked "De" or discard eligible - which means it can be dropped if there is not sufficient bandwidth.

BECN (Backward Explicit Congestion Notice) alerts the sending device that it should slow down.  BECN goes away from the congested resource to the sending resources

FECN (Forward Explicit Congestion Notice) is data used to generate traffic back to the sender to tell it to slow down, and is sent to the receiving device by the FR provider.