Guest

Cisco Prime Data Center Network Manager

Cisco DCNM Release Notes, Release 5.1

  • Viewing Options

  • PDF (400.6 KB)
  • Feedback
Cisco DCNM Release Notes, Release 5.1

Table Of Contents

Cisco DCNM Release Notes, Release 5.1

Contents

Introduction

System Requirements

Java Requirements

Server System Requirements

Client System Requirements

Supported Cisco Platforms and Software Versions

Hardware Supported

New and Changed Information for Cisco DCNM Enhancements (Support for All Cisco Nexus Series)

DHCP Log Levels

VSAN Overlays

Infrastructure Enhancements

Cisco DCNM Configuration Templates

Install Management Tool

Support for Copying the Running Configuration to Startup

Infrastructure Enhancements in Cisco DCNM Release 5.1(3u)

Trial License and Enhanced Licensing Screen

Configuration Template Changes

Support for Java JRE 1.6

Support for Windows 7 and Windows 2008

New and Changed Information for Supporting Cisco Nexus 1000V Series Switches

New Software Features for Cisco Nexus 1000V Series Switches in Cisco DCNM Release 5.1(3u)

DHCP Snooping

New and Changed Information for Supporting Cisco Nexus 4000 Series Switches

New Software Features for Cisco Nexus 4000 Series Switches in Cisco DCNM Release 5.1(1)

Blade Server Discovery

New and Changed Information for Supporting Cisco Nexus 5000 Series Switches

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

Flexible Ports

Layer 3 Interfaces

LACP Fast Timers

Port Profiles

DHCP Snooping

Configuration Rollback

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New Database Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

Support for the new Cisco Nexus 2000 Series FEXs

HIF Port Channels

Error Disabled Detection and Recovery

Discovery of Servers Connected by CNA to Cisco Nexus 5000 Series Switches

Limitations for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New and Changed Information for Supporting Cisco Nexus 7000 Series Switches

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(3u)

FabricPath VLAN Mode Change

Limitations for the Cisco Nexus 7000 Series Switches in Release 5.1(3u)

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(2)

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

FabricPath

FabricPath IS-IS Protocol

Support for the 32-Port 1- and 10-Gigabit Ethernet I/O Module

Default Interface

SVI Auto-State Exclude

Private VLAN Trunks

Fabric Extender

vPC Enhancements

Object Tracking Manager Enhancements

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(1)

Installation Notes

Caveats

Open Caveats—Cisco DCNM Release 5.1

Open Caveats—Cisco DCNM Release 5.0

Open Caveats—Cisco DCNM Release 4.2

Resolved Caveats—Cisco DCNM Release 5.1(2)

Resolved Caveats—Cisco DCNM Release 5.1(1)

Related Documentation

Platform-Specific Release Notes

Cisco DCNM Documentation

Obtaining Documentation and Submitting a Service Request


Cisco DCNM Release Notes, Release 5.1


Release Date: April 1, 2011

Part Number: OL-23744-01 C3

This document provides the release notes for Cisco Data Center Network Manager (DCNM), Release 5.1. 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-23744-01

A0

November 9, 2010

Created release notes for Release 5.1(1).

A1

November 10, 2010

Updated the FEX models that work with the Cisco Nexus 5000 Series switches.

A2

November 19, 2010

Included 32-port 10-Gigabit Ethernet I/O module with XL option.

B0

December 21, 2010

Updated for Release 5.1(2).

B1

January 6, 2011

Included caveat CSCtk12405.

C0

April 1, 2011

Updated for Release 5.1(3u).

C1

April 8, 2011

Corrected the Windows 7 and Windows 2008 information in these sections:

"Server System Requirements"

"Client System Requirements"

"Support for Windows 7 and Windows 2008"

Added Open Caveat CSCto59733 to the "Open Caveats—Cisco DCNM Release 5.1" section.

C2

April 11, 2011

Moved CSCth80524 to the "Resolved Caveats—Cisco DCNM Release 5.1(2)" section.

Moved CSCth90196 and CSCth90216 to the"Resolved Caveats—Cisco DCNM Release 5.1(1)" section.

Updated the workaround for CSCtl05105.

C3

April 19, 2011

Corrected the "Client System Requirements" to list JRE 1.6.

Removed Cisco Nexus 5000 NX-OS Release 5.0(3)N1(1) and Release 5.0(3)N1(1a) from "Supported Cisco Platforms and Software Versions" and added Release5.0(3)N1(1b).

Changed Java JDK 1.6 to Java JRE 1.6 in "Infrastructure Enhancements in Cisco DCNM Release 5.1(3u)".

Added Caveat CSCto75667 to the "Open Caveats—Cisco DCNM Release 5.1" section.


Contents

This document includes the following sections:

Introduction

System Requirements

New and Changed Information for Supporting Cisco Nexus 7000 Series Switches

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(1)

Installation Notes

Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

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

Cisco NX-OS supports the Cisco Nexus product family, including the Cisco Nexus 7000 Series, Cisco Nexus 5000 Series, Cisco Nexus 4000 Series, Cisco Nexus 2000 Fabric Extension, and Cisco Nexus 1000V Series. For the most recent information on Cisco NX-OS, refer to the following website:

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

System Requirements

This section includes the following topics:

Java Requirements

Server System Requirements

Client System Requirements

Supported Cisco Platforms and Software Versions

Hardware Supported

Java Requirements

Cisco DCNM is a Java-based client-server application. The Cisco DCNM 5.1 server and client support Java JRE 1.6.0_21. The installation process uses Java version 1.6. If your system does not have that version of Java, the installation process will download it to the DCNM_root_directory/java/jre1.6 directory.


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


Server System Requirements

Cisco DCNM Release 5.1(x) supports running the Cisco DCNM server on these operating systems:

Microsoft Windows 2008 is supported in Cisco DCNM Release 5.1(3u)

Microsoft Windows Server 2003 Enterprise Edition, Service Pack 1 and Service Pack 2 (32-bit, 64-bit).

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


Note For the 64-bit Linux version, the PostgreSQL database that comes with the Cisco DCNM installation might not work. If you encounter that problem, you can separately install a PostgreSQL version that supports a 64-bit Linux operating system.


VMware ESX 4.0.


Note You must use the static MAC address option for a virtual machine (VM). To find information about how to configure a static MAC address, search the VMware Knowledge Base at the following URL: http://kb.vmware.com/selfservice/microsites/microsite.do


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


If Cisco DCNM coexists with Cisco Fabric Manager 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.

A Perl environment must already be installed on the server system. 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.

No other programs are running on the server except for Cisco Fabric Manager Release 5.0(4a) or later releases and the database software used by Fabric Manager.

If you plan to use an Oracle 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 1000 from the default of 50.

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

Increase the number of sessions and processes to 150 each from the default of 50.

