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 lists the tested and supported hardware and software specifications for Cisco Prime Data Center Network Management (DCNM) server and client architecture. The application has been tested in English locales only. This chapter contains the following section:
This chapter includes the following sections:
The Cisco DCNM Server is distributed with JRE 1.8.0_101 or later. The Cisco DCNM installer installs JRE 1.8.0_101 into the following directory:
DCNM_root_directory/java/jre1.8
Cisco DCNM Release 10.1 supports the Cisco DCNM Server on these 64-bit operating systems:
Microsoft Windows 2008 R2 SP1
Microsoft Windows 2008 Standalone SP2
Microsoft Windows 2012 R2
Red Hat Enterprise Linux Release 6.6 and 7.0
OVA and ISO with integrated operating system
Cisco DCNM Release 10.1 supports the following databases:
Oracle11g Express (XE), Standard, and Enterprise Editions, and Oracle 11g Real Application Clusters (RAC)
PostgreSQL 9.4.5
Oracle 12c Enterprise Edition (Conventional)–(nonpluggable installation)
Note | Cisco DCNM Release 10.1 does not support Oracle 12c pluggable database version installation. |
Oracle 12c RAC (nonpluggable installation)
Note | The Cisco DCNM database size is not limited, and increases according to the number of nodes and ports that the DCNM manages with Performance Manager Collections enabled. You cannot restrict the database size. If you choose Oracle database, we recommend that you use Oracle SE or Enterprise edition, instead of Oracle XE due to table space limitations. |
Note | Customers are responsible for all the support associated with the Oracle databases, including maintenance, troubleshooting, and recovery. We recommend that customers perform regular database backups, either daily or weekly, to ensure that all the data is preserved. |
Cisco DCNM Release 10.1 supports the running of the Cisco DCNM server on the following hypervisors:
VMWare ESXi 6.0
VMware vCenter 6.0
Note | vCenter server is mandatory to deploy the Cisco DCNM 10.1 OVA Installer. |
Cisco DCNM Server resources for various installers are summarized in the following table.
LAN: 25 Switches and up to 1000 Ports SAN: 50 Switches and up to 2000 Ports |
LAN: 100 Switches and up to 3000 Ports SAN: 200 Switches and up to 5000 Ports |
LAN and SAN: 400+ nodes and 20000 ports |
---|---|---|
Dual-core CPUs, 2 GHz (or faster) |
Quad-core CPUs, 2 GHz (or faster) |
Quad-core CPU, 2 GHz, each core with two sockets |
8-GB memory, 80-GB free hard disk |
12-GB memory, 100-GB free hard disk 2 servers, LAN or SAN federation |
12GB memory, 100-GB free hard disk 2 servers, Federation for SAN 1 server, Native HA for LAN |
Oracle 10g, Oracle11g Standard or Enterprise, Oracle 12c, PostgreSQL 9.4.5 |
Oracle11g Standard or Enterprise, Oracle 12c, PostgreSQL 9.4.5 |
Native-HA PostGreSQL, Oracle 11g standard or Enterprise, Oracle12c, 11g RAC with dedicated resources |
Note | Although it is not mandatory, we recommend that you register the server system with Domain Name Service (DNS) servers. |
Cisco DCNM SAN desktop client and Cisco Device Manager support Windows 7, Windows 2008, Windows 2012, and Red Hat Linux. The following table lists the minimum hardware requirements for these client systems.
Hardware |
Minimum Requirements |
---|---|
RAM (free) |
4 GB |
CPU speed |
3GHz or faster |
Disk space (free) |
20 GB |
If you install Cisco DCNM in a virtual machine, you must reserve resources equal to the server resource requirements to ensure a baseline with the physical machines.
Some Cisco DCNM features require a license. Before using the licensed features, you must install a Cisco DCNM license for each Nexus or MDS managed platform.
Note | Resource reservations for the OVA virtual machine are required to ensure consistent performance of the Cisco DCNM server. |
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 |
12-GB memory, 100 GB |
Web browsers qualified for use with Cisco DCNM include Internet Explorer Version 11.0 and Firefox Version 38.0.
The following table lists other software supported by Cisco DCNM, Release 10.1.
Component |
Minimum Requirements |
---|---|
Security |
|
DHCP Server |
|
CentOS 6.6 |
OVA/ISO Installers |
Additionally, Cisco DCNM supports EMC call-home events, fabric change events, and events that are forwarded by traps and e-mail.
Keep the following guidelines in mind when deploying Cisco DCNM:
If you deploy Oracle database:
You must change the default setting by performing the following steps:
Note | The password for the database expires after 180 days. |
Log in to the Oracle database.
Enter the commands, as shown in this example:
SQL> GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO username IDENTIFIED by password; Grant succeeded. SQL> select username,password from dba_users where username=’username’; SQL> ALTER PROFILE DEFAULT LIMIT 2 FAILED_LOG_ATTEMPTS UNLIMITED 3 PASSWORD_LIFE_TIME UNLIMITED; Profile altered. SQL> EXIT
Network Time Protocol
General Guidelines
Do not deploy Cisco DCNM when network latency is more then 50 ms from the switch management subnet to the Cisco DCNM server and Cisco DCNM database.
Deploy Cisco DCNM on high-performance tier storage (2 to 4 ms response time).
Create users with the same password digest and encryption algorithm in the device (for example, Digest, MD5) and encryption algorithm (for example, DES). Cisco DCNM will not authenticate the devices with different digest and encryption passwords.
Deploy Cisco DCNM-SAN in a federation configuration when either of the following conditions is met:
Windows Operating System
Virtual Machines
Keep the following guidelines in mind when deploying Cisco DCNM:
If you deploy Oracle database:
You must change the default setting by performing the following steps:
Note | The password for the database expires after 180 days. |
Log in to the Oracle database.
Enter the commands, as shown in this example:
SQL> GRANT CONNECT,RESOURCE,UNLIMITED TABLESPACE TO username IDENTIFIED by password; Grant succeeded. SQL> select username,password from dba_users where username=’username’; SQL> ALTER PROFILE DEFAULT LIMIT 2 FAILED_LOG_ATTEMPTS UNLIMITED 3 PASSWORD_LIFE_TIME UNLIMITED; Profile altered. SQL> EXIT
Network Time Protocol
General Guidelines
Do not deploy Cisco DCNM when network latency is more then 50 ms from the switch management subnet to the Cisco DCNM server and Cisco DCNM database.
Deploy Cisco DCNM on high-performance tier storage (2 to 4 ms response time).
Create users with the same password digest and encryption algorithm in the device (for example, Digest, MD5) and encryption algorithm (for example, DES). Cisco DCNM will not authenticate the devices with different digest and encryption passwords.
Deploy Cisco DCNM-SAN in a federation configuration when either of the following conditions is met:
Windows Operating System
Virtual Machines
The following installation notes apply to Cisco DCNM, Release 10.1:
The Cisco DCNM Installer includes the Cisco DCNM server SAN client, Device Manager, SMI-S provider, PostgreSQL 9.4.5.
The Cisco DCNM virtual appliance includes the Cisco DCNM serve and SAN client, Device Manager, PostgreSQL, Cisco XCP, OpenLDAP, RabbitMQ, DHCPD, all of which are installed on a 64-bit CentOS.
On the Cisco DCNM Web Client, clicking the Evaluation License URL on Cisco DCNM Web Client Administration > DCNM Server > License tab results in an Invalid Referrer error message being displayed. This occurs if you have not signed out correctly during the previous instance. To resolve this, highlight the URL address in the web browser menu bar and press the Return key. Clear the web browser cache for the URL to work.
For information about installing Cisco DCNM Release 10.1, see the corresponding version of the Cisco DCNM Installation Guide at: