Before changing the Huawei network configuration, an engineer investigates: A regional edge applies a community filter without matching the correct complete community values during an interconnect cutover. Which diagnostic check should be performed first?
Inspect route communities on received paths and the community-filter and route-policy match results. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Apply a reviewed community-filter match in the relevant import or export route-policy. Successful verification is: Tagged management prefixes follow the intended permit/deny outcome without affecting unrelated production routes.
Check route tags, source protocol, import-route statements and re-advertisement history. This check would diagnose Redistribution route tag loop avoidance, but would not first isolate the described BGP community filtering in routing control. Begin with: Inspect route communities on received paths and the community-filter and route-policy match results.
Inspect adjacency graph, route source type and advertisement history on the transit router. This check would diagnose iBGP split-horizon route propagation, but would not first isolate the described BGP community filtering in routing control. Begin with: Inspect route communities on received paths and the community-filter and route-policy match results.
Check PBR next hop, track state, route resolution and tested failure behavior. This check would diagnose PBR failed-next-hop fallback, but would not first isolate the described BGP community filtering in routing control. Begin with: Inspect route communities on received paths and the community-filter and route-policy match results.
A Huawei Datacom engineer is investigating the following situation: Two IGP processes each import one another's routes and generate duplicate alternatives because redistribution has no origin tag. Which corrective action best resolves the specified issue?
Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Technical basis: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries. The measurable acceptance criterion is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Apply supported next-hop handling such as next-hop-local where appropriate and provide underlay reachability. This is a legitimate response to the different issue of iBGP next-hop reachability, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Set the Huawei ip ip-prefix network and greater-equal/less-equal bounds to the precise permitted prefixes. This is a legitimate response to the different issue of Prefix-list network and mask matching, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Reorder or narrow the route-policy nodes so specific restrictions are evaluated before general permits. This is a legitimate response to the different issue of Route-policy permit and deny node order, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
A team is validating a Huawei network repair: Two IGP processes each import one another's routes and generate duplicate alternatives because redistribution has no origin tag. Which observable result provides the clearest evidence of success?
Every prefix has a stable authoritative origin and route import does not recursively reappear. This result directly tests whether the correct action worked: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. This is explained by: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Affected prefixes select the planned reachable next hop with correct preference while unrelated paths remain stable. That observation would support a separate case of Route-policy next-hop and preference application, not verification of the reported Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
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 Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
The preferred gateway is master under healthy conditions and backup is ready for takeover. That observation would support a separate case of VRRP priority and intended master, not verification of the reported Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Consider the following Huawei Datacom deployment: Two IGP processes each import one another's routes and generate duplicate alternatives because redistribution has no origin tag. Which technical principle best explains the observed behavior?
Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries. This mechanism explains the case-specific corrective step: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Confirm the mechanism by verifying: Every prefix has a stable authoritative origin and route import does not recursively reappear.
A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. This explains PBR failed-next-hop fallback, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
QoS differentiation depends on packet classification, marking trust and congestion-aware queuing. This explains QoS DSCP remarking and trust, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
BFD fault detection sensitivity depends on negotiated intervals and missed-packet multiplier. This explains BFD detection timers and false alarms, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
A Huawei network is left in this condition: Two IGP processes each import one another's routes and generate duplicate alternatives because redistribution has no origin tag. What direct operational or security risk is most relevant if it is not corrected?
Uncontrolled reimport can create persistent false reachability after a primary path fails. This is the direct exposure created by Redistribution route tag loop avoidance. Mitigate it through: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Then test: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Assuming MED always overrides LOCAL_PREF or applies across every AS can misroute traffic. This consequence is associated more directly with BGP MED same-neighbor-AS comparison. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy. This consequence is associated more directly with PBR failed-next-hop fallback. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
An overbroad prefix filter can propagate unauthorized specifics or conceal desired routes. This consequence is associated more directly with Prefix-list network and mask matching. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
Before changing the Huawei network configuration, an engineer investigates: Two IGP processes each import one another's routes and generate duplicate alternatives because redistribution has no origin tag. Which diagnostic check should be performed first?
Check route tags, source protocol, import-route statements and re-advertisement history. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Successful verification is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Inspect traffic classifier, behavior, policy association, interface binding and match counters. This check would diagnose MQC classifier and behavior association, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
Inspect matching rule, applied attributes, selected route and resolved FIB next hop. This check would diagnose Route-policy next-hop and preference application, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
Inspect (*,G) and (S,G) state, SPT flags, source RPF and join/prune counters. This check would diagnose PIM-SM RPT to SPT switchover, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
A Huawei Datacom engineer is investigating the following situation: A campus edge brings static disaster-recovery prefixes into OSPF and then reimports the same routes into a second domain. Which corrective action best resolves the specified issue?
Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Technical basis: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries. The measurable acceptance criterion is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Select the longest matching destination prefix first, and compare route preference among eligible routes for the same prefix. This is a legitimate response to the different issue of Longest-prefix and route preference, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Configure supported RR-client relationships and confirm intended reflection rules between client and nonclient sessions. This is a legitimate response to the different issue of BGP route-reflector client scoping, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Configure an exact supported policy-based route match and viable next hop for the authorized traffic class. This is a legitimate response to the different issue of Policy-based routing for approved application, but it does not correct the specific Redistribution route tag loop avoidance condition reported. The relevant technical distinction is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
A team is validating a Huawei network repair: A campus edge brings static disaster-recovery prefixes into OSPF and then reimports the same routes into a second domain. Which observable result provides the clearest evidence of success?
Every prefix has a stable authoritative origin and route import does not recursively reappear. This result directly tests whether the correct action worked: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. This is explained by: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
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 Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
The intended region shares coherent instance topology and redundant paths remain loop-free. That observation would support a separate case of MSTP region mismatch on trunks, not verification of the reported Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Clients obtain a valid address lease, gateway and DNS options from the authorized remote DHCP server. That observation would support a separate case of DHCP relay to remote server, not verification of the reported Redistribution route tag loop avoidance. The relevant observable outcome here is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Consider the following Huawei Datacom deployment: A campus edge brings static disaster-recovery prefixes into OSPF and then reimports the same routes into a second domain. Which technical principle best explains the observed behavior?
Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries. This mechanism explains the case-specific corrective step: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Confirm the mechanism by verifying: Every prefix has a stable authoritative origin and route import does not recursively reappear.
OSPF database description negotiation can fail when peer interface MTU expectations do not match. This explains OSPF MTU stalls ExStart, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. This explains PBR failed-next-hop fallback, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
Policy-based routing can select forwarding based on packet attributes before conventional destination routing. This explains Policy-based routing for approved application, but not why the issue in this scenario occurs. The specific mechanism is: Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries.
A Huawei network is left in this condition: A campus edge brings static disaster-recovery prefixes into OSPF and then reimports the same routes into a second domain. What direct operational or security risk is most relevant if it is not corrected?
Uncontrolled reimport can create persistent false reachability after a primary path fails. This is the direct exposure created by Redistribution route tag loop avoidance. Mitigate it through: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Then test: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Misordered nodes can create routing leaks that an apparently correct later deny cannot stop. This consequence is associated more directly with Route-policy permit and deny node order. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
A broad PBR match may reroute critical unrelated flows and bypass intended segmentation. This consequence is associated more directly with Policy-based routing for approved application. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
Stripping a no-export marker can leak intended internal reachability to other networks. This consequence is associated more directly with BGP route policy community NO_EXPORT. For the stated conditions the immediate exposure is: Uncontrolled reimport can create persistent false reachability after a primary path fails.
Before changing the Huawei network configuration, an engineer investigates: A campus edge brings static disaster-recovery prefixes into OSPF and then reimports the same routes into a second domain. Which diagnostic check should be performed first?
Check route tags, source protocol, import-route statements and re-advertisement history. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Mark imported routes and deny reimport of already redistributed origins with controlled route tags. Successful verification is: Every prefix has a stable authoritative origin and route import does not recursively reappear.
Inspect peer reflect-client settings, received and advertised routes and RR topology. This check would diagnose BGP route-reflector client scoping, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
Check PBR next hop, track state, route resolution and tested failure behavior. This check would diagnose PBR failed-next-hop fallback, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
Inspect matching rule, applied attributes, selected route and resolved FIB next hop. This check would diagnose Route-policy next-hop and preference application, but would not first isolate the described Redistribution route tag loop avoidance. Begin with: Check route tags, source protocol, import-route statements and re-advertisement history.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
