Guest

Cisco Prime Data Center Network Manager

Cisco DCNM Release Notes, Release 5.2

  • Viewing Options

  • PDF (430.8 KB)
  • Feedback
Cisco DCNM Release Notes, Release 5.2

Table Of Contents

Cisco DCNM Release Notes, Release 5.2

Contents

Introduction

System Requirements

Supported Databases, DCNM-LAN and DCNM-SAN

Java Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Client System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Browsers

Other Supported Software

Supported Cisco Platforms and Software Versions

Hardware Supported

Software Download Site

Installation Notes

Cisco DCNM-LAN and Cisco DCNM-SAN Installation Notes

Cisco DCNM-LAN Installation Notes

Cisco DCNM-SAN Installation Notes

Cisco DCNM Release 5.2(2c) Installation Note

Cisco DCNM Release 5.2(2b) Installation Note

Enhancements in Cisco DCNM Release 5.2(x)

Infrastructure Enhancements

New and Changed Information for Cisco MDS 9000 Family Switches

New and Changed Information for Cisco Nexus 1000V Series Switches

New and Changed Information for Cisco Nexus 2000 Series Fabric Extenders

New and Changed Information for Cisco Nexus 3000 Series Switches

New and Changed Information for Cisco Nexus 4000 Series Switches

New and Changed Information for Cisco Nexus 5000 Series Switches

New and Changed Information for Cisco Nexus 7000 Series Switches

New and Changed Information for Catalyst 6500 Series Switches

New and Changed Information for the Cisco Unified Computing System

Limitations in Cisco DCNM Release 5.2(x)

Limitations for the Cisco MDS 9000 Family with Cisco DCNM Release 5.2(x)

Cannot Launch Windows 7 64-bit Telnet Application from Cisco DCNM-SAN

Unsupported Licenses

Smart Card in Windows 7 Is Not Supported When Cisco DCNM-SAN Creates a Cluster

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.2

Unsupported Storage VDC Features Are Filtered Out in Cisco DCNM-SAN

Remote Accounting Should be Used to Log Show Commands

ISSU That Passed Can Show as Failed

Limitations for the Cisco Nexus 5000 Series with Cisco DCNM Release 5.2

Limitations for the Cisco Nexus 1000v Series with Cisco DCNM Release 5.2

LAN Connectivity Connections Do Not Display for VMs

Limitations for Catalyst 6500 Switches with Cisco DCNM Release 5.2

Caveats

Open Caveats—Cisco DCNM Release 5.2

Open Caveats—Cisco DCNM-LAN Release 5.2

Open Caveats—Cisco DCNM-SAN Release 5.2

Resolved Caveats—Cisco DCNM Release 5.2(2e)

Resolved Caveats—Cisco DCNM LAN Release 5.2(2e)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2e)

Resolved Caveats—Cisco DCNM Release 5.2(2c)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2c)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2b)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2a)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2a)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(1)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(1)

Documentation Corrections

Related Documentation

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 7000 Series Switch Documentation

Catalyst 6500 Series Switch Documentation

Obtaining Documentation and Submitting a Service Request


Cisco DCNM Release Notes, Release 5.2


Release Date: July 26, 2012
Part Number: OL-25092-06 C0
Current Release: 5.2(2e)

This document provides the release notes for Cisco Data Center Network Manager (DCNM), Release 5.2. Use this document in combination with the 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-25092-06

A0

July 17, 2011

Created release notes for Release 5.2(1).

B0

July 25, 2011

Updated the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section and the "Client System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

C0

July 27, 2011

Corrected the IOS version number in the"New and Changed Information for Catalyst 6500 Series Switches" section.

Updated the supported MDS 9000 hardware in the "Hardware Supported" section.

D0

August 4, 2011

Changed the number of open cursors in the Oracle database configuration information in the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

E0

August 10, 2011

In the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section:

Updated the supported Red Hat Enterprise Linux version.

Explained how to verify that the Perl environment variable is set.

F0

September 7, 2011

Added open caveat CSCts32904 to the "Open Caveats—Cisco DCNM-SAN Release 5.2" section.

G0

September 20, 2011

Added RHEL 5.4 support "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

H0

September 29, 2011

Added resolved caveat CSCtr71379 "Resolved Caveats—Cisco DCNM-SAN Release 5.2(1)" section.

I0

October 19, 2011

Added Support for Switch Virtual Interface in "New and Changed Information for Cisco Nexus 5000 Series Switches" section and "New and Changed Information for Cisco Nexus 7000 Series Switches"

OL-25092-02

A0

December 23, 2011

Created release notes for Release 5.2(2).

Moved CSCtn15296, CSCtq85466, CSCtr47659, CSCtr50721, CSCtr50633 to "Resolved Caveats—Cisco DCNM-LAN Release 5.2(2)" section.

B0

January 25, 2012

Updated the introductory text in the "System Requirements" section and added a note to the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

OL-25092-03

A0

February 3, 2012

Created release notes for Release 5.2(2a).

B0

February 20, 2012

Added CSCtw59374 to Resolved Caveats—Cisco DCNM-SAN, Release 5.2(2a).

Added CSCtw71383 to Resolved Caveats—Cisco DCNM-LAN, Release 5.2(2a).

Added CSCtx16177, CSCtx39981, and CSCtx79298 to Open Caveats—Cisco DCNM-LAN, Release 5.2.

Removed CSCto8295 from Open Caveats—Cisco DCNM-LAN, Release 5.2.

OL-25092-04

A0

February 24, 2012

Created release notes for Release 5.2(2b).

B0

March 9, 2012

Updated the "Installation Notes" section.

OL-25092-05

A0

March 30, 2012

Created release notes for Release 5.2(2c).

B0

April 12, 2012

Added the "Cisco DCNM Release 5.2(2c) Installation Note" section.

C0

April 27, 2012

Removed Solaris from the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

D0

June 6, 2012

Removed duplicate content from the "Cisco DCNM-SAN Installation Notes".

Added CSCtz35287 and CSCtz39546 to the "Open Caveats—Cisco DCNM-SAN Release 5.2"

E0

June 29, 2012

Revised the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.

F0

July 6, 2012

Added a limitation in the "Limitations for the Cisco Nexus 5000 Series with Cisco DCNM Release 5.2" section.

OL-25092-06

A0

July 26, 2012

Created release notes for 5.2(2e).

B0

October 16, 2012

Added CSCth49735 to the "Resolved Caveats—Cisco DCNM-SAN Release 5.2(1)" section.

C0

January 3, 2013

Updated the "Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN" section.


Contents

This document includes the following sections:

Introduction

System Requirements

Supported Cisco Platforms and Software Versions

Hardware Supported

Software Download Site

Installation Notes

Enhancements in Cisco DCNM Release 5.2(x)

Limitations in Cisco DCNM Release 5.2(x)

Caveats

Documentation Corrections

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

Cisco DCNM is advanced management software that provides comprehensive life cycle management for the data center LAN and SAN.

Cisco DCNM Release 5.2 combines Cisco Fabric Manager, which previously managed SANs, and Cisco DCNM, which previously managed only LANs, into a unified product that can manage a converged data center fabric. As a part of the product merger in Cisco DCNM Release 5.2, the name Cisco DCNM for SAN replaces the name Cisco Fabric Manager. The name Cisco Fabric Manager still applies to Cisco Fabric Manager Release 5.0(x) and all earlier versions.

Cisco DCNM Release 5.2 supports the Cisco Nexus product family, Cisco MDS 9000 product family, Catalyst 6500 Series, and the Cisco UCS product family.

System Requirements

This section lists the software that Cisco has tested and supports for Cisco DCNM-LAN and Cisco DCNM-SAN. Both Cisco DCNM-LAN and Cisco DCNM-SAN have been tested in English locales only.

This section includes the following topics:

Supported Databases, DCNM-LAN and DCNM-SAN

Java Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Client System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Browsers

Other Supported Software

Supported Cisco Platforms and Software Versions

Hardware Supported

Supported Databases, DCNM-LAN and DCNM-SAN

Cisco DCNM Release 5.2(x) supports the following databases:

Oracle 11g and 11g2 Enterprise Edition - (Cisco recommends Oracle 11g2 Enterprise Edition for customers with large fabrics.)

OracleExpress 10g

PostgreSQL 8.3 (Windows)

PostgreSQL 8.3 (Linux)

PostgreSQL 8.1 (Solaris)


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.


Java Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Cisco DCNM is a Java-based client-server application. The Cisco DCNM Release 5.2(1) server and client support Java 1.6 update 21. The Cisco DCNM Release 5.2(2), Release 5.2(2a), Release 5.2(2b), Release 5.2(2c), and Release 5.2(2e) server and client support Java 1.6 update 29.

The DCNM Server installer installs JRE 1.6.0_21 or JRE 1.6.0_29 to the DCNM_root_directory/java/jre1.6 directory depending upon the version of the Cisco DCNM you choose to install.


Note If you need an additional version of JRE, install the additional version at DCNM_root_directory/java/jreversion_number.

When you have more than one JRE installed on a client machine, you must use Java and Java-Webstart JRE 1.6.0_29.


Server System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Cisco DCNM Release 5.2(x) supports running the Cisco DCNM-LAN and Cisco DCNM-SAN servers on these operating systems:

Microsoft Windows 2003, 32-bit or 64-bit with Service Pack 2

Microsoft Windows 2008, 32-bit with Service Pack 2

Microsoft Windows Server 2008, 64-bit with Service Pack 2

Microsoft Windows Server 2008, 64-bit R2 with Service Pack 1

Microsoft Windows 7, 32-bit or 64-bit (Cisco DCNM SAN standalone only)

Red Hat Enterprise Linux Release 5.4 (32-bit)

Red Hat Enterprise Linux Release 5.5 (32-bit and 64 bit)


Note If a service pack for the Windows operating system is not listed, then the service pack is not supported.


The system requirements depend on whether you are running the Cisco DCNM server and the database server on the same machine or distinct machines (for example, in a cluster environment). Table 2 and Table 3 list the minimum and recommended Cisco DCNM requirements for each of these deployment scenarios.

Table 2 Server System Requirements—Cisco DCNM and Database Servers Collocated

Component
Minimum Requirements
Recommended Requirements

RAM (free)

4 GB

6 GB

CPU speed

2.5 GHz with dual-processor or dual-core CPU

3.45 GHz with dual-processor or dual-core CPU

Disk space (free)

60 GB

80 GB


Table 3 Server System Requirements—Cisco DCNM and Database Servers on Separate Machines (Clustered)

Component
Minimum Requirements
Recommended Requirements
Cisco DCNM Server

RAM (free)

2 GB

3 GB

CPU speed

2.5 GHz with dual-processor or dual-core CPU

3.45 GHz with dual-processor or dual-core CPU

Disk space (free)

20 GB

30 GB

Database Server

RAM (free)

2 GB

3 GB

CPU speed

2.5 GHz with dual-processor or dual-core CPU

3.45 GHz with dual-processor or dual-core CPU

Disk space (free)

40 GB

50 GB


The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.

If Cisco DCNM-LAN coexists with Cisco DCNM-SAN on the same server, the server should have at least 6 GB of free RAM, 100 GB of free disk space, and two Ethernet ports running at 1 Gbps (each manager uses one Ethernet port). The server should include one of the following operating at 2.5 GHz:

One quad-core processor

Two dual-core processors

Four single-core processors

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

The IP address of the server system should be statically assigned.

For Cisco DCNM-LAN only, a Perl environment must already be installed on the server system. (This prerequisite does not apply to Cisco DCNM-SAN.) We recommend Active Perl version 5.8.9.827. You can download ActivePerl for your server operating system from the following location:

