Guest

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager 1.6.04

  • Viewing Options

  • PDF (167.5 KB)
  • Feedback
Release Notes for CiscoWorks Network Compliance Manager 1.6.04

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.6.04

Contents

Introduction

Installing the CiscoWorks NCM 1.6.04 Patch

What's Been Fixed in CiscoWorks NCM 1.6.04

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Additional Required Applications

Hardware Requirements

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request


Release Notes for CiscoWorks Network Compliance Manager 1.6.04


Published: July 2012, OL-27554-01

These release notes are for CiscoWorks Network Compliance Manager (NCM) 1.6.04.

CiscoWorks NCM 1.6.04 is a patch release that you can install on top of CiscoWorks NCM 1.6, 1.6.01, 1.6.02 or 1.6.03.


Note The Docs tab provided in the CiscoWorks NCM user interface might not include links to the latest documents. Therefore, we recommend that you access the CiscoWorks NCM documentation set using the following URL: http://www.cisco.com/en/US/products/ps6923/tsd_products_support_series_home.html


Contents

This document contains the following sections:

Introduction

Installing the CiscoWorks NCM 1.6.04 Patch

What's Been Fixed in CiscoWorks NCM 1.6.04

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Additional Required Applications

Hardware Requirements

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

Introduction

CiscoWorks NCM tracks and regulates configuration and software changes in a multivendor network environment. It provides visibility into network changes and tracks compliance with a broad variety of regulatory, IT, corporate governance, and technology requirements. CiscoWorks NCM helps IT staff identify and correct trends that could lead to problems, such as network instability and service interruption.

CiscoWorks NCM is integrated with CiscoWorks and is initially launchable from the CiscoWorks home page. CiscoWorks NCM is interoperable with other CiscoWorks applications, such as the LAN Management Solution (LMS) bundle through the Common Services Device Credential Repository (DCR).

Installing the CiscoWorks NCM 1.6.04 Patch

To install the CiscoWorks NCM 1.6.04 patch:


Step 1 Unzip the patch bundle on the CiscoWorks NCM server.

Step 2 Run the patch script.

For Windows, execute the patch.bat script from the command line.

For Linux or Solaris, execute the patch.sh script using the following commands:

% sh patch.sh

or

% ./patch.sh


A log file named patch.log is created in the <CWNCM_Install_Directory>/server/log/ directory, when the patch script is executed. The errors that occur during the installation process are logged in the patch.log file.

The patch installer creates a subdirectory named patch_backups in the root of the CiscoWorks NCM installation directory. This subdirectory includes a directory with the patch build number. The files that are changed by the patch installer are backed up in this directory. The backup.log file lists the files that are backed up and the original location of the files.

In a Multimaster or Horizontal Scalability environment, apply this patch to all NCM servers.

To remove the patch and roll back to the pre-patch state:


Step 1 Stop the NCM Management Engine.

Step 2 Manually restore the files listed in the backup.log file to their original locations.

Step 3 Back out any changes made to the .rcx files, if applicable.

Step 4 If the Java Runtime Environment has been upgraded on the NCM management server, back out that update.

Step 5 Restart the NCM Management Engine.


For Microsoft Windows users the backup.log file lists the following files as backed up:

asm-3.1.jar

jersey-core-1.4.jar

jersey-server-1.4.jar

jsr311-api-1.1.1.jar

Rtr2900.zip

Rtr3900.zip

However, these files are not in the backup directory. You can safely ignore these files as they are newly added in 1.6.04 and should not have been added to the backup.log file.

For customers who removed 9.00.02 build:6748-042811, the Command Scripts list might include two new entries with Script Name ????. These two scripts are the same as the Update Interface scripts, and can be ignored.

What's Been Fixed in CiscoWorks NCM 1.6.04

Table 1 describes the issues fixed in CiscoWorks NCM 1.6.04.

Table 1 Issues Fixed in CiscoWorks NCM 1.6.04

Bug ID
Bug Summary
Fix Description

QCCR1D121594

