Configuring The Chassis Identifier - OmniSwitch os6900 Network Configuration Manual

Configuring Virtual Chassis
•
The member ports configured as part of the VFL are bundled to form a single logical link. All the
member ports must operate at the same speed.
•
To help avoid a split chassis scenario the last active VFL member port cannot be deleted or disabled.
Additionally, the last NI module hosting the last active member port cannot be administratively
powered down or reloaded.
•
The VFL automatically becomes a member of all VLANs configured on the switch.
•
VFL member ports can only be configured on interfaces that are fixed ports, network ports or PFC
enabled ports. For instance, interfaces configured as Q-tag ports or ERP ports cannot be configured as
VFL member ports.
•
The hello interval parameter must match between switches. The hello protocol runs across the VFL
between the switches.
•
Some traffic loss may be seen on VFL link when sending at wire rate. Since all packets that traverse
the VFL have an additional 16 byte header prepended to the packet this reduces the effective band-
width of a given VFL port.
For more information on Virtual Fabric Link, see
Control VLAN
•
The control VLAN is a reserved VLAN used for transporting control packets among the switches
comprising the virtual chassis.
•
Runtime configuration changes to the control VLAN will only take effect after the next reboot of the
switch.
•
The control VLAN must be the same between the switches comprising the virtual chassis.
For more information on the Control VLAN, see

Configuring the Chassis Identifier

To configure the Virtual Chassis feature, a unique chassis identifier must first be assigned to each of the
switches that will form the Virtual Chassis group. Assigning the chassis identifier also enables the config-
uration of the additional virtual chassis parameters for the switch.
The virtual-chassis configured-chassis-id
switch within the virtual chassis group. For example:
-> virtual-chassis configured-chassis-id 1
By default, the chassis identifier is set to "0". This indicates the switch is running in standalone mode,
which means that no virtual chassis functionality is available.
Duplicate chassis identifier
In the event two switches have the same operational chassis identifier value, one of them will be reported
as Inconsistent role (instead of Master or Slave) and Duplicate-Chassis status. This will cause the opera-
tional chassis identifier of one of the switches to be automatically renumbered to fall into the range (101-
102). This range is reserved to represent switches whose chassis identifier is duplicate. All management
interface commands must use this new operational chassis identifier to affect any configuration. The
duplicate chassis identifier must be corrected by re-configuring the switch locally via EMP port access.
OmniSwitch AOS Release 7 Network Configuration Guide
"Creating the Virtual Fabric Link (VFL)" on page 9-20
"Configuring the Control VLAN" on page 9-21
command is used to configure a unique chassis identifier for a
June 2013
Configuring Virtual Chassis
page 9-19