Configuring A Source Rate Limit For Each Span Session - Cisco Nexus 7000 Series Configuration Manual

Configuring a Source Rate Limit for Each SPAN Session

Step 4
Step 5
Configuring a Source Rate Limit for Each SPAN Session
When a SPAN session is configured with multiple interfaces or VLANs as the sources in a high-traffic
environment, the destination port can be overloaded, causing the normal data traffic to be disrupted at the
source port. You can alleviate this problem as well as traffic overload on the source forwarding instance by
configuring a source rate limit for each SPAN session.
Note MTU truncation and the SPAN rate limit cannot be enabled for the same SPAN session on F1 Series
modules. If you configure both for one session, only the rate limit is allowed on F1 Series modules, and
MTU truncation is disabled until you disable the rate limit configuration. This limitation does not apply
to F2 and M2 Series modules or Supervisor 2.
SPAN sampling takes precedence over SPAN source rate limiting. Rate limiting takes effect after sampling
Note
is completed on SPAN source packets.
Before You Begin
Ensure that you are in the correct VDC (or use the switchto vdc command).
Procedure
Step 1
Cisco Nexus 7000 Series NX-OS System Management Configuration Guide
306
Command or Action
show monitor session session-number
Example:
switch(config)# monitor session 3
switch(config-monitor)#
copy running-config startup-config
Example:
switch(config)# copy running-config
startup-config
Command or Action
configure terminal
Example:
switch# configure terminal
switch(config)#
Purpose
(Optional) Displays the status of SPAN sessions,
including the configuration status of MTU
truncation, the maximum bytes allowed for each
packet per session, and the modules on which MTU
truncation is and is not supported.
(Optional)
Copies the running configuration to the startup
configuration.
Purpose
Enters global configuration mode.
Configuring SPAN