Layer 3 Protocols - Cisco Catalyst 4500 series Administration Manual

Understanding Virtual Switching Systems
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
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
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.
SPAN on VSL ports is not supported; VSL ports can be neither a SPAN source, nor a SPAN destination.
Note
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
VLANs"

Layer 3 Protocols

The VSS Active supervisor engine runs the Layer 3 protocols and features for the VSS. All layer 3
protocol packets are sent to and processed by the VSS Active supervisor engine. Both member switches
perform hardware forwarding for ingress traffic on their interfaces. If possible, to minimize data traffic
that must traverse the VSL, ingress traffic is forwarded to an outgoing interface on the same switch.
When software forwarding is required, packets are sent to the VSS Active supervisor engine for
processing.
Software Configuration Guide—Release IOS XE 3.6.0E and IOS 15.2(2)SG
5-18
"Dual-Active Detection" section on page
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 details on how to configure the native VLAN on isolated trunk ports.
Chapter 5 Configuring Virtual Switching Systems
5-23.
Chapter 44, "Configuring Private
OL-30933-01