http://www.activestate.com/activeperl/downloads/

The path to the Perl executable must be defined in the server system PATH environment variable. After you install Perl, open a DOS window and run the perl -version command. If the correct Perl version number displays, then the environment variable is set. If it is not set, reboot the host machine and enter the perl -version command again.

No other programs are running on the server except for Cisco DCNM-SAN Release 5.2(x) releases and the database software used by Cisco DCNM-SAN.

If you plan to use an OracleExpress 10g database, configure the Oracle database as follows:

Increase the SYSTEM tablespace to 2 GB from the default 1 GB of space.

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 50.

If you plan to use an Oracle 11g or 11g2 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.


Note Although it is not required, it is a good practice to register the server system with the DNS servers.


Client System Requirements, Cisco DCNM-LAN and Cisco DCNM-SAN

Cisco DCNM Release 5.2 supports running the Cisco DCNM client and Cisco DCNM-SAN in standalone mode on the following platforms:

Microsoft Window 7 (32-bit and 64-bit versions)

Red Hat Enterprise Linux AS Release 5.4 (32-bit and 64 bit)

Table 4 lists the minimum hardware requirements for these client systems.

Table 4 Client Hardware Requirements

Hardware
Minimum Requirements

RAM (free)

1 GB

CPU speed

2.16 GHz with one dual core processor or two single-core processors

Disk space (free)

100 MB


If Cisco DCNM-LAN coexists with Cisco DCNM-SAN on your client system, the client system should include one dual-core processor or two single-core processors operating at 2.0 GHz, 2 GB of free RAM, and 200 MB of free disk space.


Note If you install Cisco DCNM-SAN in a virtual machine, we recommend that you reserve resources equal to the server resource requirements to ensure a baseline with physical machines. See for Table 3 for Cisco DCNM-SAN resource requirements.


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 5.x.

Be sure to set the correct time zone value on the system clock (for example, UTC). Otherwise, Cisco DCNM cannot manage the switch properly.

Table 5 lists the minimum amount of resources (disk, memory, and CPU) required for both the server and client for Cisco DCNM to operate satisfactorily.

Table 5 Cisco DCNM Resource Requirements

Description
Server Requirements
Small (Up to 5000 ports)
Server Requirements
Large (5,000 to 15,000 ports)
Client Requirements
Small (Up to 5000 ports)
Client Requirements
Large (5,000 to 15,000 ports)

Hardware

Dual-core CPUs; 2 GHz

Quad-core CPUs; 2 GHz

2 GHz

2 GHz

Memory

4 GB

8 GB minimum

1 GB

2 GB

Hard Disk

40 GB

60 GB

1 GB

1 GB



Note If both Cisco DCNM-LAN and Cisco DCNM-SAN are running, users should use the larger machine requirements, regardless of the size of the fabric or network.


Browsers

Common web browsers that support Adobe Flash 10 are qualified for use with Cisco DCNM-LAN and DCN-SAN. These include Internet Explorer, Firefox, Chrome, and Safari.

Other Supported Software

Table 6 lists other software supported by Cisco DCNM Release 5.2(x).

Table 6 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

Telnet Disabled: SSH version 1, SSH version 2, Global Enforce SNMP Privacy Encryption

Web Client and Cisco DCNM-SANServer Encryption: HTTPS

 

Performance Manager:

SNMP over UDP

SNMP over TCP

 

Flash:

Adobe Flash 10

 

Solaris Containers (Base OS - Solaris 10):

Virtual Operating System: Solaris 10 Zones

 

VMs:

VMs that run any qualified or supported operating system version can run Cisco DCNM.


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.

Supported Cisco Platforms and Software Versions

For information about the software platforms and versions that Cisco DCNM-LAN supports, see the Cisco DCNM-LAN Software Compatibility Matrix.


Note Cisco Fabric Manager Release 5.0(x) cannot manage the new features introduced in Cisco DCNM-SAN Release 5.2, but it can manage the legacy features in Cisco DCNM-SAN Release 5.2. For compatibility reasons, we recommend that you run the same version of Cisco DCNM-SAN as Cisco NX-OS software.


Cisco DCNM-SAN Release 5.2(1) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running NX-OS Release 4.1(3) or an earlier release.

Hardware Supported

Table 7 lists the products and components that Cisco DCNM Release 5.2 supports.

Table 7 Hardware Features Supported by Cisco DCNM Release 5.2 

Product/Component
Part Number

Cisco MDS 9000 Family

Cisco MDS 9513 Multilayer Director

DS-C9513

Cisco MDS 9509 Multilayer Director

DS-C9509

Cisco MDS 95106Multilayer Director

DS-C9506

Cisco MDS 9222i Multilayer Fabric Switch

DS-C9222i-K9

Cisco MDS 9216i Multilayer Fabric Switch

DS-C9216i-K9

Cisco MDS 9148 48-Port Multilayer Fabric Switch

DS-C9148-K9

Cisco MDS 9134 34-Port Multilayer Fabric Switch

DS-C9134-K9

Cisco MDS 9124 24-Port Multilayer Fabric Switch

DS-C9124-K9

Cisco MDS 9500 Series Supervisor-2 Module

DS-X9530-SF2-K9

Cisco MDS 9500 Series Supervisor-2A Module

DS-X9530-SF2A-K9

Cisco MDS 9500 Series Supervisor-1 Module

DS-X9530-SF1-K9

Cisco MDS 9000 12-port 4-Gbps Fibre Channel Switching Module

DS-X9112

Cisco MDS 9000 24-port 4-Gbps Fibre Channel Switching Module

DS-X9124

Cisco MDS 9000 48-port 4-Gbps Fibre Channel Switching Module

DS-X9148

Cisco MDS 9000 Family 4-Port 10-Gbps Fibre Channel Switching Module

DS-X9704

Cisco MDS 9000 Family 14-Port Fibre Channel and 2-port Gigabit Ethernet Module

DS-X9302-14K9

Cisco MDS 9000 16-Port 2-Gbps Fibre Channel Switching Module

DS-X9016

Cisco MDS 9000 32-Port 2-Gbps Fibre Channel Switching Module

DS-X9032

Cisco MDS 9000 32-Port Storage Services Module

DS-X9032-SSM

Cisco MDS 9000 8-port 1-Gbps IP Storage Module

DS-X9308-SMIP

Cisco MDS 9000 4-port 1-Gbps IP Storage Module

DS-X9304-SMIP

Cisco MDS 9000 24-Port 8-Gbps Fibre Channel Switching Module

DS-X9224-96K9

Cisco MDS 9000 48-Port 8-Gbps Fibre Channel Switching Module

DS-X9248-96K9

Cisco MDS 9000 4/44-Port Host-Optimized 8-Gbps Fibre Channel Switching Module

DS-X9248-48K9

Cisco MDS 9000 8-port 10-Gbps Fibre Channel over Ethernet (FCoE) Module

DS-X9708-K9

Cisco MDS 9000 32-port 8-Gbps Advanced Fibre Channel Switching Module

DS-X9232-256K9

Cisco MDS 9000 48-port 8-Gbps Advanced Fibre Channel Switching Module

DS-X9248-256K9

Cisco MDS 9000 Family 16-Port Storage Services Node (SSN-16)

DS-X9316-SSNK9

Cisco MDS 9000 18/4-Port Multiservice Module (MSM-18/4)

DS-X9304-18K9

Cisco Nexus 7000 Series Switches

Cisco Nexus 7009 chassis

N7K-C7009

Cisco Nexus 7010 chassis

N7K-C7010

Cisco Nexus 7018 chassis

N7K-C7018

Supervisor module

N7K-SUP1

Fabric module, Cisco Nexus 7018 chassis

N7K-C7018-FAB-2

Fabric module, Cisco Nexus 7018 chassis

N7K-C7018-FAB-1

Fabric module, Cisco Nexus 7010 chassis

N7K-C7010-FAB-2

Fabric module, Cisco Nexus 7010 chassis

N7K-C7018-FAB-1

Fabric module, Cisco Nexus 7009 chassis

N7K-C7009-FAB-2

48-port 1/10 Gigabit Ethernet SFP+ I/O module (F2 Series)

N7K-F248XP-25

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

N7K-M148GT-11

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

N7K-M148GS-11

48-Port 1-Gigabit Ethernet Module with XL Option

N7K-M148GS-11L

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

N7K-M132XP-12

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

N7K-M132XP-12L

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

N7K-F132XP-15

8-Port 10-Gigabit Ethernet Module with XL Option (requires X2)

N7K-M108X2-12L

Cisco Nexus 5000 Series Switches

Cisco Nexus 5596UP Switch

N5K-C5596UP-FA

Cisco Nexus 5548UP Switch

N5K-C5548UP-FA

Cisco Nexus 5548P Switch

N5K-C5548P-FA

Cisco Nexus 5010 chassis

N5K-C5010P-BF

Cisco Nexus 5020 chassis

N5K-C5020P-BF

N5K-C5020P-BF-XL

16-port Universal GEM, Cisco Nexus 5500

N5K-M16UP

Layer 3 GEM, Cisco Nexus 5596

N5K-M160L3

Layer 3 GEM

N55-M160L3-V2

Layer 3 module, Cisco Nexus 5548

N55-D160L3

Version 2, Layer 3 daughter card

N55-D160L3-V2

N5000 1000 Series Module 6port 10GE

N5K-M1600(=)

N5000 1000 Series Mod 4x10GE 4xFC 4/2/1G

N5K-M1404=

N5000 1000 Series Module 8port 4/2/1G

N5K-M1008=

N5000 1000 Series Module 6port 8/4/2G

N5K-M1060=

Cisco Nexus 4000 Series Switches

Cisco Nexus 4001I Switch Module

N4K-4001I-XPX

Cisco Nexus 4005I Switch Module

N4K-4005I-XPX

Cisco Nexus 3000 Series Switches

Cisco Nexus 3016 Switch

N3K-C3016Q-40GE

Cisco Nexus 3048 Switch

N3K-C3048TP-1GE

Cisco Nexus 3064 Switch

N3K-C3064PQ

Cisco Nexus 3064-E Switch

N3K-C3064PQ-10GE

Cisco Nexus 2000 Series Fabric Extenders

Cisco Nexus 2148 1 GE Fabric Extender

N2K-C2148T-1GE

Cisco Nexus 2224TP Fabric Extender

N2K-C2224TP-1GE

Cisco Nexus 2232TM 10GE Fabric Extender

N2K-C2232TM-10GE

Cisco Nexus 2232PP 10 GE Fabric Extender

N2K-C2232PP-10GE

Cisco Nexus 2248TP 1 GE Fabric Extender

N2K-C2248TP-1GE

Cisco Nexus 2248TP E GE Fabric Extender

N2K-C2248TP-E GE

Cisco Nexus 1000V Series Switch

Cisco Nexus 1010 and 1010-X Virtual Services Appliance

Catalyst 6500 Switches

 

Software Download Site

To download the latest Cisco DCNM software, click here:


Note If you would like to request a copy of the source code under the terms of either GPL or LGPL, send an e-mail to mds-software-disclosure@cisco.com.


Installation Notes

For information about installing and uninstalling Cisco DCNM Release 5.2(x), see the Cisco DCNM Installation and Licensing Guide, Release 5.x. You can find this publication on Cisco.com at this location:

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

This section includes the following topics:

Cisco DCNM-LAN and Cisco DCNM-SAN Installation Notes

Cisco DCNM-LAN Installation Notes

Cisco DCNM-SAN Installation Notes

Cisco DCNM Release 5.2(2c) Installation Note

Cisco DCNM Release 5.2(2b) Installation Note