Increase the number of open cursors to 1000 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 Release 5.0 and later releases support running the Cisco DCNM client on Microsoft Windows XP Professional Service Pack 2 or Microsoft Windows XP Professional Service Pack 3 and Firefox browser version 3.0 on Red Hat Enterprise Linux AS Release 5.4 (32-bit and 64-bit versions).

Cisco DCNM Release 5.1(3u) and later releases support running the Cisco DCNM client on Microsoft Windows 7.

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

Network Interface Card

1 port at 1 Gbps


If Cisco DCNM coexists with Fabric Manager 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 are installing both Fabric Manager and Cisco DCNM on the same Linux system, be sure to install Fabric Manager before installing Cisco DCNM


This installation process for Cisco DCNM Release 5.1(3u) uses Java version 1.6. If your system does not have that version of Java, the installation process will download it to your system. Earlier versions of Cisco DCNM use Java version 1.5.

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.

Supported Cisco Platforms and Software Versions

Cisco DCNM is compatible with the platforms and software versions listed in Table 5.

Table 5 Cisco DCNM and Cisco Nexus Platform/NX-OS Compatibility 

DCNM Version
Platform
NX-OS Version

4.1(2)

Cisco Nexus 7000

4.1(2), 4.0(4), 4.0(3), 4.0(2)

4.1(3)

Cisco Nexus 7000

4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

4.2(1)

Cisco Nexus 7000

4.2(2a), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

4.1(3)N1(1)

4.2(3)

Cisco Nexus 7000

4.2(4), 4.2(2a), 4.2(3), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

4.1(3)N2(1), 4.1(3)N1(1a), 4.1(3)N1(1)

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

5.0(2)

Cisco Nexus 7000

5.0(2a), 4.2(4), 4.2(2a), 4.2(3), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

4.1(3)N2(1a), 4.1(3)N1(1.1E), 4.1(3)N2(1), 4.1(3)N1(1a), 4.1(3)N1(1)

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

Cisco Nexus 1000V

4.0(4)SV1(3)

MDS 9000

3.3 and higher

5.0(3)

Cisco Nexus 7000

5.0(3), 5.0(2a), 4.2(4), 4.2(2a), 4.2(3), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

4.1(3)N2(1a), 4.1(3)N1(1.1E), 4.1(3)N2(1), 4.1(3)N1(1a), 4.1(3)N1(1)

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

Cisco Nexus 1000V

4.0(4)SV1(3)

MDS 9000

3.3 and higher

5.1(1)

Cisco Nexus 7000

5.1(1), 5.1(1a), 5.0(3), 5.0(2a), 4.2(6), 4.2(5), 4.2(4), 4.2(3), 4.2(2a), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

5.0(2)N1(1)1 , 4.2(1)N2(1a), 4.2(1)N2(1b), 4.2(1)N2(1), 4.2(1)N1(1), 4.1(3)N2(1a), 4.1(3)N2(1),4.1(3)N1(1.1E), 4.1(3)N1(1a), 4.1(3)N1(1)

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

Cisco Nexus 1000V

4.0(4)SV1(3b), 4.0(4)SV1(3a), 4.0(4)SV1(3)

Cisco Nexus 1010

4.0(4)SP1(1)

MDS 9000

3.3 and higher

5.1(2)

Cisco Nexus 7000

5.1(2), 5.1(1), 5.1(1a), 5.0(3), 5.0(2a), 4.2(6), 4.2(5), 4.2(4), 4.2(3), 4.2(2a), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

Cisco Nexus 5000 and Cisco Nexus 2000

5.0(2)N1(1)1, 4.2(1)N2(1a), 4.2(1)N2(1b), 4.2(1)N2(1), 4.2(1)N1(1), 4.1(3)N2(1a), 4.1(3)N2(1),4.1(3)N1(1.1E), 4.1(3)N1(1a), 4.1(3)N1(1)

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

Cisco Nexus 1000V

4.0(4)SV1(3b), 4.0(4)SV1(3a), 4.0(4)SV1(3)

Cisco Nexus 1010

4.0(4)SP1(1)

MDS 9000

3.3 and higher

5.1(3u)

Cisco Nexus 7000

5.1(3), 5.1(2), 5.1(1), 5.0(3), 5.0(2a), 4.2(6), 4.2(5), 4.2(4), 4.2(3), 4.2(2a), 4.1(5), 4.1(4), 4.1(3), 4.1(2), 4.0(4), 4.0(3), 4.0(2)

 

Cisco Nexus 5000 and Cisco Nexus 2000

5.0(3)N1(1b), 5.0(2)N2(1), 5.0(2)N1(1)1, 4.2(1)N2(1a), 4.2(1)N2(1), 4.2(1)N1(1), 4.1(3)N2(1a), 4.1(3)N2(1), 4.1(3)N1(1.1E), 4.1(3)N1(1a), 4.1(3)N1(1)

 

Cisco Nexus 4000 (IBM)

4.1(2)E1(1)

 

Cisco Nexus 1000V

4.2(1)SV1(4), 4.0(4)SV1(3b), 4.0(4)SV1(3a), 4.0(4)SV1(3)

 

Cisco Nexus 1010

4.2(1)SP1(2), 4.0(4)SP1(1)

 

MDS 9000

3.3 and higher

1 Cisco DCNM Release 5.1(1) cannot manage the Cisco Nexus 5548 switch, but it can manage other Cisco Nexus 5000 Series switches that are running Cisco NX-OS Release 5.0(2)N1(1) as long as the new features of the Cisco NX-OS release are not configured on the switch. If they are configured on the switch, then the Cisco DCNM information for the switch will be inconsistent.


Hardware Supported

Table 6 lists the products and components that Cisco DCNM Release 5.1 supports.

Table 6 Hardware Features Supported by Cisco DCNM Release 5.1 

Product/Component
Part Number

Cisco Nexus 7000 Series Switch

Cisco Nexus 7010 chassis

N7K-C7010

Cisco Nexus 7018 chassis

N7K-C7018

Supervisor module

N7K-SUP1

Fabric module, Cisco Nexus 7010 chassis

N7K-C7010-FAB-1

Fabric module, Cisco Nexus 7018 chassis

N7K-C7018-FAB-1

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

System fan tray, Cisco Nexus 7010 chassis

N7K-C7010-FAN-S

Fabric fan tray, Cisco Nexus 7010 chassis

N7K-C7010-FAN-F

Fan tray, Cisco Nexus 7018 chassis

N7K-C7018-FAN

6-kW AC power supply unit

N7K-AC-6.0KW

7.5-kW AC power supply unit
International version
US version


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

6-kW DC power supply unit

N7K-DC-6.0KW

Cisco Nexus 5000 Series Switch

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 module, Cisco Nexus 5548

N55-D160L3

DC Power Supply, Cisco Nexus 5548

N55-PDC-750W

Back-to-Front Fan, Cisco Nexus 5596

N5596UP-FAN-B

Back-to-Front Fan, Cisco Nexus 5548

N5548P-FAN-B

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=

