- Traffic Monitoring
- Guidelines and Recommendations for Traffic Monitoring
- SPAN Ports Support Matrix
- Setting Policy Control to Global
- Creating a Traffic Monitoring Session for an Ethernet Port
- Setting the Destination Interface and Destination Aggregate Interface for Ethernet Ports
- Creating a Traffic Monitoring Session for a Fibre Channel Port
- Adding Appliance Port as a Monitoring Source
- Adding an Ethernet Uplink as a Monitoring Source
- Adding Ethernet Port Channel as a Monitoring Source
- Adding Ethernet Server Port as a Monitoring Source
- Adding an FC Uplink Port as a Monitoring Source
- Adding an FC Port Channel as a Monitoring Source
- Adding an FC Storage Port as a Monitoring Source
- Adding an FCoE Uplink Port as a Monitoring Source
- Adding an FCoE Port Channel as a Monitoring Source
- Adding an FCoE Storage Port as a Monitoring Source
- Adding a vLAN as a Monitoring Source
- Adding a vSAN as a Monitoring Source
- Adding a vHBA as a Monitoring Source
- Adding a vNIC as a Monitoring Source
Traffic
Monitoring
- Traffic Monitoring
- Guidelines and Recommendations for Traffic Monitoring
- SPAN Ports Support Matrix
- Setting Policy Control to Global
- Creating a Traffic Monitoring Session for an Ethernet Port
- Setting the Destination Interface and Destination Aggregate Interface for Ethernet Ports
- Creating a Traffic Monitoring Session for a Fibre Channel Port
- Adding Appliance Port as a Monitoring Source
- Adding an Ethernet Uplink as a Monitoring Source
- Adding Ethernet Port Channel as a Monitoring Source
- Adding Ethernet Server Port as a Monitoring Source
- Adding an FC Uplink Port as a Monitoring Source
- Adding an FC Port Channel as a Monitoring Source
- Adding an FC Storage Port as a Monitoring Source
- Adding an FCoE Uplink Port as a Monitoring Source
- Adding an FCoE Port Channel as a Monitoring Source
- Adding an FCoE Storage Port as a Monitoring Source
- Adding a vLAN as a Monitoring Source
- Adding a vSAN as a Monitoring Source
- Adding a vHBA as a Monitoring Source
- Adding a vNIC as a Monitoring Source
Traffic Monitoring
Traffic monitoring copies traffic, from one or more source ports, and sends it to a dedicated destination port for analysis by a network analyzer. This feature is also known as Switched Port Analyzer (SPAN).
For FC port channels on Cisco UCS 6200 Fabric Interconnects, you can monitor only egress traffic.
For FC port channels on Cisco UCS 6300 Fabric Interconnects, you can monitor only ingress traffic.
Traffic Monitoring Session Types
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.
Note | For Cisco UCS 6300 Fabric Interconnects, the destination port must also be an unconfigured physical Ethernet port. For Cisco UCS 6332 and Cisco UCS 6332-16UP Fabric Interconnects, you cannot choose Fibre Channel destination ports, but can use unconfigured ethernet ports as a destination for FC traffic monitoring sessions. |
Traffic Monitoring Across Ethernet
An Ethernet traffic monitoring session can monitor any of the following traffic source and destination ports:
Source Ports |
Destination Ports |
---|---|
Traffic Monitoring for UCS 6300 Interconnects
Traffic Monitoring for UCS 6200 Interconnects
Traffic Monitoring Across Fibre Channel
You can monitor Fibre Channel traffic using either a Fibre Channel traffic analyzer or an Ethernet traffic analyzer. When Fibre Channel traffic is monitored with an Ethernet traffic monitoring session, the destination traffic is FCoE. The Cisco UCS 6300 Fabric Interconnect supports FC SPAN only on the ingress side. You cannot configure a Fibre Channel port on a Cisco Cisco UCS 6248 Fabric Interconnect as a source port.
A Fibre Channel traffic monitoring session can monitor any of the following traffic source and destination ports:
Source Ports |
Destination Ports |
---|---|
|
|
Guidelines and Recommendations for Traffic Monitoring
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.
-
Create a unique traffic monitoring session on any fabric interconnect within the Cisco UCS pod.
-
Create each monitoring session with a unique name and unique source.
-
Add all vNICs from the service profile of a server to monitor traffic from a server.
-
Locate all traffic sources within the same switch as the destination port.
-
Do not add the same source in multiple traffic monitoring sessions.
-
Do not configure a port as a destination port and a source port.
-
Do not configure a member port, of a port channel, individually as a source. If you configure the port channel as a source, all member ports are source ports.
Maximum Supported Active Traffic Monitoring Sessions
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. |
vNIC
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, 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, you must reconfigure the monitoring session. All associated vNICs used as source ports are removed from monitoring.
vHBA
You can use a vHBA as 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 frames.
SPAN Ports Support Matrix
Note | For Cisco UCS 6200 and 6324 FIs, you can only set the source mode to transmit for two sources per Cisco UCS domain. |
Ethernet Span Port Sources
Source Ethernet SPAN ports are supported in the following configurations:
Source Type |
Source Mode | ||
---|---|---|---|
on Cisco UCS 6200 FI |
on Cisco UCS 6324 FI |
on Cisco UCS 6332 FI |
|
Ethernet Uplink |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
Ethernet Port-Channel |
Receive |
Receive |
Receive, Transmit, Both |
FCoE Uplink |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
FCoE Port-Channel |
Receive |
Receive |
Receive, Transmit, Both |
Appliance Port |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
FCoE Storage |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
Unified Ports |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
VLAN |
Receive |
Receive |
Receive |
Static vNIC |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
vHBA |
Receive, Transmit, Both |
Receive, Transmit, Both |
Receive, Transmit, Both |
Ethernet Span Port Destinations
Destination Ethernet SPAN ports are supported in the following configurations:
Session Type |
Admin Speed |
||
---|---|---|---|
on Cisco UCS 6200 FI |
on Cisco UCS 6324 FI |
on Cisco UCS 6332 FI |
|
Ethernet SPAN Ports |
Ethernet Unconfigured at 1 Gbps, 10 Gbps |
Ethernet Unconfigured at 1 Gbps, 10 Gbps |
Ethernet Unconfigured at 10 Gbps, 40 Gbps |
Ethernet SPAN Ports |
Ethernet Monitor at 1 Gbps, 10 Gbps |
Ethernet Monitor at 1 Gbps, 10 Gbps |
Ethernet Monitor at 10 Gbps, 40 Gbps |
FC Span Port Sources
Source FC SPAN ports are supported in the following configurations:
Source Type |
Source Mode | ||
---|---|---|---|
on Cisco UCS 6200 FI |
on Cisco UCS 6324 FI |
on Cisco UCS 6332 FI |
|
FC Uplink |
Transmit |
Not Supported |
Receive |
FC Port-Channel |
Transmit |
Not Supported |
Receive |
FC Storage |
Transmit |
Not Supported |
Receive |
VSAN |
Not Supported |
Not Supported |
Receive |
vHBA |
Receive, Transmit, Both |
Not Supported |
Receive, Transmit, Both |
FC Span Port Destinations
Destination FC SPAN ports are supported in the following configurations:
Session Type |
Admin Speed |
||
---|---|---|---|
on Cisco UCS 6200 FI |
on Cisco UCS 6324 FI |
on Cisco UCS 6332 FI |
|
FC SPAN Ports |
FC Uplink at 1 Gbps, 2 Gbps, 4 Gbps, 8 Gbps, Auto |
Not Supported |
FC Unconfigured at 1 Gbps, 2 Gbps, 4 Gbps, 8 Gbps, 16 Gbps, Auto |
FC SPAN Ports |
FC Monitor at 1 Gbps, 2 Gbps, 4 Gbps, 8 Gbps, Auto |
Not Supported |
FC Monitor at 1 Gbps, 2 Gbps, 4 Gbps, 8 Gbps, 16 Gbps, Auto |
Setting Policy Control to Global
Before creating a traffic monitoring session in Cisco UCS Central, ensure that the port configuration is set to global on the Policy Resolution Control page.
The following example shows how to set the port configuration to global:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope system UCSC(resource-mgr) /system # show policy-control-ep policy controlep: hostname or ip address ---------------------- 10.193.200.100 UCSC(resource-mgr) /system # scope policy-control-ep 10.193.200.100 UCSC(resource-mgr) /system/policy-control-ep # set port-config-ctrl source global UCSC(resource-mgr) /system/policy-control-ep*# commit-buffer UCSC(resource-mgr) /system/policy-control-ep #
Creating a Traffic Monitoring Session for an Ethernet Port
The following example shows how to create a traffic monitoring session named traffic1:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope eth-traffic-mon UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric # create eth-mon-session traffic1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session* # enable UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session* # create dest-aggr-interface 2 33 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-aggr-interface* # create br-dest-interface 2 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-aggr-interface/br-dest-interface* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-aggr-interface/br-dest-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session # create dest-interface 4 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-interface* # set speed 10gbps UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-interface* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric #
Setting the Destination Interface and Destination Aggregate Interface for Ethernet Ports
The following example shows how to create a destination interface and a destination aggregate interface:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope eth-traffic-mon UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric # scope eth-mon-session traffic1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session # create dest-aggr-interface 2 33 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-aggr-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session # create dest-interface 3 23 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-interface*# show dest-interface detail Destination Interface: Slot ID: 3 Port ID: 23 Speed: 10 Gbps Admin State: Operational State: State Reason UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-interface*# commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/dest-interface #
Creating a Traffic Monitoring Session for a Fibre Channel Port
The following example shows how to create a traffic monitoring session:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-traffic-mon UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric # create fc-mon-session traffic1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session* # enable UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session* # create dest-aggr-interface 2 33 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/dest-aggr-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session # create dest-interface 4 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/dest-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session* # create dest-eth-interface 1 11 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/dest-eth-interface* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/dest-eth-interface #
Adding Appliance Port as a Monitoring Source
The following example shows how to add an appliance port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain/ # scope eth-storage UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-storage/ # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-storage/fabric # create interface 1 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-storage/fabric/interface* # create mon-src gf1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-storage/fabric/interface/mon-src* # set direction both UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-storage/fabric/interface* # commit-buffer
Adding an Ethernet Uplink as a Monitoring Source
The following example shows how to add an ethernet uplink as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope eth-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric # scope interface 2 33 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/interface # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/interface/mon-src* # set direction both UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/interface/mon-src* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/interface/mon-src* #
Adding Ethernet Port Channel as a Monitoring Source
The following example shows how to add an ethernet port channel as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope eth-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric # create port-channel 1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/port-channel # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/port-channel* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-uplink/fabric/port-channel* #
Adding Ethernet Server Port as a Monitoring Source
The following example shows how to add an ethernet server port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain/ # scope eth-server UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/ # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric # create aggr-interface 1 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric/aggr-interface* # create br-interface 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric/aggr-interface/br-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric/aggr-interface* # up UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric* # create interface 1 2 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-server/fabric* # commit-buffer
Adding an FC Uplink Port as a Monitoring Source
The following example shows how to add an Fibre Channel uplink port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric # create interface 1 2 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fc* # create mon-src gf1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fc* # commit-buffer
Adding an FC Port Channel as a Monitoring Source
The following example shows how to add an FC port channel as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric # create port-channel 1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/port-channel # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/port-channel* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/port-channel* #
Adding an FC Storage Port as a Monitoring Source
The following example shows how to add an FC storage port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-storage UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric # create interface fc 1 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/fc # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/fc* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/interface* #
Adding an FCoE Uplink Port as a Monitoring Source
The following example shows how to add an FCoE uplink port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric # create fcoeinterface 1 2 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoeinterface # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoeinterface* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoeinterface* #
Adding an FCoE Port Channel as a Monitoring Source
The following example shows how to add an FCoE port channel as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-uplink UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric # create fcoe-port-channel 1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoe-port-channel # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoe-port-channel* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-uplink/fabric/fcoe-port-channel* #
Adding an FCoE Storage Port as a Monitoring Source
The following example shows how to add an FCoE storage port as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-storage UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric # create interface fc 1 22 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/fc # create mon-src my_monsrc1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/fc/mon-src* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-storage/fabric/fc/mon-src* #
Adding a vLAN as a Monitoring Source
The following example shows how to configure a vlan as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope eth-traffic-mon UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric # scope eth-mon-session traffic1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session* # scope vnic my_vnic1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/vnic # create vlan-member my_vlan1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/vnic/vlan-member* # commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/eth-traffic-mon/fabric/eth-mon-session/vnic/vlan-member* #
Adding a vSAN as a Monitoring Source
The following example shows how to configure a vSAN as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr)# scope domain-mgmt UCSC(resource-mgr) /domain-mgmt # scope ucs-domain 1008 UCSC(resource-mgr) /domain-mgmt/ucs-domain # scope fc-traffic-mon UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon # scope fabric a UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric # scope fc-mon-session session1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session* # scope monvsan monvsan1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/monvsan # create vsan-member my_vsan1 UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/monvsan/vsan-member*# commit-buffer UCSC(resource-mgr) /domain-mgmt/ucs-domain/fc-traffic-mon/fabric/fc-mon-session/monvsan/vsan-member #
Adding a vHBA as a Monitoring Source
The following example shows how to add a vHBA as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr) # scope org UCSC(resource-mgr) /org # scope service-profile sp1 UCSC(resource-mgr) /org/service-profile* # scope vhba test-vhba UCSC(resource-mgr) /org/service-profile/vhba* # create mon-src gf1 UCSC(resource-mgr) /org/service-profile/vhba/mon-src* # commit-buffer
Adding a vNIC as a Monitoring Source
The following example shows how to add a vNIC as a monitoring source:
UCSC# connect resource-mgr UCSC(resource-mgr) # scope org UCSC(resource-mgr) /org # scope service-profile sp1 UCSC(resource-mgr) /org/service-profile* # scope vnic test-vnic UCSC(resource-mgr) /org/service-profile/vnic* # create mon-src gf1 UCSC(resource-mgr) /org/service-profile/vnic/mon-src* # commit-buffer