Cisco Catalyst 4500 Series, Руководство по настройке программного обеспечения

Страница: 243 / 2086

5-17
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 5 Configuring Virtual Switching Systems
Understanding Virtual Switching Systems
•
Private VLANs, page 5-17
Spanning Tree Protocol
The VSS Active switch runs Spanning Tree Protocol (STP). The VSS Standby switch redirects STP
BPDUs across the VSL to the VSS Active switch.
The STP bridge ID is commonly derived from the chassis MAC address. To ensure that the bridge ID
does not change after a switchover, the VSS continues to use the original chassis MAC address for the
STP Bridge ID.
EtherChannel Control Protocols
Link Aggregation Control Protocol (LACP) and Port Aggregation Protocol (PAgP) packets contain a
device identifier. The VSS defines a common device identifier for both chassis. You should use PAgP or
LACP on MECs instead of mode ON, although all three modes are supported.
A new PAgP enhancement has been defined for assisting with dual-active scenario detection. For
additional information, see the
“Dual-Active Detection” section on page 5-23 .
Jumbo frame size restriction
The maximum jumbo frame size supported on a VSS interface is 9188 bytes (MTU of 9170 bytes). This
accommodates the overhead of transporting packets between the two member switches over VSL.
Not all frames traverse VSL. So, packets confined to one of the member switches could have a size of
9216 bytes (MTU of 9198 bytes). Such frames may require diversion over VSL when a failure occurs.
This is why the
max configured MTU on non-VSL front panel ports is 9170.
Note
The MTU CLI is unavailable on a VSL interface. It is set internally to 9198 (Max frame size of
9216), addressing the overhead of VSL.
For example, if we send traffic between two ports on the active switch, no overhead exists. However,
overhead exists when we send packets between ports of active to ports of standby. Even more overhead
exists when we send packets from standby ports to the active CPU. The higher limit accommodates the
worst case and guarantees consistent forwarding under all scenarios.
SPAN
VSS supports all SPAN features for non-VSL interfaces.
Note
SPAN on VSL ports is not supported; VSL ports can be neither a SPAN source, nor a SPAN destination.
The number of SPAN sessions available on a VSS matches that on a single switch running in standalone
mode.
Private VLANs
Private VLANs on VSS work similarly in standalone mode. The only exception is that the native VLAN
on isolated trunk ports must be configured explicitly. Refer to
Chapter 47, “Configuring Private
VLANs” for details on how to configure the native VLAN on isolated trunk ports.