Node recovery on vcstacks – Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) User Manual
Page 1574
AMF Introduction and Configuration
Software Reference for x310 Series Switches
59.30
AlliedWare Plus
TM
Operating System - Version 5.4.4C
C613-50046-01 REV A
Node recovery on VCStacks
Node recovery on VCStacks that are part of an AMF network is somewhat different to node
recovery of standalone devices. This is because VCStack has its own node recovery
mechanism which has different requirements to AMF.
Typically a failure on a VCStack will only affect one stack member.
■
The replacement device is running a compatible firmware version
■
The Stack ID on the replacement device is set to the same ID as the device being
replaced
■
The replacement device is installed with the same licence as other stack members
Then, VCStack will synchronize the configuration and firmware.
In the extremely unlikely situation of needing to replace an entire VCStack that is a
member of an AMF network, you can use AMF automatic node recovery to first recover
stack ID 1, which will become the VCstack master.
The procedure for recovering an entire stack is as follows:
1. Connect a clean device to the AMF network, and power it on. The connections into the
AMF network should be between the appropriately configured AMF links on the
neighboring node, and the ports previously configured as AMF links in the backup for
the failed node configuration.
2. The AMF network should detect the replacement device and begin automatic node
recovery. Wait until automatic node recovery completes and check that the
replacement device has come up correctly as VCStack ID 1, and that the configuration
is correct.
3. Configure the next replacement device as VCStack ID 2. Ensure it is installed with a
compatible release and the same set of licences that exist on ID 1. Connect the VCStack
cables and power it on.
4. VCStack ID 1 should detect ID 2 and synchronize the configuration and firmware
release. Once this has completed, check that the VCStack has formed correctly, and
then connect the remaining network connections.
For any additional VCStack members, repeat the last two steps, ensuring that the VCStack
ID is set to the next sequential value for each additional device that is added to the
VCStack.
Note
The replacement device which will become the VCStack master must be a clean
unit, (see the section