Fan module, Cisco Nexus 5010

N5K-C5010-FAN=

Fan module, Cisco Nexus 5020

N5K-C5020-FAN=

550 W AC Power Supply Module, Cisco Nexus 5010

N5K-PAC-550W(=)

1200 W AC Power Supply Module, Cisco Nexus 5020

N5K-PAC-1200W(=)

Cisco Nexus 4000 Series Switch

Cisco Nexus 4001I Switch Module

N4K-4001I-XPX

Cisco Nexus 4005I Switch Module

N4K-4005I-XPX

Cisco Nexus 2000 Series Fabric Extenders

 

Cisco Nexus 2148 1 GE Fabric Extender

N2K-C2148T-1GE

Cisco Nexus 2148 FEX 1GE Fan Module

N2K-C2148T-FAN=

Cisco Nexus 2000 FEX 200 W AC Power Supply

N2K-PAC-200W(=)

Cisco Nexus 2224TP Fabric Extender

N2K-C2224TP-1GE

Cisco Nexus 2232PP 10 GE Fabric Extender

N2K-C2232PP-10GE

Cisco Nexus 2232PP Fan Module

N2K-C2232-FAN=

Cisco Nexus 2000 FEX 400 W AC Power Supply

N2K-PAC-400W=

Cisco Nexus 2248TP 1 GE Fabric Extender

N2K-C2248TP-1GE

Cisco Nexus 2248TP Fan Module

N2K-C2248-FAN=

Cisco Nexus 2000 FEX 400 W AC Power Supply

N2K-PAC-400W=

Cisco Nexus 2200 DC Power Supply

 

Cisco Nexus 2200 DC Back-to-Front Fan

 

Cisco Nexus 1000V Series Switch

 

Cisco Nexus 1010 Virtual Services Appliance


New and Changed Information for Cisco DCNM Enhancements (Support for All Cisco Nexus Series)

This section includes the following topics:

DHCP Log Levels

VSAN Overlays

Infrastructure Enhancements

Infrastructure Enhancements in Cisco DCNM Release 5.1(3u)

DHCP Log Levels

Cisco DCNM Release 5.1(2) supports Dynamic Host Configuration Protocol (DHCP) logging levels at severity 5. Earlier DCNM releases required that DHCP log levels be defined as severity 6.

VSAN Overlays

Beginning with Release 5.1(1), Cisco DCNM displays forwarding and nonforwarding links between Cisco Nexus devices in VLAN networks.

Infrastructure Enhancements

This section includes the following sections:

Cisco DCNM Configuration Templates

Install Management Tool

Support for Copying the Running Configuration to Startup

Cisco DCNM Configuration Templates

Beginning with Cisco DCNM Release 5.1(1), you can use the configuration delivery templates feature to configure many complex features in Cisco DCNM using various predefined templates. You can also create custom templates depending on your specific requirements. The predefined and custom templates can be created using template scripts that are defined by Cisco DCNM. With the configuration delivery templates feature, you can configure and deploy multiple devices at a time.

Install Management Tool

Beginning with Release 5.1(1), Cisco DCNM uses the Install Management Tool, which installs, upgrades, installs licenses, starts, and stops the DCNM server on remote servers.

Support for Copying the Running Configuration to Startup

Beginning with Release 5.1(1), Cisco DCNM can copy the running configuration to the startup configuration for the devices that you specify and the devices in their topologies. You can also use Cisco DCNM to copy the running configuration to a file on the bootflash directory.

Infrastructure Enhancements in Cisco DCNM Release 5.1(3u)

This section includes the following sections:

Trial License and Enhanced Licensing Screen

Configuration Template Changes

Support for Java JRE 1.6

Support for Windows 7 and Windows 2008

Trial License and Enhanced Licensing Screen

Cisco DCNM Release 5.1(3u) adds support for a trial license. In addition, the licensing screen has been enhanced to show more details.

Configuration Template Changes

The Configuration Change Management feature is changed to the Configure Delivery Management feature. The naming convention for various flows has also been changed to be more intuitive.

Support for Java JRE 1.6

Cisco DCNM Release 5.1(3u) supports JRE Version 1.6.0.21.

Support for Windows 7 and Windows 2008

In Cisco DCNM Release 5.1(3u), the Cisco DCNM server supports Windows 2008 and the Cisco DCNM client support Windows 7.

New and Changed Information for Supporting Cisco Nexus 1000V Series Switches

This section includes the following topics:

New Software Features for Cisco Nexus 1000V Series Switches in Cisco DCNM Release 5.1(3u)

New Software Features for Cisco Nexus 1000V Series Switches in Cisco DCNM Release 5.1(3u)

This section includes the following topics:

DHCP Snooping

DHCP Snooping

Cisco DCNM Release 5.1(3u) provides support for the DHCP snooping feature on Cisco Nexus 1000V Series switches.

New and Changed Information for Supporting Cisco Nexus 4000 Series Switches

This section includes the following topics:

New Software Features for Cisco Nexus 4000 Series Switches in Cisco DCNM Release 5.1(1)

New Software Features for Cisco Nexus 4000 Series Switches in Cisco DCNM Release 5.1(1)

This section includes the following topics:

Blade Server Discovery

Blade Server Discovery

Cisco DCNM Release 5.1(1) can discover the blade servers connected to Cisco Nexus 4000 switches in the FCoE topology.

New and Changed Information for Supporting Cisco Nexus 5000 Series Switches

This section includes the following topics:

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New Database Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

Limitations for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

Cisco DCNM Release 5.1(3u) supports the following new Cisco Nexus 5000 Series switches:

Cisco Nexus 5596UP Switch—A 2 RU 10-Gigabit Ethernet, Fibre Channel, and FCoE switch that offers up to 1920 Gbps of throughput.

Cisco Nexus 5548UP Switch—A 1 RU 1- or 10-Gigabit Ethernet, Fibre Channel, and FCoE switch that offers up to 960-Gbps throughput.

Cisco Nexus 2224TP Fabric Extender (FEX)

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(3u)

This section describes the new Cisco DCNM software features introduced in Cisco DCNM Release 5.1(3u). This section includes the following topics:

Flexible Ports

Layer 3 Interfaces

LACP Fast Timers

Port Profiles

DHCP Snooping

Configuration Rollback

Flexible Ports

Cisco DCNM Release 5.1(3u) provides management capabilities for the flexible ports that are available on the new Cisco Nexus 5596UP switch and the Cisco Nexus 5548UP switch. Flexible ports can be configured in either Ethernet for Fibre Channel mode. A contiguous block of Ethernet ports followed by a contiguous block of Fibre Channel ports can be configured in a size that is also configurable.

Layer 3 Interfaces

Cisco DCNM Release 5.1(3u) provides management support on the Cisco Nexus 5596UP switch and the Cisco Nexus 5548UP switch for the following Layer 3 interfaces:

Layer 3 Ethernet interface

