Monitoring Frame Relay

After the Frame Relay configuration is complete, you can use the show interface and debug frame-relay commands to monitor and troubleshoot the configuration. The following output shows the results of the show interface command:

 
 Router# show interface serial 0   Serial0 is up, line protocol is up   Hardware is MCI Serial   Internet address is 172.59.1.1,     subnet mask is 255.255.255.252   MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 249/255,     load 1/255   Encapsulation FRAME-RELAY, loopback not set,    keepalive set (10 sec)   LMI enq sent  4, LMI stat recvd 0, LMI upd recvd 0,     DTE LMI UP   LMI enq recvd 268, LMI stat sent  264, LMI upd sent  0   LMI DLCI 1023  LMI type is CISCO  frame relay DTE   Last input 0:00:09, output 0:00:07, output hang never   Last clearing of "show interface" counters 0:44:57   Output queue 0/40, 0 drops; input queue 0/75, 0 drops   Five minute input rate 0 bits/sec, 0 packets/sec Five minute output rate 0 bits/sec, 0 packets/sec      309 packets input, 6641 bytes, 0 no buffer      Received 0 broadcasts, 0 runts, 0 giants      0 input errors, 0 CRC, 0 frame, 0 overrun,      0 ignored, 0 abort      0 input packets with dribble condition detected      268 packets output, 3836 bytes, 0 underruns      0 output errors, 0 collisions, 2 interface resets,      0 restarts      180 carrier transitions 

Use the show frame-relay pvc command to display the status of the virtual circuit, as shown in the following:

 
 RouterA#show frame-relay pvc PVC Statistics for interface Serial0 (Frame Relay DTE) DLCI = 222, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE,INTERFACE = Serial0   input pkts 50            output pkts 20         in bytes 11431   out bytes 1474           dropped pkts 2         in FECN pkts 0   in BECN pkts 0           out FECN pkts 0        out BECN pkts 0   in DE pkts 0             out DE pkts 0   pvc create time 04:14:10, last time pvc status changed 00:39:06 RouterA# 

Use the show frame-relay lmi command to determine whether LMI is being transmitted successfully:

 
 RouterA#show frame-relay lmi LMI Statistics for interface Serial0 (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 292              Num Status msgs Rcvd 292   Num Update Status Rcvd 0              Num Status Timeouts 0 RouterA# 

Use the show frame-relay map command to display mappings among protocol, protocol address, and DLCI, as shown in the following:

 
 RouterA#show frame-relay map Serial0 (up): ip 172.59.1.1 dlci 222(0xDE,0x34E0), dynamic,               broadcast, status defined, active RouterA# 

The debug frame-relay command enables you to monitor the Frame Relay activity closely. The debug frame-relay lmi command enables you to monitor LMI activity on a router closely. The following output shows sample output from the debug frame-relay lmi command.

 
 RouterA#debug frame-relay lmi Frame Relay LMI debugging is on RouterA# Serial0(out): StEnq, myseq 20, yourseen 67, DTE up  datagramstart = 0x23A3820, datagramsize = 13  FR encap = 0xFCF10309 00 75 01 01 01 03 02 14 43 Serial0(in): Status, myseq 20 RT IE 1, length 1, type 1 KA IE 3, length 2, yourseq 68, myseq 20 RouterA# Serial0(out): StEnq, myseq 21, yourseen 68, DTE up  datagramstart = 0x23A3820, datagramsize = 13 
graphics/note_icon.gif

The sequence counters for the LMI transmission are being increased properly. Enabling a single debug command on a router does not use much of the router's system resources; however, enabling several debug commands may severely affect the router's ability to perform its functions. The no debug all command quickly disables all debug commands on a router.




CCNA Exam Cram[tm] 2 (Exams 640-821, 640-811, 640-801)
CCNA Exam Cram[tm] 2 (Exams 640-821, 640-811, 640-801)
ISBN: 789730197
EAN: N/A
Year: 2005
Pages: 155

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net