Can't add more than 25 enhancement custom fields

This problem has been resolved.

QCCR1D121704

When editing a dynamic group where the search criteria is based on a custom data field, the custom data label is not displayed in the Search Criteria block.

This problem has been resolved.

QCCR1B86526

SSH exception/disconnection occurs while handling more prompts during new CLI discovery

This problem has been resolved.

QCCR1B86926

Provision Device From Template menu doesn't progress to the next page

This problem has been resolved.

QCCR1B89562

Advanced perl scripts are not working on javascript drivers

This problem has been resolved.

QCCR1B90798

The NCM topology queries are creating performance problems with MySQL

This problem has been resolved.

QCCR1B91014

Creating a group with the same name as a partition name causes exceptions

This problem has been resolved.

QCCR1B93365

NCM slow to execute scheduled child tasks from parent tasks (scheduler)

This problem has been resolved.

QCCR1B93540

Exception thrown when checking "list active policies only"

This problem has been resolved.

QCCR1B93619

Search results missing comments field

This problem has been resolved.

QCCR1B93677

Export/Import of command scripts truncates trailing whitespace, which causes errors

This problem has been resolved.

QCCR1B93688

Data on user pages not aligned correctly

This problem has been resolved.

QCCR1B94116

CSV of compliance report displays policy compliance instead of the rule compliance

This problem has been resolved.

QCCR1B94263

Tasks scheduled through a CSV file do not retain their configuration

This problem has been resolved.

QCCR1B94371

Running diagnostic on Cisco firewalls yields many failures

This problem has been resolved.

QCCR1B94763

audit_log.txt file grows without bounds with syslog messages. NCM can not process any tasks.

This problem has been resolved.

QCCR1B94918

Run Diagnostics on a device that is not in the partition results in a NullPointerException

This problem has been resolved.

QCCR1B95184

Displayed search results for MAC address differ from 'save as csv' results

This problem has been resolved.

QCCR1B95364

Java cannot find toolbar.png file

This problem has been resolved.

QCCR1B95509

Java process uses 100% of CPU; there are more NCM proxy connections at the same time

This problem has been resolved.

QCCR1B95629

SSH proxy no longer connects automatically to devices

This fix modifies the Java applet that connects to the NCM proxy from the NCM console (webUI).

To enable this fix, on each computer that runs the NCM console, use the Java control panel to delete the cached applets from the web browser.

For example, on the Windows operating system, do the following:

1. Open the Java control panel.

2. Select General tab > Settings.

3. Go to Temporary Files Settings dialog box and click Delete Files.

4. In the Delete Files and Applications dialog box, select the Cached Applications and Applets check box, and then click OK.

QCCR1B95686

Clicking a link under Compliance Center results in an SQL error

This problem has been resolved.

QCCR1B95689

Custom Actions Task Failed: Could not updateDeviceStatus for device xyz java.lang.NumberFormatException: multiple points

This problem has been resolved.

QCCR1B95710

Deleting a policy results in a Foreign Constraint Error from the database

This problem has been resolved.

QCCR1B95712

ORA-01795 error when deleting devices

This problem has been resolved.

QCCR1B95750

Policy Edit mode does not show all policies

This problem has been resolved.

QCCR1B95842

Unused port configurations are not deleted

This problem has been resolved.

QCCR1B95950

Data pruner improvements

This fix improves the algorithm for database pruning. To enable this fix, verify that the Data Pruning task is scheduled to run at least weekly.

QCCR1B95956

Uptime report is inaccurate

This problem has been resolved.

QCCR1B96067

Diagnostic task clears user attribution from Change Event Data

This problem has been resolved.

QCCR1B96076

Syslog Change Detection DNS lookup

This fix skips the DNS lookup for any string that contains the colon (:) character.

To enable this fix:

1. Add the following line to the adjustable_options.rcx file: <option name="syslog/hostname_colon_skip">true</option>

2. Reload the .rcx settings by running the "reload server options" command from the NCM proxy or by restarting the NCM services.

Troubleshooting: You can set Device/Syslog to trace and see useful log statements.

