CCNA OSPF Questions

Hello packets discover and maintain neighbor relationships; DBD packets contain a summary of the LSDB; LSR packets request specific LSAs; LSU packets send full LSAs in response to LSRs; LSAck packets acknowledge receipt of LSUs.

A virtual link connects a non-backbone area to Area 0 through a transit area. First, identify the ABR with the transit area, then configure the virtual link on both ABRs using the router ID of the neighbor, ensure the transit area has full OSPF adjacency, and finally verify the virtual link is operational.

The Dijkstra algorithm first initializes the candidate list with the root node, then iteratively moves the lowest-cost candidate to the tree, updating neighbor costs, and finally builds the routing table from the shortest-path tree.

This command injects a default route (0.0.0.0/0) into the OSPF domain unconditionally, even if the router does not have a default route in its routing table. The metric and type are set as specified.

OSPF uses different hello intervals depending on the network type. On broadcast and point-to-point networks (like Ethernet), the default hello interval is 10 seconds.

That the YANG path includes multiple leafs that change simultaneously, causing multiple updates for the same event. For example, when an OSPF neighbor goes from FULL to DOWN, multiple leafs (state, last-up-time, etc.) change, and each change triggers an on-change update. The other options are incorrect because the sample-interval is not used in on-change subscriptions; the collector is not causing duplicates; and the encoding does not cause duplicates.

Backbone area (0) connects all other areas; Stub area blocks Type 5 LSAs but allows Type 3; Totally stubby area blocks both Type 5 and Type 3 (default route only); NSSA allows Type 7 LSAs for external routes but blocks Type 5; NSSA totally stubby blocks Type 5 and Type 3 but allows Type 7.

The INIT state in OSPF indicates that a router has received a Hello packet from its neighbor but the neighbor has not yet seen its own Router ID in the received Hello. A mismatched Hello interval causes the routers to send Hellos at different rates, so one router may not receive a Hello within the expected Dead interval, preventing the neighbor from seeing its Router ID in the received Hello and thus stalling the adjacency in INIT.

OSPF authentication configuration requires two components: an area-level authentication type (configured via `area 0 authentication message-digest`) and an interface-level authentication mode (configured via `ip ospf authentication message-digest`). The interface command tells the OSPF process to actually use the key defined with `ip ospf message-digest-key`. Without it, the interface defaults to no authentication, even though the area is configured for authentication.

The default OSPF hello interval on an Ethernet (broadcast multi-access) link is 10 seconds, as defined in RFC 2328. This interval determines how often a router sends Hello packets to discover and maintain neighbor relationships. On non-broadcast multi-access (NBMA) networks, the default is 30 seconds.

The output shows R1 has a neighbor with state 2WAY/DROTHER (10.0.0.3), which indicates that R1 is also a DROTHER on this broadcast multiaccess segment. The FULL/DR neighbor (10.0.0.2) is the Designated Router, and since R1 is not the BDR (no FULL/BDR state), it must be a DROTHER.

Redistribution requires enabling redistribution, setting a seed metric (or using default-metric), optionally matching routes, and then verifying. The order ensures routes are properly injected.

Redistribution requires first configuring the routing process that will receive the routes, then defining the source protocol and metric, optionally setting route tags for loop prevention, applying a route map for filtering, and finally verifying the redistributed routes appear in the OSPF database.

OSPF requires the forwarding address (FA) in a Type 5 LSA to be reachable via an OSPF internal route (intra-area or inter-area) for the external route to be installed in the routing table. If the FA is not reachable, the router will ignore the LSA and not install the route, even though the LSA exists in the OSPF database and the neighbor adjacency is up.

On a broadcast multi-access network like Ethernet, OSPF defaults to a hello interval of 10 seconds. This is defined in RFC 2328 and is used to quickly detect neighbor failures while keeping control traffic overhead manageable. The corresponding dead interval is 40 seconds (4 times the hello interval).

