Configuring Virtual Chassis Quick Steps for Configuring A Virtual Chassis
OmniSwitch AOS Release 7 Network Configuration Guide June 2013 page 9-5
Quick Steps for Configuring A Virtual Chassis
Follow the steps below for a quick tutorial on configuring two switches to operate as a Virtual Chassis.
Additional information on how to configure a Virtual Chassis is provided in the section “Configuring
Virtual Chassis” on page 9-17.
A switch running in standalone mode can be converted to a Virtual Chassis participant by using the CLI to
create the required vcsetup.cfg and vcboot.cfg files. The virtual chassis configuration can be kept in any
directory, including the /flash/working directory. The example below uses a new directory named vc_dir.
The minimum configuration requirements for a switch to operate in virtual chassis mode are:
• A valid advanced license must be installed.
• A vcsetup.cfg file must be present in the running directory and it must have, at least, a valid chassis
identifier and virtual-fabric link configured. Additionally for the switch to join a virtual chassis topol-
ogy, the virtual-fabric link must have member ports assigned to it and the underlying interfaces admin-
istratively enabled.
• A vcboot.cfg file containing the generic virtual chassis configuration present must be present in the
running directory.
Note: Multi-Chassis Link Aggregation cannot be configured on a switch prior to converting it to virtual
chassis mode. The MC-LAG configuration must first be removed.
Virtual Chassis Conversion
1 Enter the following on each switch using the appropriate port numbers based on the chassis physical
connections. Note that vc_dir is the name of the directory where the virtual chassis configuration will be
stored, it will be automatically created if it does not exist.
Chassis_1-> virtual-chassis configured-chassis-id 1
Chassis_1-> virtual-chassis vf-link 0 create
Chassis_1-> virtual-chassis vf-link 0 member-port 1/1
Chassis_1-> virtual-chassis vf-link 0 member-port 1/24
Chassis_1-> write memory
Chassis_1-> convert-configuration to vc_dir
Chassis_2-> virtual-chassis configured-chassis-id 2
Chassis_2-> virtual-chassis vf-link 0 create
Chassis_2-> virtual-chassis vf-link 0 member-port 1/1
Chassis_2-> virtual-chassis vf-link 0 member-port 1/24
Chassis_2-> write memory
Chassis_2-> convert-configuration to vc_dir
2 Reload both chassis from the newly created vc_dir directory:
Chassis_1-> reload from vc_dir no rollback-timeout
Chassis_2-> reload from vc_dir no rollback-timeout
To Next Page
Loading...
Need help?
General