Vspan Guidelines And Restrictions; Rspan Guidelines And Restrictions - Cisco 6500 Series Software Configuration Manual
Hide thumbs
Also See for 6500 Series:
- Configuration manual (392 pages) ,
- Configuration note (212 pages) ,
- Installation manual (194 pages)
Table of Contents
Advertisement
Chapter 34
Configuring Local SPAN and RSPAN
•
•
•
•
•
VSPAN Guidelines and Restrictions
These are VSPAN guidelines and restrictions:
•
•
RSPAN Guidelines and Restrictions
These are RSPAN guidelines and restrictions:
•
•
•
•
•
•
•
•
•
78-14099-04
When enabled, local SPAN or RSPAN uses any previously entered configuration.
When you specify sources and do not specify a traffic direction (ingress, egress, or both), "both" is
used by default.
You cannot configure destination ports to receive ingress traffic.
Destination ports never participate in any spanning tree instance. Local SPAN includes BPDUs in
the monitored traffic, so any BPDUs seen on the destination port are from the source port. RSPAN
does not support BPDU monitoring.
All packets sent through the switch for transmission from a port configured as an egress source are
copied to the destination port, including packets that do not exit the switch through the port because
STP has put the port into the blocking state, or on a trunk port because STP has put the VLAN into
the blocking state on the trunk port.
For VSPAN sessions with both ingress and egress configured, two packets are forwarded from the
destination port if the packets get switched on the same VLAN (one as ingress traffic from the
ingress port and one as egress traffic from the egress port).
VSPAN only monitors traffic that leaves or enters Layer 2 ports in the VLAN.
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.
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 switches 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 those selected to carry RSPAN traffic.
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide—Release 12.1 E
Local SPAN and RSPAN Configuration Guidelines and Restrictions
34-7
Advertisement
Table of Contents
Troubleshooting
