
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Inf ormation. Page 20 of 62
Multichassis Cisco EtherChannel Link Management Protocols
Multichassis Cisco EtherChannel links support both the Cisco proprietary Port Aggregation Protocol (PAgP) and the
LACP, both of which run on the active supervisor engine on the active virtual switch. Protocol frames that the standby
virtual switch receives are relayed to the active supervisor engine on the active virtual switch through the VSL.
Virtual Switch Mode
With the first release of software supporting the Cisco Virtual Switching System, you can run the switches in either
standalone mode or virtual mode. The default configuration is for the individual chassis to operate in standalone
mode. In order to migrate to virtual mode, you must perform a conversion procedure, outlined as follows.
After the chassis reloads and is operating in virtual mode, it begins the VSL initialization sequence. Additionally, the
interface naming convention is changed to allow for the specification of a chassis identifier as part of the interface
name. Please refer to the section “Operational Management” for more information.
Switch Identifier
Each chassis within the Cisco Virtual Switching System is allocated a unique chassis identifier upon conversion to
virtual switch mode. This identifier is known as the switch identifier, or switch ID. This number is used as part of the
interface naming to make sure that the interface name remains the same regardless of the active or standby virtual
switch roles.
As mentioned previously, this variable is set during the conversion phase; if a replacement supervisor engine is
required, it is set with an enable-mode command-line interface (CLI) command. The variable that has been set is
stored as a variable in ROMmon, so it is locally significant to the individual supervisor engine. If you need to alter the
switch ID, use the following CLI:
VSS#switch set switch_num 1
Set rommon‟s switch_num to 1
VSS#switch read switch_num
Read switch_num from rommon is 1
If there is a misconfiguration in switch IDs (when both switches have the same switch ID), the formation of the VSL
will fail on initialization. When the two chassis are being brought up as a single Cisco Virtual Switching System, the
VSL initialization handshake verifies that the switch IDs of the two chassis do not match. If the switch ID is found to
be in conflict, then the VSL will not become active. If this situation occurs, both chassis assume the role of active
virtual switch and you are informed of this conflict.
Conversion to Virtual Switch Mode
This section details the steps required to convert a standalone system into virtual switch mode. The interfaces
forming the VSL should be connected prior to the conversion process to minimize the number of times the chassis is
reloaded. Additionally, you should begin the conversion process using a default configuration because the conversion
process removes any previous configuration that exists on the standalone chassis.
Refer to Figure 13 to reference the conversion process.
Komentarze do niniejszej Instrukcji