• The span-threshold least value has been updated from 0 to 2. When you set the span-threshold to a lowest
value of 2, the SPAN buffer occupied is 528. When you use the negate command no hardware profile
buffer span-threshold 2, the span-threshold value is 208. The default value is lesser then the least value
of span-threshold.
• When a source interface in a SPAN session is operationally down, then that SPAN session will not go
operationally down. This behavior does not impact any functionality
• SPAN filtering supports only 16 filters. These filters can be a combination of VLAN-based, IP-based,
and MAC-based filters.
• When a SPAN session is configured with a multicast router port being the source port, the destination
port sees all the multicast traffic even when there is no traffic that is actually being forwarded to the
source port. This is due to a current limitation of the multicast/SPAN implementation.
• SPAN filtering is applicable for all the traffic of the switch except the SPAN source interface traffic.
• You can configure only one IP-based, one MAC-based and one VLAN-based filter per SPAN session.
• The number of filters is further restricted by the number of SPAN sessions and the type of source as
follows:
• A maximum of 8 MAC-based, 8 IP-based or 8 VLAN-based filters can be configured.
• A maximum of 4 IP-based, 4 MAC-based or 4 VLAN-based filters can be attached to all
interface-based SPAN sessions.
• A maximum of 8 IP-based, 8 MAC-based or 8 VLAN-based filters can be attached to all VLAN-based
SPAN sessions.
• Filters can be used only in the ingress direction. This is not configurable.
• A SPAN session must be up to for filters to work.
• You cannot configure filters on ERSPAN-dst sessions.
• You cannot configure filters on Warp SPAN sessions.
• The control-packet filter is always applied in the egress direction.
• The control-packet filter is recommended when both, the source and the destination interfaces of the
ERSPAN session are PTP enabled.
SPAN and ERSPAN Control-packet Filtering
Cisco NX-OS Release 6.0(2)A8(9) provides the ability to filter out CPU generated packets going out of the
SPAN source interface. Control-packet filter is applied in the egress direction, and is therefore effective on
source interfaces enabled for Tx mirroring.
SPAN and ERSPAN Sampling
Cisco NX-OS Release 6.0(2)A4(1) supports sampling of source packets for each SPAN or ERSPAN session.
Monitoring only a sample number of source packets helps reduce SPAN or ERSPAN bandwidth. This sample
is defined by a range that you can configure. For example, if you configure the range as 2, 1 out of every 2
Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 7.x
136
Configuring SPAN
SPAN and ERSPAN Control-packet Filtering
To Next Page
Loading...
