Installation guide

AlliedWare Plus Version 2.2.4.0 Software Release Notes
PN 613-001748 Rev A 4 Allied Telesis, Inc.
Stacking Operational Notes
The following operational notes apply only to stacked switches:
 It is required that a full reboot of the entire stack be made after making any physical stack
changes:
— For optimum stack performance, convergence and recovery time, Allied Telesis
recommends stacking no more than 3 switches.
— Do not issue any commands into the console during stack discovery.
 When configuring a stack, make sure that the lowest ID in the stack is running the latest
version of the firmware.
 Upon stack boot up, the firmware loaded on the master switch is automatically downloaded to
all member switches unless one or more member switches are running a newer firmware
version than the master switch. In this case, the stack will not form.
 Within a stack, you must assign each switch a unique Device ID. By default, the Device ID is
set to 0 which means it is ineligible to participate in a stack. Device IDs of 1 through 8 are
reserved for stacking operation. The Device ID of 0 is for standalone switches.
 If you have PoE switches in a hardware stack, make sure the master switch is a PoE switch.
Failing to do this, may limit PoE functionality.
 After the stack becomes operational, the stack ID LED on the switches displays the switch ID
number and flashes the master number every few seconds. This is normal behavior for the
LEDs when the switches are operating in a stacked configuration. When powering up, the
stack ID LED displays “b.”
 In the event that current master switch fails or is removed from the stack, the next lowest ID
will take over as master. This change of mastership will take anywhere between 1-5 minutes
depending on the size of your stack and configuration. During the new initialization inter-
switch traffic may be disrupted. Once the stack is reinitialized under the new master, full
network connectivity will resume.
 In the event that a stack member should fail (power failure, cable disconnect, etc.) network
connectivity may be temporarily disrupted:
— In a stack of 3 or less switches, connectivity to and through the stack may be disrupted for
up to 2 minutes.
— In a stack of 4 or more switches, connectivity may be disrupted for up to 10 minutes.
During this time, the stack may require and issue a full reboot to all members.
 For reliable IGMP snooping operation, multicast sources and routers should only be
connected to the master switch.
 In 802.1x, multiple supplicant mode is not supported on stacked units.
Known Issues
The following issues are unresolved in the Version 2.2.4.0 Release:
 Hardware stacking: QoS error message is shown after save and reboot. This is only a display
issue and does not affect QoS functionality.
 PoE: Disabling PoE on an individual port is retained after a reboot.
 RIP: Triggered updates are not functioning. Regardless of any change, RIP only sends the
updated information in the next scheduled update.