Cisco DCNM-LAN and Cisco DCNM-SAN Installation Notes

If you have both Cisco Fabric Manager Release 5.0(x) and Cisco DCNM Release 5.1(x) installed on the same server, follow these steps to upgrade to Cisco DCNM Release 5.2(x):

1. Stop Cisco Fabric Manager Server.

2. Manually copy reports and performance data to a file.

3. Uninstall Cisco Fabric Manager Server.

4. Upgrade to Cisco DCNM-LAN Release 5.2(x).

5. Run a fresh installation for Cisco DCNM-SAN Release 5.2(x).

6. Step 4 is important to ensure that you can install Cisco DCNM-SAN over Cisco DCNM-LAN.

7. Discover the fabric and import historic data.

Cisco DCNM-LAN Installation Notes

If you have DCNM-LAN5.1(x) installed, you must upgrade to DCNM-LAN Release 5.2(1) before upgrading to Cisco DCNM-LAN Release 5.2(2a).

Cisco DCNM-SAN Installation Notes

If you have Fabric Manager Server Release 5.0(x) installed and you are upgrading to Cisco DCNM-SAN Release 5.2(2a), the installer will detect an existing installation and perform the upgrade.

If you have Cisco DCNM-SAN Release 4.2(7) installed, you must upgrade to DCNM-SAN Release 5.0(x) before upgrading to DCNM-SAN Release 5.2(2a).

If you have a host running Solaris 10 for the Cisco DCNM-SAN Server and the Cisco DCNM-SAN Client, the TFTP service uses port 69 on the Solaris 10 host.

If you are running NX-OS Release 4.1(3) or an earlier release on a Cisco Nexus 5000 Series switch or on a UCS device, once your upgrade to Cisco DCNM-SAN Release 5.2(x) there will be discovery and display issues for the switches and devices. The reason for this is that Cisco DCNM-SAN Release 5.2(x) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running NX-OS Release 4.1(3) or an earlier release.

Cisco DCNM Release 5.2(2c) Installation Note

If you install Cisco DCNM Release 5.2(2c) on a system that is running Internet Explorer 9, Summary Dashboards do not display after the installation. To work around this issue, select Tools > Developer Tool and change the browser mode to Internet Explorer 8, and then change the browser mode back to Internet Explorer 9. Summary Dashboards should then be able to display.

This issue does not occur if you install Cisco DCNM Release 5.2(2c) on a system that is running Internet Explorer 8 or Firefox.

Cisco DCNM Release 5.2(2b) Installation Note

Cisco DCNM Release 5.2(2b) provides a single software image:

dcnm-installer-k9.5.2.2b.iso

This image replaces the following Release 5.2(2a) image that was deferred:

dcnm-installer-k9.5.2.2a.iso

If you installed Cisco DCNM Release 5.2(2a), including the Virtual Service Blade ISO image for the Cisco Nexus 1010, you should replace the dcnm-installer-k9.5.2.2a.iso image with the dcnm-installer-k9.5.2.2b.iso image. All other software images remain at Release 5.2(2a). For additional information, see CSCty12349.

Enhancements in Cisco DCNM Release 5.2(x)

This section includes the following topics:

Infrastructure Enhancements

New and Changed Information for Cisco MDS 9000 Family Switches

New and Changed Information for Cisco Nexus 1000V Series Switches

New and Changed Information for Cisco Nexus 2000 Series Fabric Extenders

New and Changed Information for Cisco Nexus 3000 Series Switches

New and Changed Information for Cisco Nexus 4000 Series Switches

New and Changed Information for Cisco Nexus 5000 Series Switches

New and Changed Information for Cisco Nexus 7000 Series Switches

New and Changed Information for Catalyst 6500 Series Switches

Infrastructure Enhancements

Cisco DCNM Release 5.2(x) includes the following new features for all Cisco Nexus platforms:

Common Installer for Cisco DCNM-LAN and Cisco DCNM-SAN

This feature allows you to use a single installer to install Cisco DCNM-LAN, Cisco DCNM-SAN, or both.

Common Database Schema

Cisco DCNM-LAN and Cisco DCNM-SAN share a common database schema. Because of this, users can have common local credentials for local users.

Network Path Analysis (PONG)

The PONG feature that is new in Cisco DCNM-LAN allows you to trace the path latency between two nodes at a given time interval and to monitor the latency information in the form of statistics, based on the polling frequency.

New and Changed Information for Cisco MDS 9000 Family Switches

Cisco DCNM-SAN Release 5.2(x) includes the following new features for the Cisco MDS 9000 Family switches:

Licensing Model Change

Cisco DCNM can be licensed for SAN and LAN environments separately or together. A significant change for Cisco DCNM-SAN, as compared to Cisco Fabric Manager, is that licenses are no longer hosted on a specific switch. Instead, the licenses are hosted on the Cisco DCNM-SAN server. All existing Cisco Fabric Manager licenses are grandfathered into this model (which means that they continue) so customers do not need to order or deploy any additional licenses to manage their existing Cisco MDS 9000 Family switches.

Two types of Cisco DCNM-SAN licenses are available:

Cisco DCNM-SAN Essentials Edition (comparable to Cisco Fabric Manager) is included at no charge with every Cisco MDS 9000 hardware purchase and can also be downloaded from http://www.cisco.com/go/dcnm.

Cisco DCNM-SAN Advanced Edition (comparable to Cisco Fabric Manager Server) provides additional capabilities and is required to use the Virtual Machine Topology and Performance feature and the Performance Forecasting Charts feature. The Advanced Edition licenses have the following part numbers:

Product Name:
Part Number, Paper Delivery:
Part Number, Electronic Delivery:

DCNM for SAN Advanced Edition for MDS 9500

DCNM-SAN-M95-K9=

L-DCNM-SAN-M95-K9=

DCNM for SAN Advanced Edition for MDS 9200

DCNM-SAN-M92-K9=

L-DCNM-SAN-M92-K9=

DCNM for SAN Advanced Edition for MDS 9100

DCNM-SAN-M91-K9=

L-DCNM-SAN-M91-K9=

DCNM for SAN Advanced Edition for Nexus 7000

DCNM-SAN-N7K-K9=

L-DCNM-SAN-N7K-K9=

DCNM for SAN Advanced Edition for Nexus 5000

DCNM-SAN-N5K-K9=

L-DCNM-SAN-N5K-K9=


Summary and Host Dashboards

The Cisco DCNM-SAN interactive Summary Dashboard provides views into the top fabric users and includes a drill-down capability to analyze their key performance indicators (KPIs). An events table displays events based on their criticality and has links to reports that display effected devices.The Host Dashboard provides a host-to-storage topology, an associated events table, and a performance chart.

Virtual Machine Topology and Performance

Cisco DCNM-SAN simplifies management of the virtual infrastructure by managing an end-to-end path through the physical network out to virtual network across the whole data center environment. The VMpath views increase service availability by identifying bottlenecks in VM and ESX performance and extending it out to the physical fabric. The virtual machine aware (VM-aware) topology view shows all of the dependencies from the virtual machine out to the physical host to the switch and out to storage and provides easy access to a detailed view of the path attributes. The VM-aware dashboard displays all of the information needed to manage a virtual environment including performance charts, inventory information, events, and VM ESX usage information. Cisco DCNM-SAN maps out paths all the way from the server to storage which enables tracking of mission critical workloads across the network.

Performance Forecasting Charts

Cisco DCNM-SAN proactively monitors the overall health of the data center network and generates alerts when it detects a potential service impact. It identifies and predicts if bottlenecks will occur based on historical trending and forecasting, which helps with capacity planning.

External SME-S 1.4 Agent

The SMI-S agent that is installed on the Cisco DCNM-SAN server allows external applications to access fabric and switch profiles as specified in the SNIA Common Information Model (CIM).


Note CIM is supported in Cisco DCNM-SAN Release 5.2(1), but is not supported in MDS NX-OS Release 5.2(1).


FCoE Provisioning and Management

The wizard based provisioning in Cisco DCNM-SAN allows for simple configuration of Fibre Channel and Fibre Channel over Ethernet (FCoE) interfaces. The performance monitoring of the FCoE path can show how much Fibre Channel versus Ethernet traffic moves through the path. The topology view can display the FCoE path through SAN or LAN switches out to the VMware virtual infrastructure.

Cisco DCNM-SAN supports CFS region support for IVR zone sets.

In Cisco CDNM-SAN client's Data Center LAN view, you can discover and display the VLAN topology for Ethernet switches.

Cisco Device Manager and the Cisco DCNM-SAN client support provisioning and monitoring of the 48-port 8-Gbps Advanced Fibre Channel switching module (DS-X9248-256K9) and the 32-port 8-Gbps Advanced Fibre Channel switching module (DS-X9232-256K9.)

Support for Secure Erase Feature Removed from Cisco DCNM-SAN

The Secure Erase feature is no longer supported and is not available in Cisco DCNM-SAN Release 5.2(x).

New and Changed Information for Cisco Nexus 1000V Series Switches

Cisco DCNM-LAN Release 5.2(1) includes the following new features for the Cisco Nexus 1000V Series switches:

Network State Tracking

The Network State Tracking (NST) feature can be used to detect link failures on upstream devices. NST is available only on vPC-HM port channels.

Licensing

Product Name:
Part Number, Paper Delivery:
Part Number, Electronic Delivery:

100 licenses for managing Cisco Nexus 1000V through Nexus 5000 LAN

DCNM-NXACC-100-K9=

L-DCNM-NXACC-100-K9=

250 licenses for managing Cisco Nexus 1000V through Nexus 5000 LAN

DCNM-NXACC-250-K9=

L-DCNM-NXACC-250-K9=


New and Changed Information for Cisco Nexus 2000 Series Fabric Extenders

Cisco DCNM-LAN Release 5.2(1) supports for Cisco Nexus 2000 Series Fabric Extenders on the Cisco Nexus 7000 Series platform.

Cisco DCNM-LAN Release 5.2(1) supports the new Cisco Nexus 2232TM 10GE Fabric Extender (N2k-C2232TM-10GE).

New and Changed Information for Cisco Nexus 3000 Series Switches

Cisco DCNM Release 5.2(1) includes the following new features for the Cisco Nexus 3000 Series switches:

Inventory

Layer 2 physical Ethernet interface

Layer 3 physical Ethernet interface

Layer 2 port channel - LACP

Layer 3 port channel - LACP

Routed SVI

Loopback interface

Management interfaces (IPv4 and IPv6)

UDLD

Jumbo Frames

VLAN

PVLAN over physical Ethernet interface

PVLAN over port channel

Local SPAN

Spanning Tree (MST and RPVST)

IPv4 ACL

VLAN ACL

Traffic storm control

AAA

RADIUS

TACACS+

RBAC (Roles and Users)

LACP Fast Timers

ACL on mgmt interface

Port channel force option

Configuration change management, except for switch-profile

DHCP snooping

IP Source Guard

VLAN VSAN overlay

Topology (physical view, port channel view, VLAN view, and VLAN-VSAN overlay). vPC is not supported for the Cisco Nexus 3000 Series.

New and Changed Information for Cisco Nexus 4000 Series Switches

Cisco DCNM-LAN Release 5.2(1) does not have any new features for the Cisco Nexus 4000 Series switches.

New and Changed Information for Cisco Nexus 5000 Series Switches

Cisco DCNM-LAN Release 5.2(1) includes the following new features for the Cisco Nexus 5000 Series switches:

Module Pre-provisioning

This feature allows you to pre-provision a module or Fabric Extender (FEX) using Cisco DCNM. The interfaces on the pre-provisioned modules can be configured like any other interfaces.

Private VLAN Over Port Channel and vPC

