Cisco Extensible Network Controller Release Notes, Release 1.6

Table of Contents

Cisco Extensible Network Controller Release Notes, Release 1.6

Contents

Introduction

Scale Information

System Requirements

Supported Web Browsers

New Software Features

Resolved Caveats

Open Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Cisco Extensible Network Controller Release Notes, Release 1.6

---

June 11, 2014

This document describes the features, system requirements, resolved caveats, open caveats, and limitations for the Cisco Extensible Network Controller (XNC), Release 1.6.

Contents

This document includes the following sections:

• Introduction
• New Software Features
• Resolved Caveats
• Open Caveats
• Related Documentation
• Obtaining Documentation and Submitting a Service Request

Introduction

Cisco XNC provides automation and orchestration of the network fabric, and allows dynamic, application-based configuration of networks and services. Cisco XNC enables programmability of the network using the Software Defined Networking (SDN) approach.

Cisco XNC is based on OpenDaylight and is built for extensibility using the Java Open Services Gateway initiative (OSGi) 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 also provides northbound Representational State Transfer (REST) APIs for business applications to access and program policies.

Cisco XNC has the capability to support multiple protocols to communicate with the devices. In Release 1.6, Cisco XNC supports OpenFlow version 1.0 and Cisco One Platform Kit (onePK) SDK version 1.1.

---

Note Not all service sets or onePK APIs are supported in the current onePK protocol plug-in.

---

Scale Information

Table 1 lists the scale limits for Cisco XNC.

 

Table 1 Scale Limits

Description	Small	Medium	Large
Number of devices	100	300	500
Number of TIF policies	400	2000	4000
Number of slices	25	100	200
Number of proactive flows	10,000	50,000	100,000

System Requirements

Table 2 lists the system requirements for Cisco XNC.

 

Table 2 System Requirements per Deployment Size

Description	Small	Medium	Large
CPUs (virtual or physical)	6-core	12-core	18-core
Memory	8 GB RAM	16 GB RAM	24 GB RAM
Hard disk	Minimum of 40 GB of free space available on the partition on which the Cisco XNC software is installed.
Operating system	A recent 64-bit Linux distribution that supports Java, preferably Ubuntu, Fedora, or Red Hat.
Other	Java Virtual Machine 1.7 or later.

Supported Web Browsers

The following web browsers are supported for Cisco XNC:

• Firefox 18.x and later versions
• Chrome 24.x and later versions

---

Note Javascript 1.5 or a later version must be enabled in your browser.

---

New Software Features

Cisco XNC 1.6 adds support for the following software features:

• Support for running the Cisco Monitor Manager Embedded application within the Cisco Nexus 3000 or 3100 Series switches for single switch deployment (Monitor Manager Embedded).
• Availability of the Cisco One Platform Kit (onePK) protocol plugin.

---

Note Not all service sets or onePK APIs are supported in the current onePK protocol plugin.

---

• Enhanced CLI framework for Cisco XNC administration.
• Access to northbound API content from the GUI menu bar.
• Support for user-specified VLAN information in the Virtual Patch Panel (Port-to-Port Forwarding) application.
• Predefined Ether types in Cisco Monitor Manager.
• Ability to edit filters in Cisco Monitor Manager.
• Ability to save a rule in without having to install it, thereby decoupling rule creation and installation. After rules are created and saved, installation can be toggled.
• Ability to edit rules to add or remove edge ports, change priority, and update VLAN information.
• Ability to edit the names of monitoring devices.
• Ability to configure symmetric load balancing using IP plus Layer 4 information, supported on Cisco Nexus 3100 Series switches.
• Ability to configure QinQ on Cisco Nexus Series 3000 and 3100 switches
• Ability to add onePK information from within the Cisco Monitor Manager application when enabling features that require onePK support.

---

Note Time stamping and packet truncation are not supported at this time.

---

Resolved Caveats

Table 3 lists that caveats that are resolved in Cisco XNC 1.6.

.

Table 3 Resolved Caveats in Cisco XNC 1.6

Defect ID	Symptom	Found in Release	Resolved in Release
CSCun06850	Traffic loss might be seen if you bring down one controller if that controller is part of an HA cluster.	1.5	1.6
CSCun31902	When flows are added to a switch because of the TIF policies in a particular slice, the flows are not deleted when the slice is deleted.	1.5	1.6
CSCul92372	If you remove the QinQ VLAN setting from an edge port in Monitor Manager, and then toggle the connection with a onePK client, the setting remains present and active on the switch interface.	1.5	1.6
CSCum61509	Existing edge ports in rules cannot be modified.	1.5	1.6

Open Caveats

Table 4 lists that caveats that are open in Cisco XNC 1.6.

.

Table 4 Open Caveats in Cisco XNC 1.6

Defect ID	Symptom	Workaround
CSCup16875	When Cisco XNC is upgraded from version 1.5 to version 1.6, the controller does not reconnect to onePK devices that were configured in XNC 1.5, even though configuration was explicitly saved before upgrading.	After completing the upgrade process and starting XNC 1.6, reconfigure connections to onePK devices using the GUI.
CSCup22283	When XNC is restarted, saved Monitor Manager rules capturing edge ports with assigned VLAN ID will be installed as if QinQ support is not configured. This happens even if the connection to the switch with the onePK interface (onePK node) is up and dot1q tunneling is configured on the switch ports of the switch. This is because Monitor Manager reads and applies the port configuration before the connection to the onePK nodes is fully up. Therefore, after topology is stabilized and rule installation is attempted, QinQ functionality is determined to be unavailable. This causes the (multi)point-to-(multi)point rules capturing from the affected edge ports to perform a VLAN rewrite on the incoming frames.	1. Uninstall the affected rules. 2. Reconfigure the edge port VLAN IDs: a. Remove the VLAN and submit the change. b. Assign desired VLAN ID and submit the change.
CSCup32639	ResourceManager documentation is missing from northbound API UI.	There is no workaround. The ResourceManager documentation can be found at devnet with the other REST APIs.

Related Documentation

For more information, see the related documents at the following link:

http://www.cisco.com/c/en/us/support/cloud-systems-management/extensible-network-controller-xnc/tsd-products-support-series-home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html .

Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

This document is to be used in conjunction with the documents listed in the “Related Documentation” section.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2014 Cisco Systems, Inc. All rights reserved.