User guide

Configuring Virtual Chassis Configuring Virtual Chassis
OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 13-19
• A chassis reboot is required for a newly configured chassis identifier to take effect.
For information about configuring the Chassis ID, see “Configuring the Chassis Identifier” on page 13-20
Virtual Chassis Group Identifier
• Each chassis also requires a virtual chassis group identifier to identify the chassis belonging to that
specific virtual chassis topology.
• The same group identifier must be assigned to each chassis in the virtual chassis topology. Switches
belonging to other virtual chassis groups should use a different group identifier.
• If two or more chassis within the same virtual chassis group do not have the same group identifier
configured, the chassis role will be reported as Inconsistent and the chassis status will be Mismatch-
Chassis-Group. The front-panel user ports will not be brought to an operational state. The configura-
tion must be corrected by accessing the chassis directly.
• If two or more separate virtual chassis groups use the same group identifier, this inconsistency is not
detected or corrected by the virtual chassis functionality. It is up to the administrator to ensure that
each domain uses a unique group identifier.
• The virtual chassis group identifier is used to select a globally unique virtual MAC address for each
virtual chassis group to avoid duplicate MAC addresses in a network that may contain more than one
virtual chassis group.
For information about configuring the chassis group identifier, see “Configuring the Virtual Chassis
Group Identifier” on page 13-20.
Virtual Fabric Link (VFL)
• An operational VFL is a basic requirement to support a fully functional virtual chassis. OmniSwitch
6860/6860E have dedicated VFL ports.
• Explicitly configuring the VFL and the physical port members is not supported, this function is auto-
matically configured and is not user-configurable. The lowest numbered VFL port is VFL 0 and the
highest numbered VFL port is VFL 1.
• It is recommended to connect the chassis using the VFL ports prior to booting the switch.
• Only the dedicated VFL ports can be members of a VFL.
• With a Virtual Chassis consisting of two chassis, the VFL ports are bundled to form a single link
aggregate VFL 0.
• For increased resiliency and to help avoid a split chassis scenario it is strongly recommend to have the
VFL ports connected in a ring topology.
• The VFL automatically becomes a member of all VLANs configured on the chassis.
For more information on Virtual Fabric Link, see “Configuring the Hello Interval” on page 13-20
Control VLAN
• The control VLAN is a reserved VLAN used for transporting control packets among the chassis
comprising the virtual chassis.
• Runtime configuration changes to the control VLAN will only take effect after the next reboot of the
chassis.