The private VLAN feature, which was initially supported only on physical interfaces, has been extended to port channels and vPCs.

Configuration Sync Enhancements

Cisco DCNM-LAN has three enhancements that support the configuration sync feature:

You can view all the vPC Cisco Nexus 5000 peers in the network, and see if there is a switch-profile configured between the peers. If there is no switch profile, Cisco DCNM-LAN provides a wizard to create switch profiles between the vPC peers and also import the dual-homed FEX HIFs into the switch profile.

You can create a switch profile between the vPC peers using a single context menu option.

You can create a switch profile between any two Cisco Nexus 5000 switches, using a simple two-step wizard.

Support for Switch Virtual Interface

Cisco DCNM-LAN Release 5.2(x) allows you to discover and manage Cisco Nexus 5000 Series Switches using Switch Virtual Interface (SVI).

Licensing

Product Name:
Part Number, Paper Delivery:
Part Number, Electronic Delivery:

100 licenses for managing Cisco Nexus 1000V through Nexus 5000 LAN

DCNM-NXACC-100-K9=

L-DCNM-NXACC-100-K9=

250 licenses for managing Cisco Nexus 1000V through Nexus 5000 LAN

DCNM-NXACC-250-K9=

L-DCNM-NXACC-250-K9=


New and Changed Information for Cisco Nexus 7000 Series Switches

Cisco DCNM-LAN Release 5.2(x) includes the following new features for Cisco Nexus 7000 Series switches:

Port Profile Support

Starting with NX-OS Release 5.2(x), you can create, delete, and modify the Layer 2 parameters of port profiles on Cisco Nexus 7000 Series devices. You can also view the interface types that inherit a given profile.

FabricPath Resources

You can view the switch ID for devices enabled for FabricPath, and you can also view the conflicts between switches.

Cross-Launch for the Cisco Nexus 7000 Series

You can launch Cisco DCNM-SAN client from the FCoE VDC using the Cisco DCNM-LAN topology.

FEX Layer 3 Routed Port for HIF Ports

This features allows you to configure and manage Layer 3 interfaces for FEX interfaces.

Support for the 48-Port 1-Gigabit Ethernet Module XL

Cisco DCNM-LAN Release 5.2(x) allows you to manage the Cisco Nexus 7000 48-Port 1-Gigabit Ethernet Module XL.

Support for the Cisco Nexus 7009 Chassis

Cisco DCNM-LAN Release 5.2(x) includes the software to support the Cisco Nexus 7009 chassis.

Support for the Cisco Nexus N2232T FEX and Cisco Nexus N2224T FEX

Cisco DCNM-LAN Release 5.2(x) can discover the Cisco Nexus N2232T FEX and Cisco Nexus N2224T FEX and allows you to view those devices in inventory and topology. You can also manage the FEX interfaces from various feature screens.

Shared Interfaces

With the shared interfaces feature, you can create a new storage VDC, share ports across the Ethernet and storage VDC, and configure allowed VLANs from the Ethernet VDC to the storage VDC.

Separation of M1 and F1 Series Modules

You can set M1 or F1 allocation type parameters for each VDC in a chassis to take maximum advantage of the module in the corresponding VDCs.

Network Path Analysis (PONG)

The PONG feature allows you to trace the path latency between two nodes at a given time interval and to monitor the latency information in the form of statistics, based on the polling frequency.

Support for Switch Virtual Interface

Cisco DCNM-LAN Release 5.2(x) allows you to discover and manage Cisco Nexus 7000 Series Switches using Switch Virtual Interface (SVI).

Licensing

Product Name:
Part Number, Paper Delivery:
Part Number, Electronic Delivery:

Managing Cisco Nexus 7000 LAN

DCNM-N7K-K9=

L-DCNM-N7K-K9=


New and Changed Information for Catalyst 6500 Series Switches

Cisco DCNM-LAN Release 5.2(x) includes the following new features for Catalyst 6500 Series switches:

Physical Interfaces (FastEthernet, GigabitEthernet, TenGigaBitEthernet)

Port channels (PagP, LACP)

Loopback Interfaces

VLAN Network Interfaces

VLAN

PVLAN

STP (PVST, MST, RPVST+)

Inventory

Topology

Image Management

Configuration Archive Management

Configuration Delivery Management

Copy running configuration to startup configuration

Threshold and rate mode

Cisco DCNM-LAN Release 5.2(x) supports the IOS 12.2(33)SXJ release train and IOS Release 12.2(33)SXI5 and later versions in the 12.2(33)SXI release train.

New and Changed Information for the Cisco Unified Computing System

Cisco DCNM-LAN Release 5.2(x) includes the following new features for the Cisco Unified Computing System:

UCS Discovery

Cisco DCNM Release 5.2(x) supports the discovery of UCS B-Series. UCS information is displayed in topology and inventory.

Limitations in Cisco DCNM Release 5.2(x)

This section includes the following topics:

Limitations for the Cisco MDS 9000 Family with Cisco DCNM Release 5.2(x)

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.2

Limitations for the Cisco Nexus 5000 Series with Cisco DCNM Release 5.2

Limitations for the Cisco Nexus 1000v Series with Cisco DCNM Release 5.2

Limitations for Catalyst 6500 Switches with Cisco DCNM Release 5.2

Limitations for the Cisco MDS 9000 Family with Cisco DCNM Release 5.2(x)

This section describes the limitations in Cisco DCNM Release 5.2(x) for Cisco MDS 9000 Family:

Cannot Launch Windows 7 64-bit Telnet Application from Cisco DCNM-SAN

The 64-bit Telnet application that comes with Windows 7 cannot be launched from DCNM-SAN to Telnet to MDS 9000 switches because Cisco DCNM-SAN is a 32-bit application.

To work around this issue, install a 32-bit Telnet application and modify the Cisco DCNM-SAN and Device Manager preferences to set the Telnet path location to the 32-bit version of the Telnet application.


Tip On a 64-bit machine you can verify in Task Manager that you are using a 32-bit version of a client application. Look at the Image Name column in the Processes tab. If there is a 32-bit application installed, it is displayed with a *32 suffix, such as iexplore *32.


Unsupported Licenses

Cisco DCNM Client and Server do not support licenses for Cisco Data Mobility Manager (DMM) when the client is running on the same machine as the server. The Cisco DCNM-SAN standalone version does support the following DMM licenses:

DMM_FOR_SSM_PKG

DMM_184_PKG

DMM_9222i_PKG

DMM_SSN16_PKG

Cisco DCNM -SAN does not support licenses for the Cisco Storage Media Encryption (SME) application.

Smart Card in Windows 7 Is Not Supported When Cisco DCNM-SAN Creates a Cluster

If you are using Windows 7 and you connect a smart card to a host, the smart card reader is visible in Device Manager. If you create the SME cluster with standard and advanced security modes, Cisco DCNM-SAN displays a message that it cannot detect the smart card reader.

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.2

This section describes the limitations in Cisco DCNM Release 5.2(x) for the Cisco Nexus 7000 Series:

Unsupported Storage VDC Features Are Filtered Out in Cisco DCNM-SAN

The Cisco DCNM-SAN GUI does not display the following features for the storage VDC because they are not supported in Cisco NX-OS Release 5.2(x). More information about each limitation is available in the referenced bug ID.

Cisco Nexus 7000 Series switches are filtered from the following syslog tabs (CSCtk66392):

CFS tab (for the syslogd CFS configuration): Cisco Nexus 7000 Series switches are filtered from this tab because the storage VDC does not support syslogd CFS.

Servers tab (for the syslog server configuration): Cisco Nexus 7000 Series switches are filtered from this tab if any of the Cisco MDS 9000 switches in the fabric have syslog CFS enabled. If they do, CFS can distribute the syslog configuration to those MDS 9000 switches. You can use the CLI to distribute the syslog configuration to each individual Cisco Nexus 7000 Series switch.

IP ACL MIBs are not supported. (CSCto84391)

The common role cannot be created. (CSCtq10381)

The storage VDC cannot be installed through the Cisco DCNM-SAN License Install wizard. (CSCtq39086)

The storage VDC cannot be upgraded through the Upgrade wizard because Cisco Nexus 7000 Series switches do no support the MIB related to upgrade.

IP routing cannot be enabled through SNMP because Cisco Nexus 7000 Series switches do not support the MIB for IP routing. (CSCtq30553)

FlexAttach, iSNS, and Cloud-Discovery are not supported on the storage VDC. (CSCtq89856)

The storage VDC does not support IPsec. (CSCtq91091)

The storage VDC does not support iSCSI. (CSCtq95125)

Remote Accounting Should be Used to Log Show Commands

If the terminal log-all option is configured on a Cisco Nexus 7000 Series switch, then Cisco DCNM-LAN does not work correctly. To use Cisco DCNM-LAN and log show commands, remote accounting is required.

ISSU That Passed Can Show as Failed

Cisco DCNM-LAN can show an ISSU status as Failed, even though the ISSU completed successfully in the device. This issue might occur if the device exceeds the maximum XML session limit of eight sessions.

Limitations for the Cisco Nexus 5000 Series with Cisco DCNM Release 5.2

Cisco DSNM-SAN Release 5.2(x) does not support discovery and management of Cisco Nexus 5000 Series switches using Switch Virtual Interface (SVI).

Limitations for the Cisco Nexus 1000v Series with Cisco DCNM Release 5.2

This section describes the limitations in Cisco DCNM Release 5.2(x) for the Cisco Nexus 1000v Series:

LAN Connectivity Connections Do Not Display for VMs

MAC address information that discovered is through a Cisco Nexus 1000v device for the corresponding ESX server ports is not displayed in the LAN Connectivity details panel on the Servers screen under Network Servers. N/A is displayed rather than the MAC address information You can see this issue from the Servers screen under the Network Servers feature when you select a VM to see the LAN connectivity information.

To work around this issue, use Cisco DCNM to discover the ESX server for the selected VM. Specify the ESX server IP address and credentials to see the MAC information for the server ports.

Limitations for Catalyst 6500 Switches with Cisco DCNM Release 5.2

This section describes the limitations in Catalyst 6500 Switches with Cisco DCNM Release 5.2.

Supervisor-2T and the related IOS versions are not supported in Cisco DCNM-LAN Release 5.2.

There is no support for VSS.

Catalyst 6500 switches support is read-only in device feature screens. In other words, a user can see the configuration but cannot modify it in these screens. A user can deliver a configuration only through the Configuration Delivery Management feature.

Caveats

This section includes the following topics:

Open Caveats—Cisco DCNM Release 5.2

Open Caveats—Cisco DCNM-LAN Release 5.2

Open Caveats—Cisco DCNM-SAN Release 5.2

Resolved Caveats—Cisco DCNM Release 5.2(2e)

Resolved Caveats—Cisco DCNM LAN Release 5.2(2e)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2e)

Resolved Caveats—Cisco DCNM Release 5.2(2c)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2c)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2b)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2a)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2a)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2)

Resolved Caveats—Cisco DCNM-LAN Release 5.2(1)

Resolved Caveats—Cisco DCNM-SAN Release 5.2(1)

Open Caveats—Cisco DCNM Release 5.2

This section lists open caveats that apply to both Cisco DCNM-LAN and Cisco DCNM-SAN.

CSCto59733

Symptom: The Cisco DCNM installer is unable to launch.

Conditions: The Cisco DCNM installer displays the following exception when you install Cisco DCNM on a Linux machine where the shared library libXtst.so not installed.

Launching installer...
Invocation of this Java Application has caused an InvocationTargetException. This 
application will now exit. (LAX)
Stack Trace:
java.lang.UnsatisfiedLinkError: 
/tmp/install.dir.13806/Linux/resource/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: 
cannot open shared object file: No such file or directory
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(Unknown Source)
        at java.lang.ClassLoader.loadLibrary(Unknown Source)
 
   

