Back to All Scenarios
PASSEDvendor / ruckus_icx_switch_stack_partition
Ruckus ICX Switch Stack Partition
A Ruckus ICX 7650 switch stack of 6 members partitions when a stacking module fails on the middle unit, splitting the stack into two independent 3-member segments with duplicate configurations.
Pattern
SWITCH_STACK_EVENT
Severity
CRITICAL
Confidence
92%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | SWITCH_STACK_EVENT | SWITCH_STACK_EVENT | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 20 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
Ruckus ICX 7650-48P stack, 6 members in daisy-chain topology. Member 3 rear stacking module failed. Stack splits into members 1-3 and members 4-6. Duplicate management IPs. 144 ports in isolated partition.
Injected Error Messages (2)
ruckus ICX 7650 stack partition detected — member 3 rear stacking port failed, ruckus ICX stack split into two segments: units 1-3 (active master) and units 4-6 (elected new master), ruckus ICX stack ring topology broken, duplicate management IP 10.0.0.20 on both partitions causing ARP conflicts, 144 access ports on members 4-6 operating independently with potentially conflicting VLAN assignments
ruckus ICX 7650 secondary partition formed — members 4-6 elected member 4 as new master, ruckus ICX running with stale configuration from before partition, LACP port-channels spanning both partitions now broken, uplinks from members 4-6 to core operating independently, ruckus ICX health monitor on secondary partition unaware of primary partition state
Neural Engine Root Cause Analysis
The Ruckus ICX 7650 stack has experienced a critical stack split due to a failed rear stacking port on member 3, causing the ring topology to break. This has resulted in two independent partitions (units 1-3 and units 4-6) each electing their own master and sharing the same management IP 10.0.0.20, creating ARP conflicts and network instability. The 144 access ports on the split partition are now operating independently with potentially conflicting VLAN assignments, risking network loops and connectivity issues.
Remediation Plan
1. Immediately access both partitions via console connection to avoid IP conflicts. 2. Document current configuration and port assignments on both partitions. 3. Temporarily assign different management IPs to each partition to resolve ARP conflicts. 4. Check physical stacking cables on member 3 rear ports and replace if damaged. 5. Power cycle member 3 or the entire stack in a controlled manner. 6. Monitor stack reformation and verify all 6 members rejoin properly. 7. Validate VLAN assignments and port configurations post-recovery. 8. Implement stack monitoring to detect early signs of cable degradation.
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmnck8icw07joobqeb771xld5