QCCR1B96710

Server error occurs while clicking View Search Result as CSV File on Device Password Change Failures page

This problem has been resolved.

QCCR1B96788

Diagnostic Import does not appear to be working

This problem has been resolved.

QCCR1B96967

Application performance increasingly slow, requiring daily reboot

This problem has been resolved.

QCCR1B97127

Diagramming does not work correctly

This problem has been resolved.

QCCR1B97183

CiscoCatNative: the snapshot failover from SCP to TFTP does not work correctly

By default, NCM does not close the SSH connection when a SSH read timeout occurs. This fix provides an option to force NCM to close the SSH connection upon a SSH read timeout.

To enable this fix:

1. Add the following line to the adjustable_options.rcx file:<option name="Access/SSH/SshCloseOnReadTimeout">true</option>

2. 2. Restart the NCM services.

QCCR1B97378

Diagrams do not show links or connections for layer1, layer2, or layer 3

With an Oracle NCM database, certain cross-reference information is missing from the existing records in the topology table. By default, running an NCM Topology Gathering or NCM VLAN Data Gathering diagnostic does not reprocess existing records for cross referencing. This fix provides a way to force this cross referencing.

To enable this fix:

1. Add the following lines to the adjustable_options.rcx file: <option name="Diagnostics/Special/Topology/CrossReferenceExistingRecords">true</option>

If the topology database table does not reflect correct cross referencing,set this option to true and restart product before running topology gathering diagnostics. After the diagnostics have been run and the cross referencing is reflected in the topology table, set this option to false to improve performance.

2. Reload the .rcx settings by running the reload server options command from the NCM proxy or by restarting the NCM services.

3. Run a full diagnostic task against the NCM inventory.

4. In the adjustable_options.rcx file, set the Diagnostics/Special/Topology/CrossReferenceExistingRecords option to false.

5. Reload the .rcx settings by running the "reload server options" command from the NCM proxy or by restarting the NCM services.

QCCR1B97574

Diagnostic import operation imports all scripts instead of selected scripts in the exported file

This problem has been resolved.

QCCR1B97638

Import/Export to Word for compliance policies/rules

This fix delivers a way to print policies from the NCM console.

1. Go to the Policies > Import/Export Policies,

2. select the policies to print, and then click Print.

QCCR1B97785

Provide a way to enable command script task session logging through the API

This problem has been resolved.

QCCR1B97910

Missing deviceID input from WSDL APIs

This problem has been resolved.

QCCR1B98255

Provide a way to delete specific diagnostic data through the API

This problem has been resolved.

QCCR1B98390

Task duration increased after full text search implemented

This problem has been resolved.

QCCR1B98447

Show Current Configuration displays the wrong configuration

This problem has been resolved.

QCCR1B98753

Last Access Time and Last Snapshot Result show wrong values

By default, the Show Device and Show Device Template commands display a heading named Last Snapshot Result. This fix supports changing this heading to Last Task Result.

To enable this fix:

1. In the appserver.rcx file, locate the following lines:

<option name="formatting/show device/stdout/body">Device ID : $Device.DeviceID$ … Last Successful Snapshot : $Device.LastAccessSuccessDate$ … $CustomData$Comments : $Device.Comments$</option>

2. Copy the entire option definiton from the appserver.rcx file to the adjustable_options.rcx file.

3. In the adjustable_options.rcx file, locate the following copied line: Last Snapshot Result : $Device.LastAccessAttemptStatus$

4. Change the copied line to: Last Task Result : $Device.LastAccessAttemptStatus$

5. Save the adjustable_options.rcx file.

6. Reload the .rcx settings by running the "reload server options" command from the NCM proxy or by restarting the NCM services.

QCCR1B98835

Update SWIM library

This problem has been resolved.

QCCR1B98947

Scheduled tasks run too long without completion

This problem has been resolved.

QCCR1B99464

Link for "Other End" shows incorrect data

This problem has been resolved.

QCCR1B99700

