Frame Relay: © 2007 Cisco Systems, Inc. All Rights Reserved. Cisco Confidential Presentation - ID

Frame Relay
Presentation_ID
2007 Cisco Systems, Inc. All rights reserved.
Cisco Confidential
Frame Relay
Frame Relay is a packet-switched, connection-oriented, WAN service. Frame Relay operates at the data link layer of the OSI reference model. Frame Relay uses a subset of the high-level data-link control (HDLC) protocol called Link Access Procedure for Frame Relay (LAPF).
Presentation_ID
Cisco Confidential
Frame Relay DTEs and DCEs

In a Frame Relay topology the routers at the edge of each LAN are the DTEs.
The Frame Relay switch is a DCE device.
A serial connection, such as a T1 leased line (local loop), will connect the router to a Frame Relay switch of the carrier at the nearest point-of-presence for the carrier.
Presentation_ID
Cisco Confidential
Terminology
The connection through the Frame Relay network between two DTEs is called a virtual circuit (VC). Generally, permanent virtual circuits (PVCs) that have been preconfigured by the carrier are used. Virtual circuits may be established dynamically by sending signaling messages to the network. In this case they are called switched virtual circuits (SVCs).
SVCs are far less common than PVCS SVCs are more common with X.25, the predecessor of FR
Presentation_ID
Cisco Confidential
PVCs and DLCIs

The Frame Relay router connected to the Frame Relay network may have multiple virtual circuits connecting it to various end points.
The various virtual circuits on a single access line can be distinguished because each VC has its own Data Link Connection Identifier (DLCI).
Presentation_ID
Cisco Confidential
Frame Relay Functions

1.
2.
Frame Relay receives a packet from the network layer protocol, such as IP.
Frame Relay wraps it with a layer 2 address field which contains the DLCI.
3.
The frame is then passed to the physical layer and transmitted on the wire.
Presentation_ID
Cisco Confidential
Frame Relay Operation
Presentation_ID
Cisco Confidential
PVCs and DLCIs

The Frame Relay router connected to the Frame Relay network may have multiple virtual circuits connecting it to various end points. The various virtual circuits on a single access line can be distinguished because each VC has its own Data Link Connection Identifier (DLCI). The 10-bit DLCI field of the Frame Relay frame allows VC identifiers 0 through 1023.
The LMI extensions reserve some of these identifiers.
Presentation_ID
Cisco Confidential
Local Significance of DLCIs

The data-link connection identifier (DLCI) is stored in the Address field of every frame transmitted.
PVC
PVC
Presentation_ID
Cisco Confidential
Frame Relay Switches

Frame Relay switches basically route from one DLCI to another.
Each local serial interface is assigned a local DLCI.
In order for layer 3 routed protocols to run over Frame Relay interfaces, each interfaces IP address must be mapped to a layer 2 DLCI. This mapping of the remote IP address to a local DLCI occurs at the local routers interface via a frame-relay map or through inverse ARP.
-if)#frame-relay map ip 172.31.254.2 201
Presentation_ID
Cisco Confidential
10
IETF Frame Relay Frame
Cisco routers support two types of Frame Relay headers. Cisco, which is a 4-byte header (default, Cisco proprietary). IETF, which is a 2-byte header that conforms to the IETF standards.
Presentation_ID
Cisco Confidential
11
Presentation_ID
Cisco Confidential
12
Presentation_ID
Cisco Confidential
13
DLCI
A data-link connection identifier (DLCI) identifies the logical VC between the CPE and the Frame Relay switch. The Frame Relay switch maps the DLCIs between each pair of routers to create a PVC.
DLCIs have local significance, although there some implementations that use global DLCIs.
DLCIs 0 to 15 and 1008 to 1023 are reserved for special purposes. Service providers assign DLCIs in the range of 16 to 1007. DLCI 1019, 1020: Multicasts
DLCI 1023: Cisco LMI

DLCI 0: ANSI LMI
Presentation_ID
Cisco Confidential
14
DLCI
Inside the cloud, your Frame Relay provider sets up the DLCI numbers
to be used by the routers for establishing PVCs.
Presentation_ID 2007 Cisco Systems, Inc. All rights reserved. Cisco Confidential
15
Frame Relay bandwidth and flow control

