1: | The following output was captured during Trouble Ticket 6. Why is fa0/9 in a blocking state?kentnarrows#show spanning-tree vlan 1 Spanning tree 1 is executing the IEEE compatible Spanning Tree protocol Bridge Identifier has priority 32768, address 00d0.7968.8484 Configured hello time 2, max age 20, forward delay 15 Current root has priority 32768, address 0090.922a.7680 Root port is 24, cost of root path is 19 Topology change flag not set, detected flag not set, changes 1 Times: hold 1, topology change 35, notification 2 hello 2, max age 20, forward delay 15 Timers: hello 0, topology change 0, notification 0 Interface Fa0/1 (port 13) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 13, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/2 (port 14) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 14, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/3 (port 15) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 15, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/4 (port 16) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 16, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/5 (port 17) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 17, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/7 (port 19) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 19, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/8 (port 20) in Spanning tree 1 is down Port path cost 100, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 20, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 0, received 0 Interface Fa0/9 (port 22) in Spanning tree 1 is BLOCKING Port path cost 19, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 0090.922a.7680 Designated port is 27, path cost 0 Timers: message age 3, forward delay 0, hold 0 BPDU: sent 11, received 333 Interface Fa0/11 (port 24) in Spanning tree 1 is FORWARDING Port path cost 19, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 0090.922a.7680 Designated port is 26, path cost 0 Timers: message age 2, forward delay 0, hold 0 BPDU: sent 3, received 346 Interface Fa0/12 (port 25) in Spanning tree 1 is FORWARDING Port path cost 19, Port priority 128 Designated root has priority 32768, address 0090.922a.7680 Designated bridge has priority 32768, address 00d0.7968.8484 Designated port is 25, path cost 19 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 345, received 0 |
A1: | Answer: fa0/9 (port 22) is in a blocking state because there are redundant Layer 2 links. Look at Figure 10-9 to see the two additional cables added to build in this redundancy. When there is a topology change, this port may no longer be blocked. |
2: | Using the same data in the preceding question, why are fa0/6 and fa0/10 missing? |
A2: | Answer: Fa0/6 and fa0/10 are missing because they are not in VLAN1. They are in VLAN3 and VLAN2, respectively. |
3: | While troubleshooting Trouble Ticket 6, I unplugged the dongle attached to the network interface card (NIC) to see which port the host was connected to. According to the following output and Figure 10-9, which host did I perform this on?kentnarrows(config)# .Mar 1 03:47:25.507: %LINK-3-UPDOWN: Interface FastEthernet0/10, changed state to down .Mar 1 03:47:25.735: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/10, changed state to down .Mar 1 03:47:43.858: %LINK-3-UPDOWN: Interface FastEthernet0/10, changed state to up .Mar 1 03:47:44.773: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/10, changed state to up |
A3: | Answer: While troubleshooting Trouble Ticket 6, I unplugged the dongle attached to the hosta NIC to see which port it was connected to. I had configured the VLAN1 interface on kentnarrows with a duplicate IP of its gateway. The results were quite interesting; goose could get to hosta, but kentnarrows could not. I found the issue when I tried to copy the configurations to the TFTP server when things were supposedly fixed. |
4: | Refer to the following output. Are there any potential issues?chesapeakebay> (enable)show port status
Port Name Status Vlan Level Duplex Speed Type
----- ------------------ ---------- ---------- ------ ------ ----- ------------
1/1 notconnect 1 normal half 100 100BaseTX
1/2 notconnect 1 normal half 100 100BaseTX
2/1 disabled 1 normal auto auto 10/100BaseTX
2/2 disabled 1 normal auto auto 10/100BaseTX
2/3 disabled 1 normal auto auto 10/100BaseTX
2/4 disabled 1 normal auto auto 10/100BaseTX
2/5 disabled 1 normal auto auto 10/100BaseTX
2/6 disabled 1 normal auto auto 10/100BaseTX
2/7 disabled 1 normal auto auto 10/100BaseTX
2/8 disabled 1 normal auto auto 10/100BaseTX
2/9 disabled 1 normal auto auto 10/100BaseTX
2/10 to hub disabled 1 normal auto auto 10/100BaseTX
2/11 to heron disabled 1 normal auto auto 10/100BaseTX
2/12 to duck disabled 1 normal auto auto 10/100BaseTX
|
A4: | Answer: The output displays the show port status command on the 2900 CatOS box. The ports are all disabled as it appears, but nothing happens if you enable the ports. The real issue is that the ports are on module 2. If you were to issue a show modules, you would see that module 2 is disabled. To fix the issue, you can type set module 2 enable on the chesapeakebay CatOS switch. |
5: | What is likely to be the issue with the following output that was captured during Trouble Ticket 4?goose#trace hostc Tracing the route to hostc (172.16.1.43) 1 hostc (172.16.1.43) 0 msec *Mar 1 00:10:20.670: IP: s=172.16.1.43 (local), d=172.16.1.43 (FastEthernet2/0), len 28, sending *Mar 1 00:10:20.670: IP: s=172.16.1.43 (FastEthernet2/0), d=172.16.1.43, len 28, rcvd 0 *Mar 1 00:10:20.670: IP: s=172.16.1.43 (local), d=172.16.1.43 (FastEthernet2/0), len 56, sending *Mar 1 00:10:20.670: IP: s=172.16.1.43 (FastEthernet2/0), d=172.16.1.43 (FastEthernet2/0), len 56, rcvd 3 *Mar 1 00:10:20.670: IP: s=172.16.1.43 (local), d=172.16.1.43 (FastEthernet2/0), len 28, sending *Mar 1 00:10:20.674: IP: s=172.16.1.43 (FastEthernet2/0), d=172.16.1.43, len 28, rcvd 0 * 0 msec |
A5: | Answer: The output shows the source and the destination address to be one and the same. I suspect there was a duplicate IP issue. |
6: | Often trace is very much a complementary tool to ping. What is likely to be the issue with the following output that was captured during Trouble Ticket 4?swan#trace kentnarrows Tracing the route to kentnarrows (172.16.1.45) 1 duck (172.16.1.17) 4 msec 4 msec 4 msec 2 heron (10.10.10.2) 16 msec 12 msec 16 msec 3 crab (172.16.2.10) 16 msec 16 msec 16 msec 4 swan (172.16.3.9) 12 msec 12 msec 12 msec 5 duck (172.16.1.17) 8 msec 12 msec 12 msec 6 heron (10.10.10.2) 20 msec 20 msec 20 msec 7 crab (172.16.2.10) 20 msec 20 msec 20 msec 8 swan (172.16.3.9) 16 msec 16 msec 20 msec 9 duck (172.16.1.17) 16 msec 20 msec 16 msec 10 heron (10.10.10.2) 24 msec 24 msec 28 msec 11 crab (172.16.2.10) 28 msec 28 msec 28 msec 12 swan (172.16.3.9) 24 msec 24 msec 24 msec 13 duck (172.16.1.17) 24 msec 24 msec 20 msec 14 heron (10.10.10.2) 32 msec 32 msec 32 msec 15 crab (172.16.2.10) 32 msec 32 msec 32 msec 16 swan (172.16.3.9) 28 msec 28 msec 28 msec |
A6: | Answer: When trace continues to list the same routers over and over, you can bet there is a loop somewhere. This particular issue dealt with the mutual redistribution and lack of filtering. Distribute lists, passive interfaces, and route maps are helpful to eliminate these types of issues. |
7: | Analyze the following issue that occurred during Trouble Ticket 4.osprey#show arp Protocol Address Age (min) Hardware Addr Type Interface Internet 172.16.2.45 202 0090.922a.7680 ARPA Ethernet0/0 Internet 172.16.2.42 0 Incomplete ARPA Internet 172.16.2.41 - 0080.c7aa.c887 ARPA Ethernet0/0 |
A7: | Answer: When the osprey router looked for 172.16.2.42, it did not find it. The MAC address for 172.16.2.41, which was osprey e0/0 at the time, was manually configured with the MAC address of hostb. |
8: | The swan (2520) and crab (2516) routers both have ISDN BRI ports. Are they S/T or U? |
A8: | Answer: The swan (2520) and crab (2516) routers both have ISDN S/T BRI ports. They both connect into an NT1. When an external NT1 is used, the router ports are S/T, which connect to the NT1, which connects via the U ports to an ISDN switch. Alternatively in my scenario, the 804 could have been used for ISDN. It has U port and would plug directly into the ISDN switch. |
9: | What tool enables you to send traps to a network management system? |
A9: | Answer: SNMP enables you to send traps to a network management system. You can configure communities, enable traps, and identify the SNMP server via IP address. |
10: | What steps does Cisco recommend in supporting your internetwork? |
A10: | Answer: Cisco recommends the following methodology for troubleshooting internetworks:
|
3.142.197.11