Question 560
At fictional Vista Research, a network engineer supporting lab network slices is reviewing RSTP, MSTP and switching interconnects during a network troubleshooting drill (HCIP-H12-821-SWITCH-140). The observed network issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Use a supported cluster and link aggregation design instead of uncontrolled duplicate links. The specific reported fault is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Confirmation should show: MAC learning stabilizes and aggregated uplinks provide the intended redundancy. The supporting technical principle is: Multiple physical switching paths must have coherent loop and aggregation control.
Incorrect Answers
“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 downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.
“Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links” responds to another technical or business failure: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. That source case depends on: Spanning-tree selected paths depend on cumulative root cost and bridge identifiers. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.
“Check split-brain prevention mechanisms and stack topology supported by the platform” responds to another technical or business failure: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. That source case depends on: Stack resiliency requires deliberate master election and partition handling. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.