The first thing we need to do is become familiar with some of the terminology.
Local access rate This is the clock speed or port speed of the connection or local loop to the Frame Relay cloud.
It is the rate at which data travels into or out of the network, regardless of other settings.
Committed Information Rate (CIR) This is the rate, in bits per second, at which the Frame Relay switch agrees to transfer data.
The rate is usually averaged over a period of time, referred to as the committed rate measurement interval (Tc).
Presentation_ID
Cisco Confidential
16

Tc = 2 seconds Bc = 64 kbps CIR = 32 kbps
Committed burst (Bc) The maximum number of bits that the switch agrees to transfer during any Tc.
The higher the Bc-to-CIR ratio, the longer the switch can handle a sustained burst. The DE (Discard Eligibility) bit is set on the traffic that was received after the CIR was met. (FYI) For example, if the Tc is 2 seconds and the CIR is 32 kbps, the Bc is 64 kbps. (FYI) The Tc calculation is Tc = Bc/CIR.
Committed Time Interval (Tc) Tc is not a recurrent time interval. It is used strictly to measure inbound data, during which time it acts like a sliding window. Inbound data triggers the Tc interval.
17
Frame Relay bandwidth

Several factors determine the rate at which a customer can send data on a Frame Relay network.
Foremost in limiting the maximum transmission rate is the capacity of the local loop to the provider. If the local loop is a T1, no more than 1.544 Mbps can be sent. In Frame Relay terminology, the speed of the local loop is called the local access rate. Providers use the CIR parameter to provision network resources and regulate usage. For example, a company with a T1 connection to the packet-switched network (PSN) may agree to a CIR of 768 Kbps. This means that the provider guarantees 768 Kbps of bandwidth to the customers link at all times.
Presentation_ID
Cisco Confidential
18
Typically, the higher the CIR, the higher the cost of service. Customers can choose the CIR that is most appropriate to their bandwidth needs, as long as the CIR is less than or equal to the local access rate. If the CIR of the customer is less than the local access rate, the customer and provider agree on whether bursting above the CIR is allowed. If the local access rate is T1 or 1.544 Mbps, and the CIR is 768 Kbps, half of the potential bandwidth (as determined by the local access rate) remains available.
19
Many providers allow their customers to purchase a CIR of 0 (zero). This means that the provider does not guarantee any throughput. In practice, customers usually find that their provider allows them to burst over the 0 (zero) CIR virtually all of the time. If a CIR of 0 (zero) is purchased, carefully monitor performance in order to determine whether or not it is acceptable.
Frame Relay allows a customer and provider to agree that under certain circumstances, the customer can burst over the CIR.
Since burst traffic is in excess of the CIR, the provider does not guarantee that it will deliver the frames.
20
Forward Explicit Congestion Notification (FECN) When a Frame Relay switch recognizes congestion in the network, it sends an FECN packet to the destination device.
This indicates that congestion has occurred.
Backward Explicit Congestion Notification (BECN) When a Frame Relay switch recognizes congestion in the network, it sends a BECN packet to the source router.
This instructs the router to reduce the rate at which it is sending packets. With Cisco IOS Release 11.2 or later, Cisco routers can respond to BECN notifications.
21
Discard eligibility (DE) bit When the router or switch detects network congestion, it can mark the packet "Discard Eligible".
The DE bit is set on the traffic that was received after the CIR was met.
These packets are normally delivered. However, in periods of congestion, the Frame Relay switch will drop packets with the DE bit set first.
Presentation_ID
Cisco Confidential
22
Link Management Interface (LMI)

The purpose of LMI is for DTEs to dynamically acquire information about the status of the network.
Status messages help verify the integrity of logical and physical links. LMI messages are exchanged between the DTE and DCE using reserved DLCIs
Cisco The original LMI extensions (Cisco, Nortel and Digital) Ansi Corresponding to the ANSI standard T1.617 Annex D q933a Corresponding to the ITU standard Q933 Annex A
Three types of LMIs are supported by Cisco routers:

1. 2. 3.
The LMI type must be specified at the Frame Relay interface as the three LMI types are incompatible with one another. Cisco routers, of course, default to Cisco.
The LMI type can be dynamically learned Auto LMI
-if)# frame-relay lmi-type [cisco | ansi | q933a]
Presentation_ID
Cisco Confidential
23
Inverse ARP and LMI

LMI status messages combined with Inverse ARP allow a router to associate network layer and data link layer addresses. When a router that is connected to a Frame Relay network is started, it sends an LMI status inquiry message to the network. The network replies with an LMI status message containing details of every VC configured on the access link. If the router needs to map the VCs DLCIs to network layer addresses, it will send an Inverse ARP message on each VC.
Inverse ARP is enabled by default once you configure the encapsulation type on the serial interface as Frame Relay. If a static frame-relay map is configured then Inverse ARP is disabled on that interface. Inverse ARP is also disabled on point-to-point subinterfaces so try using poing-tomultipoint subinterfaces instead. config)# int s0/0.102 point-to-multipoint
Presentation_ID
Cisco Confidential
24
Frame Relay LMI Types
Presentation_ID
Cisco Confidential
25
Stages of Inverse ARP and LMI Operation #1
DLCI 101
Presentation_ID
Cisco Confidential
26
Stages of Inverse ARP and LMI Operation #2
172.16.0.1
DLCI 101
Presentation_ID
Cisco Confidential
27
Frame Relay Topologies
Presentation_ID
Cisco Confidential
28
NBMA Non Broadcast Multiple Access

Frames between two routers are only seen by those two devices (non broadcast). Similar to a LAN, multiple computers have access to the same network and potentially to each other (multiple access).
An NBMA network is the opposite of a broadcast network. On a broadcast network, multiple computers and devices are attached to a shared network cable or other medium. When one computer transmits frames, all nodes on the network "listen" to the frames, but only the node to which the frames are addressed actually receives the frames. Thus, the frames are broadcast. A nonbroadcast multiple access network is a network to which multiple computers and devices are attached, but data is transmitted directly from one computer to another over a virtual circuit or across a switching fabric. The most common examples of nonbroadcast network media include ATM (Asynchronous Transfer Mode), frame relay, and X.25.
29
Star Topology
A star topology, also known as a hub and spoke configuration, is the most popular Frame Relay network topology because it is the most costeffective. In this topology, remote sites are connected to a central site that generally provides a service or application. This is the least expensive topology because it requires the fewest PVCs. In this example, the central router provides a multipoint connection, because it is typically using a single interface to interconnect multiple PVCs.
30
Full Mesh
In a full mesh topology, all routers have PVCs to all other destinations.
This method, although more costly than hub and spoke, provides direct connections from each site to all other sites and allows for redundancy. For example, when one link goes down, a router at site A can reroute traffic through site C.
As the number of nodes in the full mesh topology increases, the topology becomes increasingly more expensive.
The formula to calculate the total number of PVCs with a fully meshed WAN is [n(n - 1)]/2, where n is the number of nodes.
31
Configuring Basic Frame Relay
Presentation_ID
Cisco Confidential
32
A Frame-Relay Configuration Supporting Multiple Sites

This is known as a Hub and Spoke Topology, where the Hub router relays information between the Spoke routers. Limits the number of PVCs needed as in a full-mesh topology.
Hub Router
Spoke Routers
Cisco Confidential
Presentation_ID
33
Mixing Inverse ARP and Frame Relay Map Statements

HubCity# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active Spokane# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 102, dynamic, broadcast, status defined, active
Serial0 (up): ip 172.16.1.3 dlci 102, static, CISCO, status defined, active
Spokomo# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 211, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.1 dlci 211, static, CISCO, status defined, active
34

HubCity# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active Spokane# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 102, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 102, static, CISCO, status defined, active Spokomo# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 211, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.1 dlci 211, static, CISCO, status defined, active
Good News:
Everything looks fine! Now all routers can ping each other! Bad News: Problem when using Frame-Relay map statements AND Inverse ARP. This will only work until the router is reloaded, here is why...
35

