User guide

Configuring Virtual Chassis Configuring Virtual Chassis
OmniSwitch AOS Release 7 Switch Management Guide March 2015 page 12-19
Chassis Identifier
• Each switch requires a chassis identifier that is unique within the virtual chassis group of topology.
• If a duplicate chassis identifier is detected within the virtual chassis group then the chassis role will be
reported as inconsistent and the chassis status will be Duplicate-Chassis. The front-panel ports will not
be operational and the configuration should be corrected by accessing the switch directly via the local
EMP port.
• The chassis identifier is used to generate globally unique values for the module identifiers as well as
allowing inter-chassis communication.
• A switch 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 12-20
Virtual Chassis Group Identifier
• Each switch also requires a virtual chassis group identifier to identify the switch as belonging to that
specific virtual chassis topology.
• When determining the chassis group ID the last byte of the Master chassis MAC address is used. For
example, if the Master's MAC address is xx:xx:xx:xx:xx:7e, the chassis group will be 126 (the decimal
equivalent to hexadecimal 7e).
• The same group identifier must be assigned to each switch in the virtual chassis topology. Switches
belonging to other virtual chassis groups must use a different group identifier.
• If two or more switches 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 should be corrected by accessing the switch directly via local EMP port.
• 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. This configuration may cause problems for the RCD
(Remote Chassis Detection) protocol used to detect virtual chassis topology splits as well as other
unpredictable issues.
• 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 12-21.
Virtual Fabric Link (VFL)
• Individual protocols such as SFlow, ERP, UDLD and LLDP are not supported on VFLs and must not
be configured on ports belonging to a VFL. This situation may occur if a previous configuration, such
as MC-LAG, is converted to a Virtual Chassis configuration. It is highly recommended to review the
configuration carefully and make the necessary changes particularly when converting from MC-LAG
to VC.
• An operational VFL is a basic requirement to support a fully functional virtual chassis.
• The Link Aggregation Control Protocol (LACP) is used to mange and monitor the state of the VFL.