Before changing the Huawei network configuration, an engineer investigates: A new WAN segment is routed locally on an ASBR, yet OSPF clients lack the external service route despite healthy adjacencies. Which diagnostic check should be performed first?
Check ASBR import-route conditions, Type 5 LSAs and installed external routes. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Configure reviewed external route import on the intended ASBR and confirm Type 5 LSA propagation into eligible areas. Successful verification is: The partner prefix appears as an external route where allowed and test traffic reaches its next hop.
Review CSS roles, health of inter-chassis paths, redundancy alarms and test traffic during failover. This check would diagnose CSS chassis clustering and failover, but would not first isolate the described OSPF type-5 external advertisement. Begin with: Check ASBR import-route conditions, Type 5 LSAs and installed external routes.
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 type-5 external advertisement. Begin with: Check ASBR import-route conditions, Type 5 LSAs and installed external routes.
Compare interface-to-area bindings and Hello area fields on both peers. This check would diagnose OSPF area-ID mismatch, but would not first isolate the described OSPF type-5 external advertisement. Begin with: Check ASBR import-route conditions, Type 5 LSAs and installed external routes.
A Huawei Datacom engineer is investigating the following situation: Two entry points advertise the same external prefix as OSPF E2 and traffic prefers a remote ASBR even when its internal cost is high. Which corrective action best resolves the specified issue?
Choose an approved external metric type and metric policy to reflect the required exit selection. Technical basis: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric. The measurable acceptance criterion is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Tune approved OSPF link costs to represent the intended path preference and re-evaluate SPF. This is a legitimate response to the different issue of OSPF SPF path-cost comparison, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
Apply supported route-policy attributes only to the documented matched prefixes and validate next-hop resolution. This is a legitimate response to the different issue of Route-policy next-hop and preference application, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
Configure supported matching OSPF authentication mode and keys on both authorized neighbors. This is a legitimate response to the different issue of OSPF authentication-key mismatch, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
A team is validating a Huawei network repair: Two entry points advertise the same external prefix as OSPF E2 and traffic prefers a remote ASBR even when its internal cost is high. Which observable result provides the clearest evidence of success?
The selected external next hop matches the documented cost calculation and changes predictably under failover. This result directly tests whether the correct action worked: Choose an approved external metric type and metric policy to reflect the required exit selection. This is explained by: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
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 E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Every device interprets intended link costs and SPF selects the documented shortest paths. That observation would support a separate case of IS-IS metric-style consistency, not verification of the reported OSPF E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Neighbor state progresses to Full where adjacency is required and timers remain consistent under observation. That observation would support a separate case of OSPF hello and dead timer mismatch, not verification of the reported OSPF E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Consider the following Huawei Datacom deployment: Two entry points advertise the same external prefix as OSPF E2 and traffic prefers a remote ASBR even when its internal cost is high. Which technical principle best explains the observed behavior?
OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric. This mechanism explains the case-specific corrective step: Choose an approved external metric type and metric policy to reflect the required exit selection. Confirm the mechanism by verifying: The selected external next hop matches the documented cost calculation and changes predictably under failover.
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 E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
PIM-SM any-source multicast uses a rendezvous point to connect new sources and receivers. This explains PIM-SM rendezvous-point mismatch, but not why the issue in this scenario occurs. The specific mechanism is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
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 E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
A Huawei network is left in this condition: Two entry points advertise the same external prefix as OSPF E2 and traffic prefers a remote ASBR even when its internal cost is high. What direct operational or security risk is most relevant if it is not corrected?
Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths. This is the direct exposure created by OSPF E1 versus E2 external metric. Mitigate it through: Choose an approved external metric type and metric policy to reflect the required exit selection. Then test: The selected external next hop matches the documented cost calculation and changes predictably under failover.
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: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
Absent or misleading attached exits can strand a local area or direct it into an invalid path. This consequence is associated more directly with IS-IS L1 default to nearest attached L1L2. For the stated conditions the immediate exposure is: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
Assuming a Hello neighbor alone provides a complete topology can create inconsistent routing decisions. This consequence is associated more directly with OSPF LSDB synchronization failure. For the stated conditions the immediate exposure is: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
Before changing the Huawei network configuration, an engineer investigates: Two entry points advertise the same external prefix as OSPF E2 and traffic prefers a remote ASBR even when its internal cost is high. Which diagnostic check should be performed first?
Compare external route type, advertised metric, internal ASBR reachability cost and route selection. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Choose an approved external metric type and metric policy to reflect the required exit selection. Successful verification is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Inspect the ABR LSDB for Type 3 prefixes, area ranges and inter-area filter policy. This check would diagnose OSPF type-3 inter-area summaries, but would not first isolate the described OSPF E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
Inspect neighbor phase, LSR retransmission lists, relevant LSAs and interface loss. This check would diagnose OSPF LSDB synchronization failure, but would not first isolate the described OSPF E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
Inspect BGP aggregate configuration, contributor routes, specific exceptions and next-hop forwarding. This check would diagnose BGP prefix aggregation and specifics, but would not first isolate the described OSPF E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
A Huawei Datacom engineer is investigating the following situation: A data-center recovery plan expects path cost to include the distance to the exit but its external routes are Type 2. Which corrective action best resolves the specified issue?
Choose an approved external metric type and metric policy to reflect the required exit selection. Technical basis: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric. The measurable acceptance criterion is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Configure supported matching OSPF authentication mode and keys on both authorized neighbors. This is a legitimate response to the different issue of OSPF authentication-key mismatch, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
Establish an approved attached L1/L2 exit and verify default inter-area forwarding for Level-1 devices. This is a legitimate response to the different issue of IS-IS L1 default to nearest attached L1L2, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
Apply supported area-range inter-area summarization at the ABR using a safe nonoverlapping aggregate. This is a legitimate response to the different issue of OSPF inter-area summarization placement, but it does not correct the specific OSPF E1 versus E2 external metric condition reported. The relevant technical distinction is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
A team is validating a Huawei network repair: A data-center recovery plan expects path cost to include the distance to the exit but its external routes are Type 2. Which observable result provides the clearest evidence of success?
The selected external next hop matches the documented cost calculation and changes predictably under failover. This result directly tests whether the correct action worked: Choose an approved external metric type and metric policy to reflect the required exit selection. This is explained by: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
The route and forwarding entries agree and a packet trace takes the selected viable next hop. That observation would support a separate case of RIB-to-FIB forwarding discrepancy, not verification of the reported OSPF E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
The adjacency leaves ExStart or Exchange and reaches Full with matching link MTU behavior. That observation would support a separate case of OSPF MTU stalls ExStart, not verification of the reported OSPF E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
The leaf follows the intended default path and its LSDB lacks the suppressed detailed inter-area summaries. That observation would support a separate case of OSPF totally stub area inter-area constraint, not verification of the reported OSPF E1 versus E2 external metric. The relevant observable outcome here is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Consider the following Huawei Datacom deployment: A data-center recovery plan expects path cost to include the distance to the exit but its external routes are Type 2. Which technical principle best explains the observed behavior?
OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric. This mechanism explains the case-specific corrective step: Choose an approved external metric type and metric policy to reflect the required exit selection. Confirm the mechanism by verifying: The selected external next hop matches the documented cost calculation and changes predictably under failover.
NSSA ASBRs advertise Type 7 external LSAs that an ABR can translate for other OSPF areas. This explains OSPF NSSA type-7 translation, but not why the issue in this scenario occurs. The specific mechanism is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
OSPF external route summarization is performed on an ASBR, distinct from ABR inter-area summary generation. This explains OSPF external summarization at ASBR, but not why the issue in this scenario occurs. The specific mechanism is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
Selective IS-IS route leaking can import chosen Level-2 reachability into a Level-1 area. This explains IS-IS selective L2-to-L1 route leaking, but not why the issue in this scenario occurs. The specific mechanism is: OSPF E1 metrics include internal path cost to the ASBR whereas E2 commonly prioritizes the external metric.
A Huawei network is left in this condition: A data-center recovery plan expects path cost to include the distance to the exit but its external routes are Type 2. What direct operational or security risk is most relevant if it is not corrected?
Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths. This is the direct exposure created by OSPF E1 versus E2 external metric. Mitigate it through: Choose an approved external metric type and metric policy to reflect the required exit selection. Then test: The selected external next hop matches the documented cost calculation and changes predictably under failover.
Duplicate router IDs can corrupt topology interpretation and interrupt route convergence. This consequence is associated more directly with OSPF duplicate router IDs. For the stated conditions the immediate exposure is: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
Forcing external redistribution into a stub without redesigning its type creates unsupported expectations. This consequence is associated more directly with OSPF stub area external LSA constraint. For the stated conditions the immediate exposure is: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
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: Misunderstanding E2 treatment can produce asymmetric or longer-than-expected external paths.
Before changing the Huawei network configuration, an engineer investigates: A data-center recovery plan expects path cost to include the distance to the exit but its external routes are Type 2. Which diagnostic check should be performed first?
Compare external route type, advertised metric, internal ASBR reachability cost and route selection. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Choose an approved external metric type and metric policy to reflect the required exit selection. Successful verification is: The selected external next hop matches the documented cost calculation and changes predictably under failover.
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 E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
Compare OSPF router IDs, neighbor tables and LSA advertising-router fields. This check would diagnose OSPF duplicate router IDs, but would not first isolate the described OSPF E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
Inspect redistributed prefix ownership, ASBR aggregation policy, and emitted Type 5 advertisements. This check would diagnose OSPF external summarization at ASBR, but would not first isolate the described OSPF E1 versus E2 external metric. Begin with: Compare external route type, advertised metric, internal ASBR reachability cost and route selection.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
