
Configuring Virtual Chassis
Configuring Virtual Chassis
page 9-20
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
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.
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 identifier.
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
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 VFL Default VLAN
Traffic belonging to the VFL default VLAN will be sent across the VFL untagged. In addition, the VFL
automatically becomes a member of any additional VLANs configured on the virtual chassis as tagged
VLANs.
To configure the VFL default VLAN, use the
virtual-chassis vf-link default-vlan
ple:
-> virtual-chassis vf-link 0 default-vlan 2
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 periodi-
cally 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
depart from the master chassis' settings to assume the
Inconsistent
role and
Misconfigured-Hello-Interval
status.