Vss configuration guidelines and restrictions, General vss restrictions and guidelines, Vsl restrictions and guidelines – Cisco 6500 User Manual

Page 27

Advertising
background image

4-27

Cisco IOS Software Configuration Guide, Release 12.2SX

OL-13013-06

Chapter 4 Configuring Virtual Switching Systems

VSS Configuration Guidelines and Restrictions

VSL Down

If the VSL is down when both chassis try to boot up, the situation is similar to a dual-active scenario.

One of the chassis becomes VSS active and the other chassis initiates recovery from the dual-active
scenario. For further information, see the

“Configuring Dual-Active Detection” section on page 4-45

.

VSS Configuration Guidelines and Restrictions

The following sections describe restrictions and guidelines for VSS configuration:

•

General VSS Restrictions and Guidelines, page 4-27

•

VSL Restrictions and Guidelines, page 4-27

•

Multichassis EtherChannel Restrictions and Guidelines, page 4-28

•

Dual-Active Detection Restrictions and Guidelines, page 4-28

•

Service Module Restrictions and Guidelines, page 4-29

•

Configuring a VSS, page 4-29

General VSS Restrictions and Guidelines

When configuring the VSS, note the following guidelines and restrictions:

•

The VSS configurations in the startup-config file must match on both chassis.

•

If you configure a new value for switch priority, the change takes effect only after you save the
configuration file and perform a restart.

•

Enable the out-of-band MAC address table synchronization among DFC-equipped switching
modules by entering the mac-address-table synchronize command.

VSL Restrictions and Guidelines

When configuring the VSL, note the following guidelines and restrictions:

•

For line redundancy, we recommend configuring at least two ports per switch for the VSL. For
module redundancy, the two ports can be on different switching modules in each chassis.

•

The no mls qos channel-consistency command is automatically applied when you configure the
VSL. Do not remove this command.

•

VSL ports cannot be Mini Protocol Analyzer sources (the monitor ... capture command). Monitor
capture sessions cannot be started if a source is the VSL on the port channel of the standby switch.
The following message is displayed when a remote VSL port channel on the standby switch is
specified and you attempt to start the monitor capture:

% remote VSL port is not allowed as capture source

The following message is displayed when a scheduled monitor capture start fails because a source
is a remote VSL port channel:

Packet capture session 1 failed to start. A source port is a remote VSL.

Advertising