Vous êtes sur la page 1sur 41

Module 3

Frame-Relay

Objectives
Describe the fundamental concepts of Frame Relay technology in
terms of enterprise WAN services, including operation, bandwidth, and
flow control, implementation requirements, maps, and LMI operation.
Configure a basic Frame Relay permanent virtual circuit (PVC),
including configuringand trouble shooting Frame Relay on a router
serial interface and configuring a static Frame Relay map.
Describe advanced concepts of Frame Relay technology in terms of
enterprise WAN services, including subinterfaces
Configure an advanced Frame Relay PVC, including solving
reachability issues, configuring subinterfaces, and verifying and
troubleshooting a Frame Relay configuration.

Basic Frame-Relay Concepts

Introducing Frame Relay


Corporate Bandwidth Requirements

Introducing Frame Relay


Dedicated Line WAN Requirements

Introducing Frame Relay


Frame-Relay WAN Requirements

Compare the cost between Dedicated (Leased-Line) and Frame-Relay?


6

Introducing Frame Relay

Introducing Frame Relay

Frame Relay is a packet-switched, connection-oriented, WAN service.


It 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).
Frames carry data between user devices called data terminal equipment (DTE),
and the data communications equipment (DCE) at the edge of the WAN.
It does not define the way the data is transmitted within the service providers
Frame Relay cloud.
This is ATM in many cases!
8

Frame-Relay Equipment

DTEs generally are considered to be terminating equipment for a specific


network and typically are located on the premises of the customer.
The customer may also own this equipment.
Examples of DTE devices are routers and Frame Relay Access Devices (FRADs)
A FRAD is a specialized device designed to provide a connection between a LAN
and a Frame Relay WAN.
DCEs are carrier-owned internetworking devices (Frame-Relay Switches)
The purpose of DCE equipment is to provide clocking and switching services in a
network.
9

Virtual Circuits
An SVC between the same two
DTEs may change.

Path may change.

A PVC between the same two DTEs


will always be the same.

Always same Path.

The connection through the Frame Relay network between two DTEs is called a
virtual circuit (VC).
With VC shared the bandwidth among multiple users, any single site can
communicate with many sites without using multiple dedicated physical links
Switched Virtual Circuits (SVCs) are Virtual circuits may be established
dynamically by sending signaling messages to the network.
However, SVCs are not very common.
Permanent Virtual Circuits (PVCs) are more common.
PVC are VCs that have been preconfigured by the carrier are used.
The switching information for a VC is stored in the memory of the switch.

10

Virtual Circuits

VCs are identified by DLCIs (10-bit length).


DLCI values typically are assigned by the Frame Relay service provider
The DLCI is stored in the address field of every frame transmitted.
DLCIs 0 to 15 and 1008 to 1023 are reserved for special purposes. Therefore,
service providers typically assign DLCIs in the range of 16 to 1007

11

Multiple Virtual Circuits


Multiple VCs on a single access line

Frame Relay is statistically multiplexed (it transmits only one frame at a time),
but many logical connections can co-exist on a single physical line.
The Frame Relay Access Device (FRAD) or router connected to the Frame
Relay network may have multiple VCs connecting it to various endpoints.
Multiple VCs on a single physical line are distinguished because each VC
has its own DLCI.
Remember that the DLCI has only local significance and may be different at
each end of a VC.

12

Frame Relay Encapsulation

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.

13

Paying for Frame Relay

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)
The CIR is the amount of data that the network receives from the access
circuit.
The service provider guarantees that the customer can send data at the CIR.
All frames received at or below the CIR are accepted

14

Paying for Frame Relay

In the example, the customer is paying for the following:


An access line with a rate of 64 kb/s connecting their DCE to the DCE of
the service provider through serial port S0/0/0.
Two virtual ports, one at 32 kb/s and the other at 16 kb/s.
A CIR of 48 kb/s across the entire Frame Relay network. This is usually a
flat charge and not connected to the distance.

15

Paying for Frame Relay

Bursting: A great advantage of Frame Relay is that any network capacity that is
being unused is made available or shared with all customers, usually at no extra
charge.
The CBIR is a negotiated rate above the CIR which the customer can use to
transmit for short burst. It allows traffic to burst to higher speeds, as available
network bandwidth permits. However, it cannot exceed the port speed of the link
The BE is the term used to describe the bandwidth available above the CBIR up to
the access rate of the link. Unlike the CBIR, it is not negotiated. Frames may be
transmitted at this level but will most likely be dropped

16

Frame Relay Flow Control

Frame Relay reduces network overhead by implementing simple


congestion-notification mechanisms rather than explicit, per-VC flow control.
These congestion-notification mechanisms are the Forward Explicit
Congestion Notification (FECN) and the Backward Explicit Congestion
Notification (BECN).
FECN and BECN are each controlled by a single bit contained in the frame
header. They let the router know that there is congestion and that the router
should stop transmission until the condition is reversed

17

Frame Relay Flow Control

Discard Eligibility (DE): identifies less important traffic that can be dropped during periods of
congestion. When the network becomes congested, Frame-Relay switch discard the frames
with the DE bit set to 1.
The following logic rules are applied to each incoming frame based on whether the CIR is
exceeded:
If the incoming frame does not exceed the CIBR, the frame is passed.
If an incoming frame exceeds the CIBR, it is marked DE.
If an incoming frame exceeds the CIBR plus the BE, it is discarded.

18

LMI Local Management Interface

