Before changing the Huawei network configuration, an engineer investigates: A campus combines a legacy static route domain with an IGP and repeatedly reoriginates the same prefix through reciprocal redistribution. Which diagnostic check should be performed first?
Trace protocol origin, import rules, tags, preferences and repeated route updates. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Restrict redistribution using explicit route policies and route tags to prevent readvertising imported prefixes. Successful verification is: The imported prefixes appear once with intended preference and do not reenter their originating protocol.
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 Route import feedback loop. Begin with: Trace protocol origin, import rules, tags, preferences and repeated route updates.
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 Route import feedback loop. Begin with: Trace protocol origin, import rules, tags, preferences and repeated route updates.
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 Route import feedback loop. Begin with: Trace protocol origin, import rules, tags, preferences and repeated route updates.
A Huawei Datacom engineer is investigating the following situation: An engineer believes a default static route should override a more-specific learned /25 route even though its route preference is numerically lower. Which corrective action best resolves the specified issue?
Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Technical basis: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix. The measurable acceptance criterion is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Restrict redistribution using explicit route policies and route tags to prevent readvertising imported prefixes. This is a legitimate response to the different issue of Route import feedback loop, but it does not correct the specific Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
Configure a valid shared VRRP virtual gateway in the client subnet and set hosts to use it. This is a legitimate response to the different issue of VRRP virtual gateway and ownership, but it does not correct the specific Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
Honor stub-area restrictions and use the ABR default route or redesign the area type for required imports. This is a legitimate response to the different issue of OSPF stub area external LSA constraint, but it does not correct the specific Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
A team is validating a Huawei network repair: An engineer believes a default static route should override a more-specific learned /25 route even though its route preference is numerically lower. Which observable result provides the clearest evidence of success?
Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry. This result directly tests whether the correct action worked: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. This is explained by: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
The imported prefixes appear once with intended preference and do not reenter their originating protocol. That observation would support a separate case of Route import feedback loop, not verification of the reported Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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 Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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 Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Consider the following Huawei Datacom deployment: An engineer believes a default static route should override a more-specific learned /25 route even though its route preference is numerically lower. Which technical principle best explains the observed behavior?
IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix. This mechanism explains the case-specific corrective step: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Confirm the mechanism by verifying: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
The routing information base selects routes while the forwarding information base programs actual packet forwarding. This explains RIB-to-FIB forwarding discrepancy, but not why the issue in this scenario occurs. The specific mechanism is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
An ASBR originates Type 5 AS-external LSAs for redistributed destinations in eligible OSPF areas. This explains OSPF type-5 external advertisement, but not why the issue in this scenario occurs. The specific mechanism is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
A Huawei network is left in this condition: An engineer believes a default static route should override a more-specific learned /25 route even though its route preference is numerically lower. What direct operational or security risk is most relevant if it is not corrected?
Confusing the two selection stages can divert traffic to the wrong WAN gateway. This is the direct exposure created by Longest-prefix and route preference. Mitigate it through: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Then test: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
Replacing a working NSSA with a stub would block intended local external redistribution. This consequence is associated more directly with OSPF NSSA type-7 translation. For the stated conditions the immediate exposure is: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
Treating a displayed RIB route as proof of working forwarding can prolong a blackhole. This consequence is associated more directly with RIB-to-FIB forwarding discrepancy. For the stated conditions the immediate exposure is: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
Before changing the Huawei network configuration, an engineer investigates: An engineer believes a default static route should override a more-specific learned /25 route even though its route preference is numerically lower. Which diagnostic check should be performed first?
Compare destination address, prefix lengths, active candidate routes and the FIB lookup. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Successful verification is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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 Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
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 Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
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 Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
A Huawei Datacom engineer is investigating the following situation: A branch receives two routes to a subnet and applies administrative preference before checking which prefix matches the actual destination. Which corrective action best resolves the specified issue?
Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Technical basis: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix. The measurable acceptance criterion is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Restrict redistribution using explicit route policies and route tags to prevent readvertising imported prefixes. This is a legitimate response to the different issue of Route import feedback loop, but it does not correct the specific Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
Compare the selected RIB entry with the programmed FIB next hop and correct the forwarding installation fault. This is a legitimate response to the different issue of RIB-to-FIB forwarding discrepancy, but it does not correct the specific Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
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 Longest-prefix and route preference condition reported. The relevant technical distinction is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
A team is validating a Huawei network repair: A branch receives two routes to a subnet and applies administrative preference before checking which prefix matches the actual destination. Which observable result provides the clearest evidence of success?
Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry. This result directly tests whether the correct action worked: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. This is explained by: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
The imported prefixes appear once with intended preference and do not reenter their originating protocol. That observation would support a separate case of Route import feedback loop, not verification of the reported Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
A simulated PBR next-hop outage selects the approved alternate without routing loops. That observation would support a separate case of PBR failed-next-hop fallback, not verification of the reported Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
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 Longest-prefix and route preference. The relevant observable outcome here is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Consider the following Huawei Datacom deployment: A branch receives two routes to a subnet and applies administrative preference before checking which prefix matches the actual destination. Which technical principle best explains the observed behavior?
IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix. This mechanism explains the case-specific corrective step: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Confirm the mechanism by verifying: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
EVPN Type 2 carries MAC or MAC/IP reachability; Type 5 is used for IP-prefix reachability. This explains EVPN Type-2 MAC/IP route interpretation, but not why the issue in this scenario occurs. The specific mechanism is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
The routing information base selects routes while the forwarding information base programs actual packet forwarding. This explains RIB-to-FIB forwarding discrepancy, but not why the issue in this scenario occurs. The specific mechanism is: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
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: IP forwarding uses longest-prefix match; protocol route preference decides among competing candidates for the same prefix.
A Huawei network is left in this condition: A branch receives two routes to a subnet and applies administrative preference before checking which prefix matches the actual destination. What direct operational or security risk is most relevant if it is not corrected?
Confusing the two selection stages can divert traffic to the wrong WAN gateway. This is the direct exposure created by Longest-prefix and route preference. Mitigate it through: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Then test: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Treating a displayed RIB route as proof of working forwarding can prolong a blackhole. This consequence is associated more directly with RIB-to-FIB forwarding discrepancy. For the stated conditions the immediate exposure is: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
Mismatched stateful/stateless configuration can cause missing DNS or addressing despite live link connectivity. This consequence is associated more directly with IPv6 DHCPv6 stateful versus stateless. For the stated conditions the immediate exposure is: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
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: Confusing the two selection stages can divert traffic to the wrong WAN gateway.
Before changing the Huawei network configuration, an engineer investigates: A branch receives two routes to a subnet and applies administrative preference before checking which prefix matches the actual destination. Which diagnostic check should be performed first?
Compare destination address, prefix lengths, active candidate routes and the FIB lookup. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. Successful verification is: Forwarding to a host inside the /25 follows the specific route while other addresses use the appropriate less-specific entry.
Trace protocol origin, import rules, tags, preferences and repeated route updates. This check would diagnose Route import feedback loop, but would not first isolate the described Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
Inspect reflector cluster ID, reflected path attributes and RR-client membership. This check would diagnose BGP route reflector cluster loop prevention, but would not first isolate the described Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
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 Longest-prefix and route preference. Begin with: Compare destination address, prefix lengths, active candidate routes and the FIB lookup.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
