Some Useful Tips and Commands to Help Identify Problems During the CCIE Lab
| When taking your CCIE Lab Exam, time matters. Consider the following steps and advice during your lab exam:
These approaches will help you keep your work under strict control. The sections that follow list and demonstrate some useful commands to help troubleshoot some of the areas covered in Practice Labs 16. Frame RelayTroubleshooting commands for Frame Relay configuration include the following:
Example C-1 provides commented output from these key commands. Example C-1. Some Frame Relay Troubleshooting CommandsR2#show frame-relay map ! It is important here to notice if the right remote IP address is mapped ! to the right DLCI. Serial0/0 (up): ip 160.10.32.1 dlci 203(0xCB,0x30B0), static, broadcast, CISCO, status defined, active Serial0/1.1 (up): ip 160.10.37.1 dlci 211(0xD3,0x3430), static, broadcast, CISCO, status defined, active Serial0/1.1 (up): ip 160.10.37.5 dlci 215(0xD7,0x3470), static, broadcast, CISCO, status defined, active Serial0/1.2 (up): point-to-point dlci, dlci 214(0xD6,0x3460), broadcast status defined, active R2# R2# R2#show frame-relay lmi ! Look for the LMI TYPE to make sure it is in accordance with the ! Frame Relay switch LMI Statistics for interface Serial0/0 (Frame Relay DTE) LMI TYPE = ANSI 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 252696 Num Status msgs Rcvd 252697 Num Update Status Rcvd 0 Num Status Timeouts 0 LMI Statistics for interface Serial0/1 (Frame Relay DTE) LMI TYPE = ANSI 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 250259 Num Status msgs Rcvd 250259 Num Update Status Rcvd 0 Num Status Timeouts 0 R2# R2# R2#show frame-relay pvc !Look for the interfaces you need to be up and verify their DLCI and PVC STATUS. ! Also look the input packets and output packets to verify if packets ! are being exchanged. PVC Statistics for interface Serial0/0 (Frame Relay DTE) Active Inactive Deleted Static Local 1 4 0 0 Switched 0 0 0 0 Unused 0 0 0 0 DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0/0 input pkts 23 output pkts 17 in bytes 7636 out bytes 5644 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 17 out bcast bytes 5644 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 4w1d, last time pvc status changed 4w1d DLCI = 203, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0 input pkts 505707 output pkts 509709 in bytes 30978546 out bytes 34593695 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 265708 out bcast bytes 22984244 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 4w1d, last time pvc status changed 4w0d PVC Statistics for interface Serial0/1 (Frame Relay DTE) Active Inactive Deleted Static Local 3 0 0 0 Switched 0 0 0 0 Unused 0 2 0 0 DLCI = 211, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/1.1 input pkts 259401 output pkts 185410 in bytes 16210516 out bytes 12698272 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 83421 out bcast bytes 7341032 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 4w1d, last time pvc status changed 4w0d DLCI = 214, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/1.2 input pkts 257970 output pkts 304963 in bytes 19103988 out bytes 36371224 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 304928 out bcast bytes 36367584 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 4w1d, last time pvc status changed 4w0d DLCI = 215, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/1.1 input pkts 251325 output pkts 179623 in bytes 17224383 out bytes 13859561 dropped pkts 0 in pkts dropped 0 out pkts dropped 0 out bytes dropped 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 83416 out bcast bytes 7340596 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 4w1d, last time pvc status changed 4w0d R2#show interfaces serial 0/0 !Look the Interface encapsulation, if the packets are being sent and received. ! If the LMI TYPE, if the LMI is up and exchanging messages Serial0/0 is up, line protocol is up Hardware is GT96K Serial Internet address is 160.10.32.2/30 MTU 1500 bytes, BW 1544 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 252702, LMI stat recvd 252703, LMI upd recvd 0, DTE LMI up LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0 LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE FR SVC disabled, LAPF state down Broadcast queue 0/64, broadcasts sent/dropped 265783/0, interface broadcasts 265771 Last input 00:00:01, output 00:00:08, output hang never Last clearing of "show interface" counters 4w1d Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 758622 packets input, 35638551 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 762500 packets output, 38155977 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 output buffer failures, 0 output buffers swapped out 2 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up R2#show interfaces serial 0/1 Serial0/1 is up, line protocol is up Hardware is GT96K Serial MTU 1500 bytes, BW 1544 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 250266, LMI stat recvd 250266, LMI upd recvd 0, DTE LMI up LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0 LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE FR SVC disabled, LAPF state down Broadcast queue 0/64, broadcasts sent/dropped 471772/0, interface broadcasts 346645 Last input 00:00:01, output 00:00:01, output hang never Last clearing of "show interface" counters 4w1d Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/2/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 1018973 packets input, 57086147 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 920273 packets output, 66433800 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=up R2# R2#debug frame-relay lmi Frame Relay LMI debugging is on Displaying all Frame Relay LMI data ! If you are experiencing problems to have your Frame relay Link to come up ! look on the debug output if LMI messages are being sent and received on the ! router interface. Observe the "message sequence" on Interfaces S0/0 and S0/1. *Mar 30 06:53:48.841: Serial0/0(out): StEnq, myseq 43, yourseen 42, DTE up *Mar 30 06:53:48.841: datagramstart = 0x6001C54, datagramsize = 14 *Mar 30 06:53:48.841: FR encap = 0x00010308 *Mar 30 06:53:48.841: 00 75 95 01 01 00 03 02 2B 2A *Mar 30 06:53:48.841: *Mar 30 06:53:48.841: Serial0/0(in): Status, myseq 43 *Mar 30 06:53:48.841: RT IE 1, length 1, type 0 *Mar 30 06:53:48.841: KA IE 3, length 2, yourseq 43, myseq 43 *Mar 30 06:53:48.841: PVC IE 0x7 , length 0x3 , dlci 201, status 0x0 *Mar 30 06:53:48.841: PVC IE 0x7 , length 0x3 , dlci 203, status 0x2 *Mar 30 06:53:48.841: PVC IE 0x7 , length 0x3 , dlci 204, status 0x0 *Mar 30 06:53:48.841: PVC IE 0x7 , length 0x3 , dlci 205, status 0x0 *Mar 30 06:53:48.841: PVC IE 0x7 , length 0x3 , dlci 206, status 0x0 *Mar 30 06:53:52.229: Serial0/1(out): StEnq, myseq 187, yourseen 186, DTE up *Mar 30 06:53:52.229: datagramstart = 0x63F5234, datagramsize = 14 *Mar 30 06:53:52.229: FR encap = 0x00010308 *Mar 30 06:53:52.229: 00 75 95 01 01 01 03 02 BB BA *Mar 30 06:53:52.229: *Mar 30 06:53:52.229: Serial0/1(in): Status, myseq 187 *Mar 30 06:53:52.229: RT IE 1, length 1, type 1 *Mar 30 06:53:52.229: KA IE 3, length 2, yourseq 187, myseq 187 *Mar 30 06:53:58.841: Serial0/0(out): StEnq, myseq 44, yourseen 43, DTE up *Mar 30 06:53:58.841: datagramstart = 0x6001394, datagramsize = 14 *Mar 30 06:53:58.841: FR encap = 0x00010308 *Mar 30 06:53:58.841: 00 75 95 01 01 01 03 02 2C 2B *Mar 30 06:53:58.841: *Mar 30 06:53:58.841: Serial0/0(in): Status, myseq 44 *Mar 30 06:53:58.841: RT IE 1, length 1, type 1 *Mar 30 06:53:58.841: KA IE 3, length 2, yourseq 44, myseq 44 *Mar 30 06:54:02.229: Serial0/1(out): StEnq, myseq 188, yourseen 187, DTE up *Mar 30 06:54:02.229: datagramstart = 0x6000AD4, datagramsize = 14 *Mar 30 06:54:02.229: FR encap = 0x00010308 *Mar 30 06:54:02.229: 00 75 95 01 01 00 03 02 BC BB *Mar 30 06:54:02.229: *Mar 30 06:54:02.229: Serial0/1(in): Status, myseq 188 *Mar 30 06:54:02.229: RT IE 1, length 1, type 0 *Mar 30 06:54:02.229: KA IE 3, length 2, yourseq 188, myseq 188 *Mar 30 06:54:02.229: PVC IE 0x7 , length 0x3 , dlci 211, status 0x2 *Mar 30 06:54:02.229: PVC IE 0x7 , length 0x3 , dlci 213, status 0x0 *Mar 30 06:54:02.229: PVC IE 0x7 , length 0x3 , dlci 214, status 0x2 *Mar 30 06:54:02.229: PVC IE 0x7 , length 0x3 , dlci 215, status 0x2 *Mar 30 06:54:02.229: PVC IE 0x7 , length 0x3 , dlci 216, status 0x0 R2# R2#debug frame-relay packet Frame Relay packet debugging is on ! Observe the "packet type" and the "packet size" as well the DCLI number to ! verify if traffic is being exchanged. You will notice that IP packets and ! CDP packets are being exchanged. *Mar 30 06:58:57.377: Serial0/0(i): dlci 203(0x30B1), pkt type 0x800, datagramsize 72 *Mar 30 06:58:57.881: Serial0/0: broadcast search *Mar 30 06:58:57.881: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:58:57.949: broadcast dequeue *Mar 30 06:58:57.949: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:58:58.781: Serial0/1.2: broadcast search *Mar 30 06:58:58.781: Serial0/1.2(o): dlci 214(0x3461), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:58:58.849: broadcast dequeue *Mar 30 06:58:58.849: Serial0/1.2(o):Pkt sent on dlci 214(0x3461), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:58:59.457: Serial0/1(i): dlci 214(0x3461), pkt type 0x800, datagramsize 72 *Mar 30 06:59:01.817: Serial0/1(i): dlci 215(0x3471), pkt type 0x800, datagramsize 72 *Mar 30 06:59:01.817: Serial0/1(i): dlci 215(0x3471), pkt type 0x800, datagramsize 72 *Mar 30 06:59:07.389: Serial0/0(i): dlci 203(0x30B1), pkt type 0x800, datagramsize 72 *Mar 30 06:59:07.881: Serial0/0: broadcast search *Mar 30 06:59:07.881: Serial0/0(o): dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:59:07.949: broadcast dequeue *Mar 30 06:59:07.949: Serial0/0(o):Pkt sent on dlci 203(0x30B1), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:59:08.781: Serial0/1.2: broadcast search *Mar 30 06:59:08.781: Serial0/1.2(o): dlci 214(0x3461), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:59:08.845: Serial0/1.2: Broadcast on DLCI 214 link 65(CDP) *Mar 30 06:59:08.845: Serial0/1.2(o): dlci 214(0x3461), pkt type 0x2000(CDP), datagramsize 328 *Mar 30 06:59:08.849: broadcast dequeue *Mar 30 06:59:08.849: Serial0/1.2(o):Pkt sent on dlci 214(0x3461), pkt type 0x800(IP), datagramsize 84 *Mar 30 06:59:08.849: broadcast dequeue *Mar 30 06:59:08.849: Serial0/1.2(o):Pkt sent on dlci 214(0x3461), pkt type 0x2000(CDP), datagramsize 328 3550 SwitchesTroubleshooting commands for 3550 switch configuration include the following:
Example C-2 provides commented output from these key commands. Example C-2. Some Catalyst 3550 Troubleshooting CommandsSw1# Sw1#show interfaces ? ! Here we explore the possibilities of the "show" command on the Catalyst 3550. Async Async interface BVI Bridge-Group Virtual Interface Dialer Dialer interface FastEthernet FastEthernet IEEE 802.3 GigabitEthernet GigabitEthernet IEEE 802.3z Loopback Loopback interface Multilink Multilink-group interface Null Null interface Port-channel Ethernet Channel of interfaces Tunnel Tunnel interface Virtual-Template Virtual Template interface Virtual-TokenRing Virtual TokenRing Vlan Catalyst Vlans accounting Show interface accounting capabilities Show interface capabilities information counters Show interface counters crb Show interface routing/bridging info debounce Show interface debounce time info description Show interface description etherchannel Show interface etherchannel information fair-queue Show interface Weighted Fair Queueing (WFQ) info fcpa Fiber Channel flowcontrol Show interface flowcontrol information irb Show interface routing/bridging info mac-accounting Show interface MAC accounting info media Show interface media info precedence Show interface precedence accounting info private-vlan Show interface private vlan information pruning Show interface trunk VTP pruning information random-detect Show interface Weighted Random Early Detection (WRED) info rate-limit Show interface rate-limit info stats Show interface packets & octets, in & out, by switching path status Show interface line status switchport Show interface switchport information trunk Show interface trunk information | Output modifiers <cr> Sw1#show interfaces fastEthernet 0/15 ! The "show interfaces" command has similar output as you see on the routers. ! Look for the interface status (is it is up and connected) and if packets ! are being sent and received on the interface. FastEthernet0/15 is up, line protocol is up (connected) Hardware is Fast Ethernet, address is 0009.e8ef.180f (bia 0009.e8ef.180f) MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s input flow-control is off, output flow-control is off ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 5000 bits/sec, 3 packets/sec 5 minute output rate 15000 bits/sec, 4 packets/sec 7927602 packets input, 1463727947 bytes, 0 no buffer Received 7673767 broadcasts (0 multicast) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 7672375 multicast, 0 pause input 0 input packets with dribble condition detected 11153955 packets output, 742431432 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out Sw1# Sw1#show interfaces trunk ! Here you can verify the trunk encapsulation and if the VLANs are allowed on ! the trunk. Notice that interfaces Fa0/15 and Fa0/17 are trunk between Sw1 and ! Sw2 but not using "FastEtherChannel". Also notice that all VLANs are allowed ! to pass through the trunk. Port Mode Encapsulation Status Native vlan Fa0/15 on 802.1q trunking 1 Fa0/17 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/15 1-4094 Fa0/17 1-4094 Port Vlans allowed and active in management domain Fa0/15 1,11,22,25,33,100,200 Fa0/17 1,11,22,25,33,100,200 Port Vlans in spanning tree forwarding state and not pruned Fa0/15 1,11,22,25,33,100 Fa0/17 1,11,200 Sw1# Sw1# Sw1#show vlan brief ! Very useful command that shows us if the VLANs are created as requested ! (or how you would like to) and if the right ports or interfaces are assigned ! to the correct VLAN. VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Fa0/7, Fa0/8, Fa0/9, Fa0/10 Fa0/11, Fa0/12, Fa0/14, Fa0/16 Fa0/18, Fa0/19, Fa0/20, Fa0/21 Fa0/22, Fa0/23, Fa0/24, Gi0/1 Gi0/2 11 VLAN_11 active Fa0/1 22 VLAN_22 active Fa0/3, Fa0/5, Fa0/6 25 VLAN_25 active 33 VLAN_33 active 100 VLAN_100 active Fa0/2, Fa0/13 200 VLAN_200 active Fa0/4 1002 fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup 1005 trnet-default act/unsup Sw1# Sw1# Sw1#show vtp status ! The "show vtp status' command will help you to identify why for example the ! VLANs are not showing on the VLAN table. Look the VTP Mode, VTP Domain Name and ! it is important to notice VTP Domain Name is case sensitive. VTP Version : 2 Configuration Revision : 6 Maximum VLANs supported locally : 1005 Number of existing VLANs : 11 VTP Operating Mode : Server VTP Domain Name : CISCO VTP Pruning Mode : Disabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0xAE 0x02 0xC5 0x62 0xBA 0xC3 0xE7 0x3C Configuration last modified by 160.10.11.10 at 3-1-93 02:47:28 Local updater ID is 160.10.11.10 on interface Vl11 (lowest numbered VLAN interface found) ATMTroubleshooting commands for ATM configuration include the following:
Example C-3 provides commented output from these key commands. Example C-3. Some ATM Troubleshooting CommandsR6# R6#show interfaces atm 3/0 ! Look to see if the interface is up and line protocol is up. Verify the ! encapsulation and if the interface is sending and receiving packets. ATM3/0 is up, line protocol is up Hardware is RS8234 ATMOC3 Internet address is 170.100.10.1/24 MTU 4470 bytes, sub MTU 4470, BW 155000 Kbit, DLY 80 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM, loopback not set Encapsulation(s): AAL5 1023 maximum active VCs, 1 current VCCs VC idle disconnect time: 300 seconds Last input 00:00:42, output 00:00:42, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: Per VC Queueing 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 9425 packets input, 583958 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 8905 packets output, 556790 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 output buffer failures, 0 output buffers swapped out R6#show atm pvc ! Here you can verify the PVC status and encapsulation. VCD / Peak Avg/Min Burst Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts 3/0 1 0 100 PVC SNAP UBR 155000 UP R6# R6#show atm map ! From this output observe the remote IP address mapping and make sure no ! mistakes were made, like typos. Map list ATM3/0pvc1 : PERMANENT ip 170.100.10.254 maps to VC 1, VPI 0, VCI 100, ATM3/0 , broadcast R6# R6#show atm traffic ! It is important to observe here if the "Input packets" and "Output packets" ! queues are increasing, so you know that traffic is being sent and received. 9431 Input packets 8911 Output packets 0 Broadcast packets 0 Packets received on non-existent VC 0 Packets attempted to send on non-existent VC 0 OAM cells received F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 0 OAM cells sent F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 0 OAM cell drops R6# OSPFTroubleshooting commands for OSPF configuration include the following:
Example C-4 provides commented output from these key commands. Example C-4. Some OSPF Troubleshooting CommandsR2#show ip ospf ! This command shows key information that will help in troubleshooting. ! Look at the "router process" and "router ID", the OSPF areas ! (that is, Area 0, NSSA, stub, etc) and number of interfaces on each area, ! which others IGP routing protocols are being redistributed into OSPF, ! if the OSPF has authentication and area ranges (summarization) is being injected. ! It is important to notice that the OSPF area 0 may expand its interfaces ! if for example you have OSPF Virtual Link configured. Routing Process "ospf 1" with ID 160.10.2.2 Supports only single TOS(TOS0) routes Supports opaque LSA Supports Link-local Signaling (LLS) It is an area border and autonomous system boundary router Redistributing External Routes from, eigrp 400 with metric mapped to 100, includes subnets in redistribution Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs 10000 msecs Maximum wait time between two consecutive SPFs 10000 msecs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs LSA group pacing timer 240 secs Interface flood pacing timer 33 msecs Retransmission pacing timer 66 msecs Number of external LSA 12. Checksum Sum 0x058931 Number of opaque AS LSA 0. Checksum Sum 0x000000 Number of DCbitless external and opaque AS LSA 0 Number of DoNotAge external and opaque AS LSA 0 Number of areas in this router is 2. 2 normal 0 stub 0 nssa External flood list length 0 Area BACKBONE(0) Number of interfaces in this area is 3 Area has no authentication SPF algorithm last executed 02:32:07.344 ago SPF algorithm executed 31 times Area ranges are Number of LSA 11. Checksum Sum 0x05BF7D Number of opaque link LSA 0. Checksum Sum 0x000000 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0 Area 1 Number of interfaces in this area is 1 Area has no authentication SPF algorithm last executed 02:31:47.344 ago SPF algorithm executed 17 times Area ranges are Number of LSA 15. Checksum Sum 0x08A42F Number of opaque link LSA 0. Checksum Sum 0x000000 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0 R2# R2#show ip ospf interface ! Important to observe here is if the interface is configured into the right area. ! Look the process ID and router id. The "network type" is crucial that it ! "matches" to the peer or remote side. Otherwise it won't work. Timers and ! adjacencies are import to verify in case of troubleshooting an OSPF problem. Serial0/1.2 is up, line protocol is up Internet Address 160.10.38.2/24, Area 0 Process ID 1, Router ID 160.10.2.2, Network Type POINT_TO_POINT, Cost: 64 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 oob-resync timeout 40 Hello due in 00:00:08 Index 3/4, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 2, maximum is 10 Last flood scan time is 0 msec, maximum is 4 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 160.10.4.4 Suppress hello for 0 neighbor(s) Serial0/1.1 is up, line protocol is up Internet Address 160.10.37.2/24, Area 0 Process ID 1, Router ID 160.10.2.2, Network Type POINT_TO_MULTIPOINT, Cost: 64 Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT, Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5 oob-resync timeout 120 Hello due in 00:00:13 Index 2/3, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 1, maximum is 8 Last flood scan time is 0 msec, maximum is 4 msec Neighbor Count is 2, Adjacent neighbor count is 2 Adjacent with neighbor 160.10.5.5 Adjacent with neighbor 160.10.1.1 Suppress hello for 0 neighbor(s) Loopback0 is up, line protocol is up Internet Address 160.10.2.2/24, Area 0 Process ID 1, Router ID 160.10.2.2, Network Type POINT_TO_POINT, Cost: 1 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 oob-resync timeout 40 Index 1/1, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 0, maximum is 0 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 0, Adjacent neighbor count is 0 Suppress hello for 0 neighbor(s) Serial0/0 is up, line protocol is up Internet Address 160.10.32.2/30, Area 1 Process ID 1, Router ID 160.10.2.2, Network Type POINT_TO_POINT, Cost: 64 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 oob-resync timeout 40 Hello due in 00:00:03 Index 1/2, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 1, maximum is 17 Last flood scan time is 0 msec, maximum is 4 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 160.10.3.3 Suppress hello for 0 neighbor(s) R2# R2#show ip ospf neighbor ! Look for the neighbors and verify their state and addresses. This information ! will indicate if the adjacencies are made or not. The state "FULL" indicates ! routers a fully adjacent with each other. Neighbor ID Pri State Dead Time Address Interface 160.10.4.4 0 FULL/ - 00:00:35 160.10.38.4 Serial0/1.2 160.10.5.5 0 FULL/ - 00:01:58 160.10.37.5 Serial0/1.1 160.10.1.1 0 FULL/ - 00:01:50 160.10.37.1 Serial0/1.1 160.10.3.3 0 FULL/ - 00:00:34 160.10.32.1 Serial0/0 R2# R2#show ip ospf database ! Observe the router ID and process ID. The OSPF areas into R2 process and ! the LSA packets types that indicates what kind of advertisement is being sent. ! OSPF has 7 types of LSA and the type depends on your topology and we can ! have different topologies per OSPF area. (look the last block of the ! output below) OSPF Router with ID (160.10.2.2) (Process ID 1) Router Link States (Area 0) Link ID ADV Router Age Seq# Checksum Link count 160.10.1.1 160.10.1.1 914 0x800004F7 0x00A4DD 3 160.10.2.2 160.10.2.2 675 0x80000509 0x001D82 6 160.10.4.4 160.10.4.4 403 0x800004F9 0x005ECD 3 160.10.5.5 160.10.5.5 1440 0x800004D5 0x007B0B 3 Summary Net Link States (Area 0) Link ID ADV Router Age Seq# Checksum 160.10.3.0 160.10.2.2 675 0x80000006 0x003A60 160.10.7.0 160.10.1.1 914 0x800004EB 0x0025BF 160.10.11.0 160.10.1.1 914 0x800004F1 0x00E2F8 160.10.25.0 160.10.1.1 914 0x800004F7 0x00A01D 160.10.25.0 160.10.5.5 1440 0x800004F6 0x00AF1A 160.10.32.0 160.10.2.2 675 0x800004F2 0x00F798 Summary ASB Link States (Area 0) Link ID ADV Router Age Seq# Checksum 160.10.5.5 160.10.1.1 914 0x800004D4 0x00836B Router Link States (Area 1) Link ID ADV Router Age Seq# Checksum Link count 160.10.2.2 160.10.2.2 677 0x800004F8 0x008C76 2 160.10.3.3 160.10.3.3 741 0x800004DA 0x005212 3 Summary Net Link States (Area 1) Link ID ADV Router Age Seq# Checksum 160.10.1.0 160.10.2.2 677 0x800004DA 0x009A29 160.10.2.0 160.10.2.2 677 0x800004F1 0x00DE0D 160.10.4.0 160.10.2.2 677 0x800004DB 0x007748 160.10.5.0 160.10.2.2 677 0x800004D6 0x00764D 160.10.7.0 160.10.2.2 677 0x800004DA 0x00BCF6 160.10.11.0 160.10.2.2 677 0x800004DA 0x00862A 160.10.25.0 160.10.2.2 677 0x800004DA 0x00911A 160.10.37.1 160.10.2.2 677 0x800004DA 0x00F8A6 160.10.37.2 160.10.2.2 678 0x800004E5 0x00567D 160.10.37.5 160.10.2.2 678 0x800004D6 0x00D8C6 160.10.38.0 160.10.2.2 678 0x800004E5 0x00E1B2 Summary ASB Link States (Area 1) Link ID ADV Router Age Seq# Checksum 160.10.4.4 160.10.2.2 678 0x800004DB 0x003784 160.10.5.5 160.10.2.2 679 0x800004D6 0x002C92 Type-5 AS External Link States ! This indicates LSA type 5 that is "Autonomous System (AS) ! External Link Advertisements. Link ID ADV Router Age Seq# Checksum Tag 130.200.10.0 160.10.2.2 1937 0x800004F0 0x0096C1 0 140.200.10.0 160.10.4.4 407 0x800004F0 0x001895 0 160.10.6.0 160.10.5.5 1192 0x80000094 0x00C98D 0 160.10.15.0 160.10.5.5 1444 0x800004D4 0x00D930 0 160.10.22.0 160.10.5.5 1444 0x800004D6 0x008878 0 160.10.33.0 160.10.5.5 1444 0x800004D8 0x000BE8 0 193.118.1.0 160.10.2.2 177 0x80000095 0x006271 0 193.118.2.0 160.10.2.2 177 0x80000095 0x00577B 0 193.118.3.0 160.10.2.2 177 0x80000095 0x004C85 0 196.1.2.0 160.10.4.4 148 0x80000095 0x00B5EE 0 196.1.8.0 160.10.4.4 149 0x80000095 0x00732B 0 196.1.10.0 160.10.4.4 149 0x80000095 0x005D3F 0 R2# R2#debug ip ospf events ! Here you can see hello packets being received and sent on a specific ! interfaces, that means the OSPF is active on this link. OSPF events debugging is on *Mar 30 10:01:27.136: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:01:27.136: OSPF: End of hello processing *Mar 30 10:01:27.880: OSPF: Send hello to 224.0.0.5 area 1 on Serial0/0 from 160.10.32.2 *Mar 30 10:01:37.176: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:01:37.176: OSPF: End of hello processing *Mar 30 10:01:37.880: OSPF: Send hello to 224.0.0.5 area 1 on Serial0/0 from 160.10.32.2 *Mar 30 10:01:47.176: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:01:47.176: OSPF: End of hello processing R2#debug ip ospf hello ! Here you have a similar information as the previous output ! where you see the hello packets being exchanged. OSPF hello events debugging is on R2# *Mar 30 10:03:17.116: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:03:17.116: OSPF: End of hello processing *Mar 30 10:03:17.880: OSPF: Send hello to 224.0.0.5 area 1 on Serial0/0 from 160.10.32.2 *Mar 30 10:03:27.116: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:03:27.116: OSPF: End of hello processing *Mar 30 10:03:27.880: OSPF: Send hello to 224.0.0.5 area 1 on Serial0/0 from 160.10.32.2 *Mar 30 10:03:37.116: OSPF: Rcv hello from 160.10.3.3 area 1 from Serial0/0 160.10.32.1 *Mar 30 10:03:37.116: OSPF: End of hello processing R2#debug ip ospf packet ! The command shows that packtes are being exchanged through the interface. ! Important to look at is: "rid" that is the router ID, "aid" is the ! area number and "aut" is the authentication method if there is any. OSPF packet debugging is on R2# *Mar 30 10:04:58.884: OSPF: rcv. v:2 t:1 l:48 rid:160.10.4.4 aid:0.0.0.0 chk:B67F aut:0 auk: from Serial0/1.2 *Mar 30 10:05:01.624: OSPF: rcv. v:2 t:1 l:48 rid:160.10.5.5 aid:0.0.0.0 chk:B51A aut:0 auk: from Serial0/1.1 *Mar 30 10:05:01.624: OSPF: rcv. v:2 t:1 l:48 rid:160.10.5.5 aid:0.0.0.0 chk:B51A aut:0 auk: from Serial0/1.1 *Mar 30 10:05:07.156: OSPF: rcv. v:2 t:1 l:48 rid:160.10.3.3 aid:0.0.0.1 chk:B683 aut:0 auk: from Serial0/0 *Mar 30 10:05:08.880: OSPF: rcv. v:2 t:1 l:48 rid:160.10.4.4 aid:0.0.0.0 chk:B67F aut:0 auk: from Serial0/1.2 EIGRPTroubleshooting commands for EIGRP configuration include the following:
Example C-5 provides commented output from these key commands. Example C-5. Some EIGRP Troubleshooting CommandsR2#show ip eigrp interfaces ! The command shows the interfaces that are participating within ! EIGRP routing process. IP-EIGRP interfaces for process 400 Xmit Queue Mean Pacing Time Multicast Pending Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes Fa0/0 1 0/0 1 0/10 50 0 R2# R2#show ip eigrp neighbors ! This command revels the EIGRP neighbors. If no output is shown means ! some problem is happening, then you should double check your configuration ! or verify if the interface is up. IP-EIGRP neighbors for process 400 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 130.200.10.200 Fa0/0 14 3d10h 1 200 0 10 R2# R2#show ip eigrp topology ! It shows the EIGRP AS number and I, who is the successor candidates ! and the interfaces participating on the routing process and if ! the interface is directed connected, if it was learned frm a neighbor or ! if it was learned via redistribution. IP-EIGRP Topology Table for AS(400)/ID(160.10.2.2) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 130.200.10.0/24, 1 successors, FD is 28160 via Connected, FastEthernet0/0 P 140.200.10.0/24, 1 successors, FD is 25602560 via Redistributed (25602560/0) P 160.10.32.0/30, 1 successors, FD is 2169856 via Connected, Serial0/0 Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 160.10.15.0/24, 1 successors, FD is 25602560 via Redistributed (25602560/0) P 193.118.2.0/24, 1 successors, FD is 156160 via 130.200.10.200 (156160/128256), FastEthernet0/0 R2# R2#show ip eigrp traffic ! The output shows the traffic that was sent and received on the interface ! as well the EIGRP AS number. IP-EIGRP Traffic Statistics for AS 400 Hellos sent/received: 549415/549363 Updates sent/received: 52/46 Queries sent/received: 31/1 Replies sent/received: 1/31 Acks sent/received: 74/76 Input queue high water mark 1, 0 drops SIA-Queries sent/received: 0/0 SIA-Replies sent/received: 0/0 Hello Process ID: 108 PDM Process ID: 145 R2#debug ip eigrp ! Notice the advertisements are sent out and received. Observe the ! IP address and interfaces as well the metric of sent and received routes. IP-EIGRP Route Events debugging is on R2# *Mar 30 10:25:54.052: IP-EIGRP(Default-IP-Routing-Table:400): 140.200.10.0/24 - do advertise out FastEthernet0/0 *Mar 30 10:25:54.052: IP-EIGRP Default-IP-Routing-Table:400): Ext 140.200.10.0/24 metric 4294967295 - 25600000 4294967295 *Mar 30 10:25:54.052: IP-EIGRP(Default-IP-Routing-Table:400): 160.10.37.5/32 - do advertise out FastEthernet0/0 * Mar 30 10:25:54.052: IP-EIGRP(Default-IP-Routing-Table:400): Processing incoming REPLY packet * Mar 30 10:25:54.052: IP-EIGRP(Default-IP-Routing-Table:400): ExtS 140.200.10.0/24 M 4294967295 - 0 4294967295 SM 4294967295 - 0 4294967295 RIPTroubleshooting commands for RIP configuration include the following:
Example C-6 provides commented output from these key commands. Example C-6. Some RIP Troubleshooting CommandsR4#show ip rip database ! Here you can see the networks participating within RIP routing process ! and the interfaces participating. 140.200.0.0/16 auto-summary 140.200.10.0/24 directly connected, Ethernet0/0 196.1.2.0/24 auto-summary 196.1.2.0/24 [1] via 140.200.10.200, 00:00:26, Ethernet0/0 196.1.8.0/24 auto-summary 196.1.8.0/24 [1] via 140.200.10.200, 00:00:26, Ethernet0/0 196.1.10.0/24 auto-summary 196.1.10.0/24 [1] via 140.200.10.200, 00:00:26, Ethernet0/0 R4# R4#debug ip rip RIP protocol debugging is on ! The output from this command shows the RIP routes being exchanged. ! Observe the interfaces, routes and RIP version. 3d08h: RIP: sending request on Ethernet0/0 to 224.0.0.9 3d08h: RIP: sending request on Ethernet0/0 to 224.0.0.9 3d08h: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 3d08h: 20.0.0.0/8 via 0.0.0.0 in 1 hops 3d08h: 30.0.0.0/8 via 0.0.0.0 in 1 hops 3d08h: 196.1.1.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.2.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.3.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.4.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.5.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.6.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.7.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.8.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.9.0/24 via 0.0.0.0 in 1 hops 3d08h: 196.1.10.0/24 via 0.0.0.0 in 1 hops 3d08h: RIP: sending v2 flash update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) 3d08h: RIP: build flash update entries - suppressing null update 3d08h: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 R4#debug ip rip database RIP database events debugging is on ! You can see below the RIP routes being updated and installed into the ! routing table. R4# 4w1d: RIP-DB: network_update with 196.1.2.0/24 succeeds 4w1d: RIP-DB: adding 196.1.2.0/24 (metric 1) via 140.200.10.200 on Ethernet0/0 to RIP database 4w1d: RIP-DB: network_update with 196.1.8.0/24 succeeds 4w1d: RIP-DB: adding 196.1.8.0/24 (metric 1) via 140.200.10.200 on Ethernet0/0 to RIP database 4w1d: RIP-DB: network_update with 196.1.10.0/24 succeeds 4w1d: RIP-DB: adding 196.1.10.0/24 (metric 1) via 140.200.10.200 on Ethernet0/0 to RIP database R4#debug ip rip events RIP event debugging is on ! This output has some similarities with the output above. You can notice ! what is being sent and received through interface Etherneth0/0. ! Also notice the updates are sent via the well-know Multicast Group ! address "224.0.0.9". The "suppressing null update means that 'no routes ! are being advertised. R4# 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update 4w1d: RIP: received v2 update from 140.200.10.200 on Ethernet0/0 4w1d: RIP: Update contains 12 routes 4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0/0 (140.200.10.4) - suppressing null update R4# IS-ISTroubleshooting commands for IS-IS configuration include the following:
Example C-7 provides commented output from these key commands. Example C-7. Some IS-IS Troubleshooting CommandsR6#show isis database ! Here we have the IS-IS database that shows R6 having Level-1 and Level-2 ! Circuit types. Important to notice are the LSPID ! (The Link State Packet identifier). The first six octets form the ! system ID of the router that originated the LSP), and the fields ATT/P/OL, ! where ATT is the Attached bit that indicates that the router is a ! Level-2 router and can reach others areas. The P bit is the IS is ! area repair capable. Cisco routers do not support area repair capable. ! The OL bit indicates if IS is congested. IS-IS Level-1 Link State Database: LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL R3.00-00 0x00000CB1 0x51AE 889 0/0/0 R5.00-00 0x00000CCB 0xAE51 940 0/0/0 R6.00-00 * 0x0000070D 0x5EC9 748 0/0/0 R6.02-00 * 0x00000706 0x02A6 543 0/0/0 IS-IS Level-2 Link State Database: LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL R3.00-00 0x00000CCB 0xBE67 758 0/0/0 R5.00-00 0x00000CDA 0x8223 911 0/0/0 R6.00-00 * 0x00000712 0x44EF 845 0/0/0 R6.02-00 * 0x00000708 0xAF7F 1167 0/0/0 R6# R6#show isis topology ! This command shows a list of all routers in all areas. You can see the ! paths to Level-1 and to Level-2 routers. Also notice the Metric as ! "10" that is the default. IS-IS paths to level-1 routers System Id Metric Next-Hop Interface SNPA R3 10 R3 Et0/0 0009.43a7.2c60 R5 10 R5 Et0/0 0009.43a7.2f60 R6 -- IS-IS paths to level-2 routers System Id Metric Next-Hop Interface SNPA R3 10 R3 Et0/0 0009.43a7.2c60 R5 10 R5 Et0/0 0009.43a7.2f60 R6 -- R6# R6#show clns protocol ! This command shows you some specific information regarding the CLNS Protocol. ! Look at the System ID, IS-Type, Manual areas address and the interfaces ! supported by IS-IS. IS-IS Router: <Null Tag> System Id: 0000.0000.0006.00 IS-Type: level-1-2 Manual area address(es): 49.0004 Routing for area address(es): 49.0004 Interfaces supported by IS-IS: Ethernet0/0 - IP Loopback0 - IP Redistribute: static (on by default) Distance for L2 CLNS routes: 110 RRR level: none Generate narrow metrics: level-1-2 Accept narrow metrics: level-1-2 Generate wide metrics: none Accept wide metrics: none R6# R6#show clns interface ! This command lists specific information about the CLNS interfaces. ! Observe the interface status, the IS-IS as the routing protocol running ! and the Circuit Type Ethernet0/0 is up, line protocol is up Checksums enabled, MTU 1497, Encapsulation SAP ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching enabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 26 seconds Routing Protocol: IS-IS Circuit Type: level-1-2 Interface number 0x1, local circuit ID 0x2 Level-1 Metric: 10, Priority: 64, Circuit ID: R6.02 Number of active level-1 adjacencies: 2 Level-2 Metric: 10, Priority: 64, Circuit ID: R6.02 Number of active level-2 adjacencies: 2 Next IS-IS LAN Level-1 Hello in 2 seconds Next IS-IS LAN Level-2 Hello in 924 milliseconds Serial0/0 is administratively down, line protocol is down CLNS protocol processing disabled TokenRing0/0 is administratively down, line protocol is down CLNS protocol processing disabled Serial0/1 is administratively down, line protocol is down CLNS protocol processing disabled FastEthernet1/0 is administratively down, line protocol is down CLNS protocol processing disabled ATM3/0 is up, line protocol is up CLNS protocol processing disabled Loopback0 is up, line protocol is up Checksums enabled, MTU 1514, Encapsulation LOOPBACK ERPDUs enabled, min. interval 10 msec. RDPDUs enabled, min. interval 100 msec., Addr Mask enabled Congestion Experienced bit set at 4 packets CLNS fast switching disabled CLNS SSE switching disabled DEC compatibility mode OFF for this interface Next ESH/ISH in 32 seconds Routing Protocol: IS-IS Circuit Type: level-1-2 Interface number 0x0, local circuit ID 0x1 Level-1 Metric: 10, Priority: 64, Circuit ID: R6.01 Number of active level-1 adjacencies: 0 Level-2 Metric: 10, Priority: 64, Circuit ID: R6.01 Number of active level-2 adjacencies: 0 Next IS-IS LAN Level-1 Hello in 2 seconds Next IS-IS LAN Level-2 Hello in 6 seconds R6# R6#show clns neighbors ! This command shows you R6 neighbors establishments and the Type ! protocol or Circuit Type for each neighbor. System Id Interface SNPA State Holdtime Type Protocol R3 Et0/0 0009.43a7.2c60 Up 25 L1L2 IS-IS R5 Et0/0 0009.43a7.2f60 Up 27 L1L2 IS-IS R6# BGPTroubleshooting commands for BGP configuration include the following:
Example C-8 provides commented output from these key commands. Example C-8. Some BGP Troubleshooting CommandsR6#show ip bgp ! This command displays the entries in the BGP routing table. ! It is important to observe the BGP table version, that is incremented ! whenever the table changes and the router ID. The status code is important ! also because identify how the route will be treated. For example the "*" ! indicates a valid path and ">" indicates that the entry is the best entry to ! use for that network and indicates that the network will be installed on the ! IP table. The "Next Hop" is the next system used when forwarding a packet ! to the destination network. The "Path" is the Autonomous system paths ! to the destination network. BGP table version is 21, local router ID is 160.10.6.6 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 198.18.1.0 170.100.10.254 0 0 300 i *> 198.18.2.0 170.100.10.254 0 0 300 i *> 198.18.3.0 170.100.10.254 0 0 300 i *> 198.18.4.0 170.100.10.254 0 0 300 i *> 198.18.5.0 170.100.10.254 0 0 300 i *> 198.18.6.0 170.100.10.254 0 0 300 i *> 198.18.7.0 170.100.10.254 0 0 300 i *> 198.18.8.0 170.100.10.254 0 0 300 i *> 198.18.9.0 170.100.10.254 0 0 300 i *> 198.18.10.0 170.100.10.254 0 0 300 i *> 200.20.1.0 170.100.10.254 0 0 300 i *> 200.20.2.0 170.100.10.254 0 0 300 i *> 200.20.3.0 170.100.10.254 0 0 300 i *> 200.20.4.0 170.100.10.254 0 0 300 i *> 200.20.5.0 170.100.10.254 0 0 300 i *> 200.20.6.0 170.100.10.254 0 0 300 i *> 200.20.7.0 170.100.10.254 0 0 300 i *> 200.20.8.0 170.100.10.254 0 0 300 i Network Next Hop Metric LocPrf Weight Path *> 200.20.9.0 170.100.10.254 0 0 300 i *> 200.20.10.0 170.100.10.254 0 0 300 i R6# R6#show ip bgp summary ! The output displays the Local AS number, the neighbors AS, how long the ! neighbors is up (UP/DOWN) and how many prefixes are being received ! form a specific neighbor. BGP router identifier 160.10.6.6, local AS number 100 BGP table version is 21, main routing table version 21 20 network entries using 1940 bytes of memory 20 path entries using 720 bytes of memory 1 BGP path attribute entries using 60 bytes of memory 1 BGP AS-PATH entries using 24 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 2744 total bytes of memory BGP activity 20/0 prefixes, 20/0 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 160.10.3.3 4 100 5039 5040 21 0 0 3d11h 0 170.100.10.254 4 300 5041 5039 21 0 0 3d11h 20 R6# R6#show ip route bgp ! The output below shows the best BGP routes the fed the IP routing table. B 198.18.10.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.4.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.5.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.8.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.6.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.9.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.7.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.1.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.2.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.3.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.2.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.3.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.1.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.6.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.8.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.7.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.9.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.4.0/24 [20/0] via 170.100.10.254, 3d11h B 200.20.10.0/24 [20/0] via 170.100.10.254, 3d11h B 198.18.5.0/24 [20/0] via 170.100.10.254, 3d11h R6 R6#show ip bgp neighbors ! The output shows the TCP and BGP connections to neighbors. ! Notice the BGP neighbor IP address, the neighbor or remote AS and router ID. ! Also the "internal" link means iBGP and "external" link means EBGP ! (look below the output for neighbor 170.100.10.254). BGP neighbor is 160.10.3.3, remote AS 100, internal link BGP version 4, remote router ID 160.10.3.3 BGP state = Established, up for 3d12h Last read 00:00:53, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: Route refresh: advertised and received(old & new) Address family IPv4 Unicast: advertised and received Message statistics: InQ depth is 0 OutQ depth is 0 Sent Rcvd Opens: 1 1 Notifications: 0 0 Updates: 1 0 Keepalives: 5047 5046 Route Refresh: 0 0 Total: 5049 5047 Default minimum time between advertisement runs is 5 seconds For address family: IPv4 Unicast BGP table version 21, neighbor version 21 Index 1, Offset 0, Mask 0x2 Route-Reflector Client NEXT_HOP is always this router Sent Rcvd Prefix activity: ---- ---- Prefixes Current: 20 0 Prefixes Total: 20 0 Implicit Withdraw: 0 0 Explicit Withdraw: 0 0 Used as bestpath: n/a 0 Used as multipath: n/a 0 Outbound Inbound Local Policy Denied Prefixes: -------- ------- Total: 0 0 Number of NLRIs in the update sent: max 20, min 0 Connections established 1; dropped 0 Last reset never ! Observe below the Connection State as "STABilished", the local host or ! source IP address and TCP Port = 1103 and the Foreign host or ! remote/destination TCP port = 179. Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local host: 160.10.6.6, Local port: 179 Foreign host: 160.10.3.3, Foreign port: 11003 Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes) Event Timers (current time is 0x120AE458): Timer Starts Wakeups Next Retrans 5050 0 0x0 TimeWait 0 0 0x0 AckHold 5047 4754 0x0 SendWnd 0 0 0x0 KeepAlive 0 0 0x0 GiveUp 0 0 0x0 PmtuAger 0 0 0x0 DeadWait 0 0 0x0 iss: 2690266982 snduna: 2690363056 sndnxt: 2690363056 sndwnd: 16175 irs: 4088662438 rcvnxt: 4088758358 rcvwnd: 16327 delrcvwnd: 57 SRTT: 300 ms, RTTO: 303 ms, RTV: 3 ms, KRTT: 0 ms minRTT: 4 ms, maxRTT: 300 ms, ACK hold: 200 ms Flags: passive open, nagle, gen tcbs Datagrams (max data segment is 536 bytes): Rcvd: 9883 (out of order: 0), with data: 5048, total data bytes: 95938 Sent: 9979 (retransmit: 0, fastretransmit: 0), with data: 5049, total data bytes: 96073 BGP neighbor is 170.100.10.254, remote AS 300, external link BGP version 4, remote router ID 200.20.1.254 BGP state = Established, up for 3d12h Last read 00:00:38, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: Route refresh: advertised and received(old & new) Address family IPv4 Unicast: advertised and received Message statistics: InQ depth is 0 OutQ depth is 0 Sent Rcvd Opens: 1 1 Notifications: 0 0 Updates: 0 1 Keepalives: 5047 5047 Route Refresh: 0 0 Total: 5048 5049 Default minimum time between advertisement runs is 30 seconds For address family: IPv4 Unicast BGP table version 21, neighbor version 21 Index 2, Offset 0, Mask 0x4 Sent Rcvd Prefix activity: ---- ---- Prefixes Current: 0 20 (Consumes 720 bytes) Prefixes Total: 0 20 Implicit Withdraw: 0 0 Explicit Withdraw: 0 0 Used as bestpath: n/a 20 Used as multipath: n/a 0 Outbound Inbound Local Policy Denied Prefixes: -------- ------- Bestpath from this peer: 20 n/a Total: 20 0 Number of NLRIs in the update sent: max 0, min 0 Connections established 1; dropped 0 Last reset never ! Observe below the Connection State as "STABilished", the local host or ! source IP address and TCP Port = 1100 and the Foreign host or ! remote/destination TCP port = 179. Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local host: 170.100.10.1, Local port: 11000 Foreign host: 170.100.10.254, Foreign port: 179 Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes) Event Timers (current time is 0x120B4A90): Timer Starts Wakeups Next Retrans 5049 0 0x0 TimeWait 0 0 0x0 AckHold 5048 4120 0x0 SendWnd 0 0 0x0 KeepAlive 0 0 0x0 GiveUp 0 0 0x0 PmtuAger 0 0 0x0 DeadWait 0 0 0x0 iss: 256698678 snduna: 256794617 sndnxt: 256794617 sndwnd: 13800 irs: 3486541483 rcvnxt: 3486637550 rcvwnd: 13686 delrcvwnd: 2698 SRTT: 300 ms, RTTO: 303 ms, RTV: 3 ms, KRTT: 0 ms minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 200 ms Flags: higher precedence, nagle Datagrams (max data segment is 4430 bytes): Rcvd: 9711 (out of order: 0), with data: 5048, total data bytes: 96066 Sent: 9191 (retransmit: 0, fastretransmit: 0), with data: 5048, total data bytes: 95938 R6#show ip bgp neighbors 170.100.10.254 ! The output displays a specific neighbor TCP and BGP connections to that neighbor. BGP neighbor is 170.100.10.254, remote AS 300, external link BGP version 4, remote router ID 200.20.1.254 BGP state = Established, up for 3d12h Last read 00:00:21, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: Route refresh: advertised and received(old & new) Address family IPv4 Unicast: advertised and received Message statistics: InQ depth is 0 OutQ depth is 0 Sent Rcvd Opens: 1 1 Notifications: 0 0 Updates: 0 1 Keepalives: 5045 5045 Route Refresh: 0 0 Total: 5046 5047 Default minimum time between advertisement runs is 30 seconds For address family: IPv4 Unicast BGP table version 21, neighbor version 21 Index 2, Offset 0, Mask 0x4 Sent Rcvd Prefix activity: ---- ---- Prefixes Current: 0 20 (Consumes 720 bytes) Prefixes Total: 0 20 Implicit Withdraw: 0 0 Explicit Withdraw: 0 0 Used as bestpath: n/a 20 Used as multipath: n/a 0 Outbound Inbound Local Policy Denied Prefixes: -------- ------- Bestpath from this peer: 20 n/a Total: 20 0 Number of NLRIs in the update sent: max 0, min 0 Connections established 1; dropped 0 Last reset never ! Observe below the Connection State as "STABilished", the local host or ! source IP address and TCP Port = 1100 and the Foreign host or ! remote/destination TCP port = 179. Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local host: 170.100.10.1, Local port: 11000 Foreign host: 170.100.10.254, Foreign port: 179 Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes) Event Timers (current time is 0x12093888): Timer Starts Wakeups Next Retrans 5047 0 0x0 TimeWait 0 0 0x0 AckHold 5046 4118 0x0 SendWnd 0 0 0x0 KeepAlive 0 0 0x0 GiveUp 0 0 0x0 PmtuAger 0 0 0x0 DeadWait 0 0 0x0 iss: 256698678 snduna: 256794579 sndnxt: 256794579 sndwnd: 13838 irs: 3486541483 rcvnxt: 3486637512 rcvwnd: 13724 delrcvwnd: 2660 SRTT: 300 ms, RTTO: 303 ms, RTV: 3 ms, KRTT: 0 ms minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 200 ms Flags: higher precedence, nagle Datagrams (max data segment is 4430 bytes): Rcvd: 9707 (out of order: 0), with data: 5046, total data bytes: 96028 Sent: 9187 (retransmit: 0, fastretransmit: 0), with data: 5046, total data bytes: 95900 R6#clear ip bgp ? ! "clear ip bgp" will cause to reset a BGP connections oe all BGP connections. * Clear all peers <1-65535> Clear peers with the AS number A.B.C.D BGP neighbor address to clear dampening Clear route flap dampening information external Clear all external peers flap-statistics Clear route flap statistics ipv4 Address family peer-group Clear all members of peer-group vpnv4 Address family R6#debug ip bgp ? A.B.C.D BGP neighbor address dampening BGP dampening events BGP events in BGP Inbound information keepalives BGP keepalives out BGP Outbound information updates BGP updates vpnv4 VPNv4 NLRI information <cr> R6#debug ip bgp events BGP events debugging is on ! The debug ip bgp events command will trace the events that occur ! between the neighbors. R6# 3d12h: BGP: Import timer expired. Walking from 1 to 1 3d12h: BGP: Import timer expired. Walking from 1 to 1 3d12h: BGP: Import timer expired. Walking from 1 to 1 R6#clear ip bgp * R6# 3d12h: BGP: reset all neighbors due to User reset 3d12h: BGP: 160.10.3.3 reset due to User reset 3d12h: %BGP-5-ADJCHANGE: neighbor 160.10.3.3 Down User reset 3d12h: BGP: 170.100.10.254 reset due to User reset 3d12h: %BGP-5-ADJCHANGE: neighbor 170.100.10.254 Down User reset 3d12h: BGP: Performing BGP general scanning 3d12h: BGP(0): scanning IPv4 Unicast routing tables 3d12h: BGP(1): scanning VPNv4 Unicast routing tables 3d12h: BGP(2): scanning IPv4 Multicast routing tables 3d12h: BGP: Import timer expired. Walking from 1 to 1 3d12h: %BGP-5-ADJCHANGE: neighbor 160.10.3.3 Up 3d12h: BGP: Delaying initial update for up to 120 seconds 3d12h: BGP: Import timer expired. Walking from 1 to 1 3d12h: BGP: Import timer expired. Walking from 1 to 1 3d12h: %BGP-5-ADJCHANGE: neighbor 170.100.10.254 Up 3d12h: BGP: compute bestpath 3d12h: BGP: Performing BGP general scanning 3d12h: BGP(0): scanning IPv4 Unicast routing tables 3d12h: BGP(IPv4 Unicast): Performing BGP Nexthop scanning for general scan 3d12h: BGP(1): scanning VPNv4 Unicast routing tables 3d12h: BGP(VPNv4 Unicast): Performing BGP Nexthop scanning for general scan 3d12h: BGP(2): scanning IPv4 Multicast routing tables 3d12h: BGP(IPv4 Multicast): Performing BGP Nexthop scanning for general scan 3d12h: BGP: Import timer expired. Walking from 1 to 1 ISDNTroubleshooting commands for ISDN configuration include the following:
Example C-9 provides commented output from these key commands. Example C-9. Some ISDN Troubleshooting CommandsR5#show interfaces bri 0/0 ! The command shows the status of the BRI interface, its IP address, ! encapsulation, etc. BRI0/0 is up, line protocol is up (spoofing) Hardware is PQUICC BRI Internet address is 160.10.15.5/24 MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Last input 00:00:03, output never, output hang never Last clearing of "show interface" counters 4w0d Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 496808 packets input, 1987304 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 496808 packets output, 1987347 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 1 carrier transitions R5# R5#show interfaces bri 0/0 1 2 ! This command displays the interface BRI and its B channels, in this case ! channels 1 and 2. Also observe the protocols, that are closed in the ! output below, as LCP, OSICP (CLNS), IPCP (IP) and CDPCP (CDP). ! The input packets and output packets indicate traffic being exchanged. BRI0/0:1 is down, line protocol is down Hardware is PQUICC BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Keepalive set (10 sec) LCP Closed Closed: OSICP, IPCP, CDPCP Last input 4w0d, output 4w0d, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/2/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 158 packets input, 84813 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 1353 packets output, 83976 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 7 carrier transitions BRI0/0:2 is down, line protocol is down Hardware is PQUICC BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Keepalive set (10 sec) LCP Closed Closed: OSICP, IPCP, CDPCP Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 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 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions R5# R5#show isdn status ! Look at the Layer 2 status and in this case the "SPID" status. ! Notice that Layer 3 status is active but no calls established. Global ISDN Switchtype = basic-ni ISDN BRI0/0 interface dsl 0, interface ISDN Switchtype = basic-ni Layer 1 Status: ACTIVE Layer 2 Status: TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED TEI 64, ces = 1, state = 5(init) spid1 configured, no LDN, spid1 sent, spid1 valid Endpoint ID Info: epsf = 0, usid = 70, tid = 1 Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x80000003 Total Allocated ISDN CCBs = 0 R5# R5#show dialer interface bri 0/0 ! This command display the ISDN connections if there is any. ! Observe the dial string and the last status. BRI0/0 - dialer type = ISDN Dial String Successes Failures Last DNIS Last status 1111 3 0 4w0d successful 0 incoming call(s) have been screened. 0 incoming call(s) rejected for callback. BRI0/0:1 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is idle BRI0/0:2 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is idle R5# ! R5#show dialer interface bri0/0 ! Here we have the same output command but now showing ! established connections. Notice that B channel 1 BRI/0:1 is ! being used and R5 is connected to R3 (1111). BRI0/0 - dialer type = ISDN Dial String Successes Failures Last DNIS Last status 1111 2 0 00:00:21 successful 0 incoming call(s) have been screened. 0 incoming call(s) rejected for callback. BRI0/0:1 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is data link layer up Dial reason: ip (s=160.10.15.5, d=160.10.15.3) Time until disconnect 102 secs Connected to 1111 (R3) BRI0/0:2 - dialer type = ISDN Idle timer (120 secs), Fast idle timer (20 secs) Wait for carrier (30 secs), Re-enable (15 secs) Dialer state is idle R5# R5#debug isdn q931 ISDN Q931 packets debugging is on ! The output from this debug shows you the sequence of commands used to ! establish and to release the connection R5#ping 160.10.15.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.15.3, timeout is 2 seconds: 3d15h: ISDN BR0/0: TX -> SETUP pd = 8 callref = 0x03 3d15h: Bearer Capability i = 0x8890 3d15h: Channel ID i = 0x83 3d15h: Keypad Facility i = '1111' 3d15h: ISDN BR0/0: RX <- CALL_PROC pd = 8 callref = 0x83 3d15h: Channel ID i = 0x89 3d15h: ISDN BR0/0: RX <- CONNECT pd = 8 callref = 0x83 3d15h: Channel ID i = 0x89 3d15h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up.! 3d15h: ISDN BR0/0: TX -> CONNECT_ACK pd = 8 callref = 0x03!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 32/34/36 ms R5# 3d15h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up 3d15h: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 1111 R3 R5# R5# 3d15h: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from 1111 R3, call lasted 121 seconds 3d15h: ISDN BR0/0: TX -> DISCONNECT pd = 8 callref = 0x03 3d15h: Cause i = 0x8090 - Normal call clearing 3d15h: ISDN BR0/0: RX <- RELEASE pd = 8 callref = 0x83 3d15h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down 3d15h: ISDN BR0/0: TX -> RELEASE_COMP pd = 8 callref = 0x03 3d15h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to down R5#R5# R5# R5#debug ppp negotiation PPP protocol negotiation debugging is on ! The output shows the PPP negotiation in order to establish de connection. Observe the LCP and CHAP protocols messages. Look below the IP, CDP and CLNS protocols being established. R5# 4w0d: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up 4w0d: BR0/0:1 PPP: Using dialer call direction 4w0d: BR0/0:1 PPP: Treating connection as a callin 4w0d: BR0/0:1 PPP: Phase is ESTABLISHING, Passive Open [0 sess, 0 load] 4w0d: BR0/0:1 LCP: State is Listen 4w0d: BR0/0:1 LCP: TIMEout: State Listen 4w0d: BR0/0:1 LCP: O CONFREQ [Listen] id 8 len 15 4w0d: BR0/0:1 LCP: AuthProto CHAP (0x0305C22305) 4w0d: BR0/0:1 LCP: MagicNumber 0x9DFDE9CD (0x05069DFDE9CD) 4w0d: BR0/0:1 LCP: I CONFACK [REQsent] id 8 len 15 4w0d: BR0/0:1 LCP: AuthProto CHAP (0x0305C22305) 4w0d: BR0/0:1 LCP: MagicNumber 0x9DFDE9CD (0x05069DFDE9CD) 4w0d: BR0/0:1 LCP: I CONFREQ [ACKrcvd] id 9 len 15 4w0d: BR0/0:1 LCP: AuthProto CHAP (0x0305C22305) 4w0d: BR0/0:1 LCP: MagicNumber 0x9DFDF362 (0x05069DFDF362) 4w0d: BR0/0:1 LCP: O CONFACK [ACKrcvd] id 9 len 15 4w0d: BR0/0:1 LCP: AuthProto CHAP (0x0305C22305) 4w0d: BR0/0:1 LCP: MagicNumber 0x9DFDF362 (0x05069DFDF362) 4w0d: BR0/0:1 LCP: State is Open 4w0d: BR0/0:1 PPP: Phase is AUTHENTICATING, by both [0 sess, 0 load] 4w0d: BR0/0:1 CHAP: O CHALLENGE id 6 len 23 from "R5" 4w0d: BR0/0:1 CHAP: I CHALLENGE id 6 len 23 from "R3" 4w0d: BR0/0:1 CHAP: Waiting for peer to authenticate first 4w0d: BR0/0:1 CHAP: I RESPONSE id 6 len 23 from "R3" 4w0d: BR0/0:1 CHAP: O SUCCESS id 6 len 4 4w0d: BR0/0:1 CHAP: Processing saved Challenge, id 6 4w0d: BR0/0:1 CHAP: O RESPONSE id 6 len 23 from "R5" 4w0d: BR0/0:1 CHAP: I SUCCESS id 6 len 4 4w0d: BR0/0:1 PPP: Phase is UP [0 sess, 0 load] 4w0d: BR0/0:1 OSICP: O CONFREQ [Closed] id 6 len 4 4w0d: BR0/0:1 IPCP: O CONFREQ [Closed] id 6 len 10 4w0d: BR0/0:1 IPCP: Address 160.10.15.5 (0x0306A00A0F05) 4w0d: BR0/0:1 CDPCP: O CONFREQ [Closed] id 6 len 4 4w0d: BR0/0:1 OSICP: I CONFREQ [REQsent] id 6 len 4 4w0d: BR0/0:1 OSICP: O CONFACK [REQsent] id 6 len 4 4w0d: BR0/0:1 IPCP: I CONFREQ [REQsent] id 6 len 10 4w0d: BR0/0:1 IPCP: Address 160.10.15.3 (0x0306A00A0F03) 4w0d: BR0/0:1 IPCP: O CONFACK [REQsent] id 6 len 10 4w0d: BR0/0:1 IPCP: Address 160.10.15.3 (0x0306A00A0F03) 4w0d: BR0/0:1 CDPCP: I CONFREQ [REQsent] id 6 len 4 4w0d: BR0/0:1 CDPCP: O CONFACK [REQsent] id 6 len 4 4w0d: BR0/0:1 OSICP: I CONFACK [ACKsent] id 6 len 4 4w0d: BR0/0:1 OSICP: State is Open 4w0d: BR0/0:1 IPCP: I CONFACK [ACKsent] id 6 len 10 4w0d: BR0/0:1 IPCP: Address 160.10.15.5 (0x0306A00A0F05) 4w0d: BR0/0:1 IPCP: State is Open 4w0d: BR0/0:1 CDPCP: I CONFACK [ACKsent] id 6 len 4 4w0d: BR0/0:1 CDPCP: State is Open 4w0d: BR0/0 IPCP: Install route to 160.10.15.3 4w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up 4w0d: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 1111 R3 R5# ! Now observe a sample of the protocols connections being disconnected ! and released. Notice the route being removed. 3d16h: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from 1111 R3, call lasted 124 seconds 3d16h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down 3d16h: BR0/0:1 OSICP: State is Closed 3d16h: BR0/0:1 IPCP: State is Closed 3d16h: BR0/0:1 CDPCP: State is Closed 3d16h: BR0/0:1 PPP: Phase is TERMINATING [0 sess, 1 load] 3d16h: BR0/0:1 LCP: State is Closed 3d16h: BR0/0:1 PPP: Phase is DOWN [0 sess, 1 load] 3d16h: BR0/0 IPCP: Remove route to 160.10.15.3 3d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to down R5#debug ppp authentication PPP authentication debugging is on ! The output below shows the "ppp" negotiation with the CHAP messages ! being exchanged. R5# 4w0d: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up 4w0d: BR0/0:1 PPP: Using dialer call direction 4w0d: BR0/0:1 PPP: Treating connection as a callin 4w0d: BR0/0:1 CHAP: O CHALLENGE id 7 len 23 from "R5" 4w0d: BR0/0:1 CHAP: I CHALLENGE id 7 len 23 from "R3" 4w0d: BR0/0:1 CHAP: Waiting for peer to authenticate first 4w0d: BR0/0:1 CHAP: I RESPONSE id 7 len 23 from "R3" 4w0d: BR0/0:1 CHAP: O SUCCESS id 7 len 4 4w0d: BR0/0:1 CHAP: Processing saved Challenge, id 7 4w0d: BR0/0:1 CHAP: O RESPONSE id 7 len 23 from "R5" 4w0d: BR0/0:1 CHAP: I SUCCESS id 7 len 4 4w0d: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up 4w0d: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 1111 R3 R5# ! It is important to observe that in some IOS images the authentication is ! no longer necessary in order to bring the ISDN link connected. R5#debug dialer Dial on demand events debugging is on ! This command shows DDR messages that establish the ISDN connection. ! Notice the dialer protocol messages. R5# R5#ping 160.10.15.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.15.3, timeout is 2 seconds: 3d17h: BR0/0 DDR: Dialing cause ip (s=160.10.15.5, d=160.10.15.3) 3d17h: BR0/0 DDR: Attempting to dial 1111 3d17h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up. 3d17h: BR0/0:1 DDR: dialer protocol up 3d17h: BR0/0:1 DDR: dialer protocol up. 3d17h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up 3d17h: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to up 3d17h: BR0/0:2 DDR: dialer protocol up 3d17h: BR0/0:2 DDR: dialer protocol up.!! Success rate is 40 percent (2/5), round-trip min/avg/max = 32/34/36 ms R5# 3d17h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:2, changed state to up 3d17h: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 1111 R3 R5# DLSwTroubleshooting commands for DLSw configuration include the following:
Example C-10 provides commented output from these key commands. Example C-10. Some DLSw Troubleshooting CommandsR3#show dlsw ? capabilities Display DLSw capabilities information circuits Display DLSw circuit information fastcache Display DLSw fast cache for FST and Direct local-circuit Display DLSw local circuits peers Display DLSw peer information reachability Display DLSw reachability information statistics Display DLSw statistical information transparent Display MAC address mappings R3#show dlsw peers ! Here the output shows R3 peering to R1 using FST. Important is to ! notice the State "CONNECT", the type "conf" meaning configured ! (not promiscuous). Peers: state pkts_rx pkts_tx type drops ckts TCP uptime FST 160.10.1.1 CONNECT 83387 83388 conf 0 - - 4w0d Expected: 0 Next Send: 0 Seq errors: 0 Total number of connected peers: 1 Total number of connections: 1 R3#show dlsw capabilities ! The output shows all parameters that are being used on this DLSW connection. DLSw: Capabilities for peer 160.10.1.1(0) vendor id (OUI) : '00C' (cisco) version number : 2 release number : 0 init pacing window : 20 unsupported saps : none num of tcp sessions : 1 loop prevent support : no icanreach mac-exclusive : no icanreach netbios-excl. : no reachable mac addresses : none reachable netbios names : none V2 multicast capable : yes DLSw multicast address : none cisco version number : 1 peer group number : 0 peer cluster support : no border peer capable : no peer cost : 3 biu-segment configured : no UDP Unicast support : yes Fast-switched HPR supp. : no NetBIOS Namecache length : 15 local-ack configured : yes priority configured : no cisco RSVP support : no configured ip address : 160.10.1.1 peer type : conf version string : Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-JK8O3S-M), Version 12.2(16), RELEASE SOFTWARE (fc3) Copyright 1986-2003 by cisco Systems, Inc. Compiled Fri 07-Mar-03 01:45 by pwade R3# R3#debug dlsw peers ! This "debug" shows the establishment of the DLSW connection. ! Notice the messages that are being exchanged. DLSw peer debugging is on R3# 4w0d: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:DLX-KEEPALIVE REQ state:CONNECT 4w0d: DLSw: dfstp_action_g() keepalive request from peer 160.10.1.1(0) 4w0d: DLSw: Keepalive Response sent to peer 160.10.1.1(0)) 4w0d: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:CONNECT->CONNECT 4w0d: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:DLX-KEEPALIVE REQ state:CONNECT 4w0d: DLSw: dfstp_action_g() keepalive request from peer 160.10.1.1(0) 4w0d: DLSw: Keepalive Response sent to peer 160.10.1.1(0)) 4w0d: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:CONNECT->CONNEC ! Below observe below a example of a DLSW session disconnection. Observe the messages. 1d01h: DLSw: Unknown run-time CV 81 with length 5 from peer 160.10.1.1(0) 1d01h: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:CONNECT->CONNECT 1d01h: DLSw: Processing delayed event:ADMIN-CLOSE CONNECTION - prev state:CONNECT 1d01h: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:ADMIN-CLOSE CONNECTION state:CONNECT 1d01h: DLSw: dfstp_action_d() close connection for peer 160.10.1.1(0) 1d01h: DLSw: FST aborting connection for peer 160.10.1.1 1d01h: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:CONNECT->DISCONN R3# 1d01h: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:ADMIN-OPEN CONNECTION state:DISCONN 1d01h: DLSw: dfstp_action_a() attempting to connect peer 160.10.1.1(0) 1d01h: DLSw: Connection opened for peer 160.10.1.1(0) 1d01h: DLSw: CapExId Msg sent to peer 160.10.1.1(0) 1d01h: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:DISCONN->WAIT_CAP 1d01h: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP 1d01h: DLSw: dfstp_action_e() cap msg rcvd for peer 160.10.1.1(0) 1d01h: DLSw: Recv CapExId Msg from peer 160.10.1.1(0) 1d01h: DLSw: received fhpr capex from peer 160.10.1.1(0): support: false, fst-prio: false 1d01h: DLSw: Pos CapExResp sent to peer 160.10.1.1(0) 1d01h: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:WAIT_CAP->WAIT_CAP 0 1d01h: DLSw: START-FSTPFSM (peer 160.10.1.1(0)): event:TIMER-TIMER EXPIRED state:WAIT_CAP 1d01h: DLSw: dfstp_action_d() close connection for peer 160.10.1.1(0) 1d01h: DLSw: FST aborting connection for peer 160.10.1.1 1d01h: DLSw: END-FSTPFSM (peer 160.10.1.1(0)): state:WAIT_CAP->DISCONN undebug all |
CCIE Routing and Switching Practice Labs
ISBN: 1587051478
EAN: 2147483647
EAN: 2147483647
Year: 2006
Pages: 268
Pages: 268
Authors: Martin J. Duggan, Maurilio P. Gorito