Workaround: This is a known issue with InstallAnywhere:

http://community.flexerasoftware.com/showthread.php?p=461440

The solution is available at this URL:

http://docsfree.com/uimodules/docs/docs_frame.jsp?meme_id=130971&category_id=null&topic_id=null&searchstring=null

Install the missing "xorg-x11-deprecated-libs" package by following these steps:

1. Enter the following command to confirm that libXp is missing:

$ rpm --query --whatprovides 'libXp.so.6'
 
   

2. Install the package by entering the following command:

# rpm -ivh xorg-x11-deprecated-libs..rpm
 
   

Examples of rpm packages that contain libXp.so.6 are as follows:

xorg-x11-deprecated-libs-6.8.1-12.i386.rpm,

xorg-x11-deprecated-libs-6.8.2-31.i386.rpm

Alternatively, you can install the package by entering the following command:

yum install xorg-x11-deprecated-libs
 
   

CSCtr53017

Symptom: The Cisco DCNM installer does not display a message regarding Cisco DCNM-SAN server startup failure during an incremental installation when Cisco DCNM-SAN is installed over Cisco DCNM-LAN.

Conditions: This issue is seen when the Cisco DCNM-SAN is installed over Cisco DCNM-LAN.

Workaround: Manually stop and restart the Cisco DCNM-SAN server.

Open Caveats—Cisco DCNM-LAN Release 5.2

CSCti47687

Symptom: The DCNM Client for tracking is not reflected in the object tracking GUI when the client is configured as a VRRP.

Conditions: You configure tracks for route reachability and interface IPv6 routing, and then configure a VRRP on the device so that it tracks the object associated with interface IPv6 routing. In the details panel for track 1 in the GUI, the VRRP is not reflected as a client.

Workaround: None.

CSCtj32535

Symptom: For the IP and IPv6 ACL features, the statistics are not updated when the sequence number of the access control rule changes.

Conditions: This problem is seen during the following operations that change the sequence number:

Move Up/Down

Insert Above/Below

Edit Sequence number

Workaround: To export or save the existing chart data for the Access Control Entry (ACE) (for which the sequence number is to be changed by the move, insert, or modify operations), delete the existing collection running for that ACE. Afterwards, a new collection can be triggered for the ACE.

CSCtj43290

Symptom: The Cisco DCNM cluster nodes cannot access the shared data path directory when stating the Cisco DCNM server as a Windows service. Because the Cisco DCNM cluster nodes are not able to access the shared data path directory, configuration archives and custom templates are not visible in the Cisco DCNM client.

Conditions: This problem occurs only with the Windows platform when starting the Cisco DCNM server using the Start DCNM shortcut or rebooting the server machine—the Cisco DCNM server starts as a Windows service. The problem is by default; Windows NT services run as a SYSTEM user. The SYSTEM user does not have permission to access network resources.

Workaround: Configure the Windows username and password for the Cisco DCNM server service (one-time task) as follows:

1. If the Cisco DCNM service is running, stop it.

2. Manually assign credentials by choosing Control Panel > Administrative Tools > Services > Cisco DCNM server > Properties > Log on Tab.

3. Restart the Cisco DCNM service.

CSCtj84081

Symptom: If you make a configuration change in Cisco DCNM, it may not be applied to the device if the Network Element exception is used in the GUI.

Conditions: This symptom might be seen when the xml server validate all command has been entered on the device.

Workaround: Enter the no xml server validate all command on the device and reapply the same configuration in Cisco DCNM.

CSCtn19363

Symptom: Following the installation of Cisco DCNM-LAN, the database user and database admin passwords can be seen in clear text in server directories.

Conditions: This symptom might be seen following the installation of Cisco DCNM-LAN. Some batch files show the password in clear text.

Workaround: None. Password encryption will be available in a future release.

CSCtn70486

Symptom: The port-channel member details that display in Cisco DCNM for a custom VDC are out of sync with a Cisco Nexus 7000 Series device.

Conditions: This symptom might be seen in these situations:

An Ethernet 1/1 interface is part of a custom VDC. The customer-A VDC and its corresponding default VDC are the VDC-default.

Module 1 of the default VDC reloads.

The Ethernet 1/1 interface that is part of customer-A will still be shown in Cisco DCNM even it is removed in the device.

The member port (Ethernet1/1) information that is shown for the port-channel will be out of sync with device.

Workaround: Rediscover the custom VDC.

CSCtr32209

Symptom: Device discovery takes more time than it normally takes or the discovery status shows "the server is crashed or restarted" even though there is no server restarts.

Conditions: This symptom might be seen very rarely when Postgres is the database server.

Workaround: Restart the Cisco DCNM-LAN server and rediscover the unmanaged devices.

CSCtr35544

Symptom: Cisco DCNM-LAN shows an unexpected difference when you compare a checkpoint archived version with the startup configuration in the version browser screen.

In addition, there are unexpected differences when you compare the Cisco DCNM Release 4.2(1) checkpoint archived version with the Cisco DCNM Release 5.2(x) checkpoint version.

Conditions: This symptom might be seen if the Cisco Nexus device has image version greater than Release 4.2(1).

Workaround: None.

CSCtx16177

Symptom: The install.conf file was not found during an upgrade of Cisco DCNM-SAN.

Conditions: This symptom might be seen if a different admin attempts to perform the upgrade.

Workaround: Read the property value USER_HOME from the $INSTALLDIR/dcm/Uninstall_DCNM/installvariables.properties file, then locate install.conf.

CSCtx39981

Symptom: Cisco DCNM-LAN is unable to discover Cisco Nexus 5000 Series or Cisco Nexus 7000 Sereis devices. The following error message appears in the debug or trace mode related to the SSH protocol being unavailable: "device didn't allow new connection because of either exceeded connection limit or transport protocol is down." The devices status is "Unmanaged" in the topology pane.

Conditions: This symptom might be seen if Cisco DCNM-LAN hangs SSH communication when Cisco NX-OS software on a Cisco Nexus 5000 Series or Cisco Nexus 7000 device takes more than eight seconds to answer with the sshd version when running the following test:

C:\>plink -v user@a.b.c.d
...
Server version: SSH-2.0-OpenSSH_5.5 FIPS
....
Using SSH protocol version 2
....

If sshd is the first process with highest usage, then high CPU occurs in the Cisco Nexus switch.

Workaround: Lower the CPU load on Cisco NX-OS to have less latency over SSH.

CSCtx75792

Symptom: A syntax error occurs when you select the Allocate unallocated interfaces menu option from the VDC summary panel of the VDC feature screen.

Conditions: This symptom might be seen because the pool of unallocated interfaces list should have F2 and non-F2 interfaces in the interface association panel.

Workaround: Rediscover the device. To avoid a reoccurrence of this issue, use either of the following approaches:

If the unallocated pool has F2 and non-F2 interfaces, use the association panel or details panel and select each unallocated interface to allocate it.

If the unallocated pool has only the supported interfaces for the selected VDC, use the Allocate unallocated interfaces menu option from the VDC screen.

CSCtx75958

Symptom: Interfaces that are present in the device (VDC) are out of sync with DCNM-LAN.

Conditions: This symptom might be seen when you attempt to allocate an interface in the unallocated pool from the interfaces association panel. Only some of the interfaces are added to the VDC, but all the interfaces that belong to the port group are added to the device.

Workaround: To work around this issue, perform one of the following actions:

Select all the port group members and reallocate them to the VDC where the ports are out of sync.

Rediscover the device.

CSCtx79298

Symptom: A VDC link is missing in Topology.

Conditions: The show hostname command displays the fully qualified domain name such as myhost-VDC.dc.example.gov.au. Cisco DCNM-LAN expects to see myhost-VDC

Workaround: None.

Open Caveats—Cisco DCNM-SAN Release 5.2

CSCtn41681

Symptom: When you create multiple flows from the Flow wizard, flows with a VFC PortChannel source may be added without reporting an error.

Conditions: If multiple flows are selected that contain flows with a VFC PortChannel source, the wizard may create those flows on a source module pertaining to another flow in the selected list, instead of reporting an error that flow creation for VFC port channels is not supported.

Workaround: To create the flow on a specific module, you can insert the flow through the End Devices > Flow Statistics table.

CSCtn90241

Symptom: Performance graphs are not sent when reports are sent by e-mail.

Conditions: This symptom might be seen because charts are not embedded in HTML reports, but are separate files. As a result, they appear as broken links in a report that is e-mailed.

Workaround: Choose the Link Only option when you send a report that contains a chart.

CSCtq60411

Symptom: The syslog page doe not show any syslogs for the scoped fabric.

Conditions: This issue might be seen anytime you open a scoped fabric in Cisco DCNM-SAN web client, but it is not seen with regular fabrics.

Workaround: Click the syslog archives link to see the syslog per switch.

CSCtq60647

Symptom: When you launch Device Manager from Cisco DCNM-SAN and go to Logs > Syslog > Verify, you can see the error message "Can't connect to FM Server - Call invocation failed; nested exception is: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage."

Conditions: This symptom is seen only when you launch Device Manager from Cisco DCNM-SAN for the first time.

Workaround: There are two ways to work around this issue:

Open Device Manager and then open Device Manager again from Cisco DCNM-SAN.

Run syslog Verify from a standalone Device Manage DM launched from a desktop shortcut.

CSCtr16608

Symptom: The Cisco DCNM-SAN client Control Panel does not support VCenter management in a federated server environment. As a result, discovered VMs are not displayed in the Cisco DCNM-SAN client.

Conditions: This symptom might be seen in a federated server environment.

Workaround: Use the Cisco DCNM-SAN web client to manage a VCenter in a federated server environment.

CSCtr21907

Symptom: When same switch exists in both Cisco DCNM-LAN and Cisco DCNM-SAN, CPU/Memory statistics are not displayed properly.

Conditions: This symptom might be seen when you select PM->Datacenter node. The PM->Other and PM->Switch->CPU/Memory tables are shown correctly, but when you select Fabric node, none of the tables is shown.

Workaround: Select Data Center in the scope tree to view all CPU/Memory statistics.

CSCtr23604

Symptom: SME Disk keys are imported multiple times.

Workaround: Do not select disks in the disk list when you use the import option. Chose the destination disk for imports during the import operation. Selecting multiple disks causes the import to be called multiple times.

CSCtr30001

Symptom: On the Performance > ISL and Performance > Flows page, all the entries are listed as n/aB.

Conditions: This symptom might be seen following fabric discovery when a user attempts to add the fabric to the Performance Manager collection and clicks Cancel when asked if they want to restart the Performance Manager, and instead selects Admin > status to restart the Performance Manager service.

Workaround: Restart Cisco DCNM-SAN.

CSCtr38694

Symptom: If a VFC is connected to a Ethernet PortChannel through a VFC PortChannel, the Device Manager device view does not show the VFC mode letter of the binding Ethernet port.

Conditions: This symptom might be seen because Device Manager is able to show the Fibre Channel PortChannel member mode in Device Manager device view, but not the Ethernet PortChannel VFC members. The Port Manager is able to report the trunk mode of a Fibre Channel PortChannel on a Fibre Channel port, but not able to report the mode of the VFC on the Ethernet port where its virtual interface member is bound.

Workaround: To work around this issue, do one of the following:

Open the Device Manager Summary page that shows all the VFCs and VFC PortChannels that are up, and the binding Ethernet port information.

Go to Device Manager Interface -> Virtual Interfaces -> Fibre Channel to see all VFC and VFC PortChannel information and go Interface -> Port Channel -> Ethernet Interfaces to get the binding Ethernet port information.