The NCM proxy cursor does not properly react on Cisco ACE devices

This problem has been resolved.

QCCR1B99755

Save 'Update Device Software task' error when selecting '*.bin' software image file

This problem has been resolved.

QCCR1B99974

VLAN search results are not predictable

This problem has been resolved.

QCCR1B100122

User with Existing View Permission Role selected and created View Partition Permissions checked is unable to see checkboxes when comparing two configurations from different devices (Devices > Configuration Changes)

This problem has been resolved.

QCCR1B100359

Enhanced custom data "limit values to" field is limited to 100 characters

This problem has been resolved.

QCCR1B100592

Rule Exception Expire Date field needs in to include future years

This problem has been resolved.

QCCR1B100996

Command script run by a user with custom permisssions throws an NPE

This problem has been resolved.

QCCR1B101416

Policy export fails when too many policies are selected

This problem has been resolved.

QCCR1B101560

When creating a command script or advanced command script with the Multiline option selected, the "Limit Values To" box is restricted to 255 characters

This problem has been resolved.

QCCR1B101600

Generate a session log when running an advanced command script through the API

This problem has been resolved.

QCCR1B101701

User permission denial throws a java exception

This problem has been resolved.

QCCR1B102225

jboss issues

This problem has been resolved.

QCCR1B102226

WSDL operation show_device missing Site Name as output

This problem has been resolved.

QCCR1B102302

HPSA - TACACS+ authentication fail over does not work when SA is unavailable

This problem has been resolved.

QCCR1B102338

Import deactivates device templates

This problem has been resolved.

QCCR1B102582

Connection through bastion host fails

This problem has been resolved.

QCCR1B103910

Issue with addins directory

This problem has been resolved.

QCCR1B105606

