• Service profile vHBA
• FCoE port
• Port channels
• Server port
AFibre Channel traffic monitoring session can monitor any of the following traffic sources:
• Uplink Fibre Channel port
• SAN port channel
• VSAN
• Service profile vHBA
• Fibre Channel storage port
Guidelines and Recommendations for Traffic Monitoring
Whenconfiguring oractivating traffic monitoring, consider the following guidelines:
• Youcan create and store up to 16 traffic monitoring sessions, but only two can be active at the same
time.
• A trafficmonitoring session is disabled by default when created. To begin monitoring traffic, you must
activatethe session.
• Tomonitor traffic from a server, add all vNICs from the service profile corresponding to the server.
• Youcan 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
Ethernetdestination port, thedestination traffic will be FCoE.
•Becausea traffic monitoring destination is a single physical port, a traffic monitoring session can monitor
onlya single fabric. To monitor uninterrupted vNIC traffic across a fabric failover, you must create two
sessions—oneper fabric—and connect two analyzers. Add the vNIC as the traffic source for both
sessions.
• All trafficsources 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
configuredas a source, all member ports are source ports.
• A vHBA can be a source for either an Ethernet or Fibre Channel monitoring session, but it cannot be a
sourcefor both simultaneously.
• A server port can be a source only if it is a non-virtualized rack server adapter-facing port.
• 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
removedfrom monitoring, and you must reconfigure the monitoring session.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
642 OL-25712-04
Guidelines and Recommendations for Traffic Monitoring