You will see a wrongly configured virtual-link command. R3(config-rtr)# no area 54 virtual-link 4.4.4.4 + Configure virtual link on R3 (from the second output above, we learned that the OSPF process ID of R3 is 1 and we have to disable the wrong configuration of “area 54 virtual-link 4.4.4.4”): (Notice that we have to use neighbor router-id 3.3.3.3, not R2’s router-id 2.2.2.2) + Configure virtual link on R2 (from the first output above, we learned that the OSPF process ID of R2 is 1):
Therefore, routers R2 and R3 must be configured with the area area-id virtual-link neighbor-router-id command. In this case, the area 11 will become the transit area. The area through which you configure the virtual link is known as a transit area.
In some cases, where this is not possible,we can use a virtual link to connect to the backbone through a non-backbone area. We knew that all areas in an Open Shortest Path First (OSPF) autonomous system must be physically connected to the backbone area (Area 0). The output of the “show running-config” command of R3: The output of the “show running-config” command of R2: Pay more attention to the outputs of routers R2 and R3
To troubleshoot the problem, first issue the show running-config on all of 4 routers. Special Note: To gain the maximum number of points you must remove all incorrect or unneeded configuration statements related to this issue. Your task is complete when R4’s loopback address (FEC0:4:4) can be seen in the routing table of R1. Identify and fix this fault, do not change the current area assignments. However, R4’s loopback address (FEC0:4:4) cannot be seen in R1. TUT is a small company that has an existing enterprise network that is running IPv6 OSPFv3.
0 kommentar(er)
