Guest

Cisco Prime Data Center Network Manager

Cisco DCNM Release Notes, Release 4.1

  • Viewing Options

  • PDF (327.4 KB)
  • Feedback
Cisco DCNM Release Notes, Release 4.1

Table Of Contents

Cisco DCNM Release Notes, Release 4.1

Contents

Introduction

System Requirements

Java Requirements

Server System Requirements

Client System Requirements

Supported Device Operating Systems

Supported Device Hardware

New Hardware Features

New Software Features

New Feature in Cisco DCNM Release 4.1(3)

vPCs

New or Changed Features in Cisco DCNM Release 4.1(2)

New Topology Views

Event Browser Tab

Configuration Change Control

Scheduling and Monitoring the Installation of the Operating System Software

Scheduling the Deletion of Old Event Data

Scheduling the Deletion of Old Statistical Data

VDC Setup Wizard Enhancement

Hot Standby Router Protocol

Limitations

vPC

Installation Notes

Caveats

Open Caveats—Cisco DCNM Release 4.1(5)

Open Caveats—Cisco DCNM Release 4.1(4)

Open Caveats—Cisco DCNM Release 4.1(3)

Resolved Caveats—Cisco DCNM Release 4.1(5)

Resolved Caveats—Cisco DCNM Release 4.1(4)

Resolved Caveats—Cisco DCNM Release 4.1(3)

Resolved Caveats—Cisco DCNM Release 4.1(2)

Related Documentation

Obtaining Documentation and Submitting a Service Request


Cisco DCNM Release Notes, Release 4.1


Release Date: August 3, 2009
Part Number: OL-18650-03 B0

This document provides the release notes for Cisco Data Center Network Manager (DCNM). Use this document in combination with documents listed in the "Obtaining Documentation and Submitting a Service Request" section.


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.

Table 1 Online History Change

Part Number
Revision
Date
Description

OL-18650-01

A0

December 18, 2008

Created release notes for Release 4.1(2).

Note Cisco NX-OS Release 4.1(1) is for use only on the Cisco MDS products.

B0

January 16, 2009

Added limitation that Release 4.1(2) DCNM does not support the vPC feature.

OL-18650-02

A0

February 6, 2009

Created release notes for Release 4.1(3).

OL-18650-03

A0

March 17, 2009

Created release notes for Release 4.1(4).

B0

March 20, 2009

Added CSCsy43995 as a resolved caveat.

OL-18650-04

A0

April 5, 2009

Created release notes for Release 4.1(5)

 

B0

August 3, 2009

Updated the client Microsoft Windows requirements.


Contents

This document includes the following sections:

Introduction

System Requirements

New Hardware Features

New Software Features

Limitations

Installation Notes

Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

DCNM is a management solution for Cisco NX-OS-enabled hardware platforms. Focused on the management requirements of data center networks, DCNM automates the provisioning process, monitors the network for performance degradation, secures the network, and streamlines the diagnosis of dysfunctional network elements.

Cisco NX-OS supports the Cisco Nexus product family, including the Cisco Nexus 7000 Series. For the most recent information on Cisco NX-OS, refer to the following website:

http://www.cisco.com/en/US/products/ps9372/prod_release_notes_list.html

System Requirements

This section includes the following topics:

Java Requirements

Server System Requirements

Client System Requirements

Supported Device Operating Systems

Supported Device Hardware

Java Requirements

DCNM is a Java-based client-server application. The DCNM 4.1 server and client support Java JRE 1.5.0_11.

Server System Requirements

DCNM 4.1 supports running the DCNM server on either of the following two operating systems:

Microsoft Windows Server 2003 Enterprise Edition, Service Pack 1, 32-bit edition only

The minimum hardware requirements for the DCNM server running on Windows Server 2003 are the following:

3.45-GHz dual-processor or dual-core CPU

6 GB of system RAM

60 GB of free disk space

Red Hat Enterprise Linux AS Release 4, 32-bit edition only

The minimum hardware requirements for the DCNM server running on Linux are the following:

3.40-GHz dual-processor or dual-core CPU

6 GB of system RAM with a maximum shared memory size of at least 128 MB

60 GB of free disk space

Additionally, the following prerequisites must be in place for the server:

A Perl environment must already be installed on the server system. We recommend using Active Perl version 5.8.8.822.

The path to the Perl executable must be defined in the server system PATH environment variable.

No other programs are running on the server.

Client System Requirements

DCNM 4.1 supports running the DCNM client on Microsoft Windows XP Professional Service Pack 2. The minimum hardware requirements for running the DCNM client are the following:

2.16-GHz single-core CPU

1 GB of system RAM

Supported Device Operating Systems

The Cisco DCNM Release 4.1(2) or later supports management and monitoring of devices that run Cisco NX-OS Release 4.0 or later.

Supported Device Hardware

DCNM Release 4.1(2) supports management and monitoring of the Cisco Nexus 7010 switch and Cisco Nexus 7018 switch. Although you can use DCNM Release 4.0 to manage a Cisco Nexus 7010 switch, you must use DCNM Release 4.1(2) (or a later release) to manage a Cisco Nexus 7018 switch, the 7.5-kW AC power supply unit, and the 48-port 1-Gigabit SFP I/O module. Table 2 shows which hardware features are supported by DCNM Release 4.0 and DCNM Release 4.1(2) (and newer).

Table 2 Hardware Features Supported by DCNM Releases  