LMI is a signaling standard between the DTE and the Frame Relay switch.
LMI is responsible for managing the connection and maintaining the status
between devices.

19

LMI
LMI

There are three types of LMI, none of which is compatible with the others.
Cisco, StrataCom, Northern Telecom, and Digital Equipment Corporation
(Gang of Four) released one type of LMI, while the ANSI and the ITU-T each
released their own versions.
The LMI type must match between the provider Frame Relay switch and the
customer DTE device.

In Cisco IOS releases prior to 11.2, the Frame Relay interface must be
manually configured to use the correct LMI type, which is furnished by the
service provider.

If using Cisco IOS Release 11.2 or later, the router attempts to automatically
detect the type of LMI used by the provider switch.

This automatic detection process is called LMI autosensing.

20

LMI

The Frame Relay switch uses LMI to report the status of configured PVCs.
The three possible PVC states are as follows:
Active state Indicates that the connection is active and that routers can
exchange data.
Inactive state Indicates that the local connection to the Frame Relay
switch is working, but the remote router connection to the Frame Relay
switch is not working.
Deleted state Indicates that no LMI is being received from the Frame
Relay switch, or that there is no service between the CPE router and
Frame Relay switch.

21

Frame Relay Topologies

Frame-Relay Star
Star (Hub and Spoke)

22

Frame Relay Topologies

Frame-Relay Mesh

Full Mesh

23

Frame-Relay Address Mapping

Before a Cisco router is able to transmit data over Frame Relay, it needs to
know which local DLCI maps to the Layer 3 address of the remote
destination
This address-to-DLCI mapping can be accomplished either by static or
dynamic mapping
24

Frame-Relay Address Mapping

Manual
Administrators use a frame-relay map command.
Dynamic
Inverse Address Resolution Protocol (I-ARP) provides a given DLCI and
requests next-hop protocol addresses for a specific connection.
On Cisco routers, Inverse ARP is enabled by default for all protocols
enabled on the physical interface

25

Configuring Frame-Relay

Configuring Basic Frame-Relay

27

Configuring Basic Frame-Relay

R1(config)#interface serial slot/port_number


R1(config-if)#ip address address subnet_mask
R1(config-if)#encapsulation frame-relay [ietf | cisco]
R1(config-if)#frame-relay interface-dlci dlci-number -> option
R1(config-if)#bandwidth number

28

Optional Frame Relay commands


There are three instances when you must define the address-to-DCLI table
statically:
When Inverse ARP is not supported by the remote router
When configuring OSPF over Frame Relay
When you want to control broadcast traffic while using routing
Router(config-if)#frame-relay map protocol remote-address
dlci_number [broadcast] [ietf | cisco]

29

Configuring Static Frame Relay Maps

Configuration for R1

30

Advanced Frame Relay Concepts

Split horizon and reachability problem


VC1

VC2

VC3

Split horizon reduces routing loops by not allowing a routing update received on
one physical interface to be sent back out that same interface
As a result, if a remote router sends an update to the headquarters router that is
connecting multiple PVCs over a single physical interface, the headquarters
router cannot advertise that route through the same physical interface to other
remote routers
32

Solving reachability issues with


subinterface

33

Configuring Frame Relay subinterfaces

Router(config)#interface serial slot/port_number


Router(config-if)#encapsulation frame-relay [ietf | cisco]
Router(config-if)#interface serial slot/port_number.subinterface-number
{multipoint | point-to-point}
Router(config-subif)# frame-relay interface-dlci dlci-number
34

Verifying Frame-Relay operation


PVC Status

35

Verifying Frame-Relay operation


LMI Statistic

36

Verifying Frame-Relay operation


Verify Inverse ARP

37

Sample: Subinterface point-to-point


configuration
10.0.0.0/8
S0/0.2: 10.0.0.1

10.0.0.2

S0/0.1: 9.0.0.1

9.0.0.2

R(config)#interface serial 0/0


R(config-if)#encapsulation frame-relay
R(config-if)#exit
R(config)#interface serial 0/0.1 point-to-point
R(config-subif)#frame-relay interface-dlci 41
R(config-subif)#ip address 9.0.0.1 255.0.0.0
R(config)#interface serial 0/0.2 point-to-point
R(config-subif)#frame-relay interface-dlci 43 ietf
R(config-subif)#ip address 10.0.0.1 255.0.0.0

38

Sample: Subinterface multipoint


configuration
9.0.0.3

S0/0.1: 9.0.0.1

9.0.0.2

R(config)#interface serial 0/0


R(config-if)#encapsulation frame-relay
R(config-if)#exit
R(config)#interface serial 0/0.1 multipoint
R(config-subif)#ip address 9.0.0.1 255.0.0.0
R(config-subif)#frame-relay interface-dlci 41
R(config-subif)#frame-relay interface-dlci 43 ietf
39

Sample: Subinterface point-to-point


configuration with static map
9.0.0.3

S0/0.1: 9.0.0.1

9.0.0.2

R(config)#interface serial 0/0


R(config-if)#encapsulation frame-relay
R(config-if)#exit
R(config)#interface serial 0/0.1 multipoint
R(config-subif)#ip address 9.0.0.1 255.0.0.0
R(config-subif)#frame-relay interface-dlci 41
R(config-subif)#frame-relay interface-dlci 43 ietf
R(config-subif)#frame-relay map ip 9.0.0.2 41
R(config-subif)#frame-relay map ip 9.0.0.3 43
40

Good luck with this module!

Vous aimerez peut-être aussi