Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Cisco Prime DCNM Release Notes, Release 6.3 Release Date: June 14, 2014 Part Number: OL-29246-04 A0 Current Release: 6.3(2) This document provides the release notes for Cisco Prime Data Center Network Manager (DCNM), Release 6.3. Use this document in combination with the documents listed in the “Obtaining Documentation and Submitting a Service Request” section on page 24. 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: http://www.cisco.com/en/US/products/ps9369/prod_release_notes_list.html Table 1 shows the online change history for this document.
24
Embed
Cisco Prime DCNM Release Notes, Release 6 Cisco Prime DCNM Release Notes, Release 6.3 OL-29246-04 System Requirements Server Requirements Cisco DCNM Release 6.3(x) supports the following
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Cisco Prime DCNM Release Notes, Release 6.3
Release Date: June 14, 2014Part Number: OL-29246-04 A0Current Release: 6.3(2)
This document provides the release notes for Cisco Prime Data Center Network Manager (DCNM), Release 6.3. Use this document in combination with the documents listed in the “Obtaining Documentation and Submitting a Service Request” section on page 24.
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: http://www.cisco.com/en/US/products/ps9369/prod_release_notes_list.html
Table 1 shows the online change history for this document.
Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
ContentsThis document includes the following sections:
• Introduction, page 3
• System Requirements, page 3
• Hardware Supported, page 11
• Software Download Site, page 6
• Deployment Best Practices, page 6
• Installation Notes, page 8
Table 1 Online History Change
Part Number Revision Date Description
OL-29246-05 A0 June 15, 2014 • Added the “Open Caveats - Cisco DCNM Release 6.3(2)”
• Added the “Resolved Caveats—Cisco DCNM Release 6.3(2)”
• Updated the “New Features and Enhancements in Cisco DCNM Release 6.3”
• Updated the “Java Requirements”section
• Updated the “Common LAN and SAN Feature Enhancements in the DCNM Web Client”.
• Updated the “LAN Features in DCNM 6.3”section
• Updated the “SAN Features in DCNM 6.3”section
• Added the “Install and Upgrade”section
• Updated the “ •UCS B-series enhanced visibility into blade attributes and LAN features”section
OL-29246-05 A0 April 15, 2014 • Added the “Open Caveats—Cisco DCNM Release 6.3(1)”
• Added the “Resolved Caveats—Cisco DCNM Release 6.3(1)”
• Updated the “New Features and Enhancements in Cisco DCNM Release 6.3”
• Updated the “Java Requirements”section
• Updated the “Common LAN and SAN Feature Enhancements in the DCNM Web Client”.
• Updated the “LAN Features in DCNM 6.3”section
• Updated the “SAN Features in DCNM 6.3”section
• Added the “Install and Upgrade”section
• Updated the “ •UCS B-series enhanced visibility into blade attributes and LAN features”section
2Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
Introduction
• New Features and Enhancements in Cisco DCNM Release 6.3, page 8
• Supported Cisco Platforms and Software Versions, page 11
• Licensing, page 15
• Limitations in Cisco DCNM Release 6.3(x), page 17
• Caveats, page 17
• Related Documentation, page 22
• Obtaining Documentation and Submitting a Service Request, page 24
IntroductionCisco 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:
• Cisco MDS 9700 and 9500 Series Multilayer Directors, and Cisco MDS 9200 and 9100 Series Multilayer Switches
• Cisco Nexus 1000V Series Switches and Cisco Nexus 1010 Virtual Services Appliance
• Cisco Nexus 2000 Series Fabric Extenders
• Cisco Nexus 3000, 4000, 5000, 6000, 7000, and 9000 Series Switches
Cisco DCNM provides limited support for the following Cisco platforms:
• Cisco Catalyst 6500 Series Switches
• Cisco Firewall Services Module (FWSM)
• Cisco UCS 6100 and 6200 Series Fabric Interconnects
System RequirementsThis 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.
This section includes the following topics:
• Java Requirements, page 3
• Server Requirements, page 4
• Client Requirements, page 5
• Browsers, page 6
• Other Supported Software, page 6
• Software Download Site, page 6
• Hardware Supported, page 11
Java Requirements Cisco DCNM Server is distributed with Java JRE 1.7.0_55. The DCNM installer installs JRE 1.7.0_55 to the following directory: DCNM_root_directory/java/jre1.7.
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
System Requirements
Server Requirements Cisco DCNM Release 6.3(x) supports the following databases:
• Oracle 10g and Oracle11g Express (XE), Standard, and Enterprise Editions, and Oracle 11g Real Application Clusters (RAC).
• PostgreSQL 8.4
For deployment best practices, see the “Deployment Best Practices” section on page 6.
Note Customers are responsible for all support associated with Oracle and PostgreSQL databases, 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 6.3(x) supports running the Cisco DCNM server on these operating systems:
• Microsoft Windows 2008 R2 SP1 and Windows 2008 Standard SP2 (64-bit)
• Red Hat Enterprise Linux Release 5.6, 5.7, 6.3 and 6.4 (64-bit).
Note If a service pack for the Windows operating system is not listed, the service pack is not supported.
Table 2 lists the minimum and recommended database server system requirements for running Cisco DCNM.
SAN-Only Cisco DCNM Server Requirements
Table 3 lists the server resource requirements for deploying Cisco DCNM in a SAN-only environment. Follow these requirements when you are running only the Cisco DCNM server and the database is remote. If you want to run the database locally with the server, which is not a best practice, include the additional resources fromTable 2.
8-GB memory, 60-GB free hard disk 8-GB memory, 80-GB free hard disk 12-GB memory, 100-GB hard disk
PostgreSQL, Oracle 10g, and Oracle11g Express (XE)
Oracle 10g and Oracle11g Express (XE) or Standard
Oracle11g Standard or Enterprise
4Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
System Requirements
LAN-Only Cisco DCNM Server Requirements
Table 4 lists the server resource requirements for deploying Cisco DCNM in a LAN-only environment. These server requirements apply to the Cisco DCNM web client when used to collect monitoring, performance, and health information with lightweight discovery through SNMP.
LAN and SAN Cisco DCNM Server Requirements
Table 5 lists the server resource requirements for deploying Cisco DCNM in a LAN and SAN environment.
Note Although it is not mandatory, we recommend that you register the server system with DNS servers.
Client Requirements Cisco DCNM clients support Windows 7, Windows 2008, and Red Hat Linux. Table 6 lists the minimum hardware requirements for these client systems.
If Cisco DCNM-LAN and DCNM-SAN clients are launched together, the need for more CPU and memory rises to 2.0 GHz, 2 GB of free RAM, and 4 GB of free disk space.
Table 4 Cisco DCNM Server Resources for a LAN-Only Environment
Small LAN: Up to 25 Switches andUp to 1000 Ports
Medium LAN: Up to 100 Switches andUp to 3000 Ports
Large LAN: More than 100 Switches and More than 3000 Ports
8-GB memory, 80-GB free hard disk 12-GB memory, 100-GB free hard disk
2 servers, LAN or SAN federation
Oracle 10g, Oracle11g Standard or Enterprise Oracle11g Standard or Enterprise
Table 6 Client Hardware Requirements
Hardware Minimum Requirements
RAM (free) 1 GB
CPU speed 2.16 GHz (or faster) with one dual core processor or two single-core processors
Disk space (free) 2 GB
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
Software Download Site
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 6.x.
Be sure to set the correct time zone value on the system clock (for example, UTC). Otherwise, Cisco DCNM-LAN cannot manage the switch properly.
BrowsersWeb browsers that support Adobe Flash 10 are qualified for use with Cisco DCNM. These include Internet Explorer, Firefox, and Safari.
Other Supported SoftwareTable 7 lists other software supported by Cisco DCNM Release 6.3(x).
In addition, Cisco DCNM supports the following types of events sent from DCNM: EMC Call Home events, fabric change events, and events that are forwarded by traps and e-mail.
Software Download SiteTo download the latest Cisco DCNM software, go to http://www.cisco.com/go/dcnm and click Download Software.
Deployment Best PracticesObserve the following guidelines when deploying Cisco DCNM:
Table 7 Other Software Supported by Cisco DCNM
Other Supported Software
Security:
ACS Versions, 4.0, and 5.1
Firewall/Cisco DCNM-SANServer Proxy: PIX Firewall, IP Tables
SSH version 1, SSH version 2, Global Enforce SNMP Privacy Encryption
Web Client and Cisco DCNM-SAN Server Encryption: HTTPS
Performance Manager:
SNMP over UDP
SNMP over TCP
Virtual Machines:
ESX Server version 4.x or 5.x.
VMs that run any qualified or supported operating system version can run Cisco DCNM.
– During the initial installation, disable all security and anti virus tools that are running on your Windows server.
– Do not run any other management applications on the Cisco DCNM server or the Cisco DCNM database server.
• Virtual Machines
– When Cisco DCNM is deployed as a virtual machine (VM), do not share CPU and memory resources with other VMs on the virtual host.
– When Cisco DCMM is deployed as a VM, do not share the data store with other VMs.
– CPU/Memory Resource must be reserved.
• Database
– We recommend PostgreSQL for small, non-production or lab environments.
– Deploy an Oracle database when managing production or mission critical environments.
– Deploy an Oracle database on a separate server from the Cisco DCNM application server.
– If you plan to use an Oracle 11g database, configure the Oracle database as follows:
Increase the number of sessions and processes to 150 each from the default of 50.
Increase the number of open cursors to 500 from the default of 300.
– We recommend deploying Oracle 10g or Oracle11g for mission-critical production environments.
Note The password for the Oracle 11g Express (XE) database expires after 180 days. You must change this setting by using the following steps.
1. Log in to the Oracle database.
2. 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
– We recommend that the Cisco DCNM server run the Network Time Protocol (NTP) to synchronize its clock with those of the managed devices.
• 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 ms to 4 ms response time).
– Deploy Cisco DCNM SAN in a federated configuration when the switch count exceeds 150 switches or the port count exceeds 15,000 connected ports per management server (whichever comes first).
– Create users with the same password digest (for example, MD5) and encryption algorithm (for example, DES) for the same user on all switches in the Fibre Channel fabric. (MD5 and DES are the defaults.) Otherwise, Cisco DCNM-SAN will not be able to authenticate a user on the fabric if that user has different digest and encryption algorithms.
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
Installation Notes
Installation NotesThe following installation notes apply to Cisco DCNM Release 6.3:
• The Cisco DCNM Installer includes the Cisco DCNM server and clients, Device Manager, SMI-S provider, PostgreSQL 8.4, and Strawberry Perl version 5.10.0.
• Upgrade support is available from Cisco DCNM Release 6.2 to Cisco DCNM Release 6.3.
For information about installing and uninstalling Cisco DCNM Release 6.(x), see the Cisco DCNM Installation and Licensing Guide, Release 6.x. You can find this publication on Cisco.com at this location:
New Features and Enhancements in Cisco DCNM Release 6.3Cisco DNCM Release 6.3 includes the new features, enhancements, and hardware support that are described in the following sections:
• Common LAN and SAN Feature Enhancements in the DCNM Web Client, page 8
• LAN Features in DCNM 6.3, page 9
• SAN Features in DCNM 6.3, page 9
• Install and Upgrade, page 9
• Platforms Support, page 10
• •UCS B-series enhanced visibility into blade attributes and LAN features, page 10
Common LAN and SAN Feature Enhancements in the DCNM Web ClientThe following features are available in the Cisco DCNM web client for LAN and SAN functionality:
• Topology view in the Summary Dashboard has been extended to separate SAN and LAN elements.
• Three layout options: organic, radial and circular.
• Shared interface configuration template.
Topology enhancement for the Summary Dashboard in the DCNM Web Client
Based on the selected Scope, you can view the enhanced topology in the Summary Dashboard of the DCNM Web Client. The new topology has the following features
• Three viewing options - Organic, radial and circular
• Ability to zoom in and zoom out
• Expand and collapse groups and VDCs
• Collapsed VDC groups display the VDC name and summary count of the elements in the group
New Features and Enhancements in Cisco DCNM Release 6.3
LAN Features in DCNM 6.3Cisco DCNM Release 6.3 supports these LAN features:
• Support for On-Demand Discovery of IPv4 and IPv6 ACLs - You can use the hyper link in IPv4 and IPv6 ACL to trigger the discovery of IPv4 and IPv6 ACL. Only on-demand discovery of ACLs are supported on the LAN Client.
• IPv4 and IPv6 ACL Widgets - ACL widgets have been added in the Advance Settings pane.
Cisco DCNM Release 6.3 supports these additional managed LAN platforms
• Discovery of Nexus 7000 and Nexus 7700 devices having F3 module support.
• Cisco Nexus 7700 6-slot switch
• Cisco Nexus 7000 F3-1 F3-100G ethernet module
• Cisco Nexus 3172PQ hardware support
• Cisco Nexus 56128P chassis support
• Cisco Nexus 5672UP chassis support
• Cisco Nexus 6004 EF CR chassis support
• Cisco Nexus 9300 chassis support
• Cisco Nexus 9500 48 Port SFP+ and 4 Port QSFP+ line card support
• Cisco Nexus 9500 48 Port 10G-T and 4 Port QSFP line card support
• Cisco Nexus B22IBM fabric extender support.
• M20UP LEM support.
• Break out ports support
– 4 X 10 Break out support on 6-port 40-gigabit ethernet I/O module with XL option)
– 4 X 10 break out support on Nexus 7000 F3-series 12-port 40G ethernet module
SAN Features in DCNM 6.3Cisco DCNM Release 6.3 supports these features for Cisco DCNM SAN:
• Virtual Fibre Channel Interfaces Support
• MDS Forward Error Correction (FEC) support for 16-Gbps ISL connections
• DM idle timeout
Install and UpgradeCisco DCNM Release 6.3 has the following enhancements to the installation and upgrade steps:
• Both DCNM LAN and SAN will be installed through the DCNM installer.
• DCNM LAN cluster is not supported.
• Common installation location for DCNM SAN and DCNM LAN.
• Only HTTP and HTTPS ports can be configured. Based on the availability, all other ports will be selected automatically by the installer.
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
New Features and Enhancements in Cisco DCNM Release 6.3
Platforms SupportCisco DCNM Release 6.3 supports the following platforms:
– Cisco Nexus 3548P switch - Cisco Nexus 3000 buffer usage charts and tabular data for micro-burst monitoring
• Cisco Nexus 2000 Series,
• Cisco Nexus 1000V for Microsoft Hyper-V
• UCS B-series enhanced visibility into blade attributes and LAN features
1Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
Supported Cisco Platforms and Software Versions
Supported Cisco Platforms and Software VersionsFor information about the software platforms and versions that Cisco DCNM supports, see the Cisco DCNM Release Compatibility Matrix, Release 6.x.
Note For compatibility reasons, we recommend that you run the same version (or a later version) of Cisco DCNM as Cisco NX-OS software.
Hardware SupportedTable 8 lists the products and components that Cisco DCNM Release 6.3 supports.
Table 8 Hardware Features Supported by Cisco DCNM Release 6.3
Product/Component Part Number
Cisco MDS 9000 Family
Cisco MDS 9000 4-port 1-Gbps IP Storage Module DS-X9304-SMIP
Cisco MDS 9000 8-port 1-Gbps IP Storage Module DS-X9308-SMIP
Table 8 Hardware Features Supported by Cisco DCNM Release 6.3
Product/Component Part Number
1Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
Licensing
LicensingThe free product features that come with Cisco Prime DCNM are referred to as Essentials Edition. 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.
For the list of these features, see the Cisco DCNM Installation and Licensing Guide, Release 6.x.
Cisco DCNM Advanced Edition can be licensed for both LAN and SAN switches using the product IDs listed in Table 9.
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
Product IDs for Cisco Fabric Manager licenses are listed in Table 10.
In addition, Cisco DCNM supports the existing switch based SAN license, FMS_SERVER_PKG. For additional information about Cisco Fabric Manager licenses, see the Cisco Fabric Manager Release Notes on Cisco.com.
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.
Cisco Nexus 7700 LAN DCNM-LS-N77-K9 L-DCNM-LS-N77K9 DCNM-LS-N77-K9
Cisco Nexus 7700 SAN and LAN
DCNM-LS-N77-K9= L-DCNM-LS-N77K9= DCNM-LS-N77-K9
Cisco Nexus 6001 SAN DCNM-SAN-N61-K9= L-DCNM-S-N61-K9= DCNM-SAN-M61-K9
Cisco Nexus 6001 LAN DCNM-LAN-N61-K9= L-DCNM-L-N61-K9= DCNM-LAN-N61-K9
Cisco Nexus 6001 SAN and LAN
DCNM-LS-N61-K9= L-DCNM-LS-N61K9 DCNM-LS-N61-K9
Cisco Nexus 6004 SAN DCNM-SAN-N64-K9= L-DCNM-S-N64-K9= DCNM-SAN-M64-K9
Cisco Nexus 6004 LAN DCNM-LAN-N64-K9= L-DCNM-L-N64-K9= DCNM-LAN-N64-K9
Cisco Nexus 6004 SAN and LAN
DCNM-LS-N64-K9= L-DCNM-LS-N64K9 DCNM-LS-N64-K9
Cisco Nexus 5000 SAN DCNM-SAN-N5K-K9= L-DCNM-SAN-N5K-K9= DCNM-SAN-N5K-K9
Cisco Nexus 5000 LAN DCNM-LAN-N5K-K9= L-DCNM-LAN-N5K-K9= DCNM-LAN-N5K-K9
Cisco Nexus 5000 SAN and LAN
DCNM-LS-N5K-K9= NA DCNM-LS-N5K-K9
Cisco Nexus 3000 LAN DCNM-LAN-N3K-K9= L-DCNM-L-N3K-K9= DCNM-LAN-N3K-K9
Table 10 Cisco Fabric Manager License Product IDs
Platform PID, Paper Delivery (envelope) PID, Electronic Delivery (e-mail)
Registering a Product Authorization KeyTo 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:
1. Go to http://www.cisco.com/go/license.
2. Enter the PAK, contact information, and MAC address or host ID of the Cisco DCNM server.
The license is sent as an e-mail attachment that is uploaded to Cisco DCNM Server and then assigned from the licensing pool to individual switches.
Limitations in Cisco DCNM Release 6.3(x)
License Installer
The license installer in Cisco DCNM Release 6.3 supports only US English. Attempting to install a license for any locale other than US English results in an error.
SMI-S API Support
A Storage Management Initiative Specification (SMI-S) API is not supported in a federated Cisco DCNM configuration. The use of an SMI-S provider for northbound integration requires at least one switch to be licensed in a fabric.
CaveatsThis section includes the following topics:
Symptom: Enabling NPV through the wizard not working for the 9148S platform.
Conditions: After the switch reload after enabling NPV, DCNM waits for 80 seconds and then tries SNMP authentication and querying the ports, but the platform takes greater than 6 minutes to reload.The timeout can not be increased from 80 seconds to 6 minutes in DCNM.
Workaround: Use DCNM SAN Client UI to enable NPV mode for the switch.
• CSCup75509
Symptom: When you select TACACS+/Radius authentication in the DCNM Web Client using Admin>Remote AAA section and click Apply, You will not be able to login in to the Web Client with the AAA credentials unlike the DCNM LAN and SAN clients.
Conditions: This happens when you select TACAS+/ Radius authentication in Admin>Remote AAA section of the DCNM Web Client
Workaround: Logout of the DCNM Web Client and other DCNM clients. Stop and re-start the DCNM server. Now, connect to the DCNM Web Client and enter the TACACS+/Radius credentials and you will be able to login.
• CSCuo31949
Symptom: Scheduled report job execution details are not getting updated in Admin->Logs>Web reports log, instead it is reflecting in the JBoss7 logs.
Conditions: When a scheduled job is executed, the execution details must be updated in the web reports log
Workaround: Look for the execution status details at the following path <DCNM_Install>/fm/logs/jboss7.log
• CSCuo15884
Symptom: In the DCNM LAN client>Topology view, when you click on the Device icon, the Discovery Port displayed in incorrect.
Conditions: Device is discovered on mgmt 0 port using an IP and managed in DCNM. Now this mgmt IP is removed from the mgmt 0 port and configured on the SVI and device is made reachable on SVI using the same IP. It is expected that when the Device icon is clicked, DCNM should display the new SVI as discovery port.
Workaround: Re-launch the client or re-discover the device.
Symptom: DCNM-SAN (Fabric Manager GUI) is reporting the following error in the ‘Fabric Configuration Analysis’ tool - Domain_Manager Domain ID not configured (value 0) on VSAN 4094.
Conditions: Fabric Configuration Analysis' tool compared two switches from same fabric.=
Workaround: Ignore the error since VSAN 4094 (isolated VSAN) not having a domain ID is expected: Isolated VSAN does not require a Domain ID. Hence, DCNM should not report the error.
• CSCum86620
Symptom: During testing, it was found that the web server hosting for Cisco Prime Data Center Network Manager (DCNM) is vulnerable to XSS attacks.
Conditions: Running versions of DCNM prior to this bugfix.
Workaround: Upgrade DCNM to 6.3(2)
1Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
Caveats
Open Caveats—Cisco DCNM Release 6.3(1)This section lists caveats that apply to both Cisco DCNM-LAN and Cisco DCNM-SAN.
• CSCui79470
Symptom: unable to move port channels from one VDC to another in the DNCM GUI, while allocating NAM ports to a different VDC from the CLI.
Conditions:
– Device Behavior - While allocating NAM ports from CLI to another VDC, the port channels will also move to the new VDC along with the NAM ports.
For non NAM ports, when the port channels are configured and allocated to another VDC, the port channel configuration will not move to the new VDC but resides as inactive on the existing VDC. You must reconfigure the VDC to add the port channel configuration
– DCNM Behavior - By default, DCNM is configured to handle non NAM ports scenario. If you move the port-channel configurations to a new VDC, it will not move to the new VDC and still be listed on the older VDC with the status as Inactive.
Workaround: Rediscover the device. Also, after the periodic discovery, the changes will reflect on DCNM.
• CSCuo23389
Symptom: One you have installed DCNM 6.3(1) on a windows machine and you navigate to Control Panel > Progams, you can see DCNM also listed as one of the installed programs. An attempt to uninstall on DCNM program from here does not work and displays an error.
Conditions: This has been observed on windows 2008 servers and is attributed to the usage of JRE 1.7 with Install.
Workaround: To uninstall DCNM, you can navigate to the Start > All Programs > Cisco DCNM server > Uninstall DCNM to uninstall DCNM from the system.
• CSCuo04743
Symptom: Cisco SMI-S agent does not start automatically after a power cycle on DCNM 6.2.5a.
Conditions: DCNM running on a RedHat Server.
Workaround: Edit the file /etc/inti.d/ciscosmis and look for the VARIABLE "CISCOSMIS". Change it from
CISCOSMIS=${INSTALLDIR}/dcm/fm/bin/CiscoSMIS.sh to CISCOSMIS=${INSTALLDIR}/bin/CiscoSMIS.sh
In DCNM 6.3(1), You must restart DCNM once the VM comes up after restart.
Resolved Caveats—Cisco DCNM Release 6.3(1)This section lists caveats that apply to both Cisco DCNM-LAN and Cisco DCNM-SAN.
• CSCun20623
Symptom: DCNM-SAN (Fabric Manager GUI) is reporting the following error in the ‘Fabric Configuration Analysis’ tool - Domain_Manager Domain ID not configured (value 0) on VSAN 4094.
Conditions: Fabric Configuration Analysis' tool compared two switches from same fabric.
• Workaround: Ignore the error since VSAN 4094 (isolated VSAN) not having a domain ID is expected: Isolated VSAN does not require a Domain ID. Hence, DCNM should not report the error.
• CSCun30503
Symptom: dmDomainId reports mismatch within VSAN in Fabric Configuration Analysis
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
Conditions: Fabric Configuration Analysis in DCNM 6.x and NExus 55xx switches are configured with static DomainIDs in all VSANs.
Workaround: Ignore the mismatch failure message in DCNM since each switch has to be set with different DomainID within the same VSAN across a fabric.
• CSCun59948
Symptom: While editing the IVR Local Full Zone database in DCNM, the following error message is displayed” civrZoneMemberVsan.42.4: wrong value- OES9710-95X-9ASJL civrZoneMemberVsan.42.4 Failed to add 1 members out of 1”
Conditions: If we try to add a member to a zone, which is not logged into the fabric yet, DCNM displays the error.
Workaround: Add the device through the CLI on the MDS or use FM Client Member addition dialog to add device alias with no end device in Fabric.
• CSCum50511
Symptom: On an MDS with VSAN trunking enabled in the switch ports, DCNM does not display SMI-S information on all the VSANs
Conditions: When we traverse from CISCO_fcport to CISCO_logicalfcport using CIM_HostedDependency, we are not getting all the hosted references.
Workaround: None.
• CSCum92934
Symptom: SMIS agent is not displaying AC in Portchannel ISL, though its trunked or not
Conditions: None
Workaround: None
• CSCun02156
Symptom: In DCNM, topology view shows links as red but there is very little traffic flowing over them.
Conditions: None
Workaround: None
• CSCun37279
Symptom: DCNM SMI-S displays an error while retrieving the zoneset.
Conditions: SMI S client query to retrieve zoneset
Workaround: None
• CSCun39195
Symptom: SMI-S query of DCNM produces the same VSAN WWN for two different VSANs.
Conditions: Using DCNM with external SMI-S agent
Workaround: None
2Cisco Prime DCNM Release Notes, Release 6.3
OL-29246-04
Caveats
• CSCun69883
Symptom: Upgrade fails if Postgres database has long password with special characters
Conditions: None
Workaround: None
• CSCun98707
Symptom: DCNM may fail to authenticate various functionality when a long password (greater than 16 characters) is used
Conditions: When password is greater than 16 characters.
Workaround: use a password which is maximum 16 characters or less.
• CSCum86141
Symptom: In the DCNM Web Client. missing end host IP addresses in dashboard>compute
Conditions: Upgrade from DCNM 6.2(3) to 6.2(5) on PostgreSQL back-end database.
Workaround: Alter lan_host table as postgres db admin to add missing column: (alter table dcmdb.lan_host add vhost_id bigint;).
• CSCum86150
Symptom: Only dynamic MAC address are stored in DCNM DB from LAN discovery action but static MAC aren't stored, Another N7k running 5.2(3a) has less XML data transmitted. Also, data is not collected from peer vPC Nexus device to create XML data for DCNM: DCNM is not processing vPC peer link
Conditions: DCNM server managing Nexus Layer-3 enabled device (N7k).
Workaround: Parse all IP addresses from Nexus and its vPC peer, not just the XML data.
• CSCum55969
Symptom: Port-channel wiz shows incorrect ISL for OUI 00:2a:6a.
Conditions: Port channel link displays like ISL link and also Fport channel displays like F-NP link, and in the port channel wizard it displays as an ISL.
Workaround: None.
• CSCun74622
Symptom: Settings in the DCNM-SAN client, such as the SNMP timeout value, are not persistent across different sessions
Conditions: Normal operating conditions.
Workaround: This workaround enables to specify your own default SNMP TIMEOUT (even though the set of client preferences are lost). You will be able to use the client installed on the DCNM server machine. You must avoid using the web-launched Java client. To use the Java client on a remote machine, you will need to install the SAN Client Package on each machine. The startup script needs updating as well.
On the machine where DCNM server is installed, add "-Dsnmp.timeout=20000" to the startup script
In the following file, set JVMARGS=%JVMARGS% -Dsnmp.preferTCP=false -Dsnmp.timeout=20000
Symptom: “Move” button is removed from the federation “Servers” tab.
Conditions: DCNM 6.3(1) running JBOSS 7.
Workaround: Due to JBOSS 7 introduced in DCNM 6.3(1), client cannot reference multiple servers simultaneously. The button is removed. You are recommended to do "Move" operation through the DCNM Web Client.
• CSCun27618
Cisco Prime DCNM Release Notes, Release 6.3OL-29246-04
Related Documentation
Symptom: Scheduled job does not work after server restart.
Conditions: When the server is restarted, job triggers are cached in local memory. and they are getting cleared after the restart.
Workaround: After the upgrade, a new job has to be created.
Related DocumentationThis section contains information about the documentation available for Cisco DCNM and for the platforms that Cisco DCNM manages.
This section includes the following topics:
• Cisco DCNM Documentation
• Cisco Nexus 1000V Series Switch Documentation
• Cisco Nexus 2000 Series Fabric Extender Documentation
• Cisco Nexus 3000 Series Switch Documentation
• Cisco Nexus 4000 Series Switch Documentation
• Cisco Nexus 5000 Series Switch Documentation
• Cisco Nexus 6000 Series Switch Documentation
• Cisco Nexus 7000 Series Switch Documentation
• Catalyst 6500 Series Switch Documentation
Cisco DCNM DocumentationThe Cisco DCNM documentation is available at the following URL:
Obtaining Documentation and Submitting a Service RequestFor 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.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)