CiscoNexus driver is not running a `copy run start' in a command script

See Fix for QCCR1B105606


Fix for QCCR1B105606

This fix enables a new task option for specifying whether NCM should overwrite the startup configuration with the current running configuration at the completion of the task.

To enable this option:


Step 1 Add the following lines to the adjustable_options.rcx file:

<option name="DeviceInteraction/EnforceConfigurationSave/Take Snapshot">false</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Discover Driver">disabled</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Run ICMP Test">disabled</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Deploy Passwords">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Deploy Config">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Configure Syslog">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Run Command Script">false</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Run Diagnostics">false</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Synchronize Startup and Running">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Update Device Software">false</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Backup Device Software">false</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Reboot Device">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Run Device Script">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/Delete ACLs">true</option>

<option name="DeviceInteraction/EnforceConfigurationSave/VLAN Task">true</option>


Note Following configures the default enforce_save setting for various device tasks. They can be overridden by user when scheduling tasks. The task type used here must be taken from TaskType.java(friendlyNames).


Step 2 Reload the .rcx settings by running the "reload server options" command from the NCM proxy or by restarting the NCM services.


Supported Platforms

Table 2 shows the supported platforms for CiscoWorks NCM 1.6.x.

Table 2 Supported Platforms for CiscoWorks NCM 1.6.x

Operating System
Architecture
32-bit
64-bit 1

Windows Server 2008 R2

x86_64

 

X

Windows Server 2003 SP2

X86_32

X

 

Solaris 10 SPARC2 ,3

Sun4u, Sun4v

 

X

RedHat RH AS 44

x86_32

X

 

RedHat RHEL Server 5

x86_64

 

X

SuSE Enterprise Linux Server 10

x86_64

 

X

1 CiscoWorks NCM 1.6 full installs are supported only on 64-bit architecture. You can upgrade from an existing 32-bit CiscoWorks NCM platform to a 64-bit platform. If you are using a RHEL 5 Server x64, it is required that you upgrade to 64-bit platform.

2 Before installing CiscoWorks NCM 1.6 on a Solaris 10 platform, you must reconfigure the Syslog server on Solaris 10 to ignore the remote Syslog messages. The Solaris Zone on which CiscoWorks NCM runs must use a dedicated Network Interface Card (NIC).

3 A large amount of swap space is required due to the fork() system call on Solaris. When you fork a 24 GB process, Solaris allocates 24 GB in the swap file. If the 24 GB is not available in swap, the fork() system call fails.

4 The last supported CiscoWorks NCM version on this platform is CiscoWorks NCM 1.5.x.


The following operating systems are no longer supported:

Windows 2000

Solaris 9

Red Hat AS3

SuSE 9


Note For all operating system upgrades, please see the respective vendor documentation or contact your system support personnel. Cisco is not responsible for issues that might arise during third-party product upgrades.


Supported Databases

Table 3 shows the databases that are supported by CiscoWorks NCM 1.6.x.

Table 3 Supported Databases for CiscoWorks NCM 1.6.x

Database
Notes

Oracle 10g (10.2.0.2 and 10.2.0.4) Standard and Enterprise Edition

64-bit Oracle is supported. If you are running CiscoWorks NCM 1.6 in a Distributed System environment, you will need Oracle 10g or 11gR1 Enterprise Edition.

Oracle 11g (11.1.0.7.0) Standard and Enterprise Edition

64-bit Oracle is supported. If you are running CiscoWorks NCM 1.6 in a Distributed System environment, you will need Oracle 10g or 11gR1 Enterprise Edition.

Microsoft SQL Server 2005 and 2008 Standard and Enterprise Edition

64-bit Microsoft SQL Server is supported. High Availability Distributed System on Microsoft SQL Server requires SQL Server 2005 Service Pack 2 (Standard Edition or Enterprise Edition) or SQL Server 2008 (Standard Edition or Enterprise Edition).

MySQL 5.0.58

MySQL 5.0.58 ships with CiscoWorks NCM 1.6.


Except for modest deployments without full enterprise scale and performance requirements, the application server and database server should be on separate physical machines. In addition, the database server should be dedicated to CiscoWorks NCM, rather than serving multiple applications.


Note CiscoWorks NCM 1.6 does not support the use of Microsoft SQL Named Instances.


The following databases are no longer supported:

Oracle 9i and Oracle 9.2

Microsoft SQL Server 2000

MySQL 3


Note For all database upgrades, please see the respective vendor documentation or contact your database analyst. Cisco is not responsible for issues that might arise during third-party product upgrades.


Additional CiscoWorks NCM Configurations

If you have configured a High Availability Distributed System, the database requirements for Oracle and Microsoft SQL Server include:

Database
Restrictions

Oracle 10g Standard or Enterprise Edition (10.2.0.2 and 10.2.0.4)

No more than five CiscoWorks NCM Cores can be configured together.

Oracle 11g Standard or Enterprise Edition (11.1.0.7.0)

No more than five CiscoWorks NCM Cores can be configured together.

Microsoft SQL Server Standard and Enterprise Edition 2005 (SP2 or higher) and 2008

No more than two CiscoWorks NCM Cores can be configured together. The maximum number of devices should not exceed 6500.


If you have configured a Horizontal Scalability environment, the database requirements for Oracle and Microsoft SQL Server include:

Database
Restrictions

Oracle 10g Standard or Enterprise Edition (10.2.0.2 and 10.2.0.4)

No more than five CiscoWorks NCM application servers can be configured together with a single database.

Oracle 11g Standard or Enterprise Edition (11.1.0.7.0)

No more than five CiscoWorks NCM Cores can be configured together with a single database.

Microsoft SQL Server Standard and Enterprise Edition 2005 (SP2 or higher) and 2008

No more than five CiscoWorks NCM application servers can be configured together with a single database.


See High Availability Distributed System Configuration Guide for CiscoWorks Network Compliance Manager for information on configuring High Availability Distributed System environment.

See Horizontal Scalability User Guide for CiscoWorks Network Compliance Manager for information on configuring Horizontal Scalability environment.


Note High Availability and Horizontal Scalability environments are not supported for MySQL.


Virtual Environments

Note the following points while running CiscoWorks NCM in a virtual environment:

VMWare guests can be run on a VMWare ESX 3.5 or VMWare ESX 4.0 server (preferred). It is important that the Disk I/O be split. The ESX server must have two arrays, one for the ESX operating system and one for the virtual machines.

Use of Vmotion is not recommended.

If you plan to use virtual machines for both CiscoWorks NCM and your database, ensure that they are running on different VMWare Guests. Note that this only works if you set a limit on managed devices and keep it low. It is recommended that you have the database on a different ESX host so there is no conflicting I/O on the array.

If you plan to run VMWare in a Distributed System or Horizontal Scalability environment, the maximum number of CiscoWorks NCM Cores should not exceed two.

Some VMWare Guests time drift. Syncing to an external time source can solve this issue.

The CiscoWorks NCM VMWare Guest system requirements are double that of standalone server requirements.

CiscoWorks NCM can be network intensive, therefore, if you have many virtual machines sharing a virtual switch and network interface card, you could experience unexpected behavior, including time-outs and failed tasks. In addition, each virtual environment is different and could function differently under loads with shared VM Guests.

If you observe any performance issues while running CiscoWorks NCM in a virtual environment, do the following:

Increase hardware resources.

Ensure that resources are dedicated through your ESX Administrator.

Decrease the number of VMWare Guests running simultaneously.

Add a dedicated network interface card to the ESX server for CiscoWorks NCM to use exclusively.

Significant performance degradation has been seen on ESX servers running multiple virtual machines where one or more virtual machine was under heavy load. It is critical that the ESX server running CiscoWorks NCM in a virtual environment be properly resourced to avoid performance degradation.


Note The number of managed devices does not have as significant of an impact on performance as the number of concurrent tasks. If performance issues are seen, reduce the number of concurrent tasks and ensure that CiscoWorks NCM is getting the appropriate resources.


Additional Required Applications

You need to install the following applications:

CiscoWorks NCM supports the following browsers:

Mozilla Firefox 3.x and higher

Internet Explorer 7.x and higher


Note Windows pop-up blockers must be disabled for the browser. Cookies must be enabled for the browser.


Microsoft Excel 2000 or higher, if you are viewing Summary Reports from the CiscoWorks NCM server.

Adobe® Acrobat Reader™ version 4.0 or higher if you are viewing CiscoWorks NCM documentation from the CiscoWorks NCM server.

ActivePerl 5.8.x (for Windows).

Perl 5.8.x (for Solaris and Linux). The CiscoWorks NCM Convert-to-Perl script feature uses Perl.

Perl Net::SSH::Expect module (for using the Connect module with SSH)


Note Third-party products mentioned in this documentation are manufactured by vendors independent of Cisco. Cisco makes no warranty, implied or otherwise, regarding the performance or reliability of these products.


Hardware Requirements

CiscoWorks NCM requires the following minimum hardware:

Table 4 Application Server Requirements

Application Server

CPU

Intel Xeon or equivalent, 3.0+ GHz (Windows, Linux), Dual UltraSparc IIIi+, 1.3 GHz (Solaris)

Memory

4 GB RAM

Swap Space

4 GB

Disk

40 GB, Fast SCSI

Network

100 Mbps Fast Ethernet, full duplex


Table 5 Database Server Requirements

Database Server

CPU

Intel Xeon or equivalent, 3.0+ GHz

Memory

4 GB RAM

Swap Space

4 GB

Disk

60 to 100 GB, Single Channel RAID, Fast SCSI

Network

100 Mbps Fast Ethernet, full duplex


Accessing the CiscoWorks NCM Documentation Set

All or any part of the CiscoWorks NCM documentation set, including this document, might be upgraded over time. Therefore, we recommend that you access the CiscoWorks NCM documentation set using the following URL: http://www.cisco.com/en/US/products/ps6923/tsd_products_support_series_home.html


Tip To cut and paste a two-line URL into the address field of your browser, you must cut and paste each line separately to get the entire URL without a break.


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.

Open a service request online at:

http://www.cisco.com/techsupport/servicerequest

View a list of Cisco worldwide contacts at:

http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html