HubCity# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active Spokane# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 102, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 102, static, CISCO, status defined, active Spokomo# show frame-relay map Serial0 (up): ip 172.16.1.2 dlci 211, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.1 dlci 211, static, CISCO, status defined, active
Frame-Relay Map Statement Rule:
When a Frame-Relay map statement is configured for a particular protocol (IP, IPX, ) Inverse-ARP will be disabled for that specific protocol, only for the DLCI referenced in the FrameRelay map statement.
Presentation_ID
Cisco Confidential
36

HubCity# show Serial0 (up): Serial0 (up): Spokane# show Serial0 (up): Serial0 (up): Spokomo# show Serial0 (up): Serial0 (up): frame-relay map ip 172.16.1.1 dlci ip 172.16.1.3 dlci frame-relay map ip 172.16.1.2 dlci ip 172.16.1.3 dlci frame-relay map ip 172.16.1.2 dlci ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active 112, dynamic, broadcast, status defined, active 102, dynamic, broadcast, status defined, active 102, static, CISCO, status defined, active 211, dynamic, broadcast, status defined, active 211, static, CISCO, status defined, active
The previous solution worked only because the Inverse ARP had taken place between Spokane and HubCity, and between Spokomo and HubCity, before the Frame-Relay map statements were added. (The Frame-Relay map statement was added after the Inverse ARP took place.) Both the Inverse-ARP and Frame-Relay map statements are in effect. Once the router is reloaded (rebooted) the Inverse-ARP will never occur because of the configured Frame-Relay map statement. (assuming the running-config is copied to the startup-config) Rule: Inverse-ARP will be disabled for that specific protocol, for the DLCI referenced in the Frame-Relay map statement.
37

HubCity# show frame-relay map (after reload) Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active Spokane# show frame-relay map NOW MISSING: Serial0 (up): ip 172.16.1.2 dlci 102, dynamic, broadcast, status defined, active
Serial0 (up): ip 172.16.1.3 dlci 102, static, CISCO, status defined, active
Spokomo# show frame-relay map NOW MISSING: Serial0 (up): ip 172.16.1.2 dlci 211, dynamic, broadcast, status defined, active Serial0 (up): ip 172.16.1.1 dlci 211, static, CISCO, status defined, active
38

HubCity# show frame-relay map (after reload) Serial0 (up): ip 172.16.1.1 dlci 101, dynamic, broadcast, status defined, active
Serial0 (up): ip 172.16.1.3 dlci 112, dynamic, broadcast, status defined, active
Spokane# show frame-relay map Serial0 (up): ip 172.16.1.3 dlci 102, static, CISCO, status defined, active Spokomo# show frame-relay map Serial0 (up): ip 172.16.1.1 dlci 211, static, CISCO, status defined, active
Spokane and Spokomo can no longer ping HubCity because they do not have a dlci-to-IP mapping for the others IP address!
39
HubCity interface Serial0 ip address 172.16.1.2 255.255.255.0 encapsulation frame-relay (Inverse-ARP still works here) Spokane interface Serial0 ip address 172.16.1.1 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.3 102 frame-relay map ip 172.16.1.2 102 Spokomo interface Serial0 ip address 172.16.1.3 255.255.255.0 encapsulation frame-relay frame-relay map ip 172.16.1.1 211 frame-relay map ip 172.16.1.2 211
Frame-Relay Map Statements
Solution: Do not mix IARP with Frame Relay maps statements. If need be use Frame-Relay map statements instead of IARP.
40
Reachability issues with routing updates

Frame Relay is an NBMA Network
An NBMA network is a multiaccess network, which means more than two nodes can connect to the network. Ethernet is another example of a multiaccess architecture.
In an Ethernet LAN, all nodes see all broadcast and multicast frames.
However, in a nonbroadcast network such as Frame Relay, nodes cannot see broadcasts of other nodes unless they are directly connected by a virtual circuit. This means that Branch A cannot directly see the broadcasts from Branch B, because they are connected using a hub and spoke topology.
41

Split Horizon prohibits routing updates received on an interface from exiting that same interface.
The Central router must receive the broadcast from Branch A and then send its own broadcast to Branch B.
In this example, there are problems with routing protocols because of the split horizon rule.
A full mesh topology with virtual circuits between every site would solve this problem, but having additional virtual circuits is more costly and does not scale well.
Presentation_ID
Cisco Confidential
42

