User guide

Configuring Virtual Chassis Configuring Virtual Chassis

page 13-18 OmniSwitch AOS Release 8 Switch Management Guide May 2014

Configuring Virtual Chassis

This section describes commands to configure virtual chassis on an OmniSwitch.

• “Virtual Chassis Configuration Guidelines” on page 13-18

• “Configuring the Chassis Identifier” on page 13-20

• “Configuring the Virtual Chassis Group Identifier” on page 13-20

• “Configuring the Hello Interval” on page 13-20

• “Configuring the Control VLAN” on page 13-21

• “Configuring Virtual Chassis EMP IP Addresses” on page 13-21

Note. See “Quick Steps for Automatically Configuring A Virtual Chassis” on page 13-5” for a brief tuto-

rial on configuring 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 are used for manu-

ally configuring the virtual chassis options. Many of these configuration options can be automatically

configured by the AOS software by incorporating switches into the virtual chassis without a vcsetup.cfg

file.

General

• One of the chassis will become the Master chassis while the remaining switches will become Slaves.

• 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.

Chassis Identifier

• Each chassis requires a chassis identifier that is unique within the virtual chassis group of topology. A

chassis identifier can be automatically or manually configured.

• 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 must be corrected by accessing the switch directly through the

local EMP port or a console connection.

• The chassis identifier is used to generate globally unique values for the module identifiers as well as

allowing inter-chassis communication.