When configuring or
activating traffic monitoring, consider the following guidelines:
Traffic Monitoring Sessions
A traffic monitoring session is disabled by default when created. To
begin monitoring traffic, you must activate the session. A traffic monitoring
session must be unique on any fabric interconnect within the Cisco UCS pod. You
must create each monitoring session with a unique name and unique VLAN source.
To monitor traffic from a server, add all vNICs from the service profile
corresponding to the server.
Maximum Number of
Supported Active Traffic Monitoring Sessions per Fabric-Interconnect
You can create and store up to 16
traffic monitoring sessions, but only four can be active at the same time. For
each UCS 6300 Fabric Interconnect, you can only monitor up to 4 traffic
directions. The receive and transmit directions each count as 1 monitoring
session, while the bi-direction monitoring session is counted as 2. For
sessions — If each session is configured to monitor traffic in only one
sessions — If each session is configured to monitor traffic bi-directionally.
sessions — If one session is uni-directional and the second session is
can impose a significant load on your system resources. To minimize the load,
select sources that carry as little unwanted traffic as possible and disable
traffic monitoring when it is not needed.
Because a traffic monitoring destination is a single physical port, a
traffic monitoring session can monitor only a single fabric. To monitor
uninterrupted vNIC traffic across a fabric failover, you must create two
sessions—one per fabric—and connect two analyzers. Add the vNIC as the traffic
source using the exact same name for both sessions. If you change the port
profile of a virtual machine, any associated vNICs being used as source ports
are removed from monitoring, and you must reconfigure the monitoring session.
If a traffic monitoring session was configured on a dynamic vNIC under a
release earlier than
Cisco UCS Manager Release 2.0, you must reconfigure the traffic
monitoring session after upgrading.
A vHBA can be a source for either an
Ethernet or Fibre Channel monitoring session, but it cannot be a source for
both simultaneously. When a VHBA is set as the SPAN source, the SPAN
destination only receives VN-Tagged frames. It does not receive direct FC