Before changing the Huawei network configuration, an engineer investigates: A school uses PBR for an approved source subnet yet the rule matches the wrong IP source range and never activates. Which diagnostic check should be performed first?
Inspect PBR classifier, interface direction, policy hits and a traffic trace. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Configure an exact supported policy-based route match and viable next hop for the authorized traffic class. Successful verification is: Only the approved source/application flows follow the private WAN while nonmatching traffic uses normal routing.
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 Policy-based routing for approved application. Begin with: Inspect PBR classifier, interface direction, policy hits and a traffic trace.
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 Policy-based routing for approved application. Begin with: Inspect PBR classifier, interface direction, policy hits and a traffic trace.
Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs. This check would diagnose RSTP edge-port BPDU protection, but would not first isolate the described Policy-based routing for approved application. Begin with: Inspect PBR classifier, interface direction, policy hits and a traffic trace.
A Huawei Datacom engineer is investigating the following situation: A PBR next hop fails, but affected flows continue being directed to it rather than the available normal route. Which corrective action best resolves the specified issue?
Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Technical basis: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. The measurable acceptance criterion is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
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 PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
Apply a reviewed community-filter match in the relevant import or export route-policy. This is a legitimate response to the different issue of BGP community filtering in routing control, but it does not correct the specific PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
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 PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
A team is validating a Huawei network repair: A PBR next hop fails, but affected flows continue being directed to it rather than the available normal route. Which observable result provides the clearest evidence of success?
A simulated PBR next-hop outage selects the approved alternate without routing loops. This result directly tests whether the correct action worked: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. This is explained by: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
Clients form valid global addresses and default-router entries for the authorized prefix. That observation would support a separate case of IPv6 SLAAC router advertisement, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Receiving iBGP routers resolve the BGP next hop and install the approved destination. That observation would support a separate case of iBGP next-hop reachability, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Traffic captures show intended markings and low-delay queue behavior during representative congestion. That observation would support a separate case of QoS DSCP remarking and trust, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Consider the following Huawei Datacom deployment: A PBR next hop fails, but affected flows continue being directed to it rather than the available normal route. Which technical principle best explains the observed behavior?
A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. This mechanism explains the case-specific corrective step: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Confirm the mechanism by verifying: A simulated PBR next-hop outage selects the approved alternate without routing loops.
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: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
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: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
BGP best-path and route installation require reachable NEXT_HOP; iBGP advertising does not always rewrite it. This explains iBGP next-hop reachability, but not why the issue in this scenario occurs. The specific mechanism is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
A Huawei network is left in this condition: A PBR next hop fails, but affected flows continue being directed to it rather than the available normal route. What direct operational or security risk is most relevant if it is not corrected?
An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy. This is the direct exposure created by PBR failed-next-hop fallback. Mitigate it through: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Then test: A simulated PBR next-hop outage selects the approved alternate without routing loops.
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: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
A permissive export filter can leak confidential topology and disrupt other routing domains. This consequence is associated more directly with BGP prefix export-filter leak. For the stated conditions the immediate exposure is: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
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: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
Before changing the Huawei network configuration, an engineer investigates: A PBR next hop fails, but affected flows continue being directed to it rather than the available normal route. Which diagnostic check should be performed first?
Check PBR next hop, track state, route resolution and tested failure behavior. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Successful verification is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Review ingress marks, traffic policy counters, queue occupancy and congestion test results. This check would diagnose QoS DSCP remarking and trust, but would not first isolate the described PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
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 PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
Inspect route-policy node IDs, if-match criteria, apply clauses and hit counts. This check would diagnose Route-policy permit and deny node order, but would not first isolate the described PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
A Huawei Datacom engineer is investigating the following situation: An administrator expects PBR to track an unreachable policy next hop even though the configured behavior lacks availability detection. Which corrective action best resolves the specified issue?
Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Technical basis: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. The measurable acceptance criterion is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
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 PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
Apply a reviewed community-filter match in the relevant import or export route-policy. This is a legitimate response to the different issue of BGP community filtering in routing control, but it does not correct the specific PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
Enforce the authorized DSCP trust boundary and remark or queue approved traffic appropriately. This is a legitimate response to the different issue of QoS DSCP remarking and trust, but it does not correct the specific PBR failed-next-hop fallback condition reported. The relevant technical distinction is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
A team is validating a Huawei network repair: An administrator expects PBR to track an unreachable policy next hop even though the configured behavior lacks availability detection. Which observable result provides the clearest evidence of success?
A simulated PBR next-hop outage selects the approved alternate without routing loops. This result directly tests whether the correct action worked: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. This is explained by: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
TCP 179 establishes to the configured peer and BGP progresses toward Established. That observation would support a separate case of BGP TCP reachability and port, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
All regional peers report a matching MST region configuration and each VLAN follows its intended instance tree. That observation would support a separate case of MSTP VLAN-to-instance mapping, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Matched voice flows receive the configured treatment and unrelated traffic remains within its approved class. That observation would support a separate case of MQC classifier and behavior association, not verification of the reported PBR failed-next-hop fallback. The relevant observable outcome here is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Consider the following Huawei Datacom deployment: An administrator expects PBR to track an unreachable policy next hop even though the configured behavior lacks availability detection. Which technical principle best explains the observed behavior?
A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails. This mechanism explains the case-specific corrective step: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Confirm the mechanism by verifying: A simulated PBR next-hop outage selects the approved alternate without routing loops.
IGMP snooping learns Layer 2 multicast forwarding ports from receiver membership control traffic. This explains IGMP snooping multicast fanout, but not why the issue in this scenario occurs. The specific mechanism is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
RSTP selects a root bridge using bridge IDs and calculates loop-free port roles relative to that root. This explains RSTP root bridge location, but not why the issue in this scenario occurs. The specific mechanism is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
Route tags support identifying redistributed route origin and suppressing feedback across policy boundaries. This explains Redistribution route tag loop avoidance, but not why the issue in this scenario occurs. The specific mechanism is: A policy route can override ordinary forwarding and needs explicit fallback behavior when its next hop fails.
A Huawei network is left in this condition: An administrator expects PBR to track an unreachable policy next hop even though the configured behavior lacks availability detection. What direct operational or security risk is most relevant if it is not corrected?
An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy. This is the direct exposure created by PBR failed-next-hop fallback. Mitigate it through: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Then test: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Untrusted DSCP markings can let ordinary traffic consume scarce high-priority capacity. This consequence is associated more directly with QoS DSCP remarking and trust. For the stated conditions the immediate exposure is: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
Misordered or misplaced ACLs can allow forbidden flows or deny legitimate services. This consequence is associated more directly with ACL packet filter rule order and direction. For the stated conditions the immediate exposure is: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
Using AS_PATH padding without understanding precedence can fail to shift traffic. This consequence is associated more directly with BGP AS_PATH length egress choice. For the stated conditions the immediate exposure is: An untracked policy next hop can blackhole a subset of application traffic while global routing remains healthy.
Before changing the Huawei network configuration, an engineer investigates: An administrator expects PBR to track an unreachable policy next hop even though the configured behavior lacks availability detection. Which diagnostic check should be performed first?
Check PBR next hop, track state, route resolution and tested failure behavior. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Add supported PBR next-hop reachability tracking or failover logic consistent with service requirements. Successful verification is: A simulated PBR next-hop outage selects the approved alternate without routing loops.
Review advertised-route output, prefix-list matches and outbound route-policy order. This check would diagnose BGP prefix export-filter leak, but would not first isolate the described PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
Inspect PBR classifier, interface direction, policy hits and a traffic trace. This check would diagnose Policy-based routing for approved application, but would not first isolate the described PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
Inspect route-policy node IDs, if-match criteria, apply clauses and hit counts. This check would diagnose Route-policy permit and deny node order, but would not first isolate the described PBR failed-next-hop fallback. Begin with: Check PBR next hop, track state, route resolution and tested failure behavior.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