Hardware
Part Number
DCNM Release 4.0 Support
DCNM Release 4.1(2) (and Later) Support

Cisco Nexus 7010 chassis

N7K-C7010

X

X

Cisco Nexus 7018 chassis

N7K-C7018

-

X

Supervisor module

N7K-SUP1

X

X

Fabric module, Cisco Nexus 7000 Series 10-slot

N7K-C7010-FAB-1

X

X

Fabric module, Cisco Nexus 7000 Series 18-slot

N7K-C7018-FAB-1

-

X

48-port 10/100/1000 Ethernet I/O module

N7K-M148GT-11

X

X

48-port 1-Gigabit Ethernet SFP I/O module

N7K-M148GS-11

-

X

32-port 10-Gigabit Ethernet SFP+ I/O module

N7K-M132XP-12

X

X

System fan tray for the Cisco Nexus 7010 chassis

N7K-C7010-FAN-S

X

X

Fabric fan tray for the Cisco Nexus 7010 chassis

N7K-C7010-FAN-F

X

X

Fan tray for the Cisco Nexus 7018 chassis

N7K-C7018-FAN

-

X

6-kW AC power supply unit

N7K-AC-6.0KW

X

X

7.5-kW AC power supply unit

N7K-AC-7.5KW-INT
N7K-AC-7.5KW-US

-
-

X
X


New Hardware Features

The Cisco DCNM Release 4.1(2) is initially released at the same time that the following hardware is released for the Cisco Nexus 7000 Series switches:

Cisco Nexus 7018 switch, which includes the new fabric module. The switch supports two supervisor modules, up to 16 I/O modules, up to five fabric modules, and up to four power supply units.

Cisco Nexus 7018 fabric module, which provides up to 230 Gbps of fabric bandwidth for each I/O and supervisor module installed on the Cisco Nexus 7018 switch.

48-port, 1-Gigabit Ethernet SFP I/O module, which is supported by the Cisco Nexus 7010 switch and the Cisco Nexus 7018 switch.

7.5-kW AC power supply unit, which is supported by the Cisco Nexus 7010 switch and the Cisco Nexus 7018 switch. You can install up to three of these power supply units in the Cisco Nexus 7010 switch and up to four of these power supply units in the Cisco Nexus 7018 switch.

Cisco Nexus 7018 fan tray, which provides cooling for the supervisor, I/O, and fabric modules.


Note The new hardware requires that you have the Cisco NX-OS Release 4.1(2) operating system installed on your switch. If you are using the Cisco DCNM software to access the hardware, you must have Cisco DCNM Release 4.1(2) or later installed on the system.


New Software Features

This section describes the new features introduced in the releases of Cisco DCNM. For detailed information about the features listed, see the documents listed in the "Obtaining Documentation and Submitting a Service Request" section. The "New and Changed Information" section in each of these books provides a detailed list of all new features and includes links to the feature description or new command.


Note There are no new software features for Releases 4.1(4) and 4.1(5).


This section includes the following topics:

New Feature in Cisco DCNM Release 4.1(3)

New or Changed Features in Cisco DCNM Release 4.1(2)

New Feature in Cisco DCNM Release 4.1(3)

This section includes the following topic:

vPCs

vPCs

A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus 7000 Series devices to appear as a single port channel by a third, downstream device. The third device can be a switch, server, or any other networking device that support IEEE 802.3ad port channels.

vPCs increase usable bandwidth by eliminating STP blocked ports in common dual-homed designs. The vPC is transparent to the neighbor devices, and those neighbors need only support port channels, using static or LACP configuration. Each device in the vPC retains it own independent control and data planes. vPC provides supports for dual supervisors on each device.


Note You create the vPC peer link on two N7K-M132XP-12 modules. If you are attempting to configure the vPC on an incorrect version of the N7K-M132XP-12 module, the screen displays the following error message:
Error when applying the configuration to the device <ip_address> (vPC enable status: Incompatible hardware not enabling vPC.

Please contact your Cisco Account Team if you see this message.


New or Changed Features in Cisco DCNM Release 4.1(2)

This section includes the following topics:

New Topology Views

Event Browser Tab

Configuration Change Control

Scheduling and Monitoring the Installation of the Operating System Software

Scheduling the Deletion of Old Event Data

Scheduling the Deletion of Old Statistical Data

VDC Setup Wizard Enhancement

Hot Standby Router Protocol

New Topology Views

The topology map has been updated with new views to support VLANs/STP.

Event Browser Tab

When you apply an event filter, DCNM generates and displays the results in an event browser tab.

Configuration Change Control

DCNM allows you to perform the following configuration change control functions:

Retrieve the configuration from Cisco Nexus 7000 Series devices.

Schedule archiving of devices.

Browse multiple configurations for a device.

Compare configurations for a device.

Merge changes for one configuration with other configurations.

Rollback to a desired configuration with the option to stop, skip erroneous commands, and continue or undo all rollback changes if one step fails.

Rollback is not supported for checkpoints across software versions.

Save a configuration to startup after a rollback.

Scheduling and Monitoring the Installation of the Operating System Software

DCNM allows you to schedule and monitor the installation of the operating system software on a managed device.

Scheduling the Deletion of Old Event Data

You can use the Auto-Synchronizing feature to schedule the deletion of old event data from the database.

Scheduling the Deletion of Old Statistical Data

You can use the Statistical Data Collection feature to schedule the deletion of old statistical data from the database.

VDC Setup Wizard Enhancement

The VDC setup wizard allows you to create a new VDC resource template to use when you create a VDC.

Hot Standby Router Protocol

The Hot Standby Router Protocol (HSRP) is a First Hop Redundancy Protocol (FHRP) that allows a transparent failover of the first-hop IP router. HSRP provides first-hop routing redundancy for IP hosts on Ethernet networks configured with a default router IP address. You can use DCNM to set up HSRP for a group of routers to select an active router and a standby router. In a group of routers, the active router is the router that routes packets; the standby router is the router that takes over when the active router fails or when preset conditions are met.

Limitations

This section describes the limitations in Cisco DCNM Release 4.1(3).

This section includes the following topics:

vPC

vPC

You can configure up to 50 vPCs with a switch.

Installation Notes

For information about installing and uninstalling Cisco DCNM 4.1, see the Cisco DCNM Fundamentals Configuration Guide, Release 4.1 at the following website:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_1/dcnm/fundamentals/configuration/guide
/dcnm_fund_config.html

Caveats

This section includes the following topics:

Open Caveats—Cisco DCNM Release 4.1(5)

Open Caveats—Cisco DCNM Release 4.1(4)

Open Caveats—Cisco DCNM Release 4.1(3)

Resolved Caveats—Cisco DCNM Release 4.1(4)

Resolved Caveats—Cisco DCNM Release 4.1(3)

Resolved Caveats—Cisco DCNM Release 4.1(2)

Open Caveats—Cisco DCNM Release 4.1(5)

This section lists the open caveats for Release 4.1(5)

CSCta99305

Symptom: When attempting to manage a Cisco Nexus 7000 Series switch using DCNM, DCNM sometimes reports the switch as unreachable.

Conditions: The DCNM server is attempting to discover the Cisco Nexus 7000 Series switch by an Interface other than mgmt0.

Workaround: Use the mgmt0 interface to manage the Cisco Nexus 7000 Series switch.

Open Caveats—Cisco DCNM Release 4.1(4)

This section lists the open caveats for Release 4.1(4).

CSCsx43116

Symptom: Failed to restart the DCNM Server service.

Condition: When the DCNM server service started, the "The Cisco DCNM Server serivce launched, but failed to start" message displays.

Workaround:

1. Delete the files in the DCNM_ROOT\jboss-4.2.2.GA\server\dcnm\data\hypersonic directory.

2. Start the DCNM Server.

CSCsy10752

Symptom: The DCNM client does not respond when you use the topology view.

Conditions: Launch the DCNM client and choose different topology options such as "PortChannel and vPC topology" or "VLAN/STP topology." Sometimes, the DCNM client does not repond.

Workaround: Terminate the client using the Windows Task Manager utility and relaunch the client.

CSCsy31174

Symptom: DCNM loads multiple chart windows for the same monitoring entity, but it plots only one chart and leaves the other charts blank. Closing any of the blank chart windows stops the monitoring for the same entity in the other windows.

Conditions: The following conditions lead to this problem:

1. Start the DCNM client and monitor for a particular entity that belongs to a licensed device.

2. Create multiple charts (by choosing New Chart on the tool bar menu or by using the tear-off of the chart window) for the same monitoring entity.

3. Stop the client without stopping the monitoring.

4. Restart the client and select the monitoring entity to load the multiple charts for the same monitoring entity. DCNM plots only one chart and leaves the other charts blank. If you close any of the blank chart windows, DCNM stops monitoring the entity.

Workaround:

1. Before closing any of the blank chart windows, stop the monitoring from any of the multiple chart windows and close the blank charts.

2. Restart the monitoring by clicking Start in the chart window that displays the plotted data.

CSCsy33464

Symptom: The vPC summary screen does not show newly created vPCs.

Conditions:

1. Create a vPC by using the wizard.

2. In the device, use the no feature vpc and feature vpc configuration commands.

3. Recreate the vPC by using the wizard.

4. Check the vPC summary screen. The table does not show the vPC that you created.

Workaround: Refresh the vPC summary screen by clicking the refresh icon or by pressing F5.

Open Caveats—Cisco DCNM Release 4.1(3)

This section lists the open caveats for Release 4.1(3).

CSCsl31907

Symptom: Device discovery goes into a loop or new syslogs are not displayed in Event Browser and the corresponding status changes for all features will not be updated. Any configurations changes will not be reflected in DCNM.

Condition: You may see this symptom under the following conditions:

1. When the system clock time (or time zone) in the device has been changed either before or after device discovery to past time.

2. When the system clock time is set to past time at the end of summer time.

For example, the device has logs with time stamp of "Tue Mar 25 16:00:00 UTC 2008," and now the device is discovered using DCNM when the system time is "Thu Mar 27 15:00:00 UTC 2008" in the device.

Now that the clock time in the device has been changed to "Tue Mar 25 15:00:00 UTC 2008," DCNM will keep discovering the device in loop.

Workaround: Clear the accounting log by entering the clear accounting log CLI command on the device. Clear the system log by enterint the clear logging logfile CLI command on the device. This will automatically trigger a rediscovery in DCNM for this device.

CSCsv40655

Symptom: A discovery of devices fails with one of the following error messages:

"Error saving data to DB for IP_address"

"Discovery of IP_address failed due to server error"

Condition: A discovery can fail if directly connected devices are discovered concurrently.

Workaround: You can use one of the following workarounds:

Discover the interconnected devices by using a single discovery task and specifying an appropriate hop count.

Run one discovery task at a time and wait for it to complete before creating a new discovery task.

CSCsw36915

Symptom: DCNM uninstallation stops with a "Deleting DCNM database" message.

Conditions: You tried to uninstall DCNM after the DCNM IP address changed.

The DCNM installer/uninstaller checks the server status before proceeding. The server running the status check fails because the IP address changed. In this case, the DCNM uninstaller is trying to delete the DCNM database while the server is connected to the database.

Workaround: Stop the DCNM server and then start the uninstallation or reinstallation.

CSCsx16430

Symptom: You cannot create, view, or associate object groups using DCNM. And you cannot attach a object group as a source or destination match address of IPv4 and IPv6 access rules using DCNM.

Conditions: DCNM does not support object groups. If you create objects group for use with some ACLs, DCNM will not show the information properly. You cannot create, view, or associate object groups using DCNM.

Workaround: No workaround.

CSCsx24328

Symptom: When you dhange the power supply redundancy mode to Combined using DCNM, the power supply redundancy mode in the device itself does not change to Combined.

Conditions: You may see this symptom under the following conditions:

- The power supply redundancy mode on the device itself is in Redundant.

- Using the DCNM Inventory screen, you change the power supply redundancy mode to Combined and deploy the configuration to the device. Because DCNM does not deliver this configuration correctly to the device, DCNM continues to display the mode as Redundant, which is what is actually on the device itself.

Workaround: No workaround.

CSCsx25247

Symptom: If you are working with the statistics tab for a feature, and launch the statistics by selecting the parameters and then immediately select the overview chart with options to view the history of the statistical data, you may see only a progress bar displaying the message: Loading data. The system does not display any historical statistics data.

Conditions: You will see this symptom only when you select options for displaying the historical statistics before even a single point of data is plotted in the statistics chart.

Workaround: Take the following steps:

- Close the statistics chart that shows progress bar displaying the message: Loading data.

- Choose New from the monitoring tool bar to create a new chart

- Select the parameters you want and wait for at least one point to be plotted in the chart.

- Select the options to view the historical data.

CSCsx28685

Symptom: Discovery of the device fails, and the device moves to the unmanaged state.

Conditions: You may see this symptom when the discovery of a device is in progress, and the device's CDP neighbor device's module is reset simultaneously.

Workaround: Rediscover the device.

CSCsx29085

Symptom: The vPC peer-keepalive configuration in DCNM is not consistent with the device configuration.

Conditions: After you discover the device using DCNM, move to the CLI on the device to configure vPC peer-keepalive messages.

Workaround: Configure the vPC peer-keepalive configuration using DCNM instead of the CLI, or rediscover the device using DCNM.

CSCsx32800

Symptom: DCNM may not detect a newly inserted supervisor module or may display the incorrect status for the supervisor module.

Conditions: You may see this symptom under the following conditions:

- You discover the device and verify the details in the Inventory screen.

- You insert a supervisor module.

- The Inventory screen does not detect the newly added supervisor module.

Workaround: Rediscover the device.

CSCsx36486

Symptom: DCNM may display the administrative status for interfaces as Down, even though the interfaces are Up on the device.

Conditions: You may see this symptom when the device is coming up with a fresh configuration and you change the default interface mode to no shutdown, or Up. DCNM always considers default configuration as shutdown, or Down, for interfaces.

Workaround: Using the CLI, enter the no shutdown command for those interfaces that are not displaying correctly in DCNM.

Resolved Caveats—Cisco DCNM Release 4.1(5)

CSCsx16283

Symptom: DCNM incorrectly displays the source and destination match addresses for IPv4 and IPv6 access rules.

Conditions: DCNM does not support object groups. If you create objects group for use with some ACLs, DCNM will not show the information properly. You cannot create, view, or associate object groups using DCNM.

Workaround: No workaround.

Resolved Caveats—Cisco DCNM Release 4.1(4)

CSCsw33266

Symptom: DCNM does not alert you when the device shuts down due to a missing fan module.

Condition: When you remove a fan tray and do not replace it within 3 minutes, the device starts to power down, but DCNM does not alert the user about this problem.

Workaround: None.

CSCsw77003

Symptom: You cannot enable the vPC feature or launch the vPC Wizard.

Conditions: If you are not using the correct version of the N7K-M148GT-11 module, you cannot enable or configure vPC.


Note If you are attempting to configure the vPC on an incorrect version of the N7K-M148GT-11 module, the screen displays the following error message:
"Error when applying the configuration to the device <ip_address> (vPC enable status: Incompatible hardware not enabling vPC."


CSCsy43995

Symptom: Unable to delete the vPC domain from the port channel screen.

Conditions:

1. Choose Interfaces and then choose Logical > Port Channels.

2. Select a device row for which the vPC feature is enabled and the domain is configured.

Workaround: Disable the vPC feature and enable it again.

Workaround: Contact Cisco about receiving the correct version of the N7K-M148GT-11 module.

Resolved Caveats—Cisco DCNM Release 4.1(3)

This section lists the resolved caveats for Release 4.1(3).

CSCsv64791

Symptom: An error message indicates that a vPC switch pair does not have a 10-Gigabit Ethernet I/O module (N7K-M132XP-12) when creating a vPC with the vPC Wizard.

Conditions: This occurs when you create a vPC with the vPC Wizard while using the following process:

1. Discover the Cisco Nexus 7000 devices with 10-Gigabit Ethernet I/O modules.

2. Launch the vPC creation wizard from the vPC screen.

3. Select the vPC peer devices which have 10-Gigabit Ethernet I/O modules.

4. Manually reload the devices.

5. Once the device becomes reachable and before all the modules become reachable, click Next. An error message appears to indicate that the vPC switch pairs do not have 10-Gigabit Ethernet I/O modules.

Workaround: Exit the wizard and relaunch the wizard when all of the modules in the device come up, and then continue creating the vPC.

CSCsv84176

Symptom: Sometimes, DCNM does not show topology links correctly.

Condition: Sometimes, even though the links are present between two Cisco Nexus 7000 Series devices, DCNM does not show the links. When you enter a show cdp neighbor detail command, DCNM displays the links for one device but not for the other device.

Workaround: No workaround.

CSCsv91350

Symptom: Archival of device configuration in the Configuration Archive does not happen even though the running configuration has changed on the Cisco Nexus 7000 Series device.

Conditions: This problem occurs when you do the following:

1. Create a Configuration Archive Job with a schedule.

2. Change the configuration in the running configuration. DCNM will fetch the changed running configuration and display in DCNM by creating the next version (version 2).

3. Change the schedule from 5 minutes to 10 minutes.

4. Change the running configuration by configuring new commands.

The Configuration Archive should create a new version (Version 3), but new version is not created in the DCNM Configuration Archive. This problem only happens when the configuration archive schedule is changed after you create a job.

Workaround: Remove the job and create a new job by specifying the schedule when job is created. Do not change the schedule after the Configuration Archive job is created.

CSCsv99354

Symptom: The topology map displays duplicate nodes for devices not running Cisco NX-OS software.

Condition: When rediscovering a network with devices not running the Cisco NX-OS software, the topology map displays duplicate nodes for those devices.

Workaround: Refresh the topology by pressing F5.

CSCsw15350

Symptom: DCNM does not display the interface mode configuration changes with the CLI.

Conditions: When you use the CLI to change the interface mode configuration for a noncontiguous range of interfaces, DCNM does not show the changed configuration.

Example 1: The following configuration does not work:

int ethernet 8/2, ethernet 8/4
  switchport 

Example 2: The following configuration works as expected because the interface range that you specified is in a continuous range.

int ethernet 8/2-4
  switchport 

Workaround: Rediscover the device or reconfigure the same missed configuration again on each interface.

CSCsw21913

Symptom: Creation of vPC fails when you use the vPC Wizard to create a vPC.

Condition: A vPC is partially created or the Port Channel parameters are not modified when you create a vPC by using the vPC Wizard.

Workaround: Check the missed configuration in the vPC summary screen after closing the Wizard. If the modified parameters of the Port Channel are not reflected, go to the Port Channel feature screen and modify the same parameters again. If a vPC is created partially, edit the vPC using the vPC Wizard and modify the parameters that were not applied earlier.

CSCsw30115

Symptom: The DCNM client freezes after almost a week of populating statistics. This problem is sporadic and cannot be consistently reproduced. After this problem was originally observed, it is no longer visible in Dev/Test setups.

Workaround: Exit from the client using the Task Manager in Windows or you can enter the Kill -9 Process_ID_of_the_DCNM_Client command in Linux.

CSCsw32710

Symptom: The keystring configured via DCNM is not shown properly in the device.

Condition: During the keychain configuration, if you try to configure an encrypted keystring from DCNM but the keystring is not already encrypted, then if you enter the show key chain command for the device, the device will show an empty keystring. This problem is due to a Cisco NX-OS problem (CSCsw45484). When you configure an unencrypted keystring as an encrypted keystring using the CLI, an error occurs. When you configure an unencrypted keystring as an encrypted keystring using XML, it is accepted as an empty string.

Workaround: Do not use an unencrypted keystring as an encrypted string in DCNM when you configure a keychain.

CSCsw33244

Symptom: DCNM displays the incorrect power capacity information.

Condition: When you disconnect the input power supply from the device, the device power capacity changes. DCNM does not recognize this change in the power capacity, so it continues to show the older power capacity information.

Workaround: Use one of the following two workarounds for this problem:

Rediscover the Cisco Nexus 7000 Series device in DCNM.

Select a Processor Card or Network Card from the summary table, select the Environment Status tab in the details panel, select the Temperature Status table, and set the refresh frequency as 30 seconds. After 30 seconds, DCNM will reflect the correct power capacity.

CSCsw33274

Symptom: DCNM displays the incorrect power capacity information.

Condition: When the power supply input is connected to the device, the device power capacity changes. DCNM does not recognize this power capacity change, so it continues to show the older power capacity information.

Workaround: Use one of the following two workarounds for this problem:

Rediscover the Cisco Nexus 7000 Series device in DCNM.

Select a Processor Card or Network Card from the summary table, select the Environment Status tab in the details panel, select the Temperature Status table, and set the refresh frequency as 30 seconds. After 30 seconds, DCNM will reflect the correct power capacity.

CSCsw45569

Symptom: When discovering a network of default and custom VDCs, some of the custom VDCs are stuck in the discovery state.

Conditions: This problem occurs when rediscovering a network after deleting the devices from DCNM. When deleting devices from DCNM using the Devices and Credentials screen, if default VDCs and custom VDCs are deleted in a single operation (using the multiple row selection), the custom VDCs will be stuck in the discovery state in a subsequent rediscovery.

Workaround: When using the Devices and Credentials window to delete VDC devices, delete the custom VDC devices and then delete the default VDC devices.

CSCsw45770

Symptom: DCNM deletes the historical data for statistics collected for the Cisco Nexus 7000 Series device that it manages. When you use the Show Overview button in a DCNM client chart, no statistics are shown even though statistics are scheduled for collection during the past period.

Conditions: The historical data for statistics collected by DCNM are deleted when a rediscovery for the Nexus 7000 Series device is triggered. A rediscovery is triggered when the device is rebooted or Online Insertion Removal (OIR) for modules or other physical components, such as a power supply, occur.

Workaround: There is no workaround.

CSCsw48735

Symptom: Modification of a Port Channel fails when you modify a vPC using the vPC editing Wizard.

Condition: When you use the vPC Edit Wizard to modify the domain Id and Port Channel bandwidth at the same time for an existing vPC, the modification of respective Port Channel fails.

Workaround: Go to the Port Channel feature screen, modify the bandwidth again, and deploy.

CSCsw51177

Symptom: The Context menu is not working in the Software Installation Job summary table when no job is already available.

Conditions: When no job is available, the context menu in the Software Installation Job summary table does not work.

Workaround: Use the tool bar icon or choose File > New to create a job when no job is available.

CSCsw62932

Symptom: The device operating system installation is frozen in a running state after a successful installation.

Conditions: This problem can occur with any of the following conditions:

Connectivity to the device is lost for more than 10 minutes while installing the image.

Software is installed on a device that has a custom VDC that are being managed by DCNM.

Workaround: Current software version on the device can be verified using the DCNM Inventory screen. Upon a successful installation, the latest software version will be indicated in Inventory screen.

Resolved Caveats—Cisco DCNM Release 4.1(2)

This section lists the resolved caveats for Release 4.1(2).

CSCsm09616

Symptom: While you are configuring loopback interfaces, you try to filter (Ctrl + F) with any column value, and the client displays an error message. Filtering occurs correctly anyway.

Conditions: Inconsistent.

Workaround: No workaround.

CSCsm17010

Symptom: The percentages shown next to the pie chart in the Event Browser overlap are incorrect.

Conditions: This problem occurs when the Event Browser contains a large number of events for one severity and a very small number of events for the next severity.

Workaround: Make the pie chart bigger by clicking and dragging the bar below the charts. The DCNM client recalculates the pie chart when you resize the pane that contains the charts.

CSCsm94859

Symptom: DCNM does not recognize the installation or uninstallation of a license on Cisco NX-OS devices.

Conditions: You installed a license on an Cisco NX-OS device to enable licensed features, such as tunnels, but you cannot use DCNM to manage the licensed Cisco NX-OS features.

Workaround: Use the Devices and Credentials feature to rediscover devices that have had an NX-OS license installed or uninstalled.

CSCso02217

Symptom: Starting a DCNM client that is already installed on a computer results in a dialog box that asks if you want to save shortcuts for the client.

Conditions: This problem occurs after you install the DCNM client on the computer by using a web browser to access the client on the DCNM server and you previously answered the same dialog box.

Workaround: Uninstall and reinstall the DCNM client. For information about installing and uninstalling the client, see the Cisco DCNM Fundamentals Configuration Guide at the following website:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/dcnm/fundamentals/configuration
/guide/dcnm_fund_config.html

CSCso19425

Symptom: Copying and pasting an entity (for example, VLANs, ACLs, etc.) from one device to another device fails to apply changes to the device.

Conditions: This problem occurs when you use the DCNM client to view the entities configured on a managed device, such as VLANs or ACLs, and someone uses a method other than DCNM to create a new entity. The DCNM client will automatically update shortly after the entity is added to the running configuration of the device, but if you try to copy the new entity and paste it into a different managed device, the operation fails in the DCNM server and changes are not applied to the device.

Workaround: Press F5 to refresh the DCNM client before copying and pasting the new entity.

CSCso28169

Symptom: Changes made for the ACL Logging for VLANs in the ARP ACL screen do not work.

Conditions: Choose Switching > Layer2 Security > ARP Inspection, and then change the configuration for ACL logging for a VLAN in the summary table or in the selected VLAN details panel.

Workaround: No workaround. Currently, enabling ACL logging in the device is not supported.

CSCso29714

Symptom: While using DCNM to create a nondefault VDC in a physical device, if you accidently assign to the management interface of the new VDC the IP address that is already assigned to an existing nondefault VDC in that same physical device, then DCNM does not give a warning. After you deploy the configuration, DCNM shows the new VDC information for the previously created VDC.

Conditions: This problem occurs when you use something other than DCNM to create a nondefault VDC on a physical device and configure the management interfaces of the default VDC and nondefault VDC, and then you use DCNM to discover both VDCs. While using DCNM to create another nondefault VDC, you assign to the management interface of the new VDC the same IP address that you previously assigned to the management interface of the existing, nondefault VDC. DCNM does not warn you and deploys the configuration to the device. After deployment, DCNM shows the new VDC information for the previously existing, nondefault VDC.

Workaround: Use the Devices and Credentials feature to rediscover the nondefault VDCs on the physical device.

CSCso35181

Symptom: DCNM has incorrect configuration data for a managed device after DCNM processes changes received from the device at the same time that you change the device configuration in the DCNM client.

Conditions: When you use something other than DCNM to configure a managed device, the Auto Synchronization with Devices feature in DCNM retrieves the configuration changes from the device and updates the configuration data for the managed device in DCNM. If you use DCNM to make changes to the configuration of the managed device at the same time that DCNM is synchronizing with the device, the changes that you made with DCNM are not applied to the running configuration of the device. Also, the changes that you made to the device by a method other than DCNM are not reflected in the DCNM client.

Workaround: Use the Devices and Credentials feature in DCNM to rediscover the device.

CSCso94565

Symptom: GLBP group state changes are not updated in the summary and details panes.

Conditions: A GLBP group state on a managed device changes after you start the DCNM client.

Workaround: Press F5 to refresh the GLBP pane.

CSCsq13902

Symptom: Inventory and Topology display the chassis state as managed when rediscovery fails.

Conditions: This problem occurs when DCNM fails to rediscover a device.

Workaround: No workaround.

CSCsq42300

Symptom: Even after the link between two Cisco Nexus 7000 Series devices comes up, the DCNM topology map does not show the links until the user refreshes the screen.

Conditions: Two devices are discovered by DCNM when the link between the two devices is down. After discovery, the link between the devices is restored by something other than DCNM, such as by the CLI. The DCNM topology screen does not reflect the link status change until the user refreshes the topology screen.

Workaround: Press F5 to refresh the topology.

CSCsq51358

Symptom: When you use the Interfaces > Physical > Ethernet feature in the DCNM client, a subinterface for the Status Description field in summary pane is blank.

Conditions: When DCNM discovers a device that has an Ethernet subinterface or when someone creates a new subinterface by using something other than DCNM, the DCNM client does not display the available information in the Status Description field for the subinterface.

Workaround: No workaround.

CSCsq61332

Symptom: The DCNM client shows an incorrect power supply redundancy mode.

Conditions: Discover a Cisco Nexus 7000 Series device using the DCNM client. Using the inventory feature, choose the device in the summary table. In the details pane, choose the Environment Status tab. Under power supply redundancy, the administrative and operational modes appear.

Now access the command-line interface of the same Cisco Nexus 7000 Series device and use the power redundancy-mode redundant command to change the power supply redundancy mode.

The DCNM client continues to show the old power supply redundancy mode.

Workaround: In the DCNM client, go to the Inventory feature, choose any I/O module in the affected device, choose the Environment Status tab in the details pane, expand the Temperature Status Table section, change the Refresh Frequency to 30 seconds, and deploy the change. Wait 30 seconds and press F5 to refresh the client. DCNM will show the new power supply redundancy mode.

CSCsq62414

Symptom: The DCNM client does not launch with Java 1.4.2.

Conditions: When the client workstation has Java 1.4.2 installed, the DCNM client does not automatically download and install Java 5, which is required to launch the application.

Workaround: Uninstall Java 1.4.2 or manually install Java 5.

CSCsq76212

Symptom: When you use the CLI to change a hostname, the DCNM window for IPv4 ACL does not display the hostname.

Conditions: Use DCNM to discover a Cisco Nexus 7000 device and then open the IPv4 ACL window to verify the device. Next, use the CLI to login to the same device and change the hostname of the device. DCNM shows the updated hostname except on the IPv4 ACL window.

Workaround: Refresh the IPv4 ACL screen.

CSCsq76959

Symptom: On the DCNM client, when you uninstall by using the Add or Remove Programs utility on the Windows control panel, it doesn't delete all the cached files stored in the client machine.

Conditions: This problem occurs when the DCNM client is uninstalled by using the Add or Remove Programs utility only.

Workaround: Uninstall the client as mentioned in DCNM Help (use the Java Application Manager. utility on the Windows control panel)

CSCsq77763

Symptom: An exception occurs when interfaces that are part of a removed module are associated with other features in any of the DCNM screens.

Conditions: This problem occurs when you remove the module from a device, which was discovered by DCNM, DCNM still lists the interfaces for the removed module. When you try to modify the interface or try to associate the interfaces with any other feature, an exception occurs.

Workaround: No workaround. The exception is harmless.

CSCsr37245

Symptom: The Devices and Credentials screen shows duplicate rows for a device with the status "Discovering" and "Managed."

Conditions: This problem occurs when you create a new VDC by using the VDC wizard, select the "Discover" check box in the final wizard screen, and then use the Devices and Credentials screen to show the newly created VDC.

Workaround: Refresh the Devices and Credentials screen.

CSCsr46487

Symptom: The DCNM uninstall process does not clear the database. You cannot log in to the DCNM server after installing Release 4.0(3).

Conditions: Uninstall DCNM version 4.0(1) or 4.0(2) on the server, and then install version 4.0(3).

Workaround: Clear the DCNM database manually.

CSCsr53247

Symptom: A device discovery fails and DCNM displays one of the following two messages:

"Error saving data to DB for IP address"

"Discovery of IP address failed due to server error"

Condition: A discovery can fail under any of the following conditions:

If the devices with directly connected links between them are discovered concurrently

If the devices are deleted when DCNM is discovering their directly connected neighbor devices

Workaround:

Discover the interconnected devices that are using a single discovery task by specifying an appropriate hop count.

Run one discovery task at a time and wait for it to complete before creating a new discovery task.

CSCsr72829

Symptoms: Even though you have given the admin credential when the VDC is created through the DCNM (VDC wizard), when you try to get into the VDC (using the switchto command), the device asks you to configure the admin user credential.

Conditions: The problem occurs when a weak password is configured for the admin user when the VDC is created using DCNM. Cisco NX-OS requires the following for a strong password:

The length of the password must be at least eight characters.

The username and password cannot be the same, and the password cannot be the reverse of the username.

The password must include any three of the following types of characters:

- Lowercase letters

- Uppercase letters

- Digits

- Special characters (except the $ character)

The password should not be a word from a dictionary.

Since DCNM is not performing the validations mentioned above, and it only validates whether the password length is at least eight characters, if a user configures a nonstrong password, then DCNM will fail to validate the password, and the device will reject that password.

Workaround: Configure a strong password based on the above instructions when you create a VDC using DCNM.

CSCsr91447

Symptom: When you configure a tunnel interface from DCNM or directly in the switch, DCNM will show an incorrect operational status for that tunnel interface.

Condition: This problem occurs when you configure a tunnel interface from either DCNM or from the switch CLI. DCNM will reflect that interface in the Tunnel Interface screen, but the operational status of that tunnel interface shown by DCNM will be incorrect. DCNM relies on the syslogs from the device to update the tunnel interface operational status. When the tunnel interface operation status changes, the device has to send a status change syslog for that tunnel interface that is similar to the status change syslogs it sends for other physical ports and VLAN interfaces. However, with a tunnel interface, there are no status change syslogs generated from the device, so DCNM will show incorrect operational status for that tunnel interface.

Workaround: Rediscover the device.

CSCsr95739

Symptoms: Sometimes DCNM shows the same device twice with a different host name.

Conditions: This problem occurs when you discover a Nexus 7000 Series switch in DCNM and go to the CLI of that device and enter the following command:

cdp format device-id serial-number 

Afterwards, when you discover the same device in DCNM, you will see two device entries in DCNM, even though you discovered and rediscovered the same device. DCNM uses the serial number to uniquely identify a chassis, and it picks that information from the Device-ID field in the show cdp neighbor detail command output. By default, that field either shows the hostname (Release 4.0(2) or earlier), or both the hostname and serial number (Release 4.0(3) and later releases). If you use above command and force the CDP to show the serial number alone in the Device-ID field, then DCNM cannot handle it.

Workaround: Do not use the cdp format device-id serial-number command. Use the default format.

CSCsr96608

Symptom: Some of the tunnel interface attributes, like MTU, Path MTU and Keepalive, are not available in the tunnel interface screen.

Condition: This problem occurs when you go to the Tunnel screen in DCNM (choose Interfaces > Logical > Tunnel), choose a tunnel interface from the summary panel, and the details panel will display its details. There are no DCNM provisions to configure the MTU, Path MTU, and Keepalive parameters for the tunnel interface.

Also, if the attributes are configured in the device for a tunnel interface, then DCNM is not allowing users to modify the other parameters of those tunnel interfaces.

MTU, Path MTU, and Keepalive parameters will be supported in the future.

Also, if you have configured those attributes in the device for a tunnel interface, then those interface attributes or parameters cannot be modified by using DCNM. Modifying them will result in an error message.

Workaround:

MTU, Path MTU and Keepalive parameters will be supported in a future release.

If you want to use DCNM to modify the tunnel parameters, make sure that the tunnel interface is not configured with the MTU, Path-MTU, and Keepalive settings in the device. If they are configured, you will remove those configurations from the device.

CSCsr99977

Symptom: When the DCNM client session has expired after the client is idle for 24 hours and the user selects a feature that was not visited earlier, the user is notified and logs in again. The screen for the selected feature does not display.

Conditions: This problem occurs only when the session has expired and the user selects a feature not visited earlier.

Workaround: Close the DCNM client and relaunch it.

CSCsu02090

Symptom: The discovery of devices with a hop count of 1 or more are shown as successful even though some of the discovered devices are shown as unmanaged.

Condition: The device cannot discover neighboring devices if probing fails for the device, but the status of the device discovery might be shown as successful.

Workaround: Discover the neighbor device with a pointed discovery.

CSCsv14655

Symptom: The DCNM client failed to launch with Java versions later than 1.5.0_11.

Condition: If the required version of Java (1.5.0_11) is not installed on the DCNM client workstation, DCNM will redirect you to the download page of the latest update of Java version 1.5.0. If you install the latest update of Java version 1.5.0, the DCNM client will not launch.

Workaround: Manually install Java version 1.5.0_11 from http://java.sun.com/products/archive/j2se/5.0_11/index.html.

Related Documentation

Cisco DCNM documentation is available at the following URL:

http://www.cisco.com/en/US/products/ps9369/tsd_products_support_series_home.html

The documentation for Cisco DCNM includes the following:

Cisco DCNM Getting Started with Virtual Device Contexts, Release 4.1

Cisco DCNM Fundamentals Configuration Guide, Release 4.1

Cisco DCNM Interfaces Configuration Guide, Release 4.1

Cisco DCNM Layer 2 Switching Configuration Guide, Release 4.1

Cisco DCNM Security Configuration Guide, Release 4.1

Cisco DCNM Unicast Routing Configuration Guide, Release 4.1

Cisco DCNM Virtual Device Context Configuration Guide, Release 4.1

Cisco DCNM Web Services API Guide, Release 4.1

The Release Notes for upgrading FPGAs/EPLDs is available at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_1/epld/epld_rn.pdf

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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.