1-10 Semester 8 Internetwork Troubleshooting v1.0 - Lab 8.3.4.3 Copyright  2001, Cisco Systems, Inc.
Lab 8.3.4.3: Troubleshooting Frame Relay 3

Frame Relay
Atlas 550
192.168.192.0/24
1/2
2/1
S0/0 S0/0
DLCI 17 DLCI 18
.2
.4
Fa0/0 192.168.200.1/24 Fa0/0 192.168.232.1/24
London Singapore
Objective

Apply the troubleshooting method to a simple Frame Relay network problem.

Scenario

A new Frame Relay connection was installed between London and Singapore
over the weekend. On Monday, both network operators at London and
Singapore call to let you know they are unable reach each other with this new
Frame Relay connection. You check connectivity between the London router
and the Singapore router and find you cannot ping or telnet between the
sites. It is your responsibility to get London and Singapore communicating.

Step 3

Gather the facts about the situation. The commands listed below are useful for
gathering factual information about each router.

• show interface
• show frame-relay lmi
• show frame-relay pvc
• show frame-relay map
• debug frame-relay lmi

Gather information about the London router first. Console into the London
router and issue a show interface serial 0/0 command. The
highlighted information in the sample output below is useful for troubleshooting
and should be the same as the information in your output.

London#show interface serial 0/0
Serial0/0 is up, line protocol is down
Hardware is PowerQUICC Serial
Internet address is 192.168.192.2/24
MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation FRAME-RELAY, loopback not set
Keepalive set (10 sec)
LMI enq sent 69, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 1023 LMI type is CISCO frame relay DTE
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0


London#show frame-relay lmi

LMI Statistics for interface Serial0/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 188 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 187Checking the status of the LMI is always a good place to start with Frame
Relay.

3. Examine the output. Do you notice anything unusual? Issue a show frame-relay pvc command on the London router. The
highlighted information in the sample output below is useful for troubleshooting
and should be the same as the information in your output. (Remember to ignore
information about other DLCIs.)London#show frame-relay pvc


must be active.
Listed below is a summary of pertinent factual information gathered about the
London router.

• The WAN interface serial 0/0 interface and line protocol are up; the
encapsulation is Frame-Relay; the LMI is up; and the LMI type is ANSI.
• LMIs are being sent and received so the router and Frame Relay switch are
exchanging LMIs.
• The PVC for DLCI 17 is active, indicating the PVC between the router and
switch is configured correctly.
• The Frame Relay map is configured correctly.

Issue a debug frame-relay lmi command on the London router. Since
LMIs were not being received, debugging the LMI process gives you a closer
look and will verify LMIs are not being received. Note: Your sequence numbers
may differ.

London#debug frame-relay lmi
Frame Relay LMI debugging is on
Displaying all Frame Relay LMI data
London#
00:18:57: Serial0/0(out): StEnq, myseq 96, yourseen 0, DTE down
00:18:57: datagramstart = 0x1A01ED4, datagramsize = 13
00:18:57: FR encap = 0xFCF10309
00:18:57: 00 75 01 01 00 03 02 60 00
00:18:57:
00:19:07: Serial0/0(out): StEnq, myseq 97, yourseen 0, DTE down
00:19:07: datagramstart = 0x1A01ED4, datagramsize = 13
00:19:07: FR encap = 0xFCF10309
00:19:07: 00 75 01 01 00 03 02 61 00

LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0
LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 29
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:38:03
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/32 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
228 packets input, 3572 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
228 packets output, 3192 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up5. Compare this output with the output from the London router. What are the
differences? So far the Singapore router seems to be successfully sending and receiving