Layer 3 port channel interface

Subinterface

Loopback Interface

Routable switch virtual interface (SVI)

LACP Fast Timers

Cisco DCNM Release 5.1(3u) provides management support for enabling LACP rate mode as FAST in port-channel member ports. In the FAST mode, the peer of a port is requested to send LACP control packets every 1 second.

Port Profiles

Cisco DCNM Release 5.1(3u) provides management support for port profiles.

DHCP Snooping

Cisco DCNM Release 5.1(3u) supports the DHCP snooping feature on Cisco Nexus 5000 Series switches.

Configuration Rollback

Cisco DCNM Release 5.1(3u) supports the configuration rollback feature.

New Hardware Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

Cisco DCNM Release 5.1(1) supports the following new Fabric Extender (FEX) chassis:

Cisco Nexus 2232PP FEX

Cisco Nexus 2248TP FEX

New Database Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

There are no limitations for the Cisco DCNM support for the Cisco Nexus 5000 Series in this release.

New Software Features for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

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

This section includes the following topics:

Support for the new Cisco Nexus 2000 Series FEXs

HIF Port Channels

Error Disabled Detection and Recovery

Discovery of Servers Connected by CNA to Cisco Nexus 5000 Series Switches

Support for the new Cisco Nexus 2000 Series FEXs

Cisco DCNM, Release 5.1(1), supports the Cisco Nexus 2232PP and Cisco Nexus 2248TP FEXs by discovering them in the network and listing them and their device inventory in the Inventory and Topology screens.

HIF Port Channels

Cisco DCNM, Release 5.1(1), allows you to configure HIF port channels for the Cisco Nexus 2232PP and Cisco Nexus 2248TP FEXs.

Error Disabled Detection and Recovery

Cisco DCNM Release 5.1(1) allows you to set the switch to automatically detect the port that is being attacked and move the port to an error-disabled state. It also allows you to set threshold values that the switch can use to automatically recover ports that are in an error-disabled state.

Discovery of Servers Connected by CNA to Cisco Nexus 5000 Series Switches

Cisco DCNM uses LLDP to discover the servers connected by CNA to Cisco Nexus 5000 Series switches, but it does not automatically correlate the servers because CNA does not advertise management IP addresses.

Cisco DCNM Release 5.1(1) can show the CNA adapters by using the Static Server Adapter Mapping feature. You can manually correlate to the group that the CNA adapters belong to a single physical server.

Limitations for Cisco Nexus 5000 Series Switches in Cisco DCNM Release 5.1(1)

The following limitation apply to Cisco DCNM Release 5.1(1) support of the Cisco Nexus 5000 Series switches:

You must use the same types of FEXs when port channeling their interfaces. Cisco DCNM, Release 5.1(1) does not support the use of different FEX types for port channeling.

Cisco DCNM Release 5.1(1) does not support the automatic correlation of servers because the CNAs do not advertise the management IP addresses of servers.

Cisco DCNM Release 5.1(1) does not enable or disable LLDP on the ports of Cisco Nexus 5000 Series switches because LLDP is not a conditional service.

New and Changed Information for Supporting Cisco Nexus 7000 Series Switches

This section includes the following topics:

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(3u)

Limitations for the Cisco Nexus 7000 Series Switches in Release 5.1(3u)

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(2)

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(1)

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(3u)

This section includes the following topics:

FabricPath VLAN Mode Change

FabricPath VLAN Mode Change

The VLAN feature screen in Cisco DCNM Release 5.1(3u) allows you to change the VLAN mode to Classical Ethernet (CE) or FabricPath.

Limitations for the Cisco Nexus 7000 Series Switches in Release 5.1(3u)

This section describes the limitations in Cisco DCNM Release 5.1(3u):

A new screen is available that allows you to manage port-profile configuration for all Cisco Nexus 7000 Series switches and modules. Although this screen is visible, its functionality is not enabled in this release.

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

The Cisco Nexus 7000 Series includes the following new hardware features for Cisco DCNM Release 5.1(2):

32-port 1- and 10-Gigabit Ethernet F1 Series I/O module (N7K-F132XP-15)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

There are no new database features in this release.

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(2)

There are no new software features in this release.

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(2)

This section describes the limitations in Cisco DCNM Release 5.1(2).

For Cisco DCNM Release 5.1(2), the only FEX type supported by the Cisco Nexus 7000 Series switches is the Cisco Nexus 2248TP.

New Hardware Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

The Cisco Nexus 7000 Series includes the following two new hardware features for Cisco DCNM Release 5.1(1):

32-port 10-Gigabit Ethernet M1 Series I/O module with XL option (N7K-M132XP-12L)

Cisco Nexus 2248TP Gigabit Ethernet Fabric Extender (FEX) (N2K-C2248TP-1GE)

New Database Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

There are no new database features in this release.

New Software Features for Cisco Nexus 7000 Series Switches in Release 5.1(1)

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

This section includes the following topics:

FabricPath

FabricPath IS-IS Protocol

Support for the 32-Port 1- and 10-Gigabit Ethernet I/O Module

Default Interface

SVI Auto-State Exclude

Private VLAN Trunks

Fabric Extender

vPC Enhancements

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(1)

FabricPath

You can use Cisco DCNM to configure the Data Center Ethernet mode on the F-series I/O ports, which are capable of handling the FabricPath feature. You can configure this feature on both the system and interface level. When you configure this feature on the system level, the configuration is effective on the I/O port, which is administratively down and does not have interface-specific FabricPath port-mode configurations.

You can perform the following FabricPath configuration functions:

Create a FabricPath topology across multiple Cisco Nexus devices

Assign and modify VLANs to the routing topology mapping

Delete the FabricPath topology

Assign an interface to the FabricPath topology

Remove an interface from the FabricPath topology

Enable users to view the VLAN topology for a given VLAN ID

Enable users to view the FabricPath links in a Layer 2 cloud by highlighting the links with a graphical representation


Note Cisco DCNM Release 5.1(1) does not support multiple FabricPath topologies.


FabricPath IS-IS Protocol

You can use Cisco DCNM to perform the following functions to configure the FabricPath IS-IS protocol:

Enable or disable the IS-IS service in a FabricPath-capable Cisco Nexus device.

View the FabricPath process configuration and interface-level IS-IS configurations.

Reach a node from other switches within the FabricPath topology.

Configure a complete Layer 2 forwarding setup by creating a Layer 2 topology for a range of VLANs and allocating interfaces to that topology.

Specify the basic IS-IS configuration that needs to be done across all of the switches in the same topology.

Assign interfaces to Layer 2 topologies.

Monitor traffic and process statistics.

Display the multi destination graph for each topology.

Display reachability information for a node to all other nodes present in the FabricPath cloud.

Support for the 32-Port 1- and 10-Gigabit Ethernet I/O Module

Cisco DCNM supports the new 32-port 1- and 10-Gigabit Ethernet I/O module as follows:

Discovers switches that have this module.