The issue is that PE2 has the prefix in its BGP VPNv4 table with a valid next-hop, but the route is not reachable from CE2. This indicates a label-switching problem in the MPLS core. The next step is to verify that LDP has allocated a label for the BGP next-hop address on PE2, because without an LDP label for the next-hop, the MPLS forwarding path is broken and packets cannot be label-switched across the provider core.

OSPF neighbors transition through Down, Init, 2-Way, ExStart, Exchange, Loading, and Full states. The correct order begins with the router sending Hello packets (Down to Init), then receiving a Hello reply (Init to 2-Way), electing DR/BDR if needed (2-Way to ExStart), exchanging database description packets (ExStart to Exchange), and finally synchronizing databases (Loading to Full).

The DR (Designated Router) generates the Network LSA and manages LSDB synchronization on multiaccess networks. The BDR (Backup Designated Router) monitors the DR and takes over if the DR fails. DROTHERs form full adjacencies only with the DR and BDR, not with each other.

Broadcast network type elects DR/BDR and uses multicast 224.0.0.5/6; Non-broadcast (NBMA) also elects DR/BDR but uses unicast; Point-to-point does not elect DR/BDR; Point-to-multipoint does not elect DR/BDR and uses multicast; Loopback interface is always advertised as a /32 host route regardless of configured mask.

On broadcast multi-access networks like Ethernet, OSPF defaults to a hello interval of 10 seconds. This is defined in RFC 2328 and is used to quickly detect neighbor failures while keeping overhead low. The corresponding dead interval is 40 seconds (4 times the hello interval).

The 'ip ospf cost' command overrides the default cost calculation based on bandwidth. The network command matches both interfaces because they fall under 10.0.0.0/8.

The output shows an entry for 1.1.1.1 with the label 'ABR' (Area Border Router) and a route type of 'i' (intra-area). An ABR connects two or more OSPF areas, so Router 1.1.1.1 must be connecting Area 0 to another OSPF area. The metric [110/10] and next-hop 192.168.1.1 confirm it is reachable within Area 0.

The default OSPF hello interval on an Ethernet (broadcast multi-access) link is 10 seconds, as defined in RFC 2328. This interval determines how often a router sends Hello packets to discover and maintain neighbor relationships. The correct answer is A because Ethernet is a broadcast network type, which uses a 10-second hello interval by default.

OSPFv3 runs per interface and uses link-local addresses for neighbor discovery. The router-id is required and must be unique. Both interfaces are in area 0.

OSPFv3 neighbor formation follows the same state machine as OSPFv2: Down, Init, 2-Way, ExStart, Exchange, Loading, Full. The steps reflect the key actions at each state.

DR (Designated Router) generates Network LSAs and manages adjacencies on multi-access networks; BDR (Backup DR) takes over if the DR fails; DROTHER routers form full adjacencies only with DR and BDR; ASBR redistributes routes from other protocols; ABR connects multiple areas.

The Net Link States entry shows the link ID 192.168.1.2 (the DR's interface IP) and ADV Router 2.2.2.2, which indicates that router 2.2.2.2 is the Designated Router (DR) on the 192.168.1.0/24 segment. In OSPF, only the DR originates the Type 2 (Network LSA) for a broadcast segment, so the advertising router in the Net Link States is always the DR.

Summarization on an ABR uses the area range command to aggregate prefixes. The order is: identify prefixes, configure range, verify, and optionally suppress more specific routes.

OSPF network types control how adjacencies are formed and how LSAs are flooded. Broadcast and non-broadcast types require a DR/BDR election, while point-to-point and point-to-multipoint do not. The loopback interface defaults to loopback network type, not point-to-point.

LSA Type 1 (Router LSA) describes a router's own links; Type 2 (Network LSA) is generated by the DR; Type 3 (Summary LSA) advertises inter-area routes; Type 4 (ASBR Summary LSA) advertises the location of an ASBR; Type 5 (AS External LSA) advertises external routes.

Virtual links require area 0 transit area, and must be configured on both ABRs. The steps ensure proper connectivity: identify endpoints, configure on each router, and verify.