Split Horizon prohibits routing updates received on an interface from exiting that same interface. Using a hub and spoke topology, the split horizon rule reduces the chance of a routing loop with distance vector routing protocols. It prevents a routing update received on an interface from being forwarded through the same interface. If the Central router learns about Network X from Branch A, that update is learned via S0/0. According to the split horizon rule, Central could not update Branch B or Branch C about Network X. This is because that update would be sent out the S0/0 interface, which is the same interface that received the update.
43
One Solution: Disable Split Horizon

Router(config-if)#no ip split-horizon Router(config-if)#ip split-horizon
To remedy this situation, turn off split horizon for IP. Of course, with split horizon disabled, the protection it affords against routing loops is lost. Split horizon is only an issue with distance vector routing protocols like RIP, IGRP and EIGRP. It has no effect on link state routing protocols like OSPF and IS-IS.
Presentation_ID
Cisco Confidential
44
Another Solution for split horizon issue: subinterfaces
To enable the forwarding of broadcast routing updates in a Frame Relay network, configure the router with subinterfaces.
Subinterfaces are logical subdivisions of a physical interface.

In split-horizon routing environments, routing updates received on one subinterface can be sent out on another subinterface. With subinterface configuration, each PVC can be configured as a point-to-point connection. This allows each subinterface to act similar to a leased line. This is because each point-to-point subinterface is treated as a separate physical interface.
45
Mulitpoint
Point-to-point A key reason for using subinterfaces is to allow distance vector routing protocols to perform properly in an environment in which split horizon is activated.
There are two types of Frame Relay subinterfaces.

Point-to-point Multipoint
46
Presentation_ID
Cisco Confidential
Mulitpoint
Point-to-point Physical interfaces: With a hub and spoke topology Split Horizon will prevent the hub router from propagating routes learned from one spoke router to another spoke router.
Point-to-point subinterfaces: Each subinterface is on its own subnet. Broadcasts and Split Horizon not a problem because each point-to-point connection is its own subnet. Multipoint subinterfaces: All participating subinterfaces would be in the same subnet. Broadcasts and routing updates are also subject to the Split Horizon Rule and may pose a problem.
47
Configuring Frame Relay subinterfaces

RTA(config)#interface s0/0 RTA(config-if)#encapsulation frame-relay ietf
Router(config-if)#interface serial number subinterface-number {multipoint | point-to-point} Router(config-subif)# frame-relay interface-dlci dlci-number
Subinterface can be configured after the physical interface has been configured for Frame Relay encapsulation
Subinterface numbers can be specified in interface configuration mode or global configuration mode.
Subinterface number can be between 1 and 4294967295. At this point in the subinterface configuration, either configure a static Frame Relay map or use the frame-relay interfacedlci command. The frame-relay interface-dlci command associates the selected subinterface with a DLCI.
2007 Cisco Systems, Inc. All rights reserved. Cisco Confidential
Presentation_ID
48
Configuring Frame Relay subinterfaces
The frame-relay interface-dlci command is required for all point-to-point subinterfaces.
It is also required for multipoint subinterfaces for which inverse ARP is enabled.
It is not required for multipoint subinterfaces that are configured with static route maps.
It can not be used on physical interfaces.

49
Show frame-relay map

Point-to-point subinterfaces are listed as a point-to-point dlci
Router#show frame-relay map Serial0.1 (up): point-to-point dlci, dlci 301 (0xCB, 0x30B0), broadcast status defined, active
With multipoint subinterfaces, they are listed as an inverse ARP entry, dynamic
Router#show frame-relay map Serial0 (up): ip 172.30.2.1 dlci, 301 (0x12D, 0x48D0), dynamic,, broadcast status defined, active
Presentation_ID
Cisco Confidential
50
Point-to-point Subinterfaces
Mulitpoint
Point-to-point subinterfaces are like conventional point-to-point interfaces (PPP, ) and have no concept of (do not need): Inverse-ARP mapping of local DLCI address to remote network address (frame-relay map statements) Frame-Relay service supplies multiple PVCs over a single physical interface and point-to-point subinterfaces subdivide each PVC as if it were a physical point-topoint interface. Point-to-point subinterfaces completely bypass the local DLCI to remote network address mapping issue.
Point-to-point
51
Point-to-point Subinterfaces
Mulitpoint
Point-to-point
With point-to-point subinterfaces you:

