Trouble Ticket 3 OSPF Lab
Paste in the configuration changes from my tt3 troubled configs file to get started. In this Trouble Ticket, the routing protocol changes from Routing Information Protocol (RIP) to Open Shortest Path First (OSPF). Update your drawings accordingly. When you are certain everything is working (and it is not right now), display the OSPF configuration on the swan router and perform a trace to the goose router. Explain why goose takes the path it chooses. Save your corrected configurations to the TFTP server. All hosts should be able to ping and trace a device on the backbone.
The chesapeakebay backbone switch and the Frame Relay ferry router should both be operational. I would much prefer to have a Gigabit Ethernet or even a 100-Mbps backbone, but it is not necessary for you to go to that expense for lab purposes. In the practical environment, that is another issue. It is also not intended for you to configure ISDN in this ticket unless you want to. OSPF is running on all routers except the 804 on the backbone, in which the particular IOS doesn't support OSPF. Instead of upgrading the IOS, use default routes. All telnets to knappsnarrows are blocked, but ping, trace, and HTTP access should work in this scenario. Make sure you are able to ping all loopbacks, and then move on to the rest of the intended solution.
Trouble Ticket 3 OSPF Lab Solution
Many times fixing one thing can break another or lead you to another issue, which is why I referred to this as the intended solution. However, you must keep a methodical mindset and divide and conquer to find the real issues. Hopefully, the practical nature of this book thus far has helped shape you into someone who has the methodology, tools, and know-how to do some troubleshooting on your own. That is your task for the rest of the Trouble Tickets in this book. You should have already pasted in the troubled configurations from the tt3 troubled configs file, but if not, you can do that now. Review your documentation that you should have been updating throughout the chapter, peek at Figure 10-6 if you must, and fix any issues at this time. Document your findings.
NOTE
If you have problems pasting in the configurations, you may need to adjust the options such as the Line Send Delay in your terminal program.
Use the following notes to make sure you found and fixed all the issues I planned for the OSPF Trouble Ticket. (There may be others, too, but you'll need to find them as you go along.)
hosta issues:
Wrong subnet mask of 255.255.255.252. You may not have had this problem, but you can configure it to observe the results.
duck (r1) issues:
Multiple OSPF routing processes are not needed here. (You need to redistribute if you leave this unless you want completely separate routing processes.) OSPF 2 uses a subnet mask rather than a wildcard mask. Depending on your IOS version, the IOS may autocorrect this into a wildcard mask.
My intent was for you to remove the router OSPF 2 configuration, not redistribute.
Missing network 172.16.1.0 statement under OSPF 1, so you can't reach the two 64 kbps links between goose and swan.
heron (r2) issues:
Password recovery.
Clock on s0 and s1.
Loopback 10 administratively shut down.
No IP subnet zero.
OSPF configuration.
goose (r3) issues:
Speed on fa2/0.
Duplex on fa2/0.
The access list should block hosta and hostc from telnetting to knappsnarrows. However, ping and HTTP should still work.
There are only deny statements in the access list. Every ACL needs at least one permit statement.
The access list should be inbound on goose fa2/0.
osprey (r4) issues:
Incorrect hostname (egret rather than osprey).
OSPF was incorrectly configured for area 2. Just because the duck router has a route to the osprey router doesn't mean that osprey has a return trip back to duck.
crab (r5) issues:
The OSPF statement for interfaces 0.0.0.0 255.255.255.255 is set to area 0. It should be area 1, but this incorrect OSPF statement causes a nice virtual link reminder on the crab router.
swan (r6) issues:
There are individual OSPF statements for the interfaces, but there is an incorrect address on the last one.
chesapeakebay (s1) issues:
Ports incorrectly set to VLAN 10.
VTP mode was set to transparent with a VTP domain name of tt3.
kentnarrows (s2) issues:
Speed on fa0/12.
If you need assistance with testing and finding the issues, the file tt3 testing may help; I have annotated it in several places to help you understand some of the issues. The fun of all this is if you did not find all the issues in one Trouble Ticket, they may still be there waiting for you in the next one. On the other hand, if you are totally frustrated, you can paste in the necessary portions of the tt3 fixed configs file.
Next use Example 10-21 to answer the question about the swan-to-goose trace.
Example 10-21. swan-to-goose Trace
swan#trace goose Type escape sequence to abort. Tracing the route to goose (172.16.1.9) 1 duck (172.16.1.17) 4 msec 4 msec 4 msec 2 goose (172.16.1.9) 12 msec * 8 msec swan#show ip ospf interface Serial1 is up, line protocol is up Internet Address 172.16.1.18/29, Area 1 Process ID 1, Router ID 172.16.3.9, 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 Hello due in 00:00:03 Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 172.16.1.1 Suppress hello for 0 neighbor(s) Serial2 is up, line protocol is up Internet Address 172.16.1.26/29, Area 1 Process ID 1, Router ID 172.16.3.9, Network Type POINT_TO_POINT, Cost: 1562 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Hello due in 00:00:00 Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 172.16.1.41 Suppress hello for 0 neighbor(s) Serial3 is up, line protocol is up Internet Address 172.16.1.34/29, Area 1 Process ID 1, Router ID 172.16.3.9, Network Type POINT_TO_POINT, Cost: 1562 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Hello due in 00:00:03 Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 172.16.1.41 Suppress hello for 0 neighbor(s) swan#!!!compare the costs to the bandwidths |
Compare your final saved fixed configurations to the tt3 fixed configs file. Compare your updated drawing to Figure 10-6.
NOTE
On the practical side of things, you may consider breaking up OSPF area 1 into two separate areas. For example, looking at Figure 10-6, 172.16.1.0/24 could be left as it is in OSPF area 1 and 172.16.2.0/24 could easily be its own area 2.
Congratulations are most definitely in order for completing this Trouble Ticket. Move along to the next or save the challenge for another day.