Virtual Chassis Overview Configuring Virtual Chassis
page 9-8 OmniSwitch AOS Release 7 Network Configuration Guide June 2013
(CMM) of the master chassis. This parameter is stored in the vcboot.cfg configuration file in a switch oper-
ating in virtual chassis mode.
Chassis EMP Address - The local chassis management IP address (EMP-CHAS1 or EMP-CHAS2). This
is a configurable IP address that is automatically assigned to the primary chassis management module
(CMM) of the local chassis regardless of its master or slave role. This parameter is stored in the switch
specific vcsetup.cfg configuration file in a switch operating in virtual chassis mode.
Virtual Fabric Link (VFL) - A single or aggregated group of ports that connects the switches participat-
ing in the Virtual Chassis. As one of the basic building blocks of a Virtual Chassis configuration, the VFL
facilitates the flow of traffic and the transfer of control data between the Master and Slave chassis.
Control VLAN - A special type of VLAN reserved for the inter-chassis communication exchange
between the switches participating in a Virtual Chassis. Only VFL ports are assigned to this VLAN, and
no other ports are allowed to join the Control VLAN.
Remote Chassis Detection (RCD) protocol - Provides a back up mechanism for helping to detect a split-
chassis scenario.
vcsetup.cfg - A file containing information pertaining to the current physical switches, helping incorpo-
rate it into a virtual chassis. This file contains information such as Chassis ID, Group ID, Chassis priority,
control VLAN, chassis EMP IP addresses and VFL links.
vcboot.cfg - A file containing information pertaining to the virtual chassis as a whole including L2 and L3
configuration, management configuration, user ports configuration, etc. Similar to the boot.cfg file used in
standalone mode. The vcboot.cfg file is only used when a switch operates in virtual chassis mode.
Converting to Virtual Chassis mode
In order for a switch to become part of a virtual chassis it must first be converted from a standalone switch.
Virtual chassis operation requires the two files below to be created. They can be created manually or auto-
matically using the vc-takeover command.
• vcsetup.cfg - Virtual chassis setup file used to incorporate the physical chassis into the virtual chassis
topology.
• vcboot.cfg - Virtual chassis configuration file.
Before converting a standalone switch’s configuration keep the following in mind:
• The switches to be converted must have the proper licenses installed.
• The switches to be converted cannot have multi-chassis link aggregation configured.o A switch operat-
ing in multi-chassis link aggregation mode must be reconfigured to operate in standalone mode and
rebooted before the conversion to a virtual chassis can be automatically accomplished via the steps
described here. An alternative conversion from multi-chassis link aggregation mode to virtual chassis is
always possible manually. This can be achieved by manually creating both vcsetup.cfg and vcboot.cfg
files offline in the appropriate running directory and rebooting the switches.
Converting chassis mode using the CLI
The following shows an example of how to convert two switches that are in standalone mode to virtual
chassis mode.
• The VFL member ports configuration should reflect the switch’s current physical connections.