Trouble Tickets

Complete the following Trouble Tickets in order. They assume you have followed along with the Shooting Trouble with Ethernet chapter scenario thus far. Use the chapter scenario drawings and tools from the previous chapters to analyze, test, and document as you go. Do not expect all troubles to be limited to just Ethernet issues. Feel free to create your own Physical Layer or other problems if you need more practice in that area. Sample solutions are provided.

Trouble Ticket 1

A new administrator is at the r5 location performing some simple tests. She tells you she can't ping to the other side of the network over on r4. You have her issue a show arp command on her router and nothing displays. You are at the r1 location and you can't get to network 10.2.2.0 either, but in your earlier testing you know you were able to get to the other end of the network because you issued a ping from hosta to hostc. Example 5-25 displays the r1 routing table. Can you spot the issue(s)? Fix the problem(s). You may or may not have this particular issue in your lab right now, but you should help the new administrator troubleshoot the problem.

Example 5-25. Trouble Ticket 1 IP Testing

r5>ping 10.2.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.2.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
r5>show arp
							r5>!!nothing is here
r1>show ip route
     192.168.5.0/24 is variably subnetted, 7 subnets, 2 masks
D       192.168.5.96/28 [90/2172416] via 192.168.5.82, 01:12:02, Serial1
D       192.168.5.64/28 [90/40537600] via 192.168.5.34, 01:12:03, Ethernet1
C       192.168.5.80/28 is directly connected, Serial1
C       192.168.5.32/28 is directly connected, Ethernet1
D       192.168.5.48/28 [90/40537600] via 192.168.5.34, 01:12:03, Ethernet1
D       192.168.5.0/24 is a summary, 01:12:08, Null0
C       192.168.5.16/28 is directly connected, Ethernet0
     10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
D       10.0.0.0/8 is a summary, 01:12:03, Null0
C       10.1.1.0/24 is directly connected, Serial0
r1#end
						

Trouble Ticket 2

You completed Trouble Ticket 1 as far as IP is concerned, but what about IPX? IPX should be running only on the LAN that hosta is on, including the server, hosts, and router interface. Note and fix any issues. The Novell server display networks command shows 516 0/1 and 346648E2 0/1, and the router display is in Example 5-26. You may or may not have this particular issue in your lab right now, but you should troubleshoot the problem as it exists here.

Example 5-26. Trouble Ticket 2 IPX Testing

r1#show ipx interface brief
Interface            IPX Network Encapsulation Status                 IPX State
Ethernet0            516         NOVELL-ETHER  up                     [up]
Ethernet1            unassigned  not config'd  up                     n/a
Serial0              unassigned  not config'd  up                     n/a
Serial1              unassigned  not config'd  up                     n/a
r1#show ipx interface ethernet 0
Ethernet0 is up, line protocol is up
  IPX address is 516.0000.0c8d.6705, NOVELL-ETHER [up]
  Delay of this IPX network, in ticks is 1 throughput 0 link delay 0
...
r1#show ipx route
1 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.
No default route known.
C        516 (NOVELL-ETHER),  Et0
r1#end
						

Trouble Ticket 3

Change the frame type for network 516 to Ethernet II only. Ping from r1 to the Novell server to verify connectivity.

Trouble Ticket 4

Configure the MAC address of r1e0 to be identical to hostb's MAC address. What happens? Turn on debug arp. Ping the r1e0 interface from the hostb command prompt. What happens? Ping hostb from r1. Fix the duplicate MAC issue. Although not shown in the answer output, it might be a good time to check your other hosts on the same Ethernet segment to verify that you gave them IP addresses. Clean up the clients so that they are running TCP/IP and the Microsoft Client. Put the Novell server to rest for the remainder of the labs.

Trouble Ticket 5

What is the effect of duplicate IP addresses? Change hosta to the same address as r1e0. Observe the results and change the address after the fact.

Trouble Ticket 6

It is helpful to be aware of housekeeping-type traffic on your network so that you can easily spot issues. Log all activity to a file (such as I do with SecureCRT for the answer). Debug CDP events and analyze the packet capturing. Optionally, turn on debugs for EIGRP, too. Use Sniffer to capture the activity for about 3 or 4 minutes to a file and save the file as chapter 5 background traffic sniffer capture.

Trouble Ticket 7

Clear the interface counters for r1e0. Turn on debug arp. Start a continuous ping from hosta to hostb using ping -t. Make sure you can see both your command-prompt window and your connection to r1 on your screen at the same time. Disconnect the cable from the Ethernet dongle on hosta. Show the interface a couple of times while you wait about 20 seconds. Plug the cable back in and observe the results. Ctrl+C stops the continuous ping. Log all activity to a file using a terminal-emulation application such as HyperTerm or SecureCRT.

Trouble Ticket 8

Configure all routers to send their syslog output to hosta, and set up hosta as a syslog server. To test this out, you can download the 3CDaemon product for free from support.3com.com/infodeli/swlib/utilities_for_windows_32_bit.htm. What is the default speed and duplex setting for r3's fast Ethernet interface? Clear the interface statistics for r3fa2/0. Turn on debug arp. Start a continuous ping from hostc to hostb using ping -t. Disconnect the cable from the Ethernet dongle on hostc. Show the interface a couple of times while you wait about 20 seconds. Plug the cable back in and observe the results. Ctrl+C stops the continuous ping.