Soru

Zorluk: OrtaOSPFv2 Neighbor Adjacencies and Router ID

A network engineer is configuring OSPFv2 between two directly connected Cisco routers over a GigabitEthernet link. Upon inspecting the neighbor status, the engineer notes that the routers fail to form a neighbor relationship. Which TWO configuration mismatches between the interconnected interfaces will prevent these routers from establishing an OSPFv2 neighbor adjacency?

  1. Mismatched OSPF Hello and Dead timer interval settingsCevap
  2. Mismatched OSPF Area ID assignments on the interconnecting interfacesCevap
  3. C
    Mismatched OSPF Process IDs configured under global router OSPF configuration mode
  4. D
    Mismatched interface metric costs manually configured on the interconnecting link

Cevap

The two conditions preventing OSPFv2 neighbor adjacency formation are mismatched Hello/Dead timer intervals and mismatched OSPF Area IDs on the connected interfaces.
For OSPFv2 routers to establish a neighbor adjacency, specific fields exchanged inside the OSPF Hello packet must match. These include matching OSPF Area IDs and identical Hello and Dead timer intervals. If either of these parameters differs between the connected interfaces, Hello packets are dropped and the routers remain in a Down state.

Adım Adım Çözüm

1
Analyze OSPF Hello packet parameter matching requirements for neighbor adjacency.
Identify parameters exchanged in Hello packets that must strictly match: Area ID, Subnet Mask, Hello/Dead Timers, Authentication, and Stub Area Flag.
OSPF Hello packets validate neighbor compatibility before establishing an adjacency.
2
Evaluate local vs network-wide OSPF configuration parameters.
Confirm that Process IDs and interface metric costs are locally significant or used for path metric calculations rather than adjacency gating.
Process IDs distinguish local routing process instances, while interface costs affect metric accumulation downstream.

Anahtar Kavram

OSPFv2 Hello Packet Parameter Verification for Neighbor Adjacencies
Bu soruyu puanla