Cannot have multiple DLCIs associated with a single point-topoint subinterface Cannot use frame-relay map statements
Cannot use Inverse-ARP

Can use the frame-relay interface dlci statement (for both point-to-point and multipoint)
52
Verifying Frame Relay

The show interfaces command displays information regarding the encapsulation and Layer 1 and Layer 2 status. It also displays information about the following:
1. 2. 3. 4. The LMI type The LMI DLCI The Frame Relay (DTE/DCE) type Clockrate on DCE
Presentation_ID
Cisco Confidential
53
The show frame-relay lmi Command
Presentation_ID
Cisco Confidential
54
The show frame-relay pvc Command
Presentation_ID
Cisco Confidential
55
The show frame-relay map Command
Presentation_ID
Cisco Confidential
56
Troubleshooting Frame Relay

Use the debug frame-relay lmi command to determine whether the router and the Frame Relay switch are sending and receiving LMI packets properly.
Presentation_ID
Cisco Confidential
57
Presentation_ID
Cisco Confidential
58

Frame Relay: © 2007 Cisco Systems, Inc. All Rights Reserved. Cisco Confidential Presentation - ID

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Frame Relay: © 2007 Cisco Systems, Inc. All Rights Reserved. Cisco Confidential Presentation - ID

Uploaded by

Copyright:

Available Formats

Frame Relay

2007 Cisco Systems, Inc. All rights reserved.

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay DTEs and DCEs

2007 Cisco Systems, Inc. All rights reserved.

2007 Cisco Systems, Inc. All rights reserved.

PVCs and DLCIs

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay Functions

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay Operation

2007 Cisco Systems, Inc. All rights reserved.

PVCs and DLCIs

2007 Cisco Systems, Inc. All rights reserved.

Local Significance of DLCIs

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay Switches

2007 Cisco Systems, Inc. All rights reserved.

IETF Frame Relay Frame

2007 Cisco Systems, Inc. All rights reserved.

IETF Frame Relay Frame

2007 Cisco Systems, Inc. All rights reserved.

IETF Frame Relay Frame

2007 Cisco Systems, Inc. All rights reserved.

DLCI 1023: Cisco LMI

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay bandwidth and flow control

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay bandwidth and flow control

Frame Relay bandwidth

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay bandwidth

Frame Relay bandwidth

Frame Relay bandwidth and flow control

Frame Relay bandwidth and flow control

2007 Cisco Systems, Inc. All rights reserved.

Link Management Interface (LMI)

Three types of LMIs are supported by Cisco routers:

-if)# frame-relay lmi-type [cisco | ansi | q933a]

2007 Cisco Systems, Inc. All rights reserved.

Inverse ARP and LMI

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay LMI Types

2007 Cisco Systems, Inc. All rights reserved.

Stages of Inverse ARP and LMI Operation #1

2007 Cisco Systems, Inc. All rights reserved.

Stages of Inverse ARP and LMI Operation #2

2007 Cisco Systems, Inc. All rights reserved.

Frame Relay Topologies

2007 Cisco Systems, Inc. All rights reserved.

NBMA Non Broadcast Multiple Access

Configuring Basic Frame Relay

2007 Cisco Systems, Inc. All rights reserved.

A Frame-Relay Configuration Supporting Multiple Sites

2007 Cisco Systems, Inc. All rights reserved.

Mixing Inverse ARP and Frame Relay Map Statements

Mixing Inverse ARP and Frame Relay Map Statements

Mixing Inverse ARP and Frame Relay Map Statements

Frame-Relay Map Statement Rule:

2007 Cisco Systems, Inc. All rights reserved.

Mixing Inverse ARP and Frame Relay Map Statements

Mixing Inverse ARP and Frame Relay Map Statements