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 contains the following sections:
Cisco Monitor Manager enables you to configure different port types. All configured ports are displayed in the Configured Ports table on the Port Types tab.
Edge ports are the ingress ports where traffic enters the monitor network. Cisco Monitor Manager supports the following edge ports:
Configuring an edge port is optional.
Delivery ports are the egress ports where the traffic exits the monitor network. These outgoing ports are connected to external monitoring devices. When you configure a monitoring device in Cisco Monitor Manager, you can associate a name and an icon with the switch and port that you configured.
Configured devices are displayed in the Monitor Devices table on the Devices tab. The icon appears in the topology diagram with a line that connects it to the node.
Cisco Monitor Manager enables you to configure a switch port as an edge port and specify a VLAN for that port. When you configure the VLAN ID, and the connection to the Cisco onePK agent is up, Cisco Monitor Manager programs the Cisco Nexus 3000 or 3100 Series switch so that all packets received in that port are VLAN tagged, and the VLAN ID is the one configured on the edge port. If the packets received in that port are already VLAN-tagged frames, they get double-tagged, and the outermost VLAN tag contains the VLAN ID that is associated with the configured edge port.
At least one monitoring device must be configured for the port.
Step 1 | In the topology diagram, choose the node from which you want to remove a monitoring device. |
Step 2 | Next to the port name for which you want to remove monitoring devices, click the Devices highlight. |
Step 3 | In the expanded Device Name list for the port, choose one of the following: |
Step 4 | Above the Device Name list, click Remove Monitoring Devices. |
Step 5 | In the confirmation dialog box, click Remove Devices. |
A root node is automatically selected by Cisco Monitor Manager. If the defined root node is too far from the source switches, you can manually configure a different switch. We recommend that you choose a switch with edge ports as your new root node.
Note | Root node changes do not take effect until you save the configuration and restart the Cisco Extensible Network Controller (XNC) application. |
The Cisco onePK plug-in for Cisco Extensible Network Controller (XNC) communicates with onePK devices through a onePK agent on the device. To support onePK device functions in Cisco Monitor Manager, the application must be connected to the onePK agent. The agent is the mediator between Cisco Monitor Manager and onePK-enabled devices that are configured in Cisco Extensible Network Controller (XNC).
To secure communication between Cisco Extensible Network Controller (XNC) onePK-enabled devices, you must configure Transport Layer Security (TLS) in Cisco Extensible Network Controller (XNC). See the Cisco Extensible Network Controller Deployment Guide, Release 1.6 for detailed procedures.
You must connect to a onePK agent to support additional functionality in Cisco Monitor Manager, including symmetric load balancing and Q-in-Q.
Step 1 | In the topology diagram, click the node to which you wish to connect a onePK agent. | ||||||||
Step 2 | In the sidebar, click Click to enable addtional functionality. | ||||||||
Step 3 | In the
Connect
to onePK agent dialog box, complete the following fields:
| ||||||||
Step 4 | Click Submit. |
Cisco Monitor Manager enables you to configure symmetric load balancing settings on the egress port channels. Load balancing settings are based on Layer 2 source MAC and destination IP addresses, or Layer 2, Layer 3, or Layer 4 source and destination ports. When you configure symmetric load balancing for all the port-channel interfaces on the switch, all the traffic from specific sources and destinations in both directions always flows on the same port-channel member link.
Note | Symmetric load balancing in Cisco Monitor Manager is available only for Cisco Nexus 3100 Series switches. |
Note | The ability to configure symmetric load balancing is available only for Cisco Nexus 3100 Series switches. |
Step 1 | In the topology diagram, click the node for which you wish to configure symmetric load balancing. |
Step 2 | In the side bar,
from the
Symmetric Load Balancing drop-down list, choose one
of the following:
|
Step 3 | Click Submit. |
Note | The ability to configure Q-in-Q is available only for Cisco Nexus 3000 and 3100 Series switches. Q-in-Q is automatically enabled when you configure a VLAN ID for an edge port, if the VLAN ID is maintained on the edge port. |
Connect to the onePK agent for the node.