Lists these modules in the Inventory screen.

Manages the ports on these modules as though they were I/O modules.

Supports online insertion and removal (OIR) of these modules.

Configures and manages all of the support Classic Ethernet parameters on FabricPath ports.

Default Interface

The Cisco DCNM client allows you to reset the default interface parameters for the Ethernet, loopback, VLAN network, and tunnel interfaces. You can set a default interface configuration for up to eight ports at any one time.


Note You cannot use the Cisco DCNM client to clear the explicitly set parameters for the management interfaces because the switch could go to an unreachable state.


SVI Auto-State Exclude

The Cisco DCNM client uses the SVI Auto-State Exclude feature to determine the status of each VLAN interface based on the spanning tree states of the ports in the corresponding VLAN. This feature marks a port so that it is not counted in the SVI bring up and bring down calculations, and it applies to all VLANs that are enabled on that port. You can use the interface and port channel feature screens to configure this parameter.

Private VLAN Trunks

The Cisco DCNM client allows you to configure private VLAN trunks as follows:

Use promiscuous and secondary private VLAN trunk configuration modes.

Create multiple associations between primary and secondary VLANs on a PVLAN secondary trunk.

Map the PVLAN promiscuous trunk port to a primary VLAN and to selected secondary VLANs.

Create a list of allowed VLANs and native VLANs for private VLAN trunks.

Fabric Extender

The Cisco DCNM client provides the following support for Cisco Nexus 2248 FEX feature:

Discovers each FEX connected to a Cisco Nexus 7000 Series chassis and displays its chassis, power supply, and fan tray information.

Allows you to manage each of the FEX ports that connect to servers. You can manage each downlink port as though it were a port on an I/O module installed in the Cisco Nexus 7000 Series chassis.

Displays the physical connections between the FEX and its servers in the Physical Topology screen.

Displays port channels and vPCs as an overlay to the physical topology.

Displays the physical topology in terms of logical vPCs.

Displays VLAN traffic as a topology overlay.

vPC Enhancements

The Cisco DCNM client provides the following vPC enhancements:

A configuration delay occurs for a vPC to become active until a peer adjacency forms and the VLAN interfaces are up.

The configuration excludes VLAN interfaces in order to ensure that VLAN interfaces do not go down when the peer link fails.

You can enable a peer-gateway to make a vPC switch act as an active gateway for packets that are addressed to the router MAC address of the vPC peer without the need to cross the peer link.

The peer-switch in a vPC pair switches to exclude the vPC peer-link from STP computations. This configuration ensures that vPC pair switches have the same root bridge ID.

Object Tracking Manager Enhancements

Cisco DCNM Release 5.1(1) supports the tracking of objects with IPv6 addresses. Previously, object tracking was done with only IPv4 addresses.

Limitations for the Cisco Nexus 7000 Series with Cisco DCNM Release 5.1(1)

This section describes the limitations in Cisco DCNM Release 5.1(1).

For Cisco DCNM Release 5.1(1), the only FEX type supported by the Cisco Nexus 7000 Series switches is the Cisco Nexus 2248TP.

Installation Notes

For information about installing and uninstalling Cisco DCNM Release 5.1(2), 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

Caveats

This section includes the following topics:

Open Caveats—Cisco DCNM Release 5.1

Open Caveats—Cisco DCNM Release 5.0

Open Caveats—Cisco DCNM Release 4.2

Resolved Caveats—Cisco DCNM Release 5.1(2)

Resolved Caveats—Cisco DCNM Release 5.1(1)

Open Caveats—Cisco DCNM Release 5.1

CSCth89613

Symptom: It takes a long time to delete a device from Cisco DCNM.

Conditions: The corresponding device configuration is large.

Workaround(s): None. The device deletion occurs in the background, and it will complete within 20 minutes.

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.

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.

CSCti59612

Symptom: Cisco DCNM failed to display an error message that indicates that you need to add all of the port-group members when allocating interfaces to a VDC.

Conditions: This problem occurs when a custom VDC uses an I/O module that has port-group members, and the I/O module is in an unmanaged state with some ports allocated.

Workaround: Discover the custom VDC or you must select all the ports in the port-group member for allocation from Cisco DCNM.

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.

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.

CSCtj83939

Symptom: The configuration delivery task deployment sometimes takes more time and ends with an "Error connecting to the server" error message.

Conditions: This problem occurs when the JBoss API calls are timed out with the following types of messages in the server log:

