300-410 OSPF Troubleshooting (v2/v3) — Timed 10 Questions

Question 1

A network engineer is troubleshooting an OSPFv2 adjacency issue between two directly connected routers, R1 and R2, both running IOS-XE. The link is a point-to-point Ethernet link. The engineer issues 'show ip ospf neighbor' on R1 and sees no neighbors. 'show ip ospf interface GigabitEthernet0/0' on R1 shows 'Network Type BROADCAST', but the link is actually a point-to-point link. Both routers have 'ip ospf 1 area 0' configured on the interface. What is the most likely cause of the adjacency not forming?

Accepted Answer

The routers have duplicate OSPF router IDs.. The default OSPF network type on Ethernet interfaces is BROADCAST, which requires a DR/BDR election and uses multicast 224.0.0.5 and 224.0.0.6. On a point-to-point link, if both routers do not agree on the network type, they may not form an adjacency because the hello packets are sent differently. However, since both are BROADCAST, they should form an adjacency. The real issue is likely a mismatch in OSPF network type if one side is manually set to POINT-TO-POINT, but here both are BROADCAST. A more common cause is that the interface is administratively down or there is a Layer 1 issue, but the stem indicates the interface is up. Another common cause is that the router IDs are not configured, leading to OSPF not starting. The most likely cause in this scenario is that the routers have duplicate router IDs, which prevents adjacency formation. The stem does not mention router IDs, so the best answer is that the engineer should check for duplicate router IDs.

Answer

The OSPF network type mismatch between the two routers (one is BROADCAST, the other is POINT-TO-POINT).

Answer

The interface is configured with 'ip ospf passive-interface'.

Answer

The OSPF process is not enabled globally; 'router ospf 1' is missing.

Question 2

A network engineer is troubleshooting OSPFv3 on a dual-stack network. Routers R1 and R2 are connected via a serial link. Both routers have OSPFv3 configured for IPv6. The engineer runs 'show ipv6 ospf neighbor' on R1 and sees R2 as FULL/DR. However, R1 cannot ping the IPv6 address of R2's loopback interface. 'show ipv6 route ospf' on R1 does not show any OSPF routes. What is the most likely cause?

Accepted Answer

The interface on R1 does not have an IPv6 address configured.. In OSPFv3, the network type on serial interfaces defaults to POINT-TO-POINT, but if the interface is configured as BROADCAST (e.g., using 'ipv6 ospf network broadcast'), a DR/BDR election occurs. However, the adjacency is FULL, so the issue is not adjacency. The lack of OSPF routes in the routing table suggests that the routes are not being installed. One common reason is that OSPFv3 requires an IPv6 address on the interface, but the router may have an IPv4-only configuration or the interface may not have an IPv6 address. Another possibility is that the OSPFv3 process is not redistributing connected routes. The most likely cause is that the interface does not have an IPv6 address configured, which is required for OSPFv3 to advertise prefixes.

Answer

The OSPFv3 process has 'no ipv6 unicast-routing' enabled globally.

Answer

The interface on R2 is configured as passive under OSPFv3.

Answer

The OSPFv3 process is configured with 'default-information originate always' but no default route exists.

Question 3

A network engineer is troubleshooting OSPFv2 route redistribution. R1 is an ASBR redistributing static routes into OSPF. R2, an internal router, receives the redistributed routes but they appear as O E2 routes. However, R1 also has a directly connected network 10.1.1.0/24 that is not being advertised as an OSPF route. 'show ip ospf database external' on R2 shows the redistributed static routes but not the connected network. What is the most likely cause?

Accepted Answer

The ASBR is missing the 'redistribute connected' command under the OSPF process.. By default, OSPF does not redistribute connected routes unless explicitly configured. The ASBR must use the 'redistribute connected' command under the OSPF process to advertise directly connected networks. The static routes are being redistributed because they are matched by the 'redistribute static' command, but the connected network is not part of the static route set unless it is also a static route. The engineer likely forgot to add 'redistribute connected' or use the 'subnets' keyword.

