Day 20.3 frame relay

© 2002, Cisco Systems, Inc. All rights reserved. ICND v2.0—8-2© 2002, Cisco Systems, Inc. All rights reserved. 2
Configuring Frame Relay

© 2002, Cisco Systems, Inc. All rights reserved. ICND v2.0—8-3
Objectives
Upon completing this lesson, you will be able to:
• Use Cisco IOS commands to configure a Frame Relay
network, given a functioning router
• Use show commands to identify anomalies in the Frame
Relay PVCs, given a functioning router and an operational
Frame Relay network
• Use debug commands to identify events and anomalies in
the Frame Relay PVCs, given a functioning router and an
operational Frame Relay network

Configuring Basic Frame Relay

Configuring a Static Frame Relay Map

Configuring Subinterfaces
• Point-to-point
– Subinterfaces act like leased lines.
– Each point-to-point subinterface requires its own subnet.
– Point-to-point is applicable to hub and spoke topologies.
• Multipoint
– Subinterfaces act like NBMA networks, so they do not
resolve the split-horizon issues.
– Multipoint can save address space because it uses a
single subnet.
– Multipoint is applicable to partial mesh and full mesh
topologies.

Configuring Point-to-Point Subinterfaces

Multipoint Subinterfaces Configuration
Example

Verifying Frame Relay Operation
Router#clear frame-relay-inarp
• Clears dynamically created Frame Relay maps, created by using Inverse ARP
Router#show interfaces type number
• Displays information about Frame Relay DLCIs and the LMI
Router#show frame-relay lmi [type number]
• Displays LMI statistics
Router#show frame-relay map
• Displays the current Frame Relay map entries
Router#show frame-relay pvc [type number [dlci]]
• Displays PVC statistics
Router#show frame-relay traffic
• Displays Frame Relay traffic statistics

show interfaces Example
• Displays line, protocol, DLCI, and LMI information
Router#show interfaces s0
Serial0 is up, line protocol is up
Hardware is HD64570
Internet address is 10.140.1.2/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)
LMI enq sent 19, LMI stat recvd 20, LMI upd recvd 0, DTE LMI up
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 1023 LMI type is CISCO frame relay DTE
FR SVC disabled, LAPF state down
Broadcast queue 0/64, broadcasts sent/dropped 8/0, interface broadcasts 5
Last input 00:00:02, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
<Output omitted>

• Displays LMI information
ame-relay lmi
for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO
bered info 0 Invalid Prot Disc 0
Call Ref 0 Invalid Msg Type 0
s Message 0 Invalid Lock Shift 0
mation ID 0 Invalid Report IE Len 0
t Request 0 Invalid Keep IE Len 0
q. Sent 113100 Num Status msgs Rcvd 113100
atus Rcvd 0 Num Status Timeouts 0
show frame-relay lmi Example

• Displays PVC traffic statistics
show frame-relay pvc Example
Router#show frame-relay pvc 100
PVC Statistics for interface Serial0 (Frame Relay DTE)
DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0
input pkts 28 output pkts 10 in bytes 8398
out bytes 1198 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 10 out bcast bytes 1198
pvc create time 00:03:46, last time pvc status changed 00:03:47

• Displays the route maps, either static or dynamic
Serial0 (up): ip 10.140.1.1 dlci 100(0x64,0x1840), dynamic,
broadcast,, status defined, active
show frame-relay map Example

• Clears dynamically created Frame Relay maps
clear frame-relay-inarp Example
Serial0 (up): ip 10.140.1.1 dlci 100(0x64,0x1840), dynamic,
broadcast,, status defined, active
Router#clear frame-relay-inarp
Router#show frame map
Router#

Troubleshooting Basic Frame Relay
Operations
• Displays LMI debug information
Router#debug frame-relay lmi
Frame Relay LMI debugging is on
Displaying all Frame Relay LMI data
Router#
1w2d: Serial0(out): StEnq, myseq 140, yourseen 139, DTE up
1w2d: datagramstart = 0xE008EC, datagramsize = 13
1w2d: FR encap = 0xFCF10309
1w2d: 00 75 01 01 01 03 02 8C 8B
1w2d:
1w2d: Serial0(in): Status, myseq 140
1w2d: RT IE 1, length 1, type 1
1w2d: KA IE 3, length 2, yourseq 140, myseq 140
1w2d: Serial0(out): StEnq, myseq 141, yourseen 140, DTE up
1w2d: datagramstart = 0xE008EC, datagramsize = 13
1w2d: FR encap = 0xFCF10309
1w2d: 00 75 01 01 01 03 02 8D 8C
1w2d:
1w2d: Serial0(in): Status, myseq 142
1w2d: RT IE 1, length 1, type 0
1w2d: KA IE 3, length 2, yourseq 142, myseq 142
1w2d: PVC IE 0x7 , length 0x6 , dlci 100, status 0x2 , bw 0

Summary
• A basic Frame Relay configuration assumes one or more
physical interfaces, and LMI and Inverse ARP are running
on the remote routers. In this type of environment, the
LMI notifies the router about the available DLCIs.
• When the remote router does not support Inverse ARP, or
when you want to control routed broadcast traffic, you
must define the address-to-DLCI table statically.
• You can configure Frame Relay subinterfaces in either
point-to-point or multipoint mode.
• After you configure Frame Relay, you can verify that the
connections are active using the available show
commands.
• Use the debug frame-relay lmi command to verify and
troubleshoot a Frame Relay connection.

Visual Objective 8-1: Connecting to
Frame Relay Services
Pod Router s0
A 10.140.1.2
B 10.140.2.2
C 10.140.3.2
D 10.140.4.2
E 10.140.5.2
F 10.140.6.2
G 10.140.7.2
H 10.140.8.2
I 10.140.9.2
J 10.140.10.2
K 10.140.11.2
L 10.140.12.2

Day 20.3 frame relay

More Related Content

What's hot (18)

Similar to Day 20.3 frame relay (20)

More from CYBERINTELLIGENTS (20)

Recently uploaded (20)

Day 20.3 frame relay