The answers provided in this section are not necessarily the only possible answers to the questions. The questions are designed to test your knowledge and to give practical exercise in certain key areas. This section is intended to test and exercise skills and concepts detailed in the body of this chapter.
If your answer is different, ask yourself whether it follows the tenets explained in the answers provided. Your answer is correct not if it matches the solution provided in the book, but rather if it has included the principles of design laid out in the chapter.
In this way, the testing provided in these scenarios is deeper: It examines not only your knowledge, but also your understanding and ability to apply that knowledge to problems.
If you do not get the correct answer, refer back to the text and review the subject tested . Be certain to also review your notes on the question to ensure that you understand the principles of the subject.
Scenario 9-1 Answers
| Q1: || |
Refer to Figure 9-9 and design the addressing scheme for the network. Then write the configuration for the central router.
Figure 9-9. The Diagram for Configuration Scenario 9-1
Ensure that you include the following:
Address the network using the private network 10.0.0.0. Design the addressing scheme so that it allows for the summarization of addresses between areas. Show the summarization that you allocate, and explain your reasons for your choices.
Area 0 is using a prefix of 28 bits within the area.
Area 2 is using a prefix of 22 bits within the area.
Area 3 is using a prefix of 24 bits within the area.
Area 4 is using a prefix of 30 bits for the serial connections. It is using a 28-bit prefix for the connections to the Ethernet routers. Do not include the subnets attached to the LANs in Area 4.
Issue the commands for the main router in Figure 9-9 to configure the following:
- The router ID
- The network commands to place the appropriate interfaces into the correct areas
- The configuration of the totally stubby area (Area 3)
- The configuration of the stub (Area 4)
- Summarization between areas
- The election of the central router as designated router, where appropriate
| A1: || |
Table 9-8 shows a possible addressing scheme using the criteria stated in Scenario 9-1. Taking the private address 10.0.0.0, there is a great deal of flexibility in the addressing scheme that can be devised. Remember, however, that careful filtering is required if the organization is to connect to the Internet.
The addressing scheme proposed here is broken out by area. It is not exhaustive in terms of designing an addressing policy down to the LAN level, as was shown in Chapter 3; instead, it deals with the principles of addressing and summarization.
Note in the allocation of addresses that this scenario deals with the allocation of subnets. The addresses displayed in this table are the address ranges of the available subnets, given the prefix length.
Table 9-8. Allocation of Addresses for Scenario 9-1
0.0.0.16 to 10.0.255.224
The use of the 0s in the second octet is an easy reminder that you are in Area 0. Because Area 0 is a transit area, it will be small. The addressing within the area would be allocated the prefix of 28 bits, allowing the range of subnets shown. The number of hosts on each of these subnets would be 15.
10.2.0.0 to 10.2.252.0
Again, the private addressing of 10.0.0.0 as a Class A address is so large that full use can be made of the documentation advantages of the addressing scheme. The second octet allows Area 2 to be identified. The prefix of 22 bits is used within the area. This allows 1022 hosts on each network, which is good for further VLSM and VLANs in switched environments.
10.3.0.0 to 10.3.255.0
The second octet identifies the area. Within the area, a 24-bit prefix is used to address the LANs.
. . .
10.4.0.16 to 10.4.255.240
10.4.100.0 to 10.4.100.250
The second octet identifies the area. Within the area, a 30-bit mask is used to identify the serial links on which only two addresses are needed. The subnet 10.4.100.0 was chosen as the subnet to sub-subnet for the serial links simply to ease troubleshooting; all serial links in the company in any area would be assigned the third octet of 100. A 28-bit mask was chosen for the Ethernet connections to allow the creation of many subnets.
Example 9-15 demonstrates a sample configuration for Scenario 9-1. The configuration file is for the central router.
Example 9-15. Sample Configuration of Scenario 9-1
Router(config)# router ospf 100 ! Network Commands Router(config-router)# network 10.0.0.0 0.0.255.255 area 0 Router(config-router)# network 10.2.0.0 0.0.255.255 area 2 Router(config-router)# network 10.3.0.0 0.0.255.255 area 3 Router(config-router)# network 10.4.0.0 0.0.255.255 area 4 ! Totally Stubby Area Router(config-router)# area 3 stub no-summary ! Stub Area Router(config-router)# area 4 stub ! Summarization between areas Router(config-router)# area 0 range 10.0.0.0 255.255.0.0 Router(config-router)# area 2 range 10.2.0.0 255.255.0.0 Router(config-router)# area 3 range 10.3.0.0 255.255.0.0 Router(config-router)# area 4 range 10.4.0.0 255.255.0.0 Router(config)# interface e0 Router(config-if)# ip address 10.4.0.33 255.255.255.240 Router(config)# interface e1 Router(config-if)# ip address 10.4.0.17 255.255.255.240 Router(config)# interface e2 Router(config-if)# ip address 10.2.4.1 255.255.252.0 !Election of Designated Router Router(config-if)# ip ospf priority 64 Router(config)# interface e3 Router(config-if)# ip address 10.0.0.193 255.255.255.240 !Ensures Router not elected as Designated Router Router(config-if)# ip ospf priority 0 Router(config)# interface e4 Router(config-if)# ip address 10.0.0.129 255.255.255.240 !Ensures Router not elected as Designated Router Router(config-if)# ip ospf priority 0 Router(config)# interface e5 Router(config-if)# ip address 10.3.3.1 255.255.255.0 Router(config)# interface e6 Router(config-if)# ip address 10.3.2.1 255.255.255.0 Router(config)# interface e7 Router(config-if)# ip address 10.3.1.1 255.255.255.0 Router(config)# interface s0 Router(config-if)# ip address 10.4.0.9 255.255.255.252 Router(config)# interface s1 Router(config-if)# ip address 10.4.0.5 255.255.255.252 !Router ID set by configuring the Router ID with the loopback command Router(config)# interface loopback 0 Router(config-if)# ip address 10.100.100.101 255.255.255.255
Scenario 9-2 Answers
| 1: || |
There are problems with Router B. There is inconsistency in the routing table, and the system is extremely slow. What commands would be used to identify the problem? In examining the diagram and configuration, what problems can you see?
| A1: || |
Router B has been configured to be the designated router for the LAN, which means that it is dealing with all the traffic on the LAN associated with the management of OSPF. Given that the system is a 2500, it is a poor choice for a designated router. A better choice would be Router A, which is a larger system that connects directly to Area 0, making it a better choice from the standpoint of the network design. If Router B were a larger system than a 2500, there could be an argument for making it the designated router to elevate Router A, which would otherwise be functioning as the ABR as well as the designated router.
The router has not been configured as a stub, so the communication between Router A and Router B will be confused , preventing any communication between the two routers.
| 2: || |
Router A is having problems connecting to Area 0, which is causing problems in other areas because this router is used to connect to Area 0. What commands would be used to identify the problem? In examining the diagram and configuration, what problems can you see?
| A2: || |
Router A is configured incorrectly. The command that would show the problem would be either show ip route, show ip protocols , or show ip ospf database . The lack of LSA traffic would indicate a configuration problem. When examining the configuration, you would see that the mask on the configuration of the network command for Area 0 is wrong. The mask for 220.127.116.11 should be 0.0.0.15. Using the mask of 0.0.0.0 will place only interfaces with the IP address 18.104.22.168, which is a subnet address not an interface address. Therefore, there will be no communication of OSPF LSAs between the areas.
| 3: || |
Issue the commands that would be used to correct the configuration problems that you see in the example configuration for Routers A and B.
| A3: || |
The commands that would solve these problems are as follows:
On Router A:
router ospf 100 network 22.214.171.124 0.0.0.15 area 0 interface fastethernet 1 no ip ospf cost 10 ip ospf priority 100
On Router B:
router ospf 200 network 126.96.36.199 0.0.0.15 area 2 area 2 stub interface FastEthernet0 no ip ospf priority 100
| 4: || |
When you issue the show ip ospf interface command, you notice that there is a discrepancy in the timers on the link between Routers A and B. The transmit timer on Router A is set to 5, and the retransmit timer is set to 1. What problems would this cause? What command would be used to change the timers, and what are the default settings?
| A4: || |
The default setting for the transmit timer is set to 1 second, and the retransmit timer is set to 5 seconds. The transmit timer determines the estimated number of seconds that it takes to send a LSA to a neighbor. The retransmit timer states the number of seconds to wait for an acknowledgment before retransmitting an LSA.
If the transmit timer is not smaller than the retransmit timer, the interface retransmits in the belief that the other side did not receive the LSA. This leads to excess traffic, confusion in the topology database, and the possibility of flapping links. To correct the settings, issue the following subinterface commands:
ip ospf retransmit-interval seconds ip ospf transmit-delay seconds
| 5: || |
There is an ISDN link into the Internet from Router B. The network manager has suggested that this link is the cause of some performance problems on the router. You have noticed that the interface is included in the OSPF network command. What might be the cause of the problem, and how could it be fixed?
| A5: || |
If the ISDN interface is configured for dial-on-demand routing (DDR) and is also included in OSPF network commands, you might find that the link that the DDR process establishes will cause the routing updates to be propagated throughout the network. This causes additional CPU utilization on the routers and flooding of packets throughout the network. The solution is to ensure that the interface is not included in the network command to the OSPF process. A more important problem is that Router B is in a stub area and will not track external routes. Router B cannot connect to the Internet as an ASBR because it will not propagate the Type 5 LSAs. The BRI interface cannot partake in the OSPF network. Therefore, the network will not be slow; it will be down.
Scenario 9-3 Answers
| 1: || |
Explain the purpose of the virtual link in Figure 9-11.
Figure 9-11. Network Diagram 1 for Scenario 9-3
| A1: || |
In this example, Area 1 does not have a direct physical connection into Area 0. A virtual link must be configured between Router A and Router B. Area 2 is to be used as a transit area, and Router B is the entry point into Area 0. This way, Router A and Area 1 will have a logical connection to the backbone.
| 2: || |
Is the configuration of the OSPF network shown in Figure 9-12 a valid configuration?
Figure 9-12. Network Diagram 2 for Scenario 9-3
| A2: || |
Yes, the configuration is valid.
| 3: || |
Why would a company implement the design shown in Figure 9-12?
| A3: || |
OSPF allows for linking discontinuous parts of the backbone using a virtual link. In some cases, different Area 0s need to be linked together. This can occur, for example, if a company is trying to merge two separate OSPF networks into one network with a common Area 0. In other instances, virtual links are added for redundancy in case some router failure causes the backbone to be split in two. Whatever the reason may be, a virtual link can be configured between separate ABRs that touch Area 0 from each side and that have a common area between them.