DCNM 7.0(1) release is specifically targeted to manage Dynamic Fabric Automation (DFA) architecture. This release is not intended for traditional DCNM LAN/SAN users, looking for 6.x upgrade for bug fixes and regular maintenance updates.
Note Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of the Cisco DCNM Release Notes:
Cisco Prime DCNM combines the management of Ethernet and storage networks into a single dashboard to help network and storage administrators manage and troubleshoot health and performance across the following product families that run Cisco NX-OS software. DCNM 7.0 specifically addresses the deployment of Cisco Dynamic Fabric Automation (DFA). The following devices are supported for DFA deployments:
Cisco Nexus 5000, 6000, and 7000 Series Switches
Cisco Nexus 2000 Series Fabric Extenders
This section lists the tested and supported hardware and software specifications for Cisco DCNM server and client architecture. The application has been tested in English locales only.
Cisco DCNM Server is distributed with Java JRE 1.6.0_31. Cisco DCNM clients should also use Java JRE 1.6.0_31. The DCNM installer installs JRE 1.6.0_31 to the following directory: DCNM_root_directory/java/jre1.6.
Cisco DCNM Release 7.0(1) supports the following databases:
Oracle11g Express (XE), Standard, and Enterprise Editions, and Oracle 11g Real Application Clusters (RAC).
Note Customers are responsible for all support associated with Oracle database, including maintenance, troubleshooting, and recovery. Cisco recommends that customers perform regular database backups, either daily or weekly, to ensure that all data is preserved.
Cisco DCNM Release 7.0(x) supports running the Cisco DCNM server on the following hypervisor:
VMware ESXi 5.1, VMware vCenter 5.1
Table 2 lists the minimum and recommended database server system requirements for running Cisco DCNM and using an external Oracle Database.
Table 2 Database Server System Requirements
2.5 GHz with dual-processor or dual-core CPU
3.45 GHz with dual-processor or dual-core CPU
Disk space (free)
DCNM Host Requirements
Table 3 lists the server resource requirements for deploying Cisco DCNM 7.0 Virtual Appliance (OVA).
Note The Cisco DCNM desktop client that manages vPC, VDC, and FabricPath features using deep discovery through XML can manage a maximum of 50 devices (2500 ports) with one Cisco DCNM server or a cluster of two servers. A cluster of two servers provides High Availability (HA) (Active-Active) in case one of the Cisco DCNM servers fails.
Table 3 Cisco DCNM Host Resources for OVA deployment
Small Deployment: Up to 50 Switches
Large Deployment: More than 50 Switches
2 vCPUs, 2 GHz (or faster)
4 vCPUs, 2 GHz (or faster)
8-GB memory, 100 GB in case of thick provisioning
12-GB memory, 100 GB in case of thick provisioning
Cisco DCNM clients support Windows 7, Windows 2008, and Red Hat Linux. Table 4 lists the minimum hardware requirements for these client systems.
Table 4 Client Hardware Requirements
2.16 GHz (or faster) with one dual core processor or two single-core processors
Disk space (free)
Some Cisco DCNM features require a license. Before you can use the licensed features, you must install the Cisco DCNM license. For more information, see the Cisco DCNM Installation and Licensing Guide, Release 7.x.
Be sure to set the correct time zone value on the client system’s clock (for example, UTC). Otherwise, Cisco DCNM-LAN cannot manage the switch properly.
Web browsers that support Adobe Flash 10 are qualified for use with Cisco DCNM. These include Internet Explorer, Firefox, and Safari.
Other Supported Software
Table 5 lists other software supported by Cisco DCNM Release 6.2(x).
Table 5 Other Software Supported by Cisco DCNM
Other Supported Software
ACS Versions, 4.0, and 5.1
Telnet Disabled: SSH version 1, SSH version 2, Global Enforce SNMP Privacy Encryption
Web Client and Cisco DCNM-SAN Server Encryption: HTTPS
Cisco Prime Network Registrar 8.2
SNMP over UDP
SNMP over TCP
Virtual Machines :
ESXi Server version 5.1
In addition, Cisco DCNM supports the following types of events: EMC Call Home events, fabric change events, and events that are forwarded by traps and e-mail.
DCNM 7.0 release provides DCNM as an Open Virtual Applianc (OVA), that can be deployed on VMware vSphere infrastructure. DCNM 7.0 ships only in the OVA format. The vCenter and ESXi must be version 5.1 or higher for a successful deployment.
This Virtual Appliance has a pre-installed operating system (CentOS) with pre-installed DCNM Cisco Data Center Network Manager components for Dynamic Fabric Architecture.
After deployment of the OVA, you can access DCNM Web UI at the configured IP address with credentials: admin/<user provided password>. To login to an ssh session of this deployment you can use the credentials: root/ <user provided password>.
Enhanced Visualization and Topology
A new topology paradigm with color-coded icons and leaf or spine representation with links is designed to give you a quick and useful view of health and functionality of the fabric and end hosts. You can view the topology at Dashboard->Dynamic Fabric Automation.
Following are a few highlights of the new DFA topology:
Inter Switch Link view and Edge Ports view of Fabric.
Node and Link status clearly color-coded for easy problem-recognition and reconciliation in large networks.
Easy Search and Filter options based on:
– Switch name
– Real-time End Host Virtual/Physical Machine association (Tenant-awareness)
– Org/Partition defined in LDAP.
Power On Auto Provisioning (POAP). This is a feature that allows a device to automatically bootup with the desired configuration and images. You can access the configuration at config->Power On Auto Provisioning (POAP).
To facilitate this feature, DCNM has useful GUI and packaged utilities for:
DHCP Scope definition
Image and Configuration repository definitions
Default POAP Templates for Leaf or Spine etc
Creating required POAP template definition
Associating a single template to multiple Device instances using a simple UI
Viewing CLI-previews of deployed templates before they are applied on the device
Cable plan management from POAP templates or learned Inter-switch links for a given fabric
Automatically import and management of POAP devices in DCNM, when a device is powered up
Auto-configuration feature enables Automated Network provisioning by integrating and interacting with:
Internal or External LDAP server to which DCNM can read or write profile, organization, partition and network definition These provide data read by the Leaf switches.
Internal or external Advanced Message Queuing Protocol (AMQP) server to monitor any creation/update/deletion of auto-configuration elements.
IP address management
Local DHCPD packaged by default where user can define DHCP scopes to be used by DHCP requests coming from the Leaf.
Internal or external Extensible Messaging and Presence Protocol (XMPP) server used for multi device communication by DCNM leaves and spines. DCNM can notify leaf switches via XMPP when an auto-configuration event occurs.
DCNM OVA packages a reference synchronization script for VMware vCD (vCloud Director) integration
DCNM OVA packages reference script for Cisco Prime Network Registrar (CPNR) integration
Settings for auto-config are available at Admin> Dynamic Fabric Automation (DFA) > Settings
Web Services API
DCNM Provides REST based API for the following operations:
For more details on actual usage guidelines and request/response samples, please refer to the Web Services API Guide.
In the Cisco DFA solution, traditional services, such as firewalls and load balancers, are deployed at regular leaf nodes within the spine-leaf topology, and at border leaf nodes. This is unlike more traditional data centers where these services are deployed at the aggregation layer.
Cisco Prime Network Services Controller (Prime NSC) provides the orchestration and automation of network services in Cisco DFA. The Prime NSC supports integration with virtual compute and storage managers such as UCS Director and Openstack Controller to provide end-to-end orchestration and automation for services in Cisco DFA.
A Prime NSC Adapter is bundled within the Cisco DCNM OVA. It performs the following functions:
Enables DCNM to interoperate with one or more instances of the Prime NSC.
Provides translation of DCNM language and objects into the Prime NSC language and objects.
Ensures that the Prime NSC and DCNM are always synchronized.
Maps the tenants and virtual data centers to the Prime NSC instances responsible for network services.
Cisco DCNM Release 7.0(1) supports the following platform-specific features:
Cisco Nexus 6004P-96Q switch
– N6004P LEM module 12xQSFP+
Cisco Nexus 3548P switch
– Cisco Nexus 3000 buffer usage charts and tabular data for microburst monitoring
UCS B-series enhanced visibility into blade attributes and LAN features
Cisco Nexus 1000v Hyper-V
Cisco DCNM Release 7.0(1) supports the following platform-specific features:
1.Cisco DCNM cannot be installed on a Cisco Nexus 1110-S or 1110-X Virtual Services Appliance. These devices can be discovered by Cisco DCNM.
The free product features that come with Cisco Prime DCNM are referred to as Essentials Edition. This includes base functionality required for DFA Fabric Management. No license is required to use these features because they are unlocked with the image. They are included at no cost and are a part of the image that can be downloaded from http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm.
Note Cisco Nexus Access licenses (DCNM-NXACC-100-K9 and DCNM-NXACC-250-K9) are no longer available in Cisco DCNM Release 6.1(1a) and later releases. Use DCNM-LAN-N3K and DCNM-LAN-N5K licenses above in place of DCNM-NXACC licenses.
Service contract PIDs are required for opening a case with TAC for breakage or repair and for upgrade from older versions of Cisco DCNM and Fabric Manager. You can also select Cisco DCNM as part of the purchase of a switch chassis, under software options. For more information on licensing, see the FAQs at this URL: http://www.cisco.com/en/US/products/ps9369/prod_literature.html.
Registering a Product Authorization Key
To receive a Cisco DCNM license, you must register the Product Authorization Key (PAK) that you receive when you purchase Cisco DCNM. To register the PAK, follow these steps:
This section lists caveats that apply to both Cisco DCNM-LAN and Cisco DCNM-SAN.
Symptom : OVA gets deployed successfully, but the user is unable to login to DCNM Web UI or connect to XMPP. However, the user is able to login to the virtual appliance using SSH terminal.
Conditions : Either the administrative password or hostname entered while deploying the OVA does not conform to the expected format. The format is indicated in the help text shown in the vSphere client screen during deployment.
Workaround : Redeploy the virtual appliance using a proper password that conforms to the description in the help text and a hostname as a fully qualified domain name.
Symptom : The two layer VPC id is not shown on topology pane and links do not display correctly on Topology--> port channel and VPC view.
Conditions : When you discover the two n5k and n1k one by one with hop 0.
Workaround : Discover all the devices (2N5ks and 1 n1k) in one task Or rediscover the 2 uplink N5ks one by one.
Symptom : Connection between Fex and N1k not shown for 2 layer vPC.
Conditions : When using 2 layer vPC setup, the connection between the Fex and N1k is not shown. This is a rare occurrence.
Workaround : Discover the devices in 2 layer vPC serially, one after the other.
Symptom : When a switch is discovered, the mgmt0 interface is not shown in the Interface listing page for the switch.
Conditions : Always.
Workaround : There is no workaround.
Symptom : From POAP definitions, if user edits a definition, goes through all the steps, and finally publishes it, and then tries to go to DFA topology, the screen becomes blank and unresponsive.
The same issue occurs when POAP definition is saved and published, then the user navigates to the DFA screen.
Conditions : When the POAP definition is saved or edited and published and the user goes to DFA topology screen.
Workaround : Doing a browser reload (clicking the reload button on the browser being used) fixes the issue.
Open Caveats—Prime NSC adapter Release 1.0.1
Symptom : Some tenants or networks are missing in NSC after addingVM-mgr for a deployment where VM-mgr has existing tenants or networks.
Conditions : When a VM-mgr is added to a Prime NSC instance where VM-mgr has tenants or networks already present. In some cases, all the tenants or networks are not synced to Prime NSC.
Workaround : Remove the NSC instance using nsc-adapter-mgr nsc remove <ip> comman and then add the NSC instance again using nsc-adapter-mgr nsc add <ip-address> <user-name> <password> command.
Symptom : Upon restarting the NSC adapter, the adapter connections command shows "initializing" state.
Conditions : This happens when one of the NSC instance specified in config.ini file is unreachable due to NSC load.
Workaround : Using the GUI login, verify the NSC instance reachability. Identify the NSC instance where GUI is not reachable to find out if NSC is unreachable even though pingable. Then follow these steps:
1. Stop the NSC adapter.
2. Remove the incorrect NSC instances using CLI.
3. Start NSC adapter.
This section contains information about the documentation available for Cisco DCNM and for the platforms that Cisco DCNM manages.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.