Trouble Tickets

Complete the following Trouble Tickets in order. Use the tools from this and the previous chapters to analyze, test, and document as you go. Feel free to create your own physical layer problems if you need more practice there. Sample solutions are provided after this section.

Trouble Ticket 1

Set up each router so that when you ping a serial interface you are pinging the wire number.router number. Use numbers such as all 1s for r1, all 2s for r2, and so on. Display the router and interface configuration for all routers as I do for r1 in the solution. Ping a serial interface on another router to verify connectivity. Document within the configuration right before you ping the other router's serial interface.

Trouble Ticket 2

Change the frame type for network 516 to 802.2. Ping from r1 to the Novell server to verify connectivity. Issue an extended trace, too.

Trouble Ticket 3

Change the routing protocols so that you are using RIP on the Novell LAN and EIGRP for everything else with an AS number of 100. Configure the WAN links between r2 and r3 to load balance if possible. View the routing table and use debug to watch the routing and SAP updates. Save the data to a log file for later review. Make sure there are no filters or ACLs blocking anything.

Trouble Ticket 4

Use Sniffer to capture the Novell server startup. Ping it when it is up from r1.

Trouble Ticket 5

Use Sniffer to capture the hostb client startup on 802.2. Verify connectivity through all layers. Set the client set to the wrong frame type. What happens?

Trouble Ticket 6

Use tools such as CDP to assist you in updating your chapter scenario diagram. Label things such as device types, IOS versions, node addresses, wire addresses, cable specs, routed/routing protocols, and so on.