Question 170
At fictional Oakridge Energy, a network engineer supporting field substations is reviewing RSTP, MSTP and switching interconnects during an initial deployment test (HCIP-H12-821-SWITCH-043). The observed network issue is: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links. The specific reported fault is: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. Confirmation should show: Correct MST port roles and predictable alternate paths appear after convergence. The supporting technical principle is: Spanning-tree selected paths depend on cumulative root cost and bridge identifiers.
Incorrect Answers
“Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” responds to another technical or business failure: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. That source case depends on: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks. The present issue is: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. The more direct action is “Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links” because Spanning-tree selected paths depend on cumulative root cost and bridge identifiers.
“Align region name, revision level and VLAN-instance mappings across the intended domain” responds to another technical or business failure: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. That source case depends on: MST region membership depends on a consistent configuration digest, not merely a label. The present issue is: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. The more direct action is “Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links” because Spanning-tree selected paths depend on cumulative root cost and bridge identifiers.
“Permit the intended tagged VLAN on both sides of the trunk without broadening unrelated VLAN access” responds to another technical or business failure: A technician adds a new VLAN but leaves it out of the allowed trunk list between access and aggregation switches. That source case depends on: VLAN trunking requires explicit compatible tagging and allowed membership. The present issue is: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. The more direct action is “Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links” because Spanning-tree selected paths depend on cumulative root cost and bridge identifiers.