Stacking Unit Role Transition Considerations; Port Down And Aging - Arris Ruckus ICX 7850 Series Configuration Manual

ICX Stack Troubleshooting

Stacking unit role transition considerations

If you do not use the write memory command but reset the stack, the stack units continue to operate in their roles as defined
by the stacking.boot file. After the reset, each unit readjusts based on the current runtime configuration. However, you may
observe different results depending on what has not been saved. If you have renumbered the stack unit IDs, you may see a
configuration mismatch because your changes no longer match the active controller configuration.
If you change priorities to elect an active controller, the new active controller assumes its role after a reboot, whether or not you
have used the write memory command. If you do not save your priority change before the next reboot, the reboot triggers an
election that may result in a different winner based on the priority in the unsaved configuration. The new winner assumes the
active controller role after the next reboot.
If you change the stacking port configuration and do not save your changes, you may encounter connectivity errors. To recover
from a configuration error, define the correct stacking port by running stack interactive-setup.
NOTE
You should always execute the write memory command after making stacking-related configuration changes such as
changing priority or changing stacking ports. If you do not want to keep the changes, change the configuration back to
the previous version, and then execute the write memory command. Do not discard configuration changes by using a
reset without executing the write memory command.

Stacking unit role transition considerations

An active or standby controller contains the stacking system configuration and its internal data structures. When an active or
standby controller becomes a member, the configuration and data structures are not cleared. This does not affect its capability
to function as a member. However, if the user changes the configuration, this member unit cannot become a standby again
because of the difference in configuration. A member unit can become a standby only if the member was never a standby or
active controller (with no configuration) or if it has the same configuration as the current active controller.

Port down and aging

Aging is only used as a safeguard. If a unit is powered down or the stacking link is removed, the system immediately detects that
the port is down and knows that its neighbor is gone. That unit is immediately removed from the active controller.
If a stacking port does not receive keep-alive messages from its neighbor within 60 seconds, it ages out the neighbor. When a
unit is no longer stack-enabled or when one stacking port becomes a non-stacking port, it sends a notification that the port is no
longer a stacking port. When the neighboring port receives the notification from its neighbor, it immediately removes the
neighbor.
The following message is logged and displayed when a port is aged out.
Warning! my mac=0000.004f.4243, age out up-stream
244
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01