Answer

The connected network is not included in the redistribution because the engineer used 'redistribute static' without the 'subnets' keyword.

Answer

The connected network is not being advertised because it is not part of the OSPF process; the engineer must configure 'network 10.1.1.0 0.0.0.255 area 0' under router ospf.

Answer

The connected network is a loopback interface, and OSPF does not advertise loopback networks by default.

Question 4

A network engineer is troubleshooting an OSPFv2 adjacency issue between two routers across a Frame Relay network. R1 and R2 are connected via a point-to-point subinterface. The engineer configures 'ip ospf network point-to-point' on both subinterfaces. However, the adjacency does not form. 'show ip ospf interface' on R1 shows the interface is up and OSPF is enabled, but no neighbors are seen. What is the most likely cause?

Accepted Answer

The Frame Relay map is missing or the DLCI is not assigned to the subinterface.. On Frame Relay point-to-point subinterfaces, the OSPF network type should be point-to-point, but the adjacency may still fail if the Layer 2 mapping is incorrect. The subinterface must be mapped to the correct DLCI. If the 'frame-relay interface-dlci' command is missing or misconfigured, the router cannot send packets to the neighbor, even though OSPF is enabled. The engineer should verify the DLCI mapping.

Answer

The OSPF network type is set to broadcast, causing a DR/BDR election that fails on a point-to-point subinterface.

Answer

The subinterface is not configured with an IP address.

Answer

The OSPF hello and dead timers are mismatched between R1 and R2.

Question 5

A network engineer is troubleshooting an OSPFv3 issue where a router R1 is not learning routes from a neighbor R2. The adjacency is FULL, but 'show ipv6 route ospf' on R1 shows only a default route. R2 is an ASBR redistributing connected routes into OSPFv3. 'show ipv6 ospf database external' on R1 shows the external routes, but they are not installed in the routing table. What is the most likely cause?

Accepted Answer

The router R1 has a distribute-list in the OSPFv3 process that filters out the external routes.. In OSPFv3, external routes are not installed if the router has a route to the forwarding address that is not reachable. However, the more common cause is that the OSPFv3 process on R1 has 'no ipv6 unicast-routing' or the router is missing a default route to reach the external destinations. Another possibility is that the external routes have a metric that is too high or the route is suppressed by a filter. The most likely cause is that the router has a route map or distribute list that is filtering the external routes from being installed.

Answer

The external routes have a metric of 16777214, which is considered infinite.

Answer

The router R1 does not have IPv6 unicast routing enabled.

Answer

The external routes are type 5 LSAs but the router is in a totally stubby area.

Question 6

A network engineer is troubleshooting an OSPFv2 route flapping issue. The router R1 is learning a route to 192.168.1.0/24 via two different paths: one through R2 and one through R3. The route is flapping between the two paths every few seconds. 'show ip ospf interface' shows that both interfaces are stable. What is the most likely cause?

Accepted Answer

The routers R2 and R3 have the same OSPF router ID.. Route flapping can be caused by a number of issues, but if the interfaces are stable, the problem is likely due to a routing loop or a metric issue. One common cause is that the routers are using the same router ID, causing OSPF to see the same route from two different neighbors as equal-cost paths, but the route may be flapping due to a change in the metric. Another cause is that the link between R1 and R2 is flapping at Layer 1, but the stem says the interfaces are stable. The most likely cause is that the routers have duplicate router IDs, which can cause OSPF to treat the same route as two different routes and cause instability.

Answer

The route is being redistributed by both R2 and R3 with different metrics.

Answer

The OSPF network type on the interfaces is set to broadcast, causing DR/BDR instability.

Answer

The link between R1 and R2 has a high error rate causing intermittent packet loss.

Question 7