CSCtr38950

Symptom: Reloading a switch causes the Cisco DCNM-SAN client map to show the red X on some ISL links, even though all the links are up.

Conditions: This issue might be seen after a switch reload or reset.

Workaround: To work around this issue, do one of the following:

Close the current Cisco DCNM-SAN client and open a new Cisco DCNM-SAN client. The issue will not be seen in the new client.

Click Resync All in the client.

CSCtr41754

Symptom: When you create flows from the Flow wizard, some flows are created on wrong source module.

Conditions: When multiple flows are selected for a switch in the Flow wizard that has different sources, all flows are created on the module pertaining to the source of one of the selected flows for that switch.

Workaround: To create flows on the corresponding source module of each flow, select all flows with a common source module in one pass of the wizard and rerun the wizard for other modules; otherwise, use table insertion to create flows on specific modules.

CSCtr42077

Symptom: A switch reload causes the Cisco DCNM-SAN client Map to show the red X on some ISL links, even though all links are up.

Conditions: This might be seen following a switch reload or reset.

Workaround: After the switch has stabilized and a full discovery is done, either close the current client and open a new client, or click Resync All in the current client when you see that the red X has not been removed.

CSCts32904

Symptom: Cisco DCNM-SAN cannot discover the fabric if a Cisco UCS 6100 Fabric Interconnect that is operating in switch mode is used as the seed switch in the fabric.

Conditions: This symptom might be seen when a Cisco UCS 6100 Fabric Interconnect is used as the seed switch.

Workaround: Use a different switch as the seed switch.

CSCtx05218

Symptom: Cisco DCNM-SAN cannot discover the fabric if a Cisco UCS 6100 Fabric Interconnect that is operating in switch mode is used as the seed switch in the fabric.

Conditions: This symptom might be seen when a Cisco UCS 6100 Fabric Interconnect is used as the seed switch.

Workaround: Use a different switch as the seed switch.

CSCtz35287

Symptom: Backup jobs and the backups view pane give inconsistent output.

Conditions: This symptom might be seen under normal operating conditions.

Workaround: None.

CSCtz39546

Symptom: The Cisco DCNM-SAN server does not start if an ampersand (&) character is used in the database password for a PostgreSQL installation.

Conditions: This symptom might be seen when you use an ampersand (&) character in the PostgreSQL password.

Workaround: Do not use an ampersand (&) character in the PostgreSQL password.

Resolved Caveats—Cisco DCNM Release 5.2(2e)

CSCua06417

Symptom: The installation of Cisco DCNM Release 5.2(1) fails with a message that port 9099 is not available.

Conditions: This symptom might be seen when you attempt to install Cisco DCNM Release 5.2(1) on a system that is running Microsoft Windows 8.

Workaround: This issue is resolved.

CSCua93596

Symptom: A topology does not get loaded if the Cisco DCNM client server mode is SSL.

Conditions: This symptom might be seen when Cisco DCNM client server mode is SSL.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM LAN Release 5.2(2e)

CSCua15366

Symptom: The Cisco DCNM LAN client becomes very slow after it is manually started.

Conditions: This symptom might be seen when SSL is enabled on Cisco DCNM LAN.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2e)

CSCtx63077

Symptom: When you double click a port image in DM device view, DM displays the following message:

2012.01.27 16:36:38   [ui.Util] Cannot write XdndAware property
2012.01.27 16:36:38   [Exception] Cannot write XdndAware property
sun.awt.X11.XException: Cannot write XdndAware property
                at sun.awt.X11.XDnDDropTargetProtocol.registerDropTarget(Unknown 
Source)
                at sun.awt.X11.XDropTargetRegistry.registerDropSite(Unknown Source)
                at sun.awt.X11.XWindowPeer.addDropTarget(Unknown Source)
                at sun.awt.X11.XComponentPeer.add
 
   

Conditions: This symptom might be seen when Linux Red Hat 5.5 and later releases and JRE 1.6u23 and later releases are installed. Because of a Java issue (7027598), you cannot open any form in a DM dialog box.

Workaround: This issue is resolved.

CSCty43268

Symptom: Statistics for ISLs continue to be collected even after they are removed from the collection.

Conditions: This symptom might be seen when you create a collection for a fabric to collect statistics for ISLs and other entities, and you subsequently uncheck ISLs to stop collecting statistics for them.

Workaround: This issue is resolved.

CSCtz55014

Symptom: In the fabric display in the Cisco DCNM-SAN client, you can select between host and target ports. The display should show the initiators under the host tab and targets under the storage tab.

Conditions: This symptom might be seen on an IBM storage device DS8700. The target ports are shown under the host tab.

Workaround: This issue is resolved.

CSCtz82233

Symptom: A Cisco DCNM server frequently logs in to a Cisco Unified Computing System (UCS) server, which slows it down.

Conditions: This symptom might be seen when a CLI or SNMP account is valid, HTTPS is enabled on UCS, and the self-signed UCS Manager HTTPS certificate is manually imported into the Cisco DCNM trust store.

Workaround: This issue is resolved.

CSCua38986

Symptom: SNMP traps are sent to the Cisco DCNM server, but they do not appear in Health > Events in the Cisco DCNM web client. The statistics in Admin > Registration > SNMP Trap Statistics show the counters increment for received, dropped, and processed for each trap generated.

Conditions: This symptom might be seen when alerts do not get forwarded using Event Forwarding.

Workaround: This issue is resolved.

CSCua74119

Symptom: The Performance Manager does not collect statistics from a Cisco MDS 9000 switch that is configured as an NPIV core switch.

Conditions: This symptom might be seen when a Cisco MDS 9000 switch that is configured as an NPIV core switch is connected to a Brocade switch in NPV mode.

Workaround: This issue is resolved.

CSCub00415

Symptom: A locking issue occurs in persistent code.

Conditions: This symptom might be seen when the fabric is not flushed into the database.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM Release 5.2(2c)

CSCty32783

Symptom: In a cluster setup, the Cisco DCNM installer fails to install JBoss in the secondary nodes.

Conditions: This symptom might be seen only when you install Cisco DCNM Release 5.2(2a).

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2c)

CACty38649

Symptom: In Cisco DCNM LAN Release 5.2(2a), disabling or enabling port security has no effect.

Conditions: This symptom might be seen when you attempt to configure port security on an Ethernet interface.

Workaround: This issue is resolved.

CSCty67089

Symptom: The error "Internal server error. java.lang.NullPointerException" appears when you modify the interface basic parameters in DCNM LAN for a Cisco Nexus 1000 device by selecting Feature Interfaces > Ethernet Port.

Conditions: This symptom might be seen when you try to modify the basic parameters of the Ethernet port that is a member of a port channel by selecting Feature Interface > Ethernet Port.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2b)

CSCty12349

Symptoms: The VSB ISO image of Cisco DCNM Release 5.2(2a) has errors that prevent the server from starting after a successful installation.

Conditions: This symptom might be seen when you install the Cisco DCNM Release 5.2(2a) Virtual Service Blade (VSB) image for the Cisco Nexus 1010.

Workaround: To work around this issue, install the VSB image of Cisco DCNM Release 5.2(2b) for the Cisco Nexus 1010.

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2a)

CSCtt97437

Symptom: Syslog message date parsing fails when the syslog message has millisecond information. Millisecond information is present when the logging timestamp milliseconds configuration is applied.

Workaround: This issue is resolved.

CSCtw71383

Symptom: If you have Cisco DCNM-SAN installed and try to install Cisco DCNM-LAN with the -i silent in a install.properties file, the installation always fails with a failed to decrypt credentials message.

Workaround: This issue is resolved.

CSCtx02174

Symptom: Due to an exception, the Cisco DCNM-LAN client does not close after multiple tries to close it from the File-> Exit menu or by clicking the close (cross) icon.

Workaround: This issue is resolved.

CSCtx52016

Symptom: The software install does not provide a DCNM instance ID. The error produced is:

getaddress:Could not find mac address for the windows host.
 
   

The physical server has a dual-network interface card.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM-SAN Release 5.2(2a)

CSCtu00959

Symptom: When you click Refresh, the Port WWN column shows a different value.

Workaround: This issue is resolved.

CSCtw59374

Symptom: Cisco DCNM-SAN Release 5.2(1) disallows UCS without FC4 features or types from zoning prior to an OS load.

Conditions: This symptom might be seen on a boot from a SAN UCS server prior to booting up any OS. After a UCS FLOGI into the fabric, UCS does not register any FC4 features or types with the FCNS, which prevents Cisco DCNM-SAN from properly recognizing this device.

Workaround: This issue is resolved.

CSCtw59456

Symptom: In the Cisco DCNM web client for Release 5.2(1), the license for each feature of switch shows 120 days as the grace period, but the CLI for the switch for license usage shows no 120 days grace period.

switch# show license usage
 Feature                      Ins  Lic   Status Expiry Date Comments      Count
     
> ----------------------------------------------------------------------
 
   
 --------
DMM_184_PKG                   No    0   Unused             -
 FM_SERVER_PKG                 Yes   -   Unused never       -
 MAINFRAME_PKG                 No    -   Unused             -
 ENTERPRISE_PKG                No    -   Unused             -
 DMM_FOR_SSM_PKG               No    0   Unused             -
 SAN_EXTN_OVER_IP              No    0   Unused             -
 PORT_ACTIVATION_PKG           No    0   Unused             -
 SME_FOR_IPS_184_PKG           No    0   Unused             -
 STORAGE_SERVICES_184          No    0   Unused             -
 SAN_EXTN_OVER_IP_18_4         No    0   Unused             -
 SAN_EXTN_OVER_IP_IPS2         No    0   Unused             -
 SAN_EXTN_OVER_IP_IPS4         No    0   Unused             -
STORAGE_SERVICES_SSN16        No    0   Unused             -
10G_PORT_ACTIVATION_PKG       No    0   Unused             -
STORAGE_SERVICES_ENABLER_PKG  No    0   Unused             -
 
   

None of the features is enabled on the switch.

Workaround: This issue is resolved.

CSCtw88021

Symptom: The DMM polling interval tool tip says "Secure Erase."

Workaround: This issue has been resolved.

CSCtx49060

Symptom: When multipath connected hosts exist in topology, the web topology does not show the multipath link to the fabric correctly in the Cisco DCNM-SAN web client.

Workaround: This issue is resolved.

CSCtx49113

Symptom: NPV discovery must be enabled in a property in the server.properties file.

Workaround: This issue is resolved.

CSCtx63077

Symptom: When you double-click port image in the DM device view, the following exception appears:

2012.01.27 16:36:38   [ui.Util] Cannot write XdndAware property
2012.01.27 16:36:38   [Exception] Cannot write XdndAware property
sun.awt.X11.XException: Cannot write XdndAware property
                at sun.awt.X11.XDnDDropTargetProtocol.registerDropTarget(Unknown 
Source)
                at sun.awt.X11.XDropTargetRegistry.registerDropSite(Unknown Source)
                at sun.awt.X11.XWindowPeer.addDropTarget(Unknown Source)
                at sun.awt.X11.XComponentPeer.add
 
   

Conditions: This symptom might be seen on a system with Linux Red Hat Release 5.5 and later releases and JRE 1.6 u23 and later releases. You cannot open any "form" type of DM dialog box because of the Java bug 7027598.

Workaround: This issue is resolved.

Resolved Caveats—Cisco DCNM-LAN Release 5.2(2)

CSCtn15296

Symptom: An error message is not clear when a user tries to create a VLAN in the reserved VLAN range in any custom VDC using Cisco DCNM-LAN.

