Before changing the Huawei network configuration, an engineer investigates: A wiring closet elects a distribution replacement as root even though the campus design designates the redundant core pair. Which diagnostic check should be performed first?
Inspect root bridge ID, path cost, port roles and current bridge priorities. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Set reviewed RSTP bridge priorities so an appropriate resilient core device remains root. Successful verification is: Root-port selection and link topology match the designed forwarding tree without a Layer 2 loop.
Inspect route communities on received paths and the community-filter and route-policy match results. This check would diagnose BGP community filtering in routing control, but would not first isolate the described RSTP root bridge location. Begin with: Inspect root bridge ID, path cost, port roles and current bridge priorities.
Inspect stack role, heartbeat, split-brain detection state and inter-member link health. This check would diagnose Switch stacking split-brain, but would not first isolate the described RSTP root bridge location. Begin with: Inspect root bridge ID, path cost, port roles and current bridge priorities.
Inspect port roles, proposal/agreement exchanges, physical link state and failover logs. This check would diagnose RSTP alternate port failover, but would not first isolate the described RSTP root bridge location. Begin with: Inspect root bridge ID, path cost, port roles and current bridge priorities.
A Huawei Datacom engineer is investigating the following situation: An employee connects a small unmanaged switch to an RSTP edge port and received BPDUs create an unexpected topology change. Which corrective action best resolves the specified issue?
Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Technical basis: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected. The measurable acceptance criterion is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Check supported PIM-SM shortest-path-tree switchover thresholds and source-side unicast reachability. This is a legitimate response to the different issue of PIM-SM RPT to SPT switchover, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
Restore valid alternate-port eligibility and verify the supported RSTP rapid convergence procedure. This is a legitimate response to the different issue of RSTP alternate port failover, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
Correct the interface security-zone assignment and scoped interzone policy matching source and destination. This is a legitimate response to the different issue of Firewall security-zone policy, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
A team is validating a Huawei network repair: An employee connects a small unmanaged switch to an RSTP edge port and received BPDUs create an unexpected topology change. Which observable result provides the clearest evidence of success?
An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root. This result directly tests whether the correct action worked: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. This is explained by: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
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 RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
An authorized failover moves the alternate link to forwarding without creating a loop. That observation would support a separate case of RSTP alternate port failover, not verification of the reported RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
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 RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Consider the following Huawei Datacom deployment: An employee connects a small unmanaged switch to an RSTP edge port and received BPDUs create an unexpected topology change. Which technical principle best explains the observed behavior?
Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected. This mechanism explains the case-specific corrective step: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Confirm the mechanism by verifying: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
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: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
An SD-WAN overlay can select among heterogeneous underlay links using measured application path quality. This explains SD-WAN underlay and application steering, but not why the issue in this scenario occurs. The specific mechanism is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
MSTP recognizes region boundaries through region name, revision and VLAN mapping digest. This explains MSTP region mismatch on trunks, but not why the issue in this scenario occurs. The specific mechanism is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
A Huawei network is left in this condition: An employee connects a small unmanaged switch to an RSTP edge port and received BPDUs create an unexpected topology change. What direct operational or security risk is most relevant if it is not corrected?
Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology. This is the direct exposure created by RSTP edge-port BPDU protection. Mitigate it through: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Then test: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Removing every nonforwarding link destroys the redundancy that spanning tree is designed to preserve. This consequence is associated more directly with RSTP alternate port failover. For the stated conditions the immediate exposure is: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
Applying the policy at the wrong routing role leaves external LSAs unchanged. This consequence is associated more directly with OSPF external summarization at ASBR. For the stated conditions the immediate exposure is: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
A receiver's healthy shared tree does not deliver an unregistered source automatically. This consequence is associated more directly with PIM first-hop source registration. For the stated conditions the immediate exposure is: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
Before changing the Huawei network configuration, an engineer investigates: An employee connects a small unmanaged switch to an RSTP edge port and received BPDUs create an unexpected topology change. Which diagnostic check should be performed first?
Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Successful verification is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Inspect port roles, proposal/agreement exchanges, physical link state and failover logs. This check would diagnose RSTP alternate port failover, but would not first isolate the described RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
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 RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
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 RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
A Huawei Datacom engineer is investigating the following situation: A campus access edge accidentally becomes a transit path when a user attaches another bridge, causing MAC flapping. Which corrective action best resolves the specified issue?
Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Technical basis: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected. The measurable acceptance criterion is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Configure supported inter-subnet or inter-AC roaming design appropriate to the mobility domain. This is a legitimate response to the different issue of Campus WLAN layer-3 roaming, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
Restore consistent MST region definitions or explicitly design a safe boundary between distinct regions. This is a legitimate response to the different issue of MSTP region mismatch on trunks, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
Validate supported CSS inter-chassis links, roles, redundancy and a controlled master-failover test. This is a legitimate response to the different issue of CSS chassis clustering and failover, but it does not correct the specific RSTP edge-port BPDU protection condition reported. The relevant technical distinction is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
A team is validating a Huawei network repair: A campus access edge accidentally becomes a transit path when a user attaches another bridge, causing MAC flapping. Which observable result provides the clearest evidence of success?
An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root. This result directly tests whether the correct action worked: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. This is explained by: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
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 RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
The multicast stream reaches subscribed ports but no longer floods uninvolved endpoints. That observation would support a separate case of IGMP snooping multicast fanout, not verification of the reported RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
The shortest-path calculation selects the intended cost path and the backup remains viable. That observation would support a separate case of OSPF SPF path-cost comparison, not verification of the reported RSTP edge-port BPDU protection. The relevant observable outcome here is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Consider the following Huawei Datacom deployment: A campus access edge accidentally becomes a transit path when a user attaches another bridge, causing MAC flapping. Which technical principle best explains the observed behavior?
Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected. This mechanism explains the case-specific corrective step: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Confirm the mechanism by verifying: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
RSTP maintains alternate port roles that can supply loop-free connectivity after selected path failure. This explains RSTP alternate port failover, but not why the issue in this scenario occurs. The specific mechanism is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
PIM SSM builds source-specific trees directly and validates source-facing RPF paths. This explains Multicast SSM and RPF source path, but not why the issue in this scenario occurs. The specific mechanism is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
BGP OPEN negotiation validates the expected peer AS and session parameters. This explains BGP peer autonomous-system mismatch, but not why the issue in this scenario occurs. The specific mechanism is: Edge-port safeguards prevent unintended bridge participation where endpoint-only connections are expected.
A Huawei network is left in this condition: A campus access edge accidentally becomes a transit path when a user attaches another bridge, causing MAC flapping. What direct operational or security risk is most relevant if it is not corrected?
Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology. This is the direct exposure created by RSTP edge-port BPDU protection. Mitigate it through: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Then test: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Simultaneous active stack fragments can duplicate gateways or destabilize Layer 2 forwarding. This consequence is associated more directly with Switch stacking split-brain. For the stated conditions the immediate exposure is: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
An accidental boundary can change port roles and send traffic over unintended links. This consequence is associated more directly with MSTP region mismatch on trunks. For the stated conditions the immediate exposure is: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
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: Failing to protect user ports can allow a rogue switch to disrupt campus spanning-tree topology.
Before changing the Huawei network configuration, an engineer investigates: A campus access edge accidentally becomes a transit path when a user attaches another bridge, causing MAC flapping. Which diagnostic check should be performed first?
Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs. This check isolates the suspected cause before an unsafe change. If confirmed, the targeted action is: Apply appropriate RSTP edge-port and BPDU protection policies while preserving legitimate uplink roles. Successful verification is: An unauthorized bridge is blocked or the port enters its defined protected state without changing the core root.
Compare received candidate paths, LOCAL_PREF values, route policy and installed best path. This check would diagnose BGP local preference internal egress, but would not first isolate the described RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
Inspect root bridge ID, path cost, port roles and current bridge priorities. This check would diagnose RSTP root bridge location, but would not first isolate the described RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
Inspect stack role, heartbeat, split-brain detection state and inter-member link health. This check would diagnose Switch stacking split-brain, but would not first isolate the described RSTP edge-port BPDU protection. Begin with: Inspect edge-port flags, BPDU-protection events, root changes and MAC-move logs.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
