Professional Documents
Culture Documents
Frame Relay Technology
Frame Relay Technology
Frame Relay is still one of the most popular WAN services deployed over the past
decade, and there's a good reason for this-cost. By default, Frame Relay is classified as a
non-broadcast multi-access (NBMA) network, meaning it doesn't send any broadcasts
like RIP updates across the network.
Frame Relay has at its roots a technology called X.25, and it essentially incorporates the
components of X.25 that are still relevant to today's reliable and relatively "clean"
telecommunications networks while leaving out the no-longer-needed error-correction
components.
It's substantially more complex than the simple leased-line networks you learned about
when I discussed the HDLC and PPP protocols, but is still relevant when looking at
even the most commonly used networks. The leased-line networks are easy to
conceptualize - but not so much when it comes to Frame Relay.
It can be significantly more complex and versatile, which is why it's often represented
as a "cloud" in networking graphics.
If, for example, you had to add seven remote sites to the corporate office and had only
one free serial port on your router-it's Frame Relay to the rescue! Of course, I should
probably mention that you now also have one single point of failure, which is not so
good. But Frame Relay is used to save money, not to make a network more resilient.
Take a look at the picture below to get an idea of what a network looked like before and
after Frame Relay.
Committed Information Rate (CIR)
Frame Relay works by providing a portion of dedicated bandwidth to each user, and it
also allows the user to exceed their guaranteed bandwidth if resources on the telco
network happen to be available. So basically, Frame Relay providers allow customers to
buy a lower amount of bandwidth than what they really use.
Encapsulation Types
When configuring Frame Relay on Cisco routers, you need to specify it as an
encapsulation on serial interfaces. You can't use HDLC or PPP with Frame Relay. When
you configure Frame Relay, you specify an encapsulation of Frame Relay (as shown in
the following output).But unlike HDLC or PPP, with Frame Relay, there are two
encapsulation types: Cisco and IETF (Internet Engineering Task Force). The following
router output shows these two different encapsulation methods when Frame Relay is
chosen on your Cisco router:
CiscoTests-HQ(config)#
CiscoTests-HQ(config)#int se 1/0
CiscoTests-HQ(config-if)#
CiscoTests-HQ(config-if)#encapsulation frame-relay ?
MFR Multilink Frame Relay bundle interface
ietf Use RFC1490/RFC2427 encapsulation
<cr>
CiscoTests-HQ(config-if)#encapsulation frame-relay
The default encapsulation is Cisco unless you manually type in ietf, and Cisco is the
type to use when connecting two Cisco devices. You'd opt for the IETF-type
encapsulation if you needed to connect a Cisco device to a non-Cisco device with Frame
Relay. Whichever you choose, make sure that the Frame Relay encapsulation is the
same on both ends.
Permanent virtual circuits (PVCs) are by far the most common type in use today. What
"permanent" means here is that the telco creates the mappings inside their gear and as
long as you pay the bill, they'll remain in place.
Switched virtual circuits (SVCs) are more like a phone call. The virtual circuit is
established when data needs to be transmitted, then it's taken down when the data
transfer is complete.
Before we go on, I want to define Inverse ARP (IARP) and discuss how it's used with
DLCIs in a Frame Relay network. It is somewhat similar to ARP in the fact that it maps
a DLCI to an IP address-kind of like ARP does with MAC addresses to IP addresses.
And even though you can't configure IARP, you can disable it. It runs on a Frame Relay
router and maps the DLCI to an IP address for Frame Relay so it knows how to get to
the Frame Relay switch. You can see IP-to-DLCI mappings with the show frame-relay
map command. But if you have a non-Cisco router living in your network and it doesn't
support IARP, then you're stuck with having to statically provide IP-to-DLCI mappings
with the frame-relay map command.
Local Management Interface (LMI)
Local Management Interface (LMI) is a signaling standard used between your router
and the first Frame Relay switch it's connected to. It allows for passing information
about the operation and status of the virtual circuit between the provider's network and
the DTE (your router). It communicates information about the following:
Keepalives - These verify that data is flowing.
Multicasting - This is an optional extension of the LMI specification that allows,
for example, the efficient distribution of routing information and ARP requests
over a Frame Relay network. Multicasting uses the reserved DLCIs from 1019
through 1022.
Global addressing - This provides global significance to DLCIs, allowing the
Frame Relay cloud to work exactly like a LAN.
Status of virtual circuits - This provides DLCI status. The status inquiries and
messages are used as keepalives when there is no regular LMI traffic to send.
There are three different types of LMI message formats: Cisco, ANSI, and Q.933A. The
different kinds in use depend on both the type and configuration of the telco's
switching gear, so it's imperative that you configure your router for the correct format,
which should be provided by the telco.