Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) - Manual (Page 2122)

VCStack Introduction
Software Reference for x310 Series Switches
82.8 AlliedWare Plus TM Operating System - Version 5.4.4C C613-50046-01 REV A
The stack also assigns a stack-ID number to each member. This number provides a
unique reference number for switches within the stack; it plays no part in selecting the
stack master. The stack-ID is used as the first digit of the three component port
identifier numbers. For example, port number 2.0.14 has the stack-ID of 2.
You can change the stack-ID by using the stack renumber command on page 83.22 .
Common Stack Configuration
Once the switches have configured themselves into a VCStack, they all share the same
configuration information and startup scripts.
Stack Management VLAN
Managing the stack is the same as managing an individual switch. You can connect to the
asynchronous console port of any stack member, or you can set an IP address on a
network VLAN (for example, VLAN 1) and use SSH for remote access.
As the switches form themselves into a stack, each switch creates a common stack
management VLAN and a management IP address. Both the VLAN ID and the IP address
are internal entities that are used between the stacked switches, via the stacking ports,
and therefore do not appear on the user network.
Initially the stack assigns the default VLAN tag ID of 4094 to the management VLAN, and
assigns an IP address from the subnet 192.168.255.0/27 to this VLAN as the management
IP address. Once the stack has formed, you can change both these settings. To change the
VLAN ID use the
stack management vlan command on page 83.20 . To change the
management IP address use the stack management subnet command on page 83.19 .
Note however, that you must keep the 27 bit subnet mask, (/27 or 255.255.255.224).
Also note that the management VLAN ID and management IP subnet must be unique
across the stack’s internal and external network. This means you cannot use the
management VLAN ID or management IP subnet elsewhere in the user network. However,
note that stacks in the same network can all use the same management VLAN ID and
management IP subnet settings internally. To view the current settings for the stack
management VLAN ID and IP address, use the
show stack command on page 83.11 .
Note This last point is an important one to remember when using configuration
scripts. You should ensure that you modify your configuration scripts to match
any changes you have made to the stack-ID assignments.
Note The ability to independently set both a stack member’s priority and its ID
means that the stack master does not need to have an ID of 1, although
configuration is simplified by arranging for ID 1 to be the device with the
lowest priority value - and thereby forcing it to be the stack master. If you
create a stack using new switches, the following (simplified) process should
ensure that the master member has an ID of 1.
New switches are shipped with a Stack Member-ID of 1 and a priority of 128. If
four such switches are created as a stack, the switch with the lowest MAC
address will be selected to be the stack master (because all priority settings are
128). The remaining three stack member devices will then reboot. The stack
master does not reboot and retains its Stack Member-ID of 1.