Inspect OSPF interface timers and received Hello packet fields on the link. This check would diagnose OSPF hello and dead timer mismatch, but would not first isolate the described Broadcast OSPF DR and BDR election. Begin with: Inspect OSPF interface network type, DR/BDR identity, priority and per-peer state.

Inspect the Huawei IP routing table, FIB entries, adjacency resolution and a test flow. This check would diagnose RIB-to-FIB forwarding discrepancy, but would not first isolate the described Broadcast OSPF DR and BDR election. Begin with: Inspect OSPF interface network type, DR/BDR identity, priority and per-peer state.

Compare address blocks, ABR area-range settings, Type 3 LSAs and specific-prefix reachability. This check would diagnose OSPF inter-area summarization placement, but would not first isolate the described Broadcast OSPF DR and BDR election. Begin with: Inspect OSPF interface network type, DR/BDR identity, priority and per-peer state.

Verify Type 7 origination in the NSSA and approved translation to Type 5 at an eligible ABR. This is a legitimate response to the different issue of OSPF NSSA type-7 translation, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Correct the IS-IS area identities or redesign the intended Level-2 boundary before forming the peer. This is a legitimate response to the different issue of IS-IS level-1 area adjacency, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Align OSPF Hello and Dead intervals on both ends with the approved link policy. This is a legitimate response to the different issue of OSPF hello and dead timer mismatch, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

The selected external next hop matches the documented cost calculation and changes predictably under failover. That observation would support a separate case of OSPF E1 versus E2 external metric, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

Eligible areas see the intended external aggregate and services within it retain correct reachability. That observation would support a separate case of OSPF external summarization at ASBR, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

A supported Level-1 adjacency forms only between appropriate same-area neighbors and routes appear correctly. That observation would support a separate case of IS-IS level-1 area adjacency, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

Uncontrolled mutual route import can form routing feedback loops and unstable route selection. This explains Route import feedback loop, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Inter-area OSPF route summarization occurs at ABRs when advertising reachability between areas. This explains OSPF inter-area summarization placement, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

OSPF Hello validation requires compatible area identifiers across a participating link. This explains OSPF area-ID mismatch, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths. This consequence is associated more directly with OSPF E1 versus E2 external metric. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Applying the policy at the wrong routing role leaves external LSAs unchanged. This consequence is associated more directly with OSPF external summarization at ASBR. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Isolated Level-1 areas cannot reach unrelated areas without a working Level-2 path. This consequence is associated more directly with IS-IS level-2 backbone continuity. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Inspect VRRP group priorities, owner role, master/backup status and election logs. This check would diagnose VRRP priority and intended master, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.

Compare received CSNP, PSNP and LSP records and inspect network filters for protocol frames. This check would diagnose IS-IS CSNP and PSNP database sync, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.

Compare interface cost values, SPF results, route cost and the selected next hop. This check would diagnose OSPF SPF path-cost comparison, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.

Align OSPF Hello and Dead intervals on both ends with the approved link policy. This is a legitimate response to the different issue of OSPF hello and dead timer mismatch, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Adopt a scalable hierarchical campus design with sensible access, distribution, core and segmentation boundaries. This is a legitimate response to the different issue of Enterprise campus layered design, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Place both ends of the adjacency in the intended common OSPF area and verify area design constraints. This is a legitimate response to the different issue of OSPF area-ID mismatch, but it does not correct the specific OSPF MTU stalls ExStart condition reported. The relevant technical distinction is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Every OSPF neighbor shows a unique router ID and LSDB advertisements have unambiguous originators. That observation would support a separate case of OSPF duplicate router IDs, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry. That observation would support a separate case of Longest-prefix and route preference, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

The other OSPF area receives an appropriate Type 3 LSA and reaches the approved destination. That observation would support a separate case of OSPF type-3 inter-area summaries, not verification of the reported OSPF MTU stalls ExStart. The relevant observable outcome here is: The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior.

Enterprise WLAN identity and network admission policies are separate from RF association and signal strength. This explains WLAN 802.1X authentication and NAC, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

OSPF requires successful database description, request and update exchange to complete adjacency. This explains OSPF LSDB synchronization failure, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

CSNP and PSNP exchanges help IS-IS identify and request missing or stale link-state packets. This explains IS-IS CSNP and PSNP database sync, but not why the issue in this scenario occurs. The specific mechanism is: OSPF database description negotiation can fail when peer interface MTU expectations do not match.

Incorrect DIS assumptions can cause inconsistent troubleshooting and churn in shared-segment LSPs. This consequence is associated more directly with IS-IS DIS and pseudonode on broadcast LAN. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Keeping all high-rate flows on a poor shared-tree path can waste core bandwidth. This consequence is associated more directly with PIM-SM RPT to SPT switchover. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Overbroad aggregates can blackhole unallocated addresses or conceal discontiguous subnets. This consequence is associated more directly with OSPF inter-area summarization placement. For the stated conditions the immediate exposure is: Resetting an otherwise correct OSPF process cannot solve a persistent interface MTU discrepancy.

Inspect pool membership, client VLAN assignment, DHCP lease utilization and authentication policy. This check would diagnose WLAN VLAN pool address distribution, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.

Compare OSPF authentication settings and discarded authentication-failure counters. This check would diagnose OSPF authentication-key mismatch, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.

Inspect import policy, level-specific LSP advertisements and the Level-1 route table. This check would diagnose IS-IS selective L2-to-L1 route leaking, but would not first isolate the described OSPF MTU stalls ExStart. Begin with: Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs.