Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual page 790

Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
The payload of a Layer 3 ERSPAN packet is a copied Layer 2 Ethernet frame, excluding any ISL or
•
802.1Q tags.
• ERSPAN adds a 50-byte header to each copied Layer 2 Ethernet frame and replaces the 4-byte cyclic
redundancy check (CRC) trailer.
• ERSPAN supports jumbo frames that contain Layer 3 packets of up to 9,202 bytes. If the length of
the copied Layer 2 Ethernet frame is greater than 9,170 (9,152-byte Layer 3 packet), ERSPAN
truncates the copied Layer 2 Ethernet frame to create a 9,202-byte ERSPAN Layer 3 packet.
Regardless of any configured MTU size, ERSPAN creates Layer 3 packets that can be as long as
•
9,202 bytes. ERSPAN traffic might be dropped by any interface in the network that enforces an MTU
size smaller than 9,202 bytes.
With the default MTU size (1,500 bytes), if the length of the copied Layer 2 Ethernet frame is
•
greater than 1,468 bytes (1,450-byte Layer 3 packet), the ERSPAN traffic is dropped by any
interface in the network that enforces the 1,500-byte MTU size.
The mtu interface command and the system jumbomtu command (see the
Note
Support" section on page
is 9,216 bytes).
All participating switches must be connected at Layer 3 and the network path must support the size
•
of the ERSPAN traffic.
ERSPAN does not support packet fragmentation. The "do not fragment" bit is set in the IP header
•
of ERSPAN packets. ERSPAN destination sessions cannot reassemble fragmented ERSPAN
packets.
ERSPAN traffic is subject to the traffic load conditions of the network. You can set the ERSPAN
•
packet IP precedence or DSCP value to prioritize ERSPAN traffic for QoS.
The only supported destination for ERSPAN traffic is an ERSPAN destination session on a PFC3.
•
All ERSPAN source sessions on a switch must use the same origin IP address, configured with the
•
origin ip address command (see the
page
• All ERSPAN destination sessions on a switch must use the same IP address on the same destination
interface. You enter the destination interface IP address with the ip address command (see the
"Configuring ERSPAN Destination Sessions" section on page
The ERSPAN source session's destination IP address, which must be configured on an interface on
•
the destination switch, is the source of traffic that an ERSPAN destination session sends to the
destination ports. You configure the same address in both the source and destination sessions with
the ip address command.
The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from
•
various different ERSPAN source sessions.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
48-10
7-10) set the maximum Layer 3 packet size (default is 1,500 bytes, maximum
48-16).
Chapter 48 Configuring Local SPAN, RSPAN, and ERSPAN
"Configuring ERSPAN Source Sessions" section on
48-18).
"Configuring Jumbo Frame
OL-11439-03