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:
A Cisco Monitor Manager network consists of one or more Cisco Nexus 3000 Series switches with Cisco Agent for OpenFlow dedicated for connecting multiple spanned ports and network taps from the production network infrastructure. Cisco XNC programs the switches using the OpenFlow protocol. Cisco Monitor Manager filters the packets that travel the network and delivers them to a pool of connected monitoring devices.
Cisco Monitor Manager supports the following forwarding path options:
With the Point-to-Multipoint (P2MP) forwarding path option, both the ingress edge port where SPAN or TAP traffic is coming in to the monitor network and the egress delivery ports are defined. Cisco Monitor Manager uses the delivery ports to direct traffic from that ingress port to one or more devices.
With the Any-to-Multipoint (A2MP) forwarding path option, the ingress edge port of the monitor network is not known, but the egress delivery ports are defined. Cisco Monitor Manager automatically calculates a loop-free forwarding path from the root node to all other nodes using the Single Source Shortest Path (SSSP) algorithm.
You can use a filter to define the Layer 2 (L2), Layer 3 (L3), and Layer 4 (L4) criteria used by Cisco Monitor Manager to filter traffic. Traffic that matches the criteria in the filter is routed to the delivery ports and from there to the attached monitor devices.
Each filter has a priority that can be configured. Flows with a higher priority are given precedence over flows with a lower priority.
You can use rules to associate filters to configured monitor devices. You can configure rules with or without a source. Rules with a source node and port use the Point-to-Multipoint forwarding path option. Rules without a source port on a node use the loop-free Any-to-Multipoint forwarding path option.
The filter name and priority are displayed in the Filters table on the Configure Filters tab. All other properties are displayed in the Filter Description dialog box.
Step 1 | On the Configure Filters tab, click the filter whose properties you want to view. |
Step 2 | Click Close to close the Filter Description dialog box. |
You can delete filters that are not assigned to a rule.
Step 1 | On the Configure Filters tab, click the filter that you want to delete. |
Step 2 | On the Filter Description dialog box, click Remove Filter. |
Step 1 | On the Apply Filters tab, click Add Rule. | ||||||||||||||||
Step 2 |
In the Add Rule dialog box, complete the following fields:
|
||||||||||||||||
Step 3 | Click Add Rule. |
After you have created a rule, you can modify the devices associated with the rule or delete the rule.
Step 1 | Navigate to the Apply Filters tab. | ||||||||||||||
Step 2 |
The Rules table displays the following information for each rule:
|
||||||||||||||
Step 3 |
Click a rule to view the forwarding path for that rule in the topology diagram. The path is highlighted in red. |
||||||||||||||
Step 4 | Click a filter to modify the rule. | ||||||||||||||
Step 5 | In the Modify Rule dialog box, perform one of the following tasks: |
Step 1 | Navigate to the Apply Filters tab. |
Step 2 | Click the radio button for the rule that you want to delete. |
Step 3 | Click Remove Rule(s). |