2010-10-29 13:52:31,843 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] 
[com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id 
-53e300eb:601:4cca1628:2229 invoked while multiple threads active within it.  

2010-10-29 13:52:31,843 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] 
[com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic 
action -53e300eb:601:4cca1628:2229 aborting with 1 threads active! 

Workaround: Restart the Cisco DCNM client and retry the operation.

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.

CSCto59733

Symptom: The Cisco DCNM installer is unable to launch.

Conditions: The Cisco DCNM installer displays the following exception when you install 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

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, 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 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 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 DCNM correctly sets the log level as 5 during the discovery.

Open Caveats—Cisco DCNM Release 5.0

CSCte54192

Symptom: DCNM takes a long time to discover the devices during a discovery task.

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

DCNM takes a long time to discover the devices with a very large configuration.

Workaround: When this issue occurs in a huge configuration, discover devices individually with hop count zero to significantly reduce the discovery time. Even though discovery takes a long time, the device will get discovered eventually.

CSCtf11112

Symptom: Statistics are not restored after the rediscovery of an unmanaged device.

Conditions: You may see this symptom if a device goes to an unmanaged state because of incorrect credentials or another reason and then the same device becomes managed again. The previously viewed statistics for the device are not restored.

Workaround: None. Start the statistics collection again.

CSCtf27611

Symptom: Cisco DCNM takes a long time to discover the devices in a discovery task.

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

When the CDP hop count is greater than three and therefore more devices are added to the scope of discovery task.

Cisco DCNM takes additional time to discover devices in a large configuration.

Workaround: In a large configuration, you can discover devices individually with the hop count of zero to significantly reduce the discovery time.

CSCtf33337

Symptom: Cisco DCNM is not able to the show a port-profile association with a newly added physical interface for a VEM.

Conditions: You may see this symptom when you add a new physical interface to a particular VEM on a Cisco Nexus 1000V switch, and you have to associate that interface with a system port profile. The association between the interface and port profile is not shown in Cisco DCNM.

Workaround: Rediscover the switch.

CSCtf48926

Symptom: Physical links take a long time to be reflected in the topology window.

Condition: This symptom may be seen when you view the topology window during a large network device discovery.

Workaround: Refresh the topology window to see the physical links once discovery is completed.

CSCtg89207

Symptom: The licensing window incorrectly shows the message "License count not same across the cluster, click to view details," even though the license count is the same on all machines in the cluster.

Conditions: You may see this symptom if you create a cluster setup with three servers and install the same license file on all the three servers.

Workaround: To work around this issue, close the Cisco DCNM client and relaunch it. After relaunch, Cisco DCNM shows the correct license count.

Open Caveats—Cisco DCNM Release 4.2


Note For caveats related to inconsistency between the information displayed in the Cisco DCNM client and the actual state or configuration of a managed device, a common workaround is to press F5 to refresh the Cisco DCNM client.


This section lists the open caveats for Release 4.2(1).

CSCsu76583

Symptom: The DCNM Inventory window does not show the hardware and software versions of the Cisco Nexus 5000 Series fan and power supply modules.

Conditions: Cisco DCNM relies on the show hardware command to display the hardware and software versions of Cisco Nexus 5000 Series fan and power supply modules, but this command is not supported on the Cisco Nexus 5000 Series switch, so Cisco DCNM cannot show any hardware or software versions for those modules.

Workaround: None.

CSCsu85966

Symptom: Cisco DCNM Release 4.2(1) does not support the vPC preempt option.

Conditions: You see this symptom in all conditions.

Workaround: No workaround.

CSCsv54482

Symptom: Cisco DCNM is not showing the traffic storm control threshold events in the events tab of the traffic storm control window.

Conditions: When you configure a threshold for a specific traffic type (for example, unicast, multicast, or broadcast) on an interface, and when the traffic on that interface reaches the upper threshold, Cisco DCNM should capture such events and display them in the events tab. Cisco DCNM relies on the switch to send the syslog on the thresholds, but the switch cannot send such syslogs, so Cisco DCNM cannot display those events.

Workaround: None.

CSCsw63130

Symptom: ImageMgmt: Version Compatibility check from the Cisco DCNM results to Error with the description "refer to client log" or [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!

Conditions: This issue could occur if the Version Compatibility check operation takes more than 5 minutes.

Workaround: Increase the TransactionTimeout attribute value from 300 to 1000 in the jboss-service.xml file, which in a subdirectory of the jboss server directory.

For example, if Cisco DCNM is installed on a Windows 2003 server in the default location, the jboss server directory is C:\Program Files\Cisco Systems\DCNM\jboss-4.2.2.GA\server\dcnm\
conf\jboss-service.xml. Edit the jboss-service.xmlm file and change the TransactionTime attribute value to 1000 as shown:

<mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
 name="jboss:service=TransactionManager">
 <attribute name="TransactionTimeout">1000</attribute>
 <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
</mbean>

CSCsw71645

Symptom: A Cisco DCNM discovery fails when the running-configuration file is not valid.

Conditions: You can use the CLI to configure a role that is allowed to make configuration changes on management interfaces, but the Cisco Nexus 5000 Series switch supports only the mgmt0 interface. If you identify the Mgmt interface as mgmt0, the device accepts the configuration, but it displays an incorrect command in the running-configuration file. When Cisco DCNM discovers these devices, device discovery fails.

Sample incorrect configuration:

role name Milan
  interface policy deny
    permit interface mgmt1 

An incorrect configuration shown in the running-configuration file:

role name Milan
  interface policy deny
    permit interface mgmt0 on slot 3     <<<<<<<< slot 3 is incorrect.

Workaround: Remove the incorrect configuration and use Cisco DCNM to rediscover the device.

CSCsy81802

Symptom: The Resolve Conflicts window does not show some of the Type 1 fields. A vPC has a consistency status of Failed, and either the Resolve Configuration Inconsistency dialog box indicates that no parameters are shown inconsistent or the STP enabled VLANs are shown inconsistent even if the disabled VLANs are consistent.

Conditions: Parameters (for example, STP MST Region name) that are not supported by the Resolve Configuration Inconsistency dialog box are inconsistent or the STP disabled VLANs are not consistent in peer devices, which Cisco DCNM does not handle.

Workaround: Check the conflicts listed by the show vpc consistency-parameters global and manually apply the same configuration as primary in the peer device. The consistency status changes to OK.

CSCsz67186

Symptom: Cisco DCNM shows an HIF port (FEX downlink port) as a SPAN destination port even though the device does not allow you to configure an HIF port as a SPAN destination. You see this message:

Configure an HIF port as a SPAN destination 

Conditions: Use the CLI to configure a Cisco Nexus 2000 downlink port (also known as an FEX or Fabric Extender) as a SPAN destination interface. An error occurs and a message indicates that HIF ports cannot be configured as SPAN destinations, but a minute later, Cisco DCNM indicates that the HIF port is a SPAN destination in a SPAN window (as if the configuration change was a success).

Workaround: Use Cisco DCNM to rediscover the switch. Cisco DCNM will choose the latest status from the switch and display it properly.

CSCsz82147

Symptom: When FEX uplinks are part of a port channel member, then the pinning max-link can only be 1 and cannot be modified. When you use Cisco DCNM to perform the configuration, the device accepts any value.

<CmdBold>
fex 100
 pinning max-link 1

interface port-channel 10
   switchport mode fex-fabric
   fex associate-id 100
   no shut

fex 100
   pinning max-link 2 >>>>>>> This command will result in error in the CLI. 

</CmdBold>

When you execute the same command using XML and Cisco DCNM, the command succeeds in the device without causing an error. Cisco DCNM assumes that the pinning has changed in the device and Cisco DCNM starts showing the new configured value.

Conditions: When you configure an FEX pinning max-links value to something other than 1 (even though the FEX uplinks are part of a port channel), Cisco DCNM allows that to occur.

Workaround: When FEX uplinks are part of a port channel, do not change the pinning value to something other than 1.

CSCsz89132

Symptom: In some cases, Cisco DCNM does not show the correct duplex setting for the Cisco Nexus 2000 host interfaces.

Conditions: This happens for the host interfaces whose duplex setting are set to full. The output for the show running-config command does not show the duplex full command under these host interfaces, so Cisco DCNM is not able to show the correct duplex settings.

Workaround: None.

CSCsz96326

Symptom: Cisco DCNM does not show the power supply status change that occurred in the switch.

Conditions: Even after a change in status of the switch power supply, Cisco DCNM continues to show the old power supply status because there is no status change syslog available for the power supply status change. Without that syslog, Cisco DCNM has no means to know that the change has occurred in the switch.

Workaround: Use Cisco DCNM to rediscover the switch. Cisco DCNM chooses the latest status for the switch and displays it properly.

CSCta02977

Symptom: Cisco DCNM does not show power supply status changes that occur in the FEX.

Conditions: The Cisco DCNM Inventory window shows only the old power supply status even after the power supply status change occurred in FEX because there is no status change syslog available for the power supply unit.

Workaround: Use Cisco DCNM to rediscover the FEX. Cisco DCNM chooses the latest status and displays it properly.

CSCta13742

Symptom: Even though FEX HIF ports (downlink port) cannot be configured with spanning-tree ports, Cisco DCNM allows you to configure them.

interface ethernet 100/1/1
         spanning-tree port type edge 

You cannot perform the above configuration by using the CLI, but you can perform it using Cisco DCNM.

Conditions: When you use Cisco DCNM to perform the above configuration, the device gets a different validation than when you use the CLI. When you use Cisco DCNM, the switch sends the XML response of "ok," which indicates that the configuration was successful.

Workaround: The above configuration is not supported, so do not perform it. If you do perform it, then use Cisco DCNM to rediscover the device. Rediscovery solves the synchronization issue.

CSCta13762

Symptom: Even though FEX HIF ports (downlink ports) cannot be configured with spanning-tree ports, Cisco DCNM displays them as configured.

Ex: interface ethernet 100/1/1
         spanning-tree port type edge 

The above configuration is not supported by the CLI, but when you use the CLI to perform it, Cisco DCNM indicates that the above configuration was successful even though the configuration failed in the device.

Conditions: When you use the CLI to perform the above configuration, an error occurs (ERROR: Command not supported on fex port), but the device logs the command status as being successful. When Cisco DCNM reads the show accounting log command response in the next polling cycle, Cisco DCNM determines that the configuration was successful and it displays the configuration in the GUI.

Workaround: The above configuration is not supported, so do not use the CLI to perform it. If you do perform it, then use Cisco DCNM to rediscover the device. Rediscovery solves the synchronization issue.

CSCta53275

Symptom: After a system switchover, Cisco DCNM displays an incorrect status for the standby supervisor.

Conditions: When you are using Cisco DCNM to manage a Cisco Nexus 7000 switch that has two supervisor modules (the supervisor in slot 5 is active and the supervisor in slot 6 is in standby mode) and there is more than one custom VDC in that device, if you use the system switchover command, Cisco DCNM continues to show the status as "initializing (vdc)" even though that supervisor goes back to the ha-standby state. This behavior occurs because the device sends an incorrect syslog.

Workaround: Rediscover the device in Cisco DCNM.

CSCta86487

Symptom: An unmanaged device is shown as a neighbor in the port channel feature window.

Conditions: When the port channels for a device have operating links with port channels of any other device and the neighboring device goes down or is rediscovered, the links still show up.

Workaround: Refresh the window using the Refresh button from the Toolbar or Menu bar or press F5.

CSCta95512

Symptom: In the Interface port window, under the Detail pane, under the Port details tab, under the Advanced Setting pane, only one SPAN session can be seen for an interface, although more than one SPAN session can be configured for an interface.

Conditions: When you configure an interface as a destination port for more than one SPAN session, Cisco DCNM shows only one SPAN session.

Workaround: None.

CSCta98661

Symptom: Using Cisco DCNM, you cannot configure both the speed and duplex settings for a port channel at the same time.

Conditions: When there is a port channel that has more than one member port and you try to change the speed and duplex value of the port channel and deploy the configuration using Cisco DCNM, the configuration fails.

Workaround: None.

CSCtb85263

Symptom: Cisco DCNM does not show the MST port status properly.

Conditions: In the root switch, if you enable the root guard to the ports connected to the nonroot switch, the status of the port connected to the nonroot switch changes to Broken and moves to the Root inconsistent state, but Cisco DCNM shows the port status as Blocked instead of Broken. The switch sends the XML response as Blocked(BLK) instead of Broken(BKN).

Workaround: None.

CSCtc05207

Symptom: The vPC creation wizard fails and reports a Network Element Exception.

Conditions: The port channels that are selected for a vPC/Peer-link are mapped to port profiles via the "inherit port profile" CLI or interfaces. The interfaces that are selected for a vPC/Peer-link port-channel members are mapped to port profiles via the "inherit port profile" CLI.

Workaround: Follow these steps:

1. Close the wizard.

2. Remove the port profile inheritance from the interfaces/port channels from the CLI.

3. If a vPC is partially created, rerun the wizard using the modify sequence.

4. If a vPC is not created, rerun the wizard.

CSCtc37951

Symptom: Cisco DCNM server creates a new VlanAccessMapEntry instead of modifying the properties of the existing VlanAccessMapEntry for device CLI changes.

Conditions: Problem occurs when you create, modify, or delete VlanAccessMapEntry without using a sequence number.

Workaround: You should create, update, or delete VlanAccessMapEntry with a sequence number from the device CLI.

CSCtc76410

Symptom: Cisco DCNM does not show the port channel speed changes when you are creating or editing FEX-VPCs.

Conditions: When using Cisco DCNM to configure the port-channel speed as 1000, the speed change is not reflected on the device because the speed change is not supported in the FEX fabric interface.

The accounting log shows a Success message instead of a Failure message when you apply a speed value 1000.

Workaround: None.

Resolved Caveats—Cisco DCNM Release 5.1(2)

CSCtb17617

Symptom: The operational status of administratively up interfaces is not synchronized with the device.

Conditions: After a module reset occurs, the operational status of the interfaces that belong to the module are not synchronized with the device if the port is administratively up.

Workaround: Enter the shutdown command on the interface and then enter the no shutdown command.

CSCth80524

Symptom: Cisco DCNM Release 5.1(1) is unable to parse the date format string for the nonstandard time zone configured with the device. This problem results in a sync up failure.

Conditions: Device clock is configured with a nonstandard time zone.

Workaround: Configure the standard time zone with the clock timezone command and then rediscover the device (otherwise the change will not be effective).

switch(config)# clock timezone IST 5 30 

CSCtj43812

Symptom: When you use a manual configuration job or create a custom configuration delivery job with one or more devices, Cisco DCNM does not detect the errors reported by the device. When this occurs, the "Stop delivery on failure" option does not function. Instead, Cisco DCNM continues delivering the job.

Conditions: This problem occurs when you misspell or use invalid commands in the configuration delivery job and follow them with an exit command.

In the following example, the l is missing from vlan:

van 66 ( Note l missing from "vlan" command) 
exit 

This also happens when you specify an I/O module that does not exist in the switch.

In the following example, I/O module 4 does not exist in the switch:

interface ethernet4/1
	description test
	exit 

Workaround(s): Make sure that there are no misspelled or invalid commands in the configuration delivery job. Make sure that the specified I/O module exists in switch. Also, make sure that you are using the proper hierarchy of commands (for example, if you are using the interface vlan 100 command, make sure that the command follows a feature interface-vlan command. After that, resubmit the configuration delivery job.

CSCtk12405

Symptom: The topology does not show the links between devices belonging to different device groups.

Conditions: This problem occurs only for those device groups which are in an expanded state when the previous client exited.

Workaround: Refresh the DCNM client to populate all of the links in the topology.

Resolved Caveats—Cisco DCNM Release 5.1(1)

CSCta73004

Symptom: Even though the device does not allow the FEX HIF ports (downlink ports) to be part of a port channel (when the FEX is connected to two Cisco Nexus 5000 Series switches [dual homed FEX]), Cisco DCNM displays the downlink port as a member of a port channel.

Conditions: Configure an FEX as a dual homed FEX (FEX connected to two Cisco Nexus 5000 Series switches in active-active state). Configure the FEX downlink ports as a part of a port channel as follows:

interface ethernet 100/1/1
   channel-group 10 

The channel-group 10 command will fail in the CLI because the configuration is not valid.

Fabric in Fex A-A mode, can't configure sat port as member 

During the next polling interval, Cisco DCNM will show the above configuration as successful, even though it failed in the CLI. The command log shows the command status as successful. When Cisco DCNM reads the accounting log, it determines that the command was successful.

Workaround: Use Cisco DCNM to rediscover the switch. Cisco DCNM chooses the latest status for the switch and displays it properly.

CSCtb17617

Symptom: The operational status of administratively up interfaces is not synchronized with the device.

Conditions: After a module reset occurs, the operational status of the interfaces that belong to the module are not synchronized with the device if the port is administratively up.

Workaround: Enter the shutdown command on the interface and then enter the no shutdown command.

CSCte37117

Symptom: The status of the RADIUS/TACACS+ server that is shown in DCNM is not in sync with the status shown on the switch.

Conditions: When a RADIUS or TACACS+ server is created in the switch without idle or dead time, the servers are in a non-monitored state. DCNM shows the status of the corresponding servers as non-monitored. If a user configures the idle time or dead time for that server on the switch, the switch will start monitoring the server. As soon as user configures idle time or dead time for that server, the server status will move from a non-monitored state to alive state. Because there is no syslog generated for this status change, DCNM is not aware of this status change, so it continues to show the status as non-monitored.

Workaround: None.

CSCtg44540

Symptom: When you click a link in the Port Channel and vPC view in the topology, device names are truncated in the window. In addition, the ports are not sorted and there is no option to sort them.

Conditions: If the device names are long, then they are truncated in the window that shows details for the link.

Workaround: Use the mouse cursor to hover over the truncated device name. The full name is displayed in a tool tip. There is no workaround for the sorting for the ports.

CSCtg77948

Symptom: Cisco Nexus series devices that do not support custom VDCs, such as the Cisco Nexus 5000 Series switch, become unmanageable in Cisco DCNM after their discovery.

Conditions: This symptom may be seen when the hostname that is set is longer than 20 characters.

Workaround: Set a short hostname of less than 20 characters and then discover the device. Cisco DCNM should be able to discover and manage the devices with hostnames shorter than 20 characters.

CSCtg78225

Symptom: While adding the V6 address during a V6 HSRP Group creation, the address that you enter gets somewhat distorted.

Conditions: You may see this symptom when trying to enter the V6 Address while creating a V6 Group.

Workaround: Create the V6 Group and deploy it using Cisco DCNM, and then provide the required V6 address.

CSCtg80791

Symptom: In the VDC setup wizard, Step 2 shows slot -1 under the selected interfaces table. Expanding slot -1 shows the port profiles that are configured on the device. When you allocate these port profiles, DCNM displays an error message and fails to create the VDC.

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

You configure a port profile on the device through the CLI.

You discover the device using DCNM.

You create new VDC using DCNM.

Workaround: To work around this issue, do not select port profiles under Slot-1 to allocate the port profile in a VDC.

CSCtg87233

Symptom: In an MDS device, when a module is powered up or a module is inserted, the device remains in the discovering state.

Conditions: You may see this symptom when a module is powered up or a module is inserted.

Workaround: Rediscover the device.

CSCtg90264

Symptom: Port information for a link between a Cisco Nexus 7000 Series device and a Linux server is shown incorrectly. The port information is reversed, so that the port on the Cisco Nexus 7000 Series device is shown as a port on a Linux server and vice-versa.

Conditions: You may see this symptom when you click the Show End Devices menu to show the server connected to a Cisco Nexus 7000 Series device.

Workaround: To work around this issue, rediscover the Cisco Nexus 7000 Series device.

CSCth64121

Symptom: When you remove devices from the license pool, the license screen hangs.

Conditions: This symptom might be seen when multiple devices or devices with large configurations are selected for removal.

Workaround: Close the existing DCNM client and relaunch a new DCNM client.

CSCth90196

Symptom: The Cisco DCNM GUI hangs when roles have any interface policy that is specific to VFC, FC, or SAN port-channel interfaces. A slow response might also be seen during various operations in the RBAC screen.

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

1. Start the Cisco DCNM server.

2. Discover any Cisco Nexus 5000 Series device that has a role with an interface policy specific to VFC, FC, or SAN port channels. That is, the show role name role-name command on the device displays a configuration like the following:

..................

..................

permit interface fc2/1-8

permit interface san-port-channel 1-256

permit interface vfc1-8192

..................

3. Launch the Cisco DCNM client and visit Security->RBAC->Roles screen and select the role with the configuration shown in step 2.

4. Try to launch the permitted interfaces combination in the table for the role.

Workaround: Remove the configuration related to the FC, VFC, or SAN port channel and rediscover the Cisco Nexus 5000 Series device.

CSCth90216

Symptom: The syslog poller stops polling in DCNM when roles on a Cisco Nexus 5000 device have a large number of VFC interface configurations as part of the interface policy.

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

1. Start the DCNM server is started.

2. Discover any Cisco Nexus 5000 Series device.

3. Configure a role with an interface policy to permit or deny a large number of VFCs. The show role name role-name command on the device has a configuration like the following:

..................

..................

...................

permit interface vfc1-8192

..................

The syslog poller does not work after Cisco DCNM parses the preceding CLI. Any changes on the device are not reflected in Cisco DCNM.

Workaround: Remove the configuration related to the role with the interface permit or deny policy for the large number of VFCs and rediscover the device.

CSCti83365

Symptoms: The problem occurs with the server start and stop scripts when the scripts are running on Linux. The scripts do not always honor shutdowns. Instead, you must enter the kill -9 command for the Cisco DCNM process that is using the underlying operating system.

Workaround: None.

Related Documentation

This section includes the following topics:

Platform-Specific Release Notes

Cisco DCNM Documentation

Platform-Specific Release Notes

The software release notes for the platforms that Cisco DCNM supports are available on Cisco.com at the following locations:

Cisco Nexus 7000 Series NX-OS Release Notes

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

Cisco Nexus 5000 Series Release Notes

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

Cisco Nexus 4000 Series Release Notes

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

Cisco Nexus 2000 Series Release Notes

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

Cisco Nexus 1000V Series Release Notes

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

Cisco DCNM Documentation

Cisco DCNM documentation is available on Cisco.com at the following location:

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

The documentation for Cisco DCNM includes the following:

Cisco DCNM Installation and Licensing Guide, Release 5.x

Cisco DCNM Fundamentals Configuration Guide, Release 5.x

Cisco DCNM System Management Configuration Guide, 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 Unicast Routing Configuration Guide, Release 5.x

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

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

Cisco DCNM Web Services API Guide, Release 5.x

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.