User guide

Configuring Virtual Chassis Configuring Virtual Chassis
page 12-18 OmniSwitch AOS Release 7 Switch Management Guide March 2015
Configuring Virtual Chassis
This section describes commands to configure virtual chassis on an OmniSwitch.
• “Virtual Chassis Configuration Guidelines” on page 12-18
• “Configuring the Chassis Identifier” on page 12-20
• “Configuring the Virtual Chassis Group Identifier” on page 12-21
• “Creating the Virtual Fabric Link (VFL)” on page 12-21
• “Configuring the Hello Interval” on page 12-21
• “Configuring the Control VLAN” on page 12-22
• “Configuring EMP IP Addresses” on page 12-22
Note. See “Quick Steps for Configuring A Virtual Chassis” on page 12-5” for a brief tutorial on configur-
ing these parameters on an OmniSwitch.
Virtual Chassis Configuration Guidelines
The following sections provide configuration guidelines to follow when configuring a virtual chassis on an
OmniSwitch. The configuration commands related to the virtual chassis functionality vary depending on
whether they are executed while a switch is operating in standalone mode (conversion process) or virtual
chassis mode (runtime configuration). The following guidelines focus on the initial configuration, when a
switch is still operating in standalone mode. For a thorough description of the configuration process while
a switch is already operating in virtual chassis mode, please refer to the CLI guide.
General
• Virtual chassis functionality is only active for switches on which a valid chassis identifier is config-
ured.
• One of the chassis will become the Master chassis while the remaining switches will become Slaves.
• A virtual chassis cannot contain a mix of OS6900 and OS10K switches.
• Some of the virtual chassis parameters runtime modification only take effect after the next reboot of the
switch. These parameters are chassis identifier, chassis priority, control VLAN and hello interval. For
this type of parameters, the following terminology is used.
• Operational values - The current or running values, are those in effect at the present time.
• Configured values - The next or future values are those that are currently configured or set, but that
are not in effect at the present time. These values will only become effective after the next reboot of
the switch.
• When a new chassis is added to an existing virtual chassis the new chassis will reboot two times under
any of the following conditions:
• The new chassis has a different running configuration directory name than the existing VC.
• The new chassis has different images than the existing VC.
• The new chassis has a different vcboot.cfg file than the existing VC.