A network engineer is troubleshooting an OSPFv2 adjacency issue between two routers connected via a VLAN trunk. R1 and R2 are in different VLANs but are connected through a Layer 2 switch. The engineer has configured 'ip ospf 1 area 0' on the subinterfaces. The adjacency forms but is stuck in INIT state. What is the most likely cause?

Accepted Answer

The routers have the same OSPF router ID.. The INIT state indicates that the router has received a hello packet from the neighbor but the neighbor has not seen its own router ID in the hello packet. This is often due to a mismatch in the OSPF network type or a unicast communication issue. In a VLAN trunk scenario, if the subinterfaces are not in the same VLAN, the routers may not be able to communicate at Layer 2. However, the most common cause is that the routers are using the same router ID, which causes the hello packet to be ignored because the router sees its own router ID in the neighbor list.

Answer

The OSPF hello interval is mismatched between the two routers.

Answer

The subinterfaces are in different VLANs, preventing Layer 2 communication.

Answer

The OSPF network type is set to point-to-point on one side and broadcast on the other.

Question 8

A network engineer is troubleshooting an OSPFv2 issue where a router R1 is not receiving a specific route for 10.0.0.0/8 from a neighbor R2. The adjacency is FULL, and 'show ip ospf database' on R1 shows the LSA for 10.0.0.0/8 as a type 5 LSA. However, the route is not in the routing table. 'show ip route 10.0.0.0' shows no route. What is the most likely cause?

Accepted Answer

The router R1 has a distribute-list applied to the OSPF process that filters the route 10.0.0.0/8.. If the LSA is in the database, the route should be installed unless there is a filtering mechanism or a routing table issue. One common cause is that the router has a route map that filters the route from being installed. Another possibility is that the router has a static route that is being preferred, but the stem says no route is present. The most likely cause is that the router has a distribute-list that filters the route.

Answer

The route is a type 5 LSA, but the router is in a stub area.

Answer

The router has a higher administrative distance for OSPF routes, causing it to prefer another routing protocol.

Answer

The route has a metric of 16777214, which is considered infinite.

Question 9

A network engineer is troubleshooting an OSPFv3 adjacency issue between two routers over an IPv6-only link. The engineer configures OSPFv3 on both routers and sees that the adjacency is stuck in EXSTART state. 'debug ipv6 ospf packet' shows that the routers are exchanging DBD packets but not progressing. What is the most likely cause?

Accepted Answer

The OSPFv3 interface MTU is mismatched between the two routers.. The EXSTART state indicates that the routers are trying to establish the master/slave relationship and exchange DBD packets. If they are stuck, it is often due to a mismatch in the OSPF MTU or the interface MTU. If the MTU is mismatched, the DBD packets may be too large to be sent, causing the routers to keep retransmitting. Another cause could be a mismatch in the OSPF network type, but that usually causes issues earlier. The most likely cause is an MTU mismatch.

Answer

The routers have different OSPFv3 router IDs.

Answer

The OSPFv3 process is configured with 'ipv6 ospf 1 area 0' on the interface, but the interface is not IPv6-enabled.

Answer

The link is a point-to-point link, but the OSPF network type is set to broadcast.

Question 10

A network engineer runs the following command on Router R1:

R1# show ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
10.1.1.2         1   FULL/DROTHER    00:00:35    192.168.12.2    GigabitEthernet0/0
10.1.1.3         1   FULL/DR         00:00:32    192.168.13.3    GigabitEthernet0/1

Based on this output, which statement is correct?

Accepted Answer

Router R1 has a full adjacency with both neighbors and is in a stable state.. The output shows two OSPF neighbors. The neighbor with state FULL/DROTHER indicates it is not the DR or BDR on that segment. The neighbor with state FULL/DR is the designated router. The dead times are within normal range, indicating the adjacency is stable.

Answer

Router R1 is the DR on the segment connected to GigabitEthernet0/0.

Answer

Router R1 is experiencing a neighbor timeout on GigabitEthernet0/1.

Answer

Router R1 is not receiving hello packets from 10.1.1.2.