User guide

Configuring Virtual Chassis Configuring Virtual Chassis
OmniSwitch AOS Release 7 Switch Management Guide March 2015 page 12-21
The virtual-chassis configured-chassis-id command is used to configure a unique chassis identifier for a
switch within the virtual chassis group. For example:
-> virtual-chassis configured-chassis-id 1
By default, the chassis identifier is set to “0”. This indicates the switch is running in standalone mode,
which means that no virtual chassis functionality is available.
Duplicate chassis identifier
In the event two switches have the same operational chassis identifier value, one of them will be reported
as Inconsistent role (instead of Master or Slave) and Duplicate-Chassis status. This will cause the opera-
tional chassis identifier of one of the switches to be automatically renumbered to fall into the range (101-
102). This range is reserved to represent switches whose chassis identifier is duplicate. All management
interface commands must use this new operational chassis identifier to affect any configuration. The
duplicate chassis identifier must be corrected by re-configuring the switch locally via EMP port access.
Configuring the Virtual Chassis Group Identifier
A virtual chassis group identifier must be assigned to each of the switches that will form the Virtual Chas-
sis group. Each of these switches must use the same group identifier, which identifies the switch as
belonging to that virtual chassis group.
The virtual-chassis chassis-group command is used to configure the same group identifier for each
switch within the virtual chassis group. For example:
-> virtual-chassis chassis-group 1
By default, the virtual chassis group identifier is set to “0”. In a network environment where more than
one virtual chassis group may exist, configure each virtual chassis group with its own unique group identi-
fier. Duplicate group identifiers are not supported.
Creating the Virtual Fabric Link (VFL)
The VFL is an aggregate of high-speed ports used for inter-chassis user traffic and control data. For a
virtual chassis group to become operational, a VFL must be configured and brought to an operational
state.
To configure a VFL and its member ports, use the virtual-chassis vf-link create and virtual-chassis vf-
link member-port commands. For example:
-> virtual-chassis vf-link 0 create
-> virtual-chassis vf-link 0 member-port 1/1
-> virtual-chassis vf-link 0 member-port 1/24
Configuring the Hello Interval
Hello packets are used for establishing and maintaining the neighbor relationship between virtual chassis
switches and ensures that communication between switches is bidirectional. Hello packets are sent period-
ically out VFL interfaces. Bidirectional communication is indicated when the switch sees itself listed in
the neighbor's hello packet. The hello interval value determines how often these packets are sent.
It is recommended that the same hello interval be used for all switches that will participate on the same
virtual chassis topology. Failure to adhere to this recommendation will lead the switches whose values