Before changing the Huawei network configuration, an engineer investigates: A new OSPF peer forms a neighbor relationship but never synchronizes its database because LSA retransmissions are dropped. Which diagnostic check should be performed first?
Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Repair reliable OSPF LSA request and update exchange before depending on the new peer for routing. Successful verification is: Both routers report Full and their relevant area LSDBs are synchronized.
Inspect Level-2 LSDBs, adjacency levels, attached bits and inter-area route tables. This check would diagnose IS-IS level-2 backbone continuity, but would not first isolate the described OSPF LSDB synchronization failure. Begin with: Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss.
Check area stub configuration on all routers, Type 3 default and any local ASBR attempts. This check would diagnose OSPF stub area external LSA constraint, but would not first isolate the described OSPF LSDB synchronization failure. Begin with: Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss.
Compare interface MTU, DD packet MTU fields, and OSPF neighbor transition logs. This check would diagnose OSPF MTU stalls ExStart, but would not first isolate the described OSPF LSDB synchronization failure. Begin with: Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss.
A Huawei Datacom engineer is investigating the following situation: Two area-0 paths reach a data-center prefix but the slower circuit has a lower OSPF cost and attracts traffic unexpectedly. Which corrective action best resolves the specified issue?
Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Technical basis: OSPF SPF computes paths from the link-state topology using accumulated interface costs. The measurable acceptance criterion is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Repair the allowed IS-IS database synchronization exchanges and check CSNP/PSNP and LSP sequence handling. This is a legitimate response to the different issue of IS-IS CSNP and PSNP database sync, but it does not correct the specific OSPF SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
Apply suitable ASBR external summarization for the verified imported prefix range. This is a legitimate response to the different issue of OSPF external summarization at ASBR, but it does not correct the specific OSPF SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
Choose an approved external metric type and metric policy to reflect the required exit selection. This is a legitimate response to the different issue of OSPF E1 versus E2 external metric, but it does not correct the specific OSPF SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
A team is validating a Huawei network repair: Two area-0 paths reach a data-center prefix but the slower circuit has a lower OSPF cost and attracts traffic unexpectedly. Which observable result provides the clearest evidence of success?
The shortest-path calculation selects the intended cost path and the backup remains viable. This result directly tests whether the correct action worked: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. This is explained by: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
DR and BDR maintain required Full adjacencies while DROther-to-DROther neighbors may remain 2-Way. That observation would support a separate case of Broadcast OSPF DR and BDR election, not verification of the reported OSPF SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Downstream areas learn the intended aggregate while required exceptions remain reachable. That observation would support a separate case of OSPF inter-area summarization placement, not verification of the reported OSPF SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Every prefix has a stable authoritative origin and route import does not recursively reappear. That observation would support a separate case of Redistribution route tag loop avoidance, not verification of the reported OSPF SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Consider the following Huawei Datacom deployment: Two area-0 paths reach a data-center prefix but the slower circuit has a lower OSPF cost and attracts traffic unexpectedly. Which technical principle best explains the observed behavior?
OSPF SPF computes paths from the link-state topology using accumulated interface costs. This mechanism explains the case-specific corrective step: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Confirm the mechanism by verifying: The shortest-path calculation selects the intended cost path and the backup remains viable.
OSPF LSAs and neighbor identities use router IDs that must uniquely identify routers in the routing domain. This explains OSPF duplicate router IDs, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
IS-IS Level-1 neighbor relationships require compatible area addressing while Level-2 uses broader backbone reachability. This explains IS-IS level-1 area adjacency, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
OSPF stub areas exclude Type 5 external LSAs and rely on an ABR-generated default for external destinations. This explains OSPF stub area external LSA constraint, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
A Huawei network is left in this condition: Two area-0 paths reach a data-center prefix but the slower circuit has a lower OSPF cost and attracts traffic unexpectedly. What direct operational or security risk is most relevant if it is not corrected?
Changing static-route priority will not fix unintended OSPF intra-area path cost. This is the direct exposure created by OSPF SPF path-cost comparison. Mitigate it through: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Then test: The shortest-path calculation selects the intended cost path and the backup remains viable.
Repeated import can advertise stale paths and blackhole services after topology changes. This consequence is associated more directly with Route import feedback loop. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
Removing all protocol authentication to restore routing exposes adjacencies to spoofed updates. This consequence is associated more directly with OSPF authentication-key mismatch. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
A healthy adjacency without a consistent LSDB may produce transient wrong paths. This consequence is associated more directly with IS-IS CSNP and PSNP database sync. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
Before changing the Huawei network configuration, an engineer investigates: Two area-0 paths reach a data-center prefix but the slower circuit has a lower OSPF cost and attracts traffic unexpectedly. Which diagnostic check should be performed first?
Compare interface cost values, SPF results, route cost and the selected next hop. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Successful verification is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Check attached bits in LSPs, candidate L1/L2 routes and default forwarding behavior. This check would diagnose IS-IS L1 default to nearest attached L1L2, but would not first isolate the described OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
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 OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
Compare external route type, advertised metric, internal ASBR reachability cost and route selection. This check would diagnose OSPF E1 versus E2 external metric, but would not first isolate the described OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
A Huawei Datacom engineer is investigating the following situation: An engineer increases physical bandwidth yet leaves configured OSPF interface costs that prefer the congested backup hop. Which corrective action best resolves the specified issue?
Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Technical basis: OSPF SPF computes paths from the link-state topology using accumulated interface costs. The measurable acceptance criterion is: The shortest-path calculation selects the intended cost path and the backup remains viable.
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 SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
Use the ABR-provided summary default in a totally stub area or restore a normal stub if detailed routes are required. This is a legitimate response to the different issue of OSPF totally stub area inter-area constraint, but it does not correct the specific OSPF SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
Use an ordered narrow ACL with the correct interface and traffic direction for the required filter. This is a legitimate response to the different issue of ACL packet filter rule order and direction, but it does not correct the specific OSPF SPF path-cost comparison condition reported. The relevant technical distinction is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
A team is validating a Huawei network repair: An engineer increases physical bandwidth yet leaves configured OSPF interface costs that prefer the congested backup hop. Which observable result provides the clearest evidence of success?
The shortest-path calculation selects the intended cost path and the backup remains viable. This result directly tests whether the correct action worked: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. This is explained by: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
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 SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Branch routers use the correct default/inter-area reachability without forbidden Type 5 LSAs inside the stub. That observation would support a separate case of OSPF stub area external LSA constraint, not verification of the reported OSPF SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
The chosen route matches the documented origin tie-break sequence and other path attributes. That observation would support a separate case of BGP origin attribute tie break, not verification of the reported OSPF SPF path-cost comparison. The relevant observable outcome here is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Consider the following Huawei Datacom deployment: An engineer increases physical bandwidth yet leaves configured OSPF interface costs that prefer the congested backup hop. Which technical principle best explains the observed behavior?
OSPF SPF computes paths from the link-state topology using accumulated interface costs. This mechanism explains the case-specific corrective step: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Confirm the mechanism by verifying: The shortest-path calculation selects the intended cost path and the backup remains viable.
IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix. This explains Longest-prefix and route preference, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
BGP AS_PATH loop detection prevents a route from circulating back through an AS already in its path. This explains BGP AS_PATH loop detection, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric. This explains OSPF E1 versus E2 external metric, but not why the issue in this scenario occurs. The specific mechanism is: OSPF SPF computes paths from the link-state topology using accumulated interface costs.
A Huawei network is left in this condition: An engineer increases physical bandwidth yet leaves configured OSPF interface costs that prefer the congested backup hop. What direct operational or security risk is most relevant if it is not corrected?
Changing static-route priority will not fix unintended OSPF intra-area path cost. This is the direct exposure created by OSPF SPF path-cost comparison. Mitigate it through: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Then test: The shortest-path calculation selects the intended cost path and the backup remains viable.
Misdiagnosing normal 2-Way state can lead to disruptive election and network-type changes. This consequence is associated more directly with Broadcast OSPF DR and BDR election. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
A WAN interface reporting link-up does not prove acceptable end-to-end application performance. This consequence is associated more directly with SD-WAN underlay and application steering. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
Changing MTU or route preference cannot repair an area mismatch and can delay recovery. This consequence is associated more directly with OSPF area-ID mismatch. For the stated conditions the immediate exposure is: Changing static-route priority will not fix unintended OSPF intra-area path cost.
Before changing the Huawei network configuration, an engineer investigates: An engineer increases physical bandwidth yet leaves configured OSPF interface costs that prefer the congested backup hop. Which diagnostic check should be performed first?
Compare interface cost values, SPF results, route cost and the selected next hop. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. Successful verification is: The shortest-path calculation selects the intended cost path and the backup remains viable.
Compare destination address, prefix lengths, active candidate routes and the FIB lookup. This check would diagnose Longest-prefix and route preference, but would not first isolate the described OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
Check VRRP preempt state and delay, recovered link stability and transition timestamps. This check would diagnose VRRP preemption maintenance behavior, but would not first isolate the described OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
Trace Type 7 advertisements, P-bit or translation selection and Type 5 LSAs outside the NSSA. This check would diagnose OSPF NSSA type-7 translation, but would not first isolate the described OSPF SPF path-cost comparison. Begin with: Compare interface cost values, SPF results, route cost and the selected next hop.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
