Configuring Virtual Chassis Configuring Virtual Chassis
page 9-18 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
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 9-19
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.
• 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 9-20.
Virtual Fabric Link (VFL)
• 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.
• Explicitly configuring the VFL and the physical port members is required. It’s recommended to config-
ure the VFL during network maintenance time or when the virtual chassis is first configured. Changing
the VFL configuration at runtime is supported but should be performed with caution as an incorrect
VFL configuration can cause undesirable disruption to traffic flows.
• It is recommended to configure the VFL at the same time as the chassis identifier. This ensures that the
switch reboots with the correct VFL configuration.
• For increased resiliency, there should be a minimum of two member ports and they should be distrib-
uted across different port groups and NI modules.
• Only physical ports operating at 10-Gbps (not including 10GBaseT) or 40-Gbps can be members of a
VFL. Additionally, 10-Gbps and 40-Gbps links cannot be mixed in the same VFL. Any type of 10Gbps
or 40-Gbps transceiver or direct-attached cable can be used for creating the VFL.
• 10GBase-T ports cannot be members of a VFL.
To Next Page
Loading...
Need help?
General