User guide

Automatically Setting up a Virtual Chassis Configuring Virtual Chassis
page 12-32 OmniSwitch AOS Release 7 Switch Management Guide March 2015
virtual-chassis auto-vf-link-port 1/1/21
virtual-chassis auto-vf-link-port 1/1/22
virtual-chassis auto-vf-link-port 1/1/23
virtual-chassis auto-vf-link-port 1/1/24
virtual-chassis auto-vf-link-port 1/1/25 (this port has not become VFL, i.e. link
is down)
After issuing the virtual-chassis vf-link-mode static command the VFL mode is converted from auto to
static. All auto VFL ports that have become VFL member ports are converted to static VFL with their
current VFL IDs.
For example, below is the new configuration after the mode is converted to static:
virtual-chassis chassis-id 1 configured-chassis-id 1
virtual-chassis vf-link-mode static
virtual-chassis chassis-id 1 vf-link 0 create
virtual-chassis chassis-id 1 vf-link 0 member-port 1/1/23
virtual-chassis chassis-id 1 vf-link 0 member-port 1/1/24
virtual-chassis chassis-id 1 vf-link 1 create
virtual-chassis chassis-id 1 vf-link 1 member-port 1/1/21
virtual-chassis chassis-id 1 vf-link 1 member-port 1/1/22
Please note the following:
• There is no entry for port 1/1/25 in the new configuration because at the time of the conversion
port 1/1/25 was not part of a VFL and there is no way to know which VFL ID this port belongs to.
• Use the write memory command to save the new configuration.
Automatic Chassis ID Assignment
As part of the automatic VC feature, each chassis will also automatically be assigned a chassis ID. Auto-
matic chassis ID assignment happens when a chassis boots up without vcsetup.cfg. This is the case for a
new 'out-of-the-box' chassis. On its first bootup, a vcsetup.cfg file will be created and a chassis ID will be
assigned and stored in the newly created vcsetup.cfg file. On subsequent reboots, this chassis will use the
chassis ID that was configured in vcsetup.cfg. As long as the vcsetup.cfg file exists, automatic chassis ID
assignment will not be attempted.
When an out-of-the-box chassis boots up, it will have temporary chassis ID of 1 and a special flag indicat-
ing that this chassis needs a chassis ID assigned. After VC discovery process is completed, master elec-
tion process will take place and a master chassis will be elected based on the master election parameters
(chassis priority, uptime, chassis-id, and chassis MAC address).
Master will assign each chassis in the VC (including itself) a unique chassis ID based on the chassis ID
assignment algorithm. Each chassis will store its newly assigned chassis ID by writing it in vcsetup.cfg
file, so this chassis id can be used in subsequent reboots. After receiving its newly assigned chassis id,
each slave chassis will reboot for the new chassis id to take effect. Master will not reboot.
For Master election, chassis with configured chassis id will always win over chassis with temporary chas-
sis id (has no vcsetup.cfg).