Conditions: This symptom might be seen in this situation:

1. A user modifies the reserved VLANs in the default VDC.

2. The user then uses Cisco DCNM-LAN to create a new VLAN in a custom VDC, which falls within the new reserved VLAN range.

Workaround: Rediscover the custom VDC in Cisco DCNM-LAN to see the correct error message when creating VLANs in the reserved VLAN range.

CSCtq85466

Symptom: After the GUI restarts or a device is rediscovered, you cannot re-open the Port-Channel statistics for a selected port-channel interface.

Conditions: This symptom might be seen when port-channel statistics have been started. If the GUI restarts or a device is rediscovered, the following port-channel statistics are not restarted: i:

Channel Utilization Statistics

Channel Traffic Rate Statistics

Link Utilization Statistics

Link Traffic Rate Statistics

Channel Link Load Distribution

Workaround: There is no workaround to re-open the existing chart. You can create a new chart for this statistics and start monitoring.

CSCtr47659

Symptom: In the VLAN screen for Cisco Nexus 1000V devices, the context menus Enable PVLAN Conditional Service and Disable PVLAN Conditional Service in the VLAN summary table are not enabled.

Conditions: This symptom might be seen under the following conditions:

The PVLAN conditional service is disabled on the device and a user tries to enable it using the context menu Enable PVLAN Conditional Service in the VLAN summary table.

The PVLAN conditional service is enabled on device and a user tries to disable it using the context menu Disable PVLAN Conditional Service in the VLAN summary table.

Workaround: Enable or disable the PVLAN conditional service directly on the device.

CSCtr50721

Symptom: Following a nondisruptive software upgrade to, or a downgrade from Cisco DCNM, a port mode change in the interfaces screen, or entering the fex type number command from the fabric extender screen triggers a network element exception with the message "command configure executed with err status [-30]".

Conditions: This symptom might be seen when the device operating system installation wizard is closed without a proper status update in Cisco DCNM. For example, the ISSU or ISSD completes on the device, but Cisco DCNM does not reflect the status and the user closes the wizard.

Workaround: Refresh the device operating system installation screen.

CSCtr50633

Symptom: The Cisco DCNM installer does not display a message regarding port conflicts during an incremental installation when Cisco DCNM-SAN is installed over Cisco DCNM-LAN.

Conditions: The symptom might be seen when you manually update the port numbers and override the default values. This scenario occurs when you install Cisco DCNM-SAN over Cisco DCNM-LAN.

Workaround: To work around this issue, do one of the following:

Install Cisco DCNM-LAN and Cisco DCNM-SAN at the same time to avoid the port conflicts.

Install Cisco DCNM-SAN first, then install Cisco DCNM-LAN if you perform an incremental installation.

Suspend the process where port conflict occurred and then activate it once the installation is complete.

CSCtt29393

Symptom: Cisco DCNM may include a version of Java JRE that may be vulnerable to published vulnerabilities. The vulnerability is not confirmed to be exploitable on Cisco DCNM, however Cisco is improving DCNM product security by upgrading Java to the latest available version. Additional information about the specific vulnerabilities listed above including condition and possible workarounds can be found at: http://www.oracle.com/technetwork/topics/security/alerts-086861.html.

Workaround: To work around this issue, upgrade to Java version 1.6.0.29

CSCts93988

Symptom: The Cisco DCNM-LAN interface shows the Rate Mode as dedicated in the switch when it is configured as shared.

Conditions: The symptom might be because of the force keyword in the rate mode dedicated command.

Workaround: Use Cisco NX-OS Release 5.2(2) or a later version which includes a fix for this issue.

CSCtw53685

Symptom: When a user launches DCNM LAN client, the following popup message is displayed:

JRE 1.6.0_21 version is recommended for DCNM-LAN client. Found JRE 1.6.0_29 installed. Do you want to continue with existing JRE?JRE 1.6.0_29 is recommended for DCNM and the above redundant message will be removed from further releases.

Conditions: This symptom might be seen when you install JRE 1.6.0_29 on your system.

Workaround: You must click OK to continue with the installation.

CSCtx02174

Symptom: You cannot terminate the Cisco DCNM Client either by closing the application interface or by using the exit menu.

Conditions: The symptom might be seen when you try to manually exit the application due to some exception.

Workaround: To work around this issue, do the following depending upon the operating system that you use:

If you are running Cisco DCNM Client on windows, terminate the Cisco DCNM Client process using the Windows task manager.

If you are running Cisco DCNM Client on Linux, use the kill command to terminate the application.

CSCtx05218

Symptom: The Cisco DCNM fails to display STP enabled VLAN information in the topology.

Conditions: The symptom might be seen when you discover the devices in the client interface.

Workaround: There is no workaround.

Resolved Caveats—Cisco DCNM-LAN Release 5.2(1)

CSCti03031

Symptom: Cisco DCNM does not display the ports that are part of the unallocated pool so you cannot assign ports to VDCs.

Conditions: This problem occurs when you delete a VDC. The ports from the deleted VDC are moved to the unallocated pool.

Workaround(s): You need to allocate the ports from the unallocated pool. Cisco DCNM recognizes the added ports from the syslog information generated by the switch.

CSCtj00827

Symptom: When you try to enable the FabricPath feature, Cisco DCNM displays an error message.

Conditions: This problem occurs when you try to enable the FabricPath feature without using the install feature-set fabricpath command.

Workaround(s): Use the install feature-set fabricpath command before enabling the feature set.

CSCtj27762

Symptom: After you create an HSRP IPv6 group, it disappears when you create a usecase in the GUI.

Conditions: The created HSRP IPv6 group disappears from the HSRP GUI although the creation command is successful on the device.

Workaround: Refresh the screen to bring back the created group.

CSCtj83947

Symptom: In a sequential delivery with the "Rollback on all selected devices in case of any failure in any device" option, Cisco DCNM still delivers the configuration for remaining devices even if the first device delivery has failed. Cisco DCNM should stop delivering configurations for other devices when a device delivery fails.

Conditions: The first device delivery has failed.

Workaround: None.

CSCtj88281

Symptom: Unable to complete the Fabric Manager installation on LINUX RHEL 5.0 from the DB option screen.

Conditions: This problem occurs when Cisco DCNM Release 5.1(1) is installed with the install Postgres option before you install Fabric Manager Release 5.0(4a). The Postgres version installed with Cisco DCNM Release 5.1(1) is not supported by Fabric Manager.

Workaround: If you are using Linux, you must install Fabric Manager Release 5.0(4a) before you install Cisco DCNM Release 5.1(1). When you install the Cisco DCNM client, you must install it when using the Existing Database option.

CSCtl01205

Symptom: The virtual device context (VDC) link connection swapping on the device is not synchronized in the Cisco DCNM topology.

Conditions: After swapping the connection among custom VDCs, new links are updated in the DCNM topology, but old links are also shown as active.

Workaround: Refresh the Cisco DCNM GUI to update the topology.

CSCtl05105

Symptom: The XMLSA process fails in Cisco DCNM discovery for very large configurations during the reply for the spanning tree topology.

Conditions: This problem occurs in very large configurations, such as configurations with over 300 VLANs and 12000 ports. The following message appears:

%XMLMA-xx-XMLMACRIT: XML master agent: XML subagent session xxx terminated, may be 
crashed or killed.  
 
   

This message by itself is not sufficient to determine this problem—it occurs in a spanning tree configuration. This problem does not affect the system operation; it affects only Cisco DCNM discovery.

Workaround: Use Cisco NX-OS Release 5.1(3) or a later version which includes a fix for this issue.

CSCto75667

Symptom: The DHCP log level is set to 6 when Cisco NX-OS software is upgraded to Release 5.1(3).

Conditions: Starting with Cisco DCNM Release 5.1(2), the DHCP log level is set to severity 5 instead of severity 6. If you upgrade to NX-OS Release 5.1(3) or a later version, Cisco DCNM sets the log level to severity 6 during rediscovery. This issue is seen only if the switch is upgraded to NX-OS Release 5.1(3) or a later version.

Workaround: To work around this issue:

1. Stop the Cisco DCNM server.

2. Go to the "<DCNM root folder>\jboss-4.2.2.GA\server\dcnm\conf" directory.

For example:

On Windows: C:\Program Files\Cisco Systems\dcm\jboss-4.2.2.GA\server\dcnm\conf

On Linux: /usr/local/cisco/dcm/jboss-4.2.2.GA/server/dcnm/conf ]

3. Open device-logginglevel.properties, remove the "#" symbol before "cisco.dcbu.dcm.logginglevel.dc3.dhcp=5" and save the file.

4. Open jboss-service.xml, uncomment the following tag by removing the highlighted text, and save the file.

Original file snippet:

<!--

<attribute name="URLList">

./conf/device-logginglevel.properties

</attribute>

-->

File snippet after changes:

<attribute name="URLList">

./conf/device-logginglevel.properties

</attribute>

5. Start the Cisco DCNM server.

6. Navigate to Feature selector -> DCNM Server Administration -> Device and Credentials.

7. Select the device which has the log level issue, right click the context menu, and select the rediscover option.

Now the newly managed device from Cisco DCNM correctly sets the log level as 5 during the discovery.

CSCts60248

Symptom: The link between two devices is not seen in the DCNM topology.

Conditions: This symptom might be seen when the following conditions are true:

Either of the devices are configured with the same domain name.

Both the devices configured with the same domain name.

Workaround:

If you configure both the device with the same domain name, there is no workaround.

If you configure one of the devices with the same domain name, then you can discover the device without domain name first and discover with the domain name later.

CSCtt97442

Symptom: CPU utilization goes high while using the DCNM-LAN client discovery screen.

Conditions: This issue may occur if the Cisco DCNM-LAN client is configured with non English locale.

Workaround: To work around this issue:

1. Stop the Cisco DCNM-LAN client.

2. From the Control Panel choose Region and Language.

3. In the Administration tab, click Change system locale and then select English (United States).

4. Start the Cisco DCNM-LAN client.

Resolved Caveats—Cisco DCNM-SAN Release 5.2(1)

CSCsz04599

Symptom: It should be possible to suspend an SNMP trap destination, but keep the destination in the IP configuration.

Workaround: This enhancement request is resolved.

CSCtd53604

Symptom: Flows are needed for custom host group reporting.

Workaround: This enhancement request is resolved.

CSCtf03534

Symptom: Polling interval changes cannot be saved under the Device Manager summary tab.

Workaround: This enhancement request is resolved.

CSCtf22898

Symptom: You cannot use Device Manager to transfer files from the switch to the server.

Conditions: This symptom might be seen when you choose Admin > Flash Files > Copy Files > Switch to Server, and there is no filename in the Server File or the Switch File Field.

If you click (...), a list of files on the server (and not on the switch) is displayed.

If you type the filename in the Server File field and do not type the filename in the Switch File field, the transfer indicates that it is successful, but instead a file is created on the sever with the filename entered in the Server File field but it has a length of 0 bytes.

Workaround: This issue is resolved.

CSCtf87579

Symptom: PortChannel members should be shown in pairs in the tool tip.

Workaround: This enhancement request is resolved.

SCSCth22350

Symptom: Users should be able to set and save a different topology map layout in Cisco Fabric Manager Server.

Workaround: This enhancement request is resolved.

CSCth24101

Symptom: The message that displays when a user exits Device Manager and there is a pending CFS lock should be enhanced to show the CFS application that has pending changes, the user that obtained the lock, and the time the lock was obtained.

Workaround: This enhancement request is resolved.

CSCth49735

Symptom: The version of PostgreSQL in Cisco Fabric Manager is 8.2.3.

Conditions: This caveat addresses the need to upgrade the version of PostgreSQL that is bundled with Cisco Fabric Manager.

Workaround: This issue is resolved.

CSCti06223

Symptom: Custom SAN health reports cannot be generated in CSV format.

Conditions: This symptom might be seen after you create custom templates to generate reports on SAN health.

Workaround: This issue is resolved.

CSCtj03976

Symptom: Xiotech storage devices appear as hosts in Cisco Fabric Manager.

Conditions: This symptom might be seen because Xiotech storage devices have an OUI of 00:1F:93 and they are not registering FC4 feature types.

Workaround: This issue is resolved.

CSCtj19501

Symptom: A password that is copied and pasted from the Cisco Fabric Manager control panel appears as clear text.

Conditions: This symptom might be seen when you copy and paste a password from the Cisco Fabric Manager control panel.

Workaround: This issue is resolved.

CSCtj66117

Symptom: The Performance Manager GUI shows more entries than the Print or Export screens.

Conditions: This symptom might be seen when you try to export a report to CSV format. The Performance Manager exports fewer devices to CSV than are displayed in the Web User Interface.

Workaround: This issue is resolved.

CSCtj87495

Symptom: The following out-of range statistics are sent in the alert e-mail:

Time: Thu Oct 14 07:21:23 EDT 2010

Source: FABRIC_1

Severity: Critical

Description: WC1100_L5-12C > 668.822M Tx bytes/sec

This description does not match with the speed of the interface.

Conditions: This symptom might be seen when threshold alerts are turned on in Fabric Manager Server and in the Performance Manager.

Workaround: This issue is resolved.

CSCtj69380

Symptom: Cisco Fabric Manager Server sets the interval for report generation to 24 hours, but should allow the user to select other intervals.

Workaround: This enhancement request is resolved.

CSCtk09225

Symptom: The formatting of header rows in CSV reports needs to be aligned.

Workaround: This enhancement request is resolved.

CSCtk13722

Symptom: Users should be able to add new switch OUIs and have Cisco Fabric Manager discover them.

Workaround: This enhancement request is resolved.

CSCtk19187

Symptom: When you use the Cisco Fabric Manager web client to generate custom template reports, an e-mail report is not generated.

Conditions: This symptom might be seen when there is spacing in the custom template name, such as "admin.test user."

Workaround: This issue is resolved.

CSCtk36665

Symptom: A generic "traffic disruption" error message displays when your select a supervisor module and choose Module->Config->Reset.

Conditions: This message displays for the MDS 9500 Series switches, but it only applies to single supervisor switches.

Workaround: This issue is resolved.

CSCtk58587

Symptom: The switch interface is not shown for IVR zone members in the fabric in the IVR Local Full Zone display.

Conditions: This symptom might be seen under normal operating conditions for Cisco Fabric Manager.

Workaround: This issue is resolved.

CSCtl59054

Symptom: In the second step of the FCIP Wizard, the Enforce IPSEC Security checkbooks is not shown if the selected ports belong to the SSN-16 module (DS-X9316-SSNK9). Workaround

Conditions: This symptom might be seen when an FCIP interface is created for SSN-16 ports.

Workaround: This issue is resolved.

CSCtl76814

Symptom: FC aliases that are renamed may show old values in the zone set or zone creation window, even after manual rediscovery of the fabric or a forced refresh of the active window in Cisco Fabric Manager. The latest value can be shown in the current session, but it reverts to the old values when the Fabric Manager GUI next opens.

Conditions: This symptom might be seen when an FC alias is renamed in enhanced zoning mode.

Workaround: This issue is resolved.

CSCtl81737

Symptom: The Cisco Fabric Manager Server cannot send a SNMPv2c trap. Because of this, the SNMPv2c traps that an MDS 9000 Family switch sends to Cisco Fabric Manager Server are translated to SNMPv1 traps, which leads to errors on SNMP servers that set the version of SNMP to v2c.

Workaround: This enhancement request is resolved.

CSCtn66212

Symptom: When using the Webinspector to check a 404 error, the resulting page has server information.

Conditions: This symptom might be seen when the Webinspector is used.

Workaround: This issue is resolved.

CSCto02287

Symptom: Cisco Fabric Manager opens switches sequentially, but as of Cisco DCNM-SAN Release 5.2(x), multiple switches within a fabric can be opened at the same time (multiple threads).

Workaround: This enhancement request is resolved.

CSCto05481

Symptom: A Performance Manager report cannot be saved.

Conditions: This symptom might be seen when Oracle 11g Enterprise Edition is used.

Workaround: This issue is resolved.

CSCto08507

Symptom: The ISL link between an MDS 9134 switch and an MDS 9513 switch does not appear in Cisco Fabric Manager. The issue is cosmetic because connectivity between the target and initiator exists.

Conditions: This symptom was seen when the MDS switches had NPV configured and Cisco Fabric Manager Release 5.0(4b) was running.

Workaround: This issue is resolved.

CSCto12553

Symptom: The Cisco Fabric Manage client freezes when a user edits the device alias settings. The following errors are displayed:

ERROR [JDBCExceptionReporter] No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))

ERROR [fms.event] EventForward receive JMS Exception

org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)

at org.jboss.mq.Connection$PingTask.run(Connection.java:1313)

at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)

at java.lang.Thread.run(Unknown Source)

Caused by: java.io.IOException: ping timeout.

... 3 more

ERROR [fms.event] can not send message:Cannot send a message to the JMS server; - nested throwable: (java.net.SocketTimeoutException: Read timed out)

Conditions: This symptom might be seen following an upgrade to Cisco Fabric Release 5.0(4). A large number of sessions may contribute to this failure.

Workaround: This issue is resolved.

CSCto56347

Symptom: Following a successful software grade from a release with a patch, the Cisco Fabric Manager GUI client was getting stuck when trying to open fabrics.

Conditions: This symptom was seen because there was no mechanism in place to clean up the patch after the upgrade.

Workaround: This issue is resolved.

CSCto83540

Symptom: A meaningful error message is needed when Cisco Fabric Manager client attempts to open Cisco Fabric Manager Server and the versions are incompatible.

Workaround: This enhancement request is resolved.

CSCtq14099

Symptom: When you add a new VSAN using Cisco Fabric Manager, the Logical Domains window does not get updated with the new VSAN information. Refreshing does not help and it takes about 15 minutes for the window to update.

Conditions: This symptom might be seen when you use Cisco Fabric Manager to add a new VSAN.

Workaround: This issue is resolved.

CSCtr36327

Symptom: Cisco DCNM-SAN web client reports are visible to all users, even if the option to make them viewable based username is selected.

Conditions: This symptom might be seen when the web client login user's role is network-admin.

Workaround: This issue is resolved.

CSCtr71379

Symptom: When you install Cisco DCNM on a Linux machine you receive the following message:

"Graphical installers are not supported by the vm..."
Attempts to continue with the installation in Console mode fail with the following 
error because the DCNM installer does not support Console mode install:
"Installer User Interface Mode Not Supported...".
 
   

Conditions: This symptom might be seen under the following conditions:

The $DISPLAY environment variable is not properly set.

The necessary X Windows libraries for running the GUI installer are not available.

Workaround: To work around this issue, do one of the following:

Set the $DISPLAY environment variable to a valid value.

Ensure that the following X Windows libraries are installed on the system:

libXt-1.0.2-3.2.el5

libXpm-3.5.5-3

libXdmcp-1.0.1-2.1

libXau-1.0.1-3.1

libXext-1.0.1-2.1

libXrender-0.9.1-3.1

libXaw-1.0.2-8.1

libXau-1.0.1-3.1

libX11-1.0.3-11.el5

libXt-1.0.2-3.2.el5

libXmu-1.0.2-5

libXp-1.0.0-8.1.el5

libXi-1.0.1-4.el5_4

libXtst-1.0.1-3.1

libXft-2.1.10-1.1

libXp-1.0.0-8.1.el5

libXrender-0.9.1-3.1

Documentation Corrections

There are several differences in the Cisco DCNM online help and the product documentation that appears on Cisco.com:

Information on "Installing a Cisco DCNM License on a Cisco Nexus 1010 Switch" is not available in the online help. Refer to the Cisco DCNM Installation and Licensing Guide, Release 5.x for information.

References to Cisco DCNM-SAN Server Federation Deployment Guide are present in the online help. These references are changed to Cisco Fabric Manager Server Federation Deployment Guide in the guide available on Cisco.com.

The upgrade procedure for "Upgrading a Primary Cisco DCNM-LAN Server" is not up-to-date in the online help. Refer to the Cisco DCNM Installation and Licensing Guide, Release 5.x for the latest information.

Related Documentation

This 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 7000 Series Switch Documentation

Catalyst 6500 Series Switch Documentation

Cisco DCNM Documentation

The 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 set for Cisco DCNM includes the following documents:

Release Notes

Cisco DCNM Release Notes, Release 5.x

Compatibility Information

Cisco DCNM Software Compatibility Matrix, Release 5.x

Installation and Licensing

Cisco DCNM Installation and Licensing Guide, Release 5.x

Cisco DCNM Fundamentals Guide

Cisco DCNM Fundamentals Guide, Release 5.x

Cisco DCNM for LAN Configuration Guides

FabricPath Configuration Guide, Cisco DCNM for LAN, Release 5.x

Cisco DCNM Interfaces Configuration Guide, Release 5.x

Cisco DCNM Layer 2 Switching Configuration Guide, Release 5.x

Cisco DCNM Security Configuration Guide, Release 5.x

Cisco DCNM System Management Configuration Guide, Release 5.x

Cisco DCNM Unicast Routing Configuration Guide, Release 5.x

Cisco DCNM Virtual Device Context Configuration Guide, Release 5.x

Cisco DCNM Getting Started with Virtual Device Contexts, Release 5.x

Cisco DCNM Web Services API Guide, Release 5.x

Cisco DCNM for SAN Configuration Guides

System Management Configuration Guide, Cisco DCNM for SAN, Release 5.x

Interfaces Configuration Guide, Cisco DCNM for SAN, Release 5.x

Fabric Configuration Guide, Cisco DCNM for SAN, Release 5.x

Quality of Service Configuration Guide, Cisco DCNM for SAN, Release 5.x

Security Configuration Guide, Cisco DCNM for SAN, Release 5.x

IP Services Configuration Guide, Cisco DCNM for SAN, Release 5.x

Intelligent Storage Services Configuration Guide, Cisco DCNM for SAN, Release 5.x

High Availability and Redundancy Configuration Guide, Cisco DCNM for SAN, Release 5.x

Inter-VSAN Routing Configuration Guide, Cisco DCNM for SAN, Release 5.x

SMI-S and Web Services Programming Guide, Cisco DCNM for SAN, Release 5.x

Cisco Nexus 1000V Series Switch Documentation

The Cisco Nexus 1000V Series switch documentation is available at the following URL:

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

Cisco Nexus 2000 Series Fabric Extender Documentation

The Cisco Nexus 2000 Series Fabric Extender documentation is available at the following URL:

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

Cisco Nexus 3000 Series Switch Documentation

The Cisco Nexus 3000 Series switch documentation is available at the following URL:

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

Cisco Nexus 4000 Series Switch Documentation

The Cisco Nexus 4000 Series switch documentation is available at the following URL:

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

Cisco Nexus 5000 Series Switch Documentation

The Cisco Nexus 5000 Series switch documentation is available at the following URL:

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

Cisco Nexus 7000 Series Switch Documentation

The Cisco Nexus 7000 Series switch documentation is available at the following URL:

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

Catalyst 6500 Series Switch Documentation

The Catalyst 6500 Series documentation is available at the following URL:

http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html

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.