Rspan Guidelines And Restrictions; Erspan Guidelines And Restrictions - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Software configuration guide
Hide thumbs Also See for WS-SUP32-GE-3B - Supervisor Engine 32:
Table of Contents

Advertisement

Chapter 48
Configuring Local SPAN, RSPAN, and ERSPAN

RSPAN Guidelines and Restrictions

These are RSPAN guidelines and restrictions:

ERSPAN Guidelines and Restrictions

These are ERSPAN guidelines and restrictions:
OL-11439-03
If you configure a VLAN as an ingress source and traffic gets routed into the monitored VLAN,
the routed traffic is not monitored because it never appears as ingress traffic entering a Layer 2
port in the VLAN.
If you configure a VLAN as an egress source and traffic gets routed out of the monitored VLAN,
the routed traffic is not monitored because it never appears as egress traffic leaving a Layer 2
port in the VLAN.
Supervisor Engine 2 does not support RSPAN if you configure an egress SPAN source for a local
SPAN session.
Supervisor Engine 2 does not support egress SPAN sources for local SPAN if you configure RSPAN.
All participating switches must be trunk-connected at Layer 2.
Any network device that supports RSPAN VLANs can be an RSPAN intermediate device.
Networks impose no limit on the number of RSPAN VLANs that the networks carry.
Intermediate network devices might impose limits on the number of RSPAN VLANs that they can
support.
You must configure the RSPAN VLANs in all source, intermediate, and destination network devices.
If enabled, the VLAN Trunking Protocol (VTP) can propagate configuration of VLANs numbered
1 through 1024 as RSPAN VLANs. You must manually configure VLANs numbered higher than
1024 as RSPAN VLANs on all source, intermediate, and destination network devices.
If you enable VTP and VTP pruning, RSPAN traffic is pruned in the trunks to prevent the unwanted
flooding of RSPAN traffic across the network.
RSPAN VLANs can be used only for RSPAN traffic.
Do not configure a VLAN used to carry management traffic as an RSPAN VLAN.
Do not assign access ports to RSPAN VLANs. RSPAN puts access ports in an RSPAN VLAN into
the suspended state.
Do not configure any ports in an RSPAN VLAN except trunk ports selected to carry RSPAN traffic.
MAC address learning is disabled in the RSPAN VLAN.
You can use output access control lists (ACLs) on the RSPAN VLAN in the RSPAN source switch
to filter the traffic sent to an RSPAN destination.
RSPAN does not support BPDU monitoring.
Do not configure RSPAN VLANs as sources in VSPAN sessions.
You can configure any VLAN as an RSPAN VLAN as long as all participating network devices
support configuration of RSPAN VLANs and you use the same RSPAN VLAN for each RSPAN
session in all participating network devices.
For ERSPAN packets, the "protocol type" field value in the GRE header is 0x88BE.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
48-9

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Catalyst supervisor engine 32 pisa

Table of Contents