The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
Traffic monitoring copies traffic from one or more sources and sends the copied traffic to a dedicated destination port for analysis by a network analyzer. This feature is also known as Switched Port Analyzer (SPAN).
You can monitor or use SPAN on port channels only for ingress traffic.
When you create a traffic monitoring session, you can choose either an Ethernet or Fibre Channel destination port to receive the traffic. The type of destination port determines the type of session, which in turn determines the types of available traffic sources. For an Ethernet traffic monitoring session, the destination port must be an unconfigured physical port. For a Fibre Channel traffic monitoring session, the destination port must be a Fibre Channel uplink port.
An Ethernet traffic monitoring session can monitor any of the following traffic sources:
Uplink Ethernet port
Ethernet port channel
VLAN
Service profile vNIC
Service profile vHBA
FCoE port
Port channels
Unified uplink port
A Fibre Channel traffic monitoring session can monitor any of the following traffic sources:
Fibre Channel, Fibre Channel over Ethernet, vHBA, VSAN, and SAN are not supported in Cisco UCS Release 2.5
You can create and store up to 16 traffic monitoring sessions, but only two can be active at the same time.
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. Therefore, 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.
You can monitor Fibre Channel traffic using either a Fibre Channel traffic analyzer or an Ethernet traffic analyzer. When Fibre Channel traffic is monitored using an Ethernet traffic monitoring session, with an Ethernet destination port, the destination traffic will be FCoE.
Fibre Channel and Fibre Channel over Ethernet are not supported in Cisco UCS Manager Release 2.5.
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 for both sessions.
All traffic sources must be located within the same switch as the destination port.
A port configured as a destination port cannot also be configured as a source port.
A member port of a port channel cannot be configured individually as a source. If the port channel is configured as a source, all member ports are source ports.
A Fibre Channel port on a Cisco UCS 6248 fabric interconnect cannot be configured as a source port.
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.
SPAN traffic is rate-limited to 1 Gbps on Cisco UCS 6200 Series fabric interconnects.
Note | Traffic monitoring 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. |
Step 1 | In the Navigation pane, click the LAN tab. | ||||||
Step 2 | On the LAN tab, expand . | ||||||
Step 3 | In the Work pane, click the General tab. | ||||||
Step 4 | In the Actions area, click Set Destination. | ||||||
Step 5 | In the Set Destination dialog box, complete the following fields: Example:
| ||||||
Step 6 | Click OK. |
Step 1 | In the Navigation pane, click the SAN tab. | ||||||||||
Step 2 | On the LAN tab, expand . | ||||||||||
Step 3 | Right-click Fabric_Interconnect_Name and choose Create Traffic Monitoring Session. | ||||||||||
Step 4 | In the Create Traffic Monitoring Session dialog box, complete the following fields:
| ||||||||||
Step 5 | Click OK. |
Step 1 | In the Navigation pane, click the SAN tab. | ||||||
Step 2 | On the SAN tab, expand . | ||||||
Step 3 | In the Work pane, click the General tab. | ||||||
Step 4 | In the Actions area, click Set Destination. | ||||||
Step 5 | In the Set Destination dialog box, complete the following fields:
| ||||||
Step 6 | Click OK. |
You can choose multiple sources from more than one source type to be monitored by a traffic monitoring session. The available sources depend on the components configured in the Cisco UCS domain.
Note | This procedure describes how to add sources for Ethernet traffic monitoring sessions. To add sources for a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. |
A traffic monitoring session must be created.
Step 1 | In the Navigation pane, click the LAN tab. |
Step 2 | On the LAN tab, expand . |
Step 3 | Expand Fabric_Interconnect_Name and click the monitor session that you want to configure. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Sources area, expand the section for the type of traffic source that you want to add. |
Step 6 | To see the components that are available for monitoring, click the + button in the right-hand edge of the table to open the Add Monitoring Session Source dialog box. |
Step 7 | Select a source component and click OK.
You can repeat the preceding three steps as needed to add multiple sources from multiple source types. |
Step 8 | Click Save Changes. |
Activate the traffic monitoring session. If the session is already activated, traffic will be forwarded to the monitoring destination when you add a source.
Note | This procedure describes how to activate an Ethernet traffic monitoring session. To activate a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. |
A traffic monitoring session must be created.
Step 1 | In the Navigation pane, click the LAN tab. |
Step 2 | On the LAN tab, expand . |
Step 3 | Expand Fabric_Interconnect_Name and click the monitor session that you want to activate. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Properties area, click the enabled radio button for Admin State. |
Step 6 | Click Save Changes. |
If a traffic monitoring source is configured, traffic begins to flow to the traffic monitoring destination port.
Note | This procedure describes how to delete an Ethernet traffic monitoring session. To delete a Fibre Channel monitoring session, select the SAN tab instead of the LAN tab in Step 2. |
Step 1 | In the Navigation pane, click the LAN tab. |
Step 2 | On the LAN tab, expand . |
Step 3 | Expand Fabric_Interconnect_Name and click the monitor session that you want to delete. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click the Delete icon. |
Step 6 | If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |