Guest

Cisco Extensible Network Controller (XNC)

Cisco Extensible Network Controller: Monitor Manager Application Data Sheet

  • Viewing Options

  • PDF (571.8 KB)
  • Feedback

Product Overview

Every enterprise depends on the smooth running of its business applications and the underlying infrastructure. Visibility into application traffic has traditionally been important for infrastructure operations to maintain security, resolve problems, and perform resource planning. Now, however, as a result of technological advances and the ubiquity of the Internet, organizations increasingly are seeking not just visibility but real-time feedback about their business systems to more effectively engage their customers. Essentially, traffic monitoring is evolving from a tool to manage network operations to a tool for achieving smart business agility that can materially affect the revenue of the business.

Using the Cisco® Extensible Network Controller (XNC), the Monitor Manager application, and Cisco Nexus® 3000 Series Switches, which support OpenFlow, Cisco provides a new software-defined networking (SDN)-based solution that offers a scalable, cost-effective, and programmable test access point (TAP) and monitoring environment.

Traditional approaches to network traffic visibility have used a purpose-built matrix network to which the monitoring and analysis tools are connected. Figure 1 shows the traditional approach to network traffic monitoring.

Figure 1. Traditional Approach to Network Traffic Visibility

The traditional approach poses three primary challenges:

The approach is too expensive to scale the visibility to meet today’s business requirements.

The purpose-built switches are statically programmed with predetermined filtering and forwarding rules, and so they cannot act in an event-based way to provide traffic visibility in real time. This limitation lengthens response times as coverage increases.

As the need for visibility into traffic patterns unique to a specific data center becomes more common, third-party tools cannot provide adequate coverage, resulting in coverage gaps.

Using the Monitor Manager application, Cisco’s approach replaces the matrix network with one or more OpenFlow enabled Cisco Nexus switches. The traffic is tapped into this bank of Cisco Nexus switches in the same manner as in a matrix network. However, with Cisco XNC and Monitor Manager application, the filtering and forwarding rules can change dynamically, based on business logic, allowing unique traffic patterns to flow directly to the tools in real time. In addition, because Cisco XNC supports common programmable interfaces such as Java and REST, network operators can write applications to detect and capture unique traffic, closing any coverage gaps. Figure 2 shows the solution using Cisco XNC, the Monitor Manager application, and Cisco Nexus switches.

Figure 2. Cisco Monitor Manager Solution for Network Traffic Visibility

OpenFlow implementation on Cisco Nexus switches supports hybrid mode which allows the customers to share the same switch for both production traffic and as tap/SPAN aggregation switch. With these features, Cisco approach provides superior economics, saving both capital expenditures (CapEx) and operating expenses (OpEx), when compared with the traditional matrix network approach. The Cisco approach also helps ensure short response times and full coverage as monitoring needs scale.

Cisco XNC is built for extensibility using the Java Open Services Gateway initiative (OSGi) application framework. This framework provides the flexibility needed for Cisco and Cisco partners and customers to extend the functions of the controller based on business needs. Cisco XNC and Monitor Manager also provides robust northbound Representational State Transfer (REST) APIs for business applications to access and program policies.

Features and Benefits of Monitor Manager Application

Table 1 summarizes the main features and benefits of the Cisco XNC Monitor Manager solution.

Table 1. Main Features and Benefits

Feature

Benefit

Supported topology for Monitor Manager network

Support for any type of topology for the monitoring environment using Cisco Nexus switches
Capability to configure delivery ports at which various monitoring tools are connected
Capability to set end-device names for easy identification in the topology
Point-to-multipoint and any-to-multipoint support for delivery of traffic to endpoint devices

Management for multiple disjointed Monitor Manager networks

Customers can manage multiple Monitor Manager topologies that may be disjointed using the same Cisco XNC instance. For example, if you have 5 data centers and want to deploy an independent Monitor Manager solution for each data center, you can manage all these 5 independent deployments using a single Cisco XNC instance by creating a logical partition (network slice) for each monitoring network.

Support for QinQ to tag input source SPAN/Tap port

Capability to tag traffic with a VLAN for each input TAP or SPAN port
Support for Q-in-Q in edge TAP and SPAN ports to uniquely identify the source of traffic and preserving production VLAN information

Time Stamping*

Ability to timestamp a packet at ingress using Precision Time Protocol (IEEE 1588) there by providing nano-second accuracy. Timestamping the packets using PTP could be leveraged for critical transaction monitoring and archiving data for regulatory compliance and advance troubleshooting

Packet Truncation*

Ability to truncate a packet beyond specified bytes
Minimum is 64 bytes
Ability to retain header only for analysis and troubleshooting
Discard the payload for security or compliance reasons

Symmetric Hashing or Symmetric load balancing+

Provides the ability to configure the hashing based on Layer 3 (IP address) or Layer 3 + Layer 4 (Protocol Ports) for load balancing the traffic across a port-channel link
Ability to spread the traffic across multiple tool instances to meet the high traffic volume scale

Rules for matching monitored traffic

Capability to match traffic based on Layer 1 through Layer 4 criteria
Capability to send only the required traffic to the monitoring tools without flooding the tools with unnecessary traffic
Capability to forward traffic to multiple destinations connected across the monitoring network
Option to configure action to set the VLAN ID for the matched traffic

Role-based access control (RBAC)

Application access integrated with Cisco XNC RBAC
Capability to create port groups and associate the port groups with roles
Capability to assign users to specific roles and port groups; users can manage only those ports

Northbound interface support for Monitor Manager application

All application configuration support through northbound REST interface
Dynamic creation of matching rules through northbound API based on network traffic patterns

Cost-effective and safe approach to introducing SDN in the network environment

Cost effective compared to conventional network tapping solutions
Scalable network traffic monitoring solution based on Cisco Nexus 3000 Series
Introduction of SDN to the network environment without affecting production network traffic

Monitor Manager Embedded

Suitable for single-switch deployments, Monitor Manager Embedded allows customer to run Cisco XNC and Monitor Manager application on the Cisco Nexus switch itself
Monitor Manager Embedded option can be deployed on the Cisco Nexus 3000 Series switches

* Feature supported only on Nexus 3500
+ Feature supported only on Nexus 3100

The Cisco XNC and Monitor Manager application can be accessed through the web based GUI or REST API. Figure 3 shows the various access mechanisms for Cisco XNC and Monitor Manager application.

Figure 3. Cisco XNC Monitor Manager Application Access Mechanism

OpenFlow Hybrid Support

Cisco Nexus Switches support hybrid OpenFlow mode that provides the flexibility to allocate certain ports TAP/SPAN aggregation that will be controller by Cisco XNC and Monitor Manager application, and remaining ports to be normal ports controlled by the local control plane. Normal ports can carry the regular production traffic. Cisco XNC and Monitor Manager application will see only the ports that are allocated for Tap/SPAN aggregation.

Additional features include

Flexibility in assigning monitoring ports depending on the network requirements

Ability to increase the number of monitoring ports depending on traffic requirements without having to disrupt production traffic

Monitor Manager Embedded

Customers who want to run Monitor Manager using a single Cisco Nexus 3000 Series switch in their topology have the option to run Cisco XNC and Monitor Manager on the switch itself through Monitor Manager Embedded functionality. Monitor Manager Embedded is provided as an open virtual appliance (OVA), which contains Cisco XNC, and Monitor Manager application that can be deployed on the Cisco Nexus switch’s Linux container. After this OVA is downloaded to the switch, it needs to be activated, and by default Cisco XNC uses the management interface IP address of the Cisco Nexus switch. All features of the Monitor Manager application are available in this option as well except:

Clustering and high availability

Management for multiple switches in the Monitor Manager network topology

Please see Table 4 in the next section for ordering information.

Device Support Matrix for Cisco XNC and Monitor Manager Application

Table 2. Cisco XNC and Monitor Manager Application Device Support Matrix

Device Model

Cisco XNC and Monitor Manager Version

Cisco Nexus 3000 (3048/3064/3016)

Cisco XNC and Monitor Manager version 1.5

Cisco XNC and Monitor Manager version 1.6

Cisco Nexus 3100 (3132/3172)

Cisco XNC and Monitor Manager version 1.5

Cisco XNC and Monitor Manager version 1.6

Cisco Nexus 5548

Cisco XNC and Monitor Manager version 1.5

Cisco Nexus 6001

Cisco XNC and Monitor Manager version 1.5

Licensing and Ordering Information

Tables 2 through 4 present ordering information for the Cisco XNC Monitor Manager application.

Table 3. Cisco XNC and Application Promotional Bundles

Part Number

Description

L-XNC-MM-B-ST-K9

Starter Bundle that includes one instance of Cisco XNC and Monitor Manager application RTM 5 Top of Rack (1-2 RU) Nexus fixed switches

L-XNC-MM-B-S-K9

Small size deployment Bundle that includes two instance of Cisco XNC for HA and Monitor Manager application RTM 10 Top of Rack (1-2 RU) Nexus fixed switches

L-XNC-MM-B-M-K9

Medium size deployment Bundle that includes two instance of Cisco XNC for HA and Monitor Manager application RTM 25 Top of Rack (1-2 RU) Nexus fixed switches

L-XNC-MM-B-L-K9

Large size deployment Bundle that includes two instance of Cisco XNC for HA and Monitor Manager application RTM 50 Top of Rack (1-2 RU) Nexus fixed switches

Table 4. Monitor Manager Embedded

Part Number

Description

L-XNC-MM-LITE-K9=

Monitor Manager Embedded, which provides the option to run the XNC and Monitor Manager application on the Nexus 3000/3100/3500 switch. This is a special built OVA file which has to be run on Nexus 3000/3100 switch and suitable only for single switch deployment

XNC-MM-LITE-K9

This SKU is also for Monitor Manager Embedded function, which provides the option to run the XNC and Monitor Manager application on the Nexus 3000/3100 switch. This is a special built OVA file which has to be run on Nexus 3000/3100/3500 switch and suitable only for single switch deployment. But this SKU is available only within the Nexus 3000/3100/3500 configuration bundle

Table 5. Combined Cisco XNC and Hardware Bundles for Monitor Manager Application

Part Number

Description

N3K-XNC-MM-B-ST

Starter bundle that includes XNC with Monitor Manager application and flexibility to choose up to 5 Nexus 3000 devices (3048/3064/3016)

N3K-XNC-MM-B-SM

Small size deployment bundle that includes XNC with Monitor Manager application and flexibility to choose up to 10 Nexus 3000 devices (3048/3064/3016)

References

Monitor Manager solution implementation quick start guide - http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/extensible-network-controller-xnc/guide-c07-731460.html.

For More Information

For more information about Cisco XNC, visit http://www.cisco.com/go/xnc or contact your local account representative.