Guest

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager, 1.5.01

  • Viewing Options

  • PDF (365.2 KB)
  • Feedback
Release Notes for CiscoWorks Network Compliance Manager 1.5.01

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.5.01

Contents

What's Been Fixed in CiscoWorks NCM 1.5.01

Known Problems in CiscoWorks NCM 1.5.01

Documentation Addendum

What's Been Fixed in CiscoWorks NCM 1.5

What's New in CiscoWorks NCM 1.5

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Additional Required Applications

Hardware Requirements

Caveats

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

Notices

OpenSSL/Open SSL Project

License Issues


Release Notes for CiscoWorks Network Compliance Manager 1.5.01


Revised: March 2010, OL-21880-01

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


Note The CiscoWorks NCM 1.5.01 release requires Driver Packs dated July 2009 (or later) to operate properly.


CiscoWorks NCM tracks and regulates configuration and software changes in a multivendor network infrastructure. 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 intergrated with CiscoWorks and is initially launchable from the CiscoWorks home page. NCM is interoperable with other CiscoWorks applications such as the LAN Management Solution (LMS) bundle through the Common Services Device Credential Repository (DCR).


Note The Docs tab provided in the CiscoWorks NCM UI 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:

What's Been Fixed in CiscoWorks NCM 1.5.01

Known Problems in CiscoWorks NCM 1.5.01

Documentation Addendum

What's Been Fixed in CiscoWorks NCM 1.5

What's New in CiscoWorks NCM 1.5

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Additional Required Applications

Hardware Requirements

Caveats

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

Notices

What's Been Fixed in CiscoWorks NCM 1.5.01

Table 1 describes the issues fixed in CiscoWorks NCM 1.5.01.

Table 1 Issues Fixed in CiscoWorks NCM 1.5.01 

Bug Summary
Fix Description

Policy Rules were tested against unspecified devices

Policy Rules are now tested against specified devices.

CPU usage was 100% when a Discover Driver task was run in a Distributed System environment with 10,000 devices

CPU usage percentage for running Discover Driver task has been brought down significantly.

No option was provided to continue or cancel subsequent sub-tasks for multi-task projects

You can now run the subsequent sub-tasks or cancel all the remaining sub-tasks, if a sub-task completes with a Warning status.

Community String propagation did not trigger configuration polling in NNMi

NNMi Community String propagation now triggers configuration polling in NNMi. Also, new NNMi Community Strings take effect immediately.

The View Diagnostics option on the Event Detail page generated an error for diagnostic policy non-compliance

The View Diagnostics option now functions properly. Diagnostic policy non-compliance information is shown on the Event Detail page.

The NNMi/CiscoWorks NCM Integration installer did not verify the Remote Method Invocation (RMI) communication between the NNMi and CiscoWorks NCM servers

The NNMi/CiscoWorks NCM Integration installer now verifies the RMI communication between NNMi and CiscoWorks NCM servers.

Inappropriate module changed events occurred when an Event Notification rule was configured

Event Notification rules now function properly.

The Deploy Password task did not propagate SNMP string changes to NNMi

The Deploy Password task now propagates SNMP string changes to NNMi.

You must upgrade to CiscoWorks NCM 1.4 before upgrading to CiscoWorks NCM 1.5

You can now upgrade from CiscoWorks NCM 1.0x to CiscoWorks NCM 1.5.x.

Device groups cannot be created from the CSV file input

You can now select the Device Group option in the Import Task page. The Device Group CSV Template contains various fields for device group names, partition names, and parent device group names.

CiscoWorks NCM did not allow you to login to most of the Cisco devices using the AAA credentials in the enable mode

You can now use AAA credentials to login to the Cisco devices in the enable mode.

CiscoWorks NCM traps did not map to source objects in NNMi

CiscoWorks NCM traps now function properly in NNMi.

Device templates were displayed in the Device Selector

Device templates are not displayed in the Device Selector.

Ports cannot be added to a secondary private VLAN

You can now add a port to a secondary private VLAN.

CiscoWorks NCM install was not automatically updated with new NNMi install UUIDs

CiscoWorks NCM install is now automatically updated with new NNMi install UUIDs.

Returning ports with null port names caused exception errors while editing VLANs

CiscoWorks NCM now returns ports with null port type as valid ports, so that you can verify if there are any issues during provisioning.

New search criteria did not appear on Search pages

The new search criteria are now properly displayed on the Search pages.

Deleting a device from CiscoWorks NCM with more than 1,000 VLANs generated an error

You can now delete a device with more than 1,000 VLANs from CiscoWorks NCM.

The upload failed, when you try to upload an image file larger than the default maximum size of Tomcat

You can now upload an image file larger than the default maximum size of Tomcat.

Cross-site Scripting Checks does not check for the %00 character

Cross-site Scripting Checks now function properly.


Known Problems in CiscoWorks NCM 1.5.01

Table 2 describes the known problems in CiscoWorks NCM 1.5.01.

Table 2 Known Problems in CiscoWorks NCM 1.5.01 

Problem
Description

Licensing not found issue

While logging into CiscoWorks NCM Server, if the server shows the No Valid License found error, then check the following:

Make sure that all license files are installed under CiscoWorks NCM install folder.

Make sure that there are no lingering expired license files, especially Evaluation license in the CiscoWorks NCM install folder.

Make sure that the output of the command <CWNCM_install_Dir>/server/ext/wrapper/bin/lmutil lmhostid output matches the hostid on the license file. Do not modify the license file.

CSCsx38253—SWIM process status is incorrect

1. Enter /etc/init.d/truecontrol status to make sure that all services are running normally.

2. Choose Admin > Start/Stop Services, and stop the Software Image Management Server.

The following error message appears:

Unable to stop the TrueControl SWIM Server service.

Workaround: Ignore the error message. Directly check the TrueControl SWIM server status with the Services application on Windows platforms.

Enter /etc/init.d/truecontrol status on Linux or Solaris platforms to check the TrueControl SWIM server status.

CSCsk95754—SNMPv3 Engine Id check is not needed.

This occurs when you

1. Select a device that has SNMP-v3 configured from the Inventory.

2. Choose View > Device Details > Software Upgrade Recommendation.

3. Select any image to launch the details.

The following warning message will be displayed:

SWIM1094: SNMP-V3 parameters is incorrect or not available for the device. Check whether the SNMP-V3 password, SNMP-V3 algorithm, and SNMP-V3 engine ID is configured for the device.

Ignore the message if the SNMP-V3 password and SNMP-V3 algorithm are configured correctly.

CSCtd63942—!: not found warning message is displayed when CiscoWorks NCM is installed on Solaris platform.

!: not found warning message is displayed when CiscoWorks NCM is installed on Solaris platform.

Example:

-bash-3.00# ncm/Solaris_5830-111009_setup.bin

Preparing to install...

ncm/Solaris_5830-111009_setup.bin: !: not found

Extracting the JRE from the installer archive...

Unpacking the JRE...

This message does not indicate a problem and is invalid. No workaround is needed.

CSCtd69969—Device Selector sometimes does not work in Firefox 3.5 or higher.

This occurs when you:

1. Select a device from the device selector.

2. Run a task on the selected device.

The task will fail and Missing field: Device error will be displayed.

Or

1. Select multiple devices from the device selector.

2. Select the task that you want to run against the selected devices, from the Actions drop-down list.

The selected devices are not displayed in the device selector.

Workaround:

1. Install the latest Adobe Flash browser plug-in.

2. Clear browser cache and cookies.


Documentation Addendum

This section contains the most recent CiscoWorks NCM 1.5.01 information that will be incorporated into the next version of the CiscoWorks NCM User Guide and Online Help files.

This section contains the following topics:

Import Task Page

Upgrading CiscoWorks NCM 1.0x in a High Availability Distributed System Environment

Option to Continue or Stop the Sub-tasks, When a Sub-task Completes with a Warning Status

Enabling FIPS Mode

CiscoWorks NCM/NNMi Integration

Changing CiscoWorks NCM Credentials While Connecting to a New Database Location

Importing Devices into CiscoWorks NCM from NNMi

Import Task Page

The Data Type field in the Import Task page has the following options:

Devices—The Device CSV Template contains various fields for network device IP addresses and host names.

Device Group—The Device Group CSV Template contains various fields for device group names, partition names, and parent device group names.

Device Password—The Device Passwords CSV Template is required only if you are not using the Device Password Rules.

To create a new CSV file using a CSV template:

1. Select the Device, Device Group, or Device Password CSV template file option.

The CSV template file appears.

2. Save the CSV file under a different name on your local hard drive.

3. Modify the CSV file to suit your device data or password.

Upgrading CiscoWorks NCM 1.0x in a High Availability Distributed System Environment

If you are running the CiscoWorks NCM 1.0x in a High Availability Distributed System environment, you must do the following to upgrade to CiscoWorks NCM 1.5.01:

1. Upgrade to CiscoWorks NCM 1.4.

2. Upgrade to CiscoWorks NCM 1.5.

3. Upgrade to CiscoWorks NCM 1.5.01.

Option to Continue or Stop the Sub-tasks, When a Sub-task Completes with a Warning Status

You can run the subsequent sub-tasks or cancel all the remaining sub-tasks, if a sub-task of a multi-task project completes with a Warning status. This feature enables you to cancel the tasks that are running against a device that could be experiencing issues.

To enable this feature:


Step 1 Choose Admin > Custom Data Setup.

Step 2 Scroll down to the sixth API Name field under the Tasks section.

Step 3 Enter subtask_control in the sixth API Name field.

Step 4 Enter Cancel Remaining Tasks That Have Warning Messages in the Display Name field.

Step 5 Check the Limit To check box and enter Yes or No in the Values field.

Step 6 Click Save.


If this feature is enabled, a new field (with the name, Cancel Remaining Tasks That Have Warning Messages) is displayed on all sub-task pages, when you create sub-tasks for a multi-task project.

This field has the following options:

Blank—The remaining sub-tasks continue to run.

Yes—The remaining sub-tasks are canceled.

No—The remaining sub-tasks continue to run.

To disable this feature, uncheck the sixth API Name check box on the Custom Data Setup page and click Save.

Enabling FIPS Mode

The Federal Information Processing Standardization (FIPS) specifies cryptography requirements for both software and hardware.

In CiscoWorks NCM, FIPS functionality is applicable only for the devices that support SSH/SCP or SNMPv3. Devices that do not support SSH/SCP or SNMPv3 are not affected.


Note Enabling the FIPS mode, restricts the algorithms that the CiscoWorks NCM uses to communicate with the devices, thereby rendering some non-FIPS compliant devices unreachable.


To enable FIPS mode:


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

<option name="crypto/fips/enabled">true</option>

Step 2 Restart the CiscoWorks NCM.

The following message is displayed in the log file, if the FIPS mode is enabled.

{system/crypto} [main] 75 FIPS140Mode: Loading FIPS JCE Provider

Step 3 Login to CiscoWorks NCM as Admin.

Step 4 Choose Admin System Status > BaseServerMonitor > View Details.

The following message is displayed:

crypto/fips/cipher_list = [3des-cbc, aes128-cbc, aes128-ctr, aes192-cbc

crypto/fips/mac_list = [hmac-sha1, hmac-sha1-96]


To disable FIPS mode:


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

<option name="crypto/fips/enabled">false</option>

Step 2 Restart the CiscoWorks NCM.


Using High Availability Distributed System and Horizontal Scalability Functionality

CiscoWorks NCM High Availability Distributed System software supports database tier scaling. CiscoWorks NCM Horizontal Scalability software supports application server tier scaling. You can combine both High Availability Distributed System and Horizontal Scalability for optimal performance.

To combine High Availability Distributed System and Horizontal Scalability functionality, do the following:


Step 1 Configure a High Availability Distributed System environment. See CiscoWorks NCM High Availability Distributed System User Guide for detailed information.

Step 2 Configure a Horizontal Scalability environment. See Adding Additional NCM Cores section in the CiscoWorks NCM Horizontal Scalability User Guide for detailed information.

Step 3 Set the following attributes while adding the Horizontal Scalability cores:

<option name="distributed/enabled">true</option>

<option name="distributed/replication_enabled">false</option>

Step 4 Set the following attributes for High Availability Distributed System cores:

<option name="distributed/enabled">true</option>

<option name="distributed/replication_enabled">true</option>

Step 5 Set the following attribute for the Networks cores connected to each database:

<option name="distributed/replication_enabled">true</option>

For example, if NewYork-app1 core and NewYork-app2 core are connected to NewYork-db1, and the LA-app1 core and LA-app2 core are connected to LA-db1, the following attributes are set for the NewYork-app1 and LA-app1 cores:

<option name="distributed/enabled">true</option>

<option name="distributed/replication_enabled">true</option>

NewYork-app2 and LA-app2 must include the following:

<option name="distributed/enabled">true</option>

<option name="distributed/replication_enabled">false</option>


CiscoWorks NCM/NNMi Integration

For the CiscoWorks NCM/NNMi integration to function properly on a RedHat ES 4.x platform, you must have the following libraries on the server:

zlib-1.2.1.2-1.2.i386.rpm

freetype-2.1.9-8.el4.6.i386.rpm

expat-1.95.7-4.i386.rpm

fontconfig-2.2.3-13.el4.i386.rpm

xorg-x11-Mesa-libGL-6.8.2-1.EL.63.i386.rpm

xorg-x11-libs-6.8.2-1.EL.63.i386.rpm

If you are running a more recent version of RedHat, you might have to download newer versions of these libraries. These libraries are available from RedHat.

Changing CiscoWorks NCM Credentials While Connecting to a New Database Location

If the CiscoWorks NCM database has been moved to a new server, you can configure CiscoWorks NCM to connect to the new database location using the tc_tools utility.

The tc_tools utility enables you to update the following information on the CiscoWorks NCM server:

Database server name

Database name

Database username

Database user password

The CiscoWorks NCM database must be configured through database administration tasks or through the CiscoWorks NCM install procedure. See CiscoWorks NCM 1.5 Upgrade and Installation Guide for information on installing the CiscoWorks NCM database.

The tc_tools utility is located at:

<installdir>/client/tc_tools.bat in Windows platform

<installdir>/client/tc_tools.sh in Unix platform

To execute the tc_tools utility:


Step 1 Run the tc_tools utility.

The following options are displayed:

1 - Change database connection information

2 - Save device passwords to file

3 - Reset update in progress information

4 - Exit

Step 2 Select Option 1 (Change database connection information).

The following message is displayed:

Database Server [devsql2k]:Database Name [Caladan_Bruce]:Database User [sa]:Database Password [********]:Database connection information changed.

where the entries inside the brackets are the previous values. If you are confirming an existing value, you can retype it or simply press Enter. To confirm all existing values without updating them, you can exit the script by entering ctrl-C.

Step 3 Make the required changes and save the file.

Step 4 Select Option 4 (Exit) or enter ctrl-C.

Step 5 Restart the CiscoWorks NCM Management Engine.


Importing Devices into CiscoWorks NCM from NNMi

The client_nnm.rcx file is created, when the CiscoWorks NCM/NNMi Connector is installed. This file exists on both the CiscoWorks NCM and NNMi servers. Therefore, devices can be imported into CiscoWorks NCM using both the servers.

The client_nnm.rcx file has the following configuration options:

nnmImportGroup - Networking Infrastructure Devices

nnmImportRequireSysOIDMatch - false

The sysoid match is ignored, if the nnmImportRequireSysOIDMatch configuration option is set to false. The devices in the NNMi are filtered by the group defined in the nnmImportGroup configuration option.

If you want to import devices from another group, you must edit the client_nnm.rcx file and change the group name. The group name is always used even if the nnmImportRequireSysOIDMatch value is set to true.

What's Been Fixed in CiscoWorks NCM 1.5

Table 3 describes the issues fixed in CiscoWorks NCM 1.5.

Table 3 Issues Fixed in CiscoWorks NCM 1.5 

Bug Summary
Fix Description

Per-task credentials were not working properly

Per-task credentials now work properly.

Per-task credentials enable you to specify the credentials used to access devices.

Large sets of data pasted into the proxy, caused an error due to buffer overflow

You can now paste large amount of data, for example, a long configuration file, into the proxy.

Snapshot tasks failed with a constraint error when the Device Access log was updated

Snapshot tasks now function properly.

Error message was displayed, when the policies bound to deactivated devices were edited

You can now edit the polices bound to deactivated devices.

Issue with accessing a device in remote Realms using the console server. CiscoWorks NCM could only access console servers in the local Realm (i.e., the same Realm as the CiscoWorks NCM Core)

CiscoWorks NCM can now access the devices in remote Realms using the console servers.

Network Status reports did not display policy rule violations

Network Status reports now provide an overview of network configuration, health, compliance, and policy rule violations.

You cannot save a policy rule that contains large configuration text

You can now include large configuration text in the Block Start Pattern field while creating a policy rule.

Database queries failed, when a list having more than 1,000 device groups was processed

Database queries have been retooled to properly handle large lists.

Need a VLAN Data Gathering diagnostic

The VLAN Data Gathering diagnostic gathers the latest VLAN information.

Device template provisioning does not function properly

Device template provisioning now functions properly.

Device templates enable you to define configurations, OS or file specifications, and other device-specific information that can be applied to existing devices.

Advanced command scripts and diagnostics using the Perl API returned errors

Advanced command scripts and diagnostics using the Perl API now function properly.

CiscoWorks NCM was not updating the OS software history version for devices

CiscoWorks NCM now updates the OS software history version for devices and displays the information in the Software Audit Trail report.

Command scripts failed, when CSV input was used

You can now run command scripts using CSV input.

No policies found message was displayed on the Policies page even when policies existed

You can view all available policies on the Policies page.

SA and TACACS servers did not allow local authentication failover

SA and TACACS servers now allow local authentication failover.

The CiscoWorks NCM Installer allowed upgrades from any version of CiscoWorks NCM schema

The CiscoWorks NCM Installer now upgrades only the correct version of CiscoWorks NCM schema.

Per device dynamic grouping recalculation was incorrect

Per device dynamic grouping recalculation is done properly.

The Batch Edit option for Bastion Hosts does not work

The Batch Edit option for Bastion Hosts now functions properly.

Use Task Owner's AAA Credentials option was not saved properly

The Use Task Owner's AAA Credentials option now functions properly.

Extra backslahes were added, if a backslash was used while creating a policy rule

Extra backslashes are not added, if a backslash is used while creating a policy rule.

You cannot select a second date to specify a date range while doing an Advanced search

You can now select a second date on the Advanced Search page to specify a date range.

AAA credentials did not function properly

You can now select the Use Task Owner's AAA Credentials option while using the AAA credentials.

Policy rule conditions were not saved while creating a diagnostics policy rule using memory troubleshooting condition

You can now save the policy rule conditions while creating a diagnostics policy rule using the memory troubleshooting condition.

Dynamic group recalculations caused Out of Memory errors

Dynamic group recalculations now function properly.

Boolean expressions were not properly evaluated for dynamic groups

Boolean expressions are properly evaluated for dynamic groups.

Viewing sub-tasks of a multi-task project could delete the multi-task project

You can now configure a multi-task project to run several sub-tasks sequentially.

CiscoWorks NCM cannot be connected to Juniper WXC-500 device

CiscoWorks NCM can now be connected to Juniper WXC-500 device.

The Remote Agent was not deleting the SNMP objects

The Remote Agent now functions properly.

Users can search device configurations for which they do not have permissions

Only users with proper permissions can now search the device configurations.

Policy Compliance searches used the old query infrastructure

Policy Compliance searches now use the new, ad hoc query infrastructure.

Users with View permission cannot view dynamic groups

Users with View permission can now view the dynamic groups.

You cannot select a new Site while editing a device

You can now edit a device and change the device's Site designation.

Could not connect to all the devices after upgrading to CiscoWorks NCM 1.4.

You can now upgrade to CiscoWorks NCM 1.5 and connect to all your devices.

Incorrect Policy Compliance search results were displayed on the Policy, Rule, and Compliance Search Results page

Policy Compliance search results are now properly displayed on the Policy, Rule, and Compliance Search Results page.


What's New in CiscoWorks NCM 1.5

CiscoWorks NCM 1.5 includes the following new features and enhancements:

Solaris 64-bit support—64-bit Java Virtual Machine (JVM) is used to install CiscoWorks NCM on a Solaris platform. Therefore, CiscoWorks NCM can utilize more memory.

Enhanced task scheduling—While creating or updating a CiscoWorks NCM task, you can now set a priority for the task, so that it runs at higher priority than other tasks. There are five task priority levels, 1 through 5. 1 is the highest task priority level. Higher priority tasks run before lower priority tasks.

In addition, you can use the Round-robin algorithm on group tasks. For example, if you start a group task for 10,000 devices at 10am and then start a group task for 10 devices at 10:05am, using the Round-robin algorithm, you need not wait for the first task group to complete before the second group task is started.

Enhanced Device Selector and Device Group Explorer—The enhanced Device Selector and Device Group Explorer enable you to easily navigate through group trees to select devices and device groups for a variety of applications.

Multiple VLAN per port support—CiscoWorks NCM enables you to view and provision VLANs on network switches. CiscoWorks NCM 1.5 allows you to:

View a complete list of a device's VLANs

View specific VLAN details

View a list of ports assigned to a VLAN

View trunk ports

View a list of VLANs on a trunk port

View the native VLAN of a trunk port

View VTP settings of a network switch

Create a new VLAN on a network switch

Change a port assigned to a VLAN

Configure a port as a trunk port

Change trunk port native VLANs

Configure a trunk port as a non-trunk

Virtual device and virtual context support—CiscoWorks NCM now supports virtual devices, including VMware's Virtual Switch (vSwitch) technology available via VMware's Infrastructure (ESX) and the Cisco Nexus 1000V series switches. These new virtual devices can be managed along with legacy devices.

Virtual devices as well as devices that support virtual contexts, including Cisco Firewall Services Module (FWSM) and Cisco ACE Application Control Engine Module, now benefit from device relationship enhancements. CiscoWorks NCM 1.5 enables you to manage non-IP address contexts and to view the underlying relationships between the actual hardware and virtual contexts.

Device relationships—Device relationships maintain data for parent, peer, and child devices. Device dependencies can be defined by the new Device Relationships API.

Connection Path enhancements—You can now enable or disable device access via primary IP addresses.

Link aggregation support—Link aggregation support enables CiscoWorks NCM to list all the links (or connections) associated with a specific port on a device. This information is derived from enhanced diagnostics or from new device context information.

Link aggregation enables you to manage a device with virtual contexts that assign multiple connections to a physical port.

Provisioning and Scripting API enhancements—You can use the Device Relationships API to list device templates, show device template configurations, modify device template configurations, and provision devices.

Supported Platforms

Table 4 shows the supported platforms for CiscoWorks NCM 1.5.

Table 4 Supported Platforms for CiscoWorks NCM 1.5

Vendor
OS
Version
Architecture

Microsoft

Windows Server, Enterprise Edition (32-bit and 64-bit)

2003

i386

Sun Microsystems

Solaris (patch 118833-36 or later)

10

Dual UltraSparc IIIi+, 1.3 GHz

Red Hat

RH AS 4 32-bit, and RH AS 5 32-bit and 64-bit

4 and 5

i386

SuSE

Enterprise Linux Server

10.0

i386



Note CiscoWorks NCM is a 32-bit application that runs in 32-bit mode on 64-bit operating systems.


The following operating systems are no longer supported:

Windows 2000

Solaris 9

Red Hat AS3

SuSE 9

While upgrading to CiscoWorks NCM 1.5, if you are moving from a deprecated operating system to a supported operating system, do the following:


Step 1 Back up the CiscoWorks NCM folder.

Step 2 Upgrade the operating system.

Step 3 Upgrade to CiscoWorks NCM 1.5.



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

While installing CiscoWorks NCM, the database can be installed on any platform.

Table 5 shows the databases that are supported by CiscoWorks NCM.

Table 5 Supported Databases for CiscoWorks NCM

Database
Notes

Oracle 10g (10.2.0.4) Standard Edition

If you are running CiscoWorks NCM in a Distributed System environment, you will need Oracle Enterprise Edition.

Microsoft SQL Server 2005 Standard Edition

 

MySQL 5.0.41 or later versions, including 5.0.58

MySQL 5.0.58 ships with CiscoWorks NCM.


CiscoWorks NCM supports 64-bit Oracle and SQL Server.

The following databases are no longer supported:

Oracle 9i and Oracle 9.2

Microsoft SQL Server 2000

MySQL 3


Note Existing MySQL 3.x databases can be upgraded to MySQL 5.0.41 or later using the MySQL Upgrade Installer. See the Installation and Upgrade Guide for CiscoWorks Network Compliance Manager 1.5 for more information.


While upgrading to CiscoWorks NCM 1.5, if you are moving from a deprecated version of the database, to a supported version of the database, do the following:


Step 1 Back up the CiscoWorks NCM database.

Step 2 Upgrade the database.

Step 3 Upgrade to CiscoWorks NCM 1.5.



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

Table 6 shows the database requirements for Oracle and Microsoft SQL Server in a High Availability Distributed System environment.

Table 6 Database Requirements for Oracle and Microsoft SQL Server

Database
Restrictions

Oracle Enterprise Edition 10.2.0.2 and 10.2.0.4

No more than five CiscoWorks NCM Cores can be configured.

SQL Server Standard Edition 2005 SP2 or higher

No more than two CiscoWorks NCM Cores can be configured. The maximum number of devices should not exceed 6,500.


See the High Availability Distributed System on Oracle Configuration Guide for CiscoWorks Network Compliance Manager or the High Availability Distributed System on Microsoft SQL Configuration Guide for CiscoWorks Network Compliance Manager for information on configuring High Availability Distributed System environment.

Table 7 shows the supported platforms for CiscoWorks NCM in Satellite environment.

Table 7 Supported Platforms for Satellite Environment

Vendor
OS
Version
Architecture

Red Hat

RHEL AS (32-bit)

3 and 4

i386

Novell

SuSE Enterprise Linux Server

9

i386

Sun Microsystems

Solaris (patch 118833-36 or later)

9 and 10

Sun Sparc



Note SuSE Linux 9 and Solaris 9 are supported on the Satellite remote gateway, however, these two operating systems are not supported in CiscoWorks NCM 1.5 Core.


See the Satellite User's Guide for CiscoWorks Network Compliance Manager for information on configuring a Satellite environment.

Table 8 shows the supported platforms for CiscoWorks NCM in a Virtual Environment.

Table 8 Supported Platforms for CiscoWorks NCM in Virtual Environment

Vendor
OS
Version

Sun Microsystems

Solaris Zones

10

VMware ESX 3.5 or 4.0

Windows

2003, SP1



Note Troubleshooting and performance issues related to VMware cannot be resolved via Cisco Support.


Keep the following in mind while running CiscoWorks NCM in Virtual Environment:

Running CiscoWorks NCM and the database in the same Virtual Environment is not recommended.

Running the database for the CiscoWorks NCM High Availability Core in Virtual Environment is not recommended.

The maximum number of devices is 3,000.

The maximum number of concurrent tasks is less than 20.

The minimum VMware Guest requirements include:

2.6 GHz CPU

4 GB dedicated RAM

40 to 60 GB HD

100 Mbps or higher dedicated Ethernet port

Linux RHEL AS 3 and 4

CiscoWorks NCM is not certified to run with Oracle in a VMware instance.

CiscoWorks NCM is not certified to run in an environment where VMotion is used with the Virtual Environment.

Additional Required Applications

You will need to install the following applications:

CiscoWorks NCM supports the following browsers:

Mozilla Firefox 2.0 or 3.0

Internet Explorer 6.x, 7.0


Note Mozilla Firefox 1.x is no longer supported.


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


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. We provide third-party contact information to help you find technical support. However, third-party contact information is subject to change without notice and, therefore, Cisco can in no way guarantee the accuracy of this contact information.


Hardware Requirements

CiscoWorks NCM requires the following minimum hardware:

Table 9 shows the hardware requirements for an application server.

Table 9 Hardware Requirements for Application Server

Component
Requirement

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 10 shows the hardware requirements for a database server.

Table 10 Hardware Requirements for Database Server

Component
Requirement

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


Caveats

Please read the following usability issues before using CiscoWorks NCM 1.5.

RSA SecurID Support in CiscoWorks NCM 1.5

While using RSA SecurID 4.x 128-bit tokens with CiscoWorks NCM 1.5 for device authentication, you must use the RSA SecurID 3.x software token client with RSA SecurID 4.x 128-bit tokens for CiscoWorks NCM to successfully import devices.

VLAN Data Gathering Diagnostic

If you are running several diagnostics, including the VLAN Data Gathering diagnostic, on a device that does not support the VLAN Data Gathering diagnostic, there is no Session Log available for that task.

Workaround: Remove the VLAN Data Gathering diagnostic from the task.

Stopping the CiscoWorks NCM Management Engine on a Solaris platform

While running CiscoWorks NCM on a Solaris platform, if you select the Start/Stop Services option from the Admin menu, and then select the Stop option for the Management Engine, the CiscoWorks NCM Management Engine (also referred to as the CiscoWorks NCM server) is not stopped.

Workaround: Go to the operating system and run /etc/init.d/truecontrol stop

VLAN Searches

Previously saved VLAN searches are not valid in CiscoWorks NCM 1.5 due to the addition of new VLAN features. If you try to view a saved VLAN search, you could see the following error message:

Error executing query VLAN: PortInVlanName is not a valid field name for this query.

Workaround: Remove the VLAN search and re-create a new VLAN search.

Uploading Large Image Files

Currently, CiscoWorks NCM is limited to uploading device configurations less than 250MB.

Provision Device Task

Although the Provision Device task enables you to select more than one device, the task only works with one device. Attempting to select more than one device or a device group, using the Device Selector will cause an error.

Using Firefox 2.0

For most versions of Firefox 2.0, the browser crashes when you try to expand the Device Selector or Device Group Selector.

Workaround: Upgrade to Firefox 2.0.0.19 or higher.

Device Selector Display

Some of the Device Selector display features might not work properly in Internet Explorer 6 due to browser limitation.

Workaround: Upgrade to Internet Explorer 7.

Security Partitions

While modifying Security Partition details, if you save the Security Partition before the Device Selector loads, you will lose all the devices from that Security Partition.

Canceling Tasks

If you cancel a task that is currently communicating with a device, CiscoWorks NCM will mark subsequent attempts to run the task (or similar tasks) as skipped. This could happen even if communication between the task and the device seem to be hung and you are waiting for a timeout.

This issue can occur if CiscoWorks NCM is trying to end communication between the task and the device before actually canceling the task. Because of this, CiscoWorks NCM will continue to execute the task until that point is reached. Any attempt to rerun the task before it is canceled will appear to CiscoWorks NCM as if the task is already in progress. Therefore, CiscoWorks NCM will mark the new task as skipped. You must give CiscoWorks NCM ample time to process the canceled task. Once that has occurred, CiscoWorks NCM will be able to rerun the task.

Using the $tc_device_enable_password$ Variable in Command Scripts

While using the $tc_device_enable_password$ variable in a command script, if the device enable password contains an at sign (@) character, the at sign character will be preceded by a backslash.

Device Managed IP Addresses Page

Changes made to the Device Managed IP Address are not reflected properly in the Device Managed IP Address page.

Workaround: Click the Reset Last Used IP link in the Device Managed IP Addresses page.

Setting Parent Task Priority

If you change the priority of a parent task that is currently running, any existing child tasks that are in the Pending or Waiting state will appropriately change their priority. However, child tasks that have not been created yet or are in other states, such as Running or Paused will retain the parent task's original priority. If a parent task is not running and its priority is changed, all child tasks take the new priority.

Duplicate VLANs Displayed in Layer 2 Diagrams

While drawing VLANs diagrams, if a VLAN includes an IP address, both the VLAN name and the VLAN ID are included in the VLAN port table. Duplicate VLANs could be displayed in Layer 2 diagrams because CiscoWorks NCM assumes that the VLAN name and the VLAN ID refer to different VLANs.

Using LDAP Servers

If you are using a LDAP server for external user authentication, you might need to modify certain LDAP related options in the appserver.rcx file. The default settings will work with the ActiveDirectory server under most situations. However, for other types of LDAP servers (depending on the LDAP schema configurations), you might need to customize the following settings if you are experiencing issues with the default settings:

<!-- Attribute mapping for Generic LDAP server-->

<option name="ldap_server/attr_mapping/Generic/group_search">group,organizationalunit, container,groupOfUniqueNames</option>

<option name="ldap_server/attr_mapping/Generic/group_name">name,cn,commonName</option>

<option name="ldap_server/attr_mapping/Generic/member_search">member,uniqueMember </option>

<option name="ldap_server/attr_mapping/Generic/username_search">samAccountName,uid,cn </option>

You can ignore the following settings:

<!-- Attribute mapping for SunLDAP server-->

<!-- Attribute mapping for OpenLDAP server-->

The group_search option specifies the list of LDAP entries to be searched for LDAP groups. This information is used in Step 3 of LDAP Setup Wizard, where you define the LDAP groups whose members are allowed to login to CiscoWorks NCM.

Consult your LDAP administrator to ensure that the list contains all necessary group attributes. For example, it might be necessary to add groupOfName to the list for the LDAP group search to work properly.

The same concept applies to username_search and member_search options. Both of these are used during the CiscoWorks NCM login process to identify the user and to determine the user's group memberships. If the default LDAP attribute names do not match your LDAP schema configuration, change them accordingly.

Testing OpenLDAP User Authentication

While configuring OpenLDAP for CiscoWorks NCM user authentication, the Test function might not work. In this case, save all the options before testing if they work.

Device Relationships

Scripting to a vSwitch is done via direct API calls to the containing ESX server. As a result, the scripts modify the ESX server settings that are not related to the vSwitch. This is true even if MSP permissions are granted only to the vSwitch.

Running CiscoWorks NCM on a Solaris Platform

While starting the CiscoWorks NCM server on a Solaris platform, there is a possibility that the CiscoWorks NCM server will crash due to an error in the native frame_sparc.cpp file. This is due to a bug in the Solaris JVM Biased Locking feature.

Workaround: Add the following VM argument to the jboss_wrapper.conf file located in NCM_INSTALLED_DIR/server/ext/wrapper/conf:

wrapper.java.additional.#=-XX:-UseBiasedLocking

Where # is the next number in sequential order of all parameters. For example, if the jboss_wrapper.conf file has the following arguments, the workaround VM argument would be number 6.

wrapper.java.additional.1=-DTCMgmtEngine=1 wrapper.java.additional.2=-Duser.dir=C:\NA\server\ext\jboss\bin wrapper.java.additional.3=-Xmn170m wrapper.java.additional.4=-Djava.awt.headless=true wrapper.java.additional.5=-Dfile.encoding=UTF8 wrapper.java.additional.6=-XX:-UseBiasedLocking

Viewing VLAN Information for a Port/Interface

While viewing device MAC Addresses details on the MAC Address Details page, the VLAN field is not populated.

Workaround: To display VLAN information for a port or interface, click the Port Name link for that port on the MAC Address Details page. The Interface Details page will appear. Scroll down to the Member VLANs field to view the VLAN information.

Using Active Directory

If you are using Active Directory, you must modify the corresponding options in the appserver.rcx file to include the correct attributes in the search mapping session. To do this:

1. In the appserver.rcx file, locate <!-- Attribute mapping for Generic LDAP server--> session.

2. Make sure that:

groupOfName is included in the group_search

uid is included in the username_search

member is included in the member_search

3. Save the changes to the appserver.rcx file.

4. Restart the CiscoWorks NCM server.

Using ActiveState ActivePerl on Windows

Due to limitations of ActiveState ActivePerl on Windows, if you use this environment you will not be able to use SSH connections with the CiscoWorks NCM Perl API.

Workaround: Install the CiscoWorks NCM client on a supported Linux or Solaris system and run the CiscoWorks NCM Perl API from that system.

Including URLs in Policies

When you create a policy and include a vendor solution URL or a vendor advisory URL, the URL must start with the http:// prefix. Otherwise, the link might not be correctly interpreted by the browser. If the URL field is left blank, the link could open the CiscoWorks NCM Home page.

Java Plug-in Version

If the Connect function fails and the CiscoWorks NCM server hangs, check the version of Java that you are running on your Windows system. This is an issue with the Java Plug-in of your Web browser. This issue is not due to the CiscoWorks NCM server.

To check the Java version that you are running on your system:

1. Choose Start  > Control Panel.

2. Double-click Java.

3. In the General tab, click the About button.

If you have Version 6 Update 11 or later, you must install an older JRE on your Windows system. This issue will not occur in Version 6 Update 10 and earlier.

Using the Device Group Selector

Some Chinese characters will not be displayed while using the Device Group Selector.

Using CiscoWorks NCM with NNMi

When you add a device manually to CiscoWorks NCM that is managed by NNMi, and navigate from NNMi to the device in CiscoWorks NCM, whether via an SNMP trap or the Actions menu, an error message (indicating that the NNMi UUID is unknown) is displayed.

Workarounds:

1. Remove the device from CiscoWorks NCM, then add the device to NNMi, and run the Import task to import the device into CiscoWorks NCM.

2. Choose Administrative Settings  > Server  > Device Import and set the Overwrite Existing Devices option to yes and then run the NNMi Import task.

Creating Advanced Perl Scripts

While creating an advanced Perl script, remember that CiscoWorks NCM treats variables that do not have space in between them as reserved variables. If you use $-pairs in the script for non CiscoWorks NCM variables, separate them with a space.

For example:

Incorrect: my($host,$port,$user,$pass) = ('localhost','$tc_proxy_telnet_port$', '$tc_user_username$','$tc_user_password$');

Correct: my($host, $port, $user, $pass) = ('localhost','$tc_proxy_telnet_port$', '$tc_user_username$','$tc_user_password$');

Error When Viewing Results for Diagnostics with Single Quotes in their Name

When a diagnostic is created with single quotes in its name, for example `Ana's Diagnostic', the diagnostic results are not displayed for that device, .

Workaround: Do not use single quotes in diagnostic names.

Diagnostic Name Limit

CiscoWorks NCM allows you to enter up to 100 characters while naming a diagnostic. However, CiscoWorks NCM allows only 50 characters for the name, while running the diagnostics.

Workaround: Limit diagnostic names to 50 or less characters.

Using SCP with Devices in Remote Realms

Devices in remote Realms cannot use the Secure Copy (SCP) Transfer Protocol because the remote Gateway Satellite Agent cannot use SSH/SCP port 22. The Gateway OS uses the SSH/SCP port 22.

Workaround: Disable SCP for devices in remote Realms.

MySQL Install and Upgrade

If you are using a MySQL database and MySQL is installed or upgraded on a CiscoWorks NCM build generated prior to February 5, 2009, do the following:


Step 1 Stop CiscoWorks NCM services.

Step 2 On Windows, open the my.ini file (under the MySQL Install folder). On Solaris or Linux, open the /etc/my.cnf file.

Step 3 Search for max_allowed_packet.

If not found, append max_allowed_packet=16776192 to the bottom of the file. If found, change its value to 16776192.

Step 4 Restart MySQL.

Step 5 Restart CiscoWorks NCM services.


Solaris and SecurID

Configuring CiscoWorks NCM to use SecurID as the authentication method can cause the management service to crash. The SecurID libraries provided by RSA cause this problem. Currently, this problem occurs on Solaris 10 with a version string, SunOS 5.10 Generic_118833-22. However, SunOS 5.10 Generic_120011-14 version works fine.

Workaround: Update your OS to SunOS 5.10 Generic_120011-14 version, if you are experiencing problems with SecurID on Solaris.

Using SCP on Linux and Solaris

The SCP Transfer Protocol enables you to securely transfer files between a local and remote host or between two remote hosts using the Secure Shell (SSH) protocol.

While using SCP on a Linux platform, you need to modify your system's SSH daemon (SSHD) to run on an alternate port and restart the SSHD service. Port 8022 is recommended.

After reconfiguring the system's SSHD, restart the CiscoWorks NCM to bind it to Port 22. Use the following to login via the system's SSHD:

ssh -p 8022 username@host


Note Use ssh username@host for a direct connection to the CiscoWorks NCM proxy.


After logging into CiscoWorks NCM, navigate to the Device Access page. Enter the SSH Username and SSH Password in the SSH Device Access field. The device driver will use this information while copying the files to the CiscoWorks NCM server.

The device specific settings must be configured to enable SCP and SSH to function properly. In addition, the device and the device driver must support SCP to use the CiscoWorks NCM SSH server for SCP.

The SCP connection must be made to the managing CiscoWorks NCM server to use SCP with remote Realms. A SCP connection to the CiscoWorks NCM Gateway will not succeed if the CiscoWorks NCM Gateway runs the Linux and Solaris system SSHD.

The CiscoWorks NCM Gateway sets the host as the CiscoWorks NCM Gateway. This can be overridden by setting the access variable (TFTPServer) to the IP address of the managing CiscoWorks NCM Core. See the User's Guide for CiscoWorks Network Compliance Manager 1.5 for detailed information.

Using SCP

The SSH protocol runs on port 22. By default, Linux and Solaris installs run on port 8022. Windows installs run on port 22.

For Windows installs, if the port is switched to 8022, there could be connectivity issues. This issue is uncommon because most devices do not allow for the specification of an alternate port.

SCP will not work if the device is in a remote Realm and access to the device is managed via a CiscoWorks NCM Satellite. You must run the CiscoWorks NCM SSHD proxy on port 22.

If you use port 8022 on any platform, SCP copies from a device to CiscoWorks NCM will not work. Refer to the Satellite User's Guide for CiscoWorks Network Compliance Manager for information on configuring CiscoWorks NCM Satellites.

Using a Non-English Operating System

While running CiscoWorks NCM on a non-English operating system, unreadable text is displayed in the Password Information section of the Edit Device page, when you select a Partition from the drop-down menu.

Auto-remediation Scripts

While creating an Auto-remediation script on the New Policy Rule page, if you input extended characters in the Rule Conditions field, it will produce unreadable text.

Proxy Interface

If you login to CiscoWorks NCM as a limited access user and attempt to connect to a device via the proxy interface, you will be dropped at the username/password prompt.

Searching for Diagnostics

CiscoWorks NCM Topology Data Gathering diagnostic has two options: CiscoWorks NCM Topology Data Gathering and Topology. Selecting either of these options will only search for the CiscoWorks NCM Topology Data Gathering diagnostic.

SNMP Timeouts

Using SNMP device discovery over networks with latency can cause SNMP timeouts. To resolve this issue:


Step 1 Login to CiscoWorks NCM.

Step 2 Choose Admin > Administrative Settings > Device Access.

The Device Access page appears.

Step 3 Scroll down to the Detect Network Devices Task Settings section and set SNMP Timeout to a higher value (for example, 2500 milliseconds).


-sync Option

When you enable the Workflow and run a CLI or API task with the -sync option, the task will fail and the following error message is displayed:

No such directory

Database Passwords

CiscoWorks NCM does not accept multiple dollar signs ($$). If the password that you use to connect to the database contains multiple dollar signs, you must modify the password before installing CiscoWorks NCM.

Installation Address

The IPv4 address range 169.254.0.0/16 is reserved for link-local usage (referred to as Automatic Private Internet Protocol Addressing (APIPA), by Microsoft) and is not an applicable address range for CiscoWorks NCM. For more information, refer to http://www.ietf.org/ (rfc3330 and rfc3927).

SSH Communication

CiscoWorks NCM 1.5 uses a new set of keys for SSH communication. In previous releases, CiscoWorks NCM used only one Digital Signature Algorithm (DSA) key for all installations.

When you install CiscoWorks NCM, it creates two new 1024 bit keys. The first key uses the DSA algorithm. The second key uses the RSA algorithm. These keys are used when you connect to CiscoWorks NCM via SSH.

Custom Data Setup

The Custom data field in the Custom Data Setup page accepts alphanumerics and underscores. Though you can use dashes, custom data field names with dashes cannot be used for the tc_device_custom device variables in custom scripts.

Advanced ACL Scripts

If you use the Update Script button while specifying an advanced ACL script, the variables are not updated when the script is run or re-run.

Workaround: Avoid using the Update Script button with advanced ACL scripts.

Use of Dollar Signs ($) in Scripts

If the script generated from a Telnet/SSH session log, contains dollar signs ($) in the executed commands, the script will fail or perform in unexpected ways.

OS Analysis Task

While using CiscoWorks NCM in an environment with overlapping IP addresses, the OS Analysis task is not supported for devices behind the remote Realm gateways.

OS Analysis tasks run on the devices that are located in the locally reachable network. Because of this, there is a possibility of error in the image recommendation generated for the devices behind the gateway.

CiscoWorks NCM will report OS recommendations for a device in the default Realm instead of a remote Realm if they share an IP address.

Device Tasks Ignores the User-defined enforce_save Device Variable

Device tasks that modify a device's configuration ignore the enforce_save device access setting. Because of this, startup configuration is always set as the current configuration.

Workaround: The DeviceInteraction/EnforceConfigurationSave/ConfiguringModels configuration option (in appserver.rcx) can be set to false. In this way, startup configuration is not run for all device tasks that reconfigure the device.

Email Report Task

While scheduling an Email Report task, if you select a report other than Summary Reports in the Reports To Run field, the task is reported as failed. However, the report is successfully emailed to the recipient. You can ignore the error message.

Template Scripts

While using template scripts, selecting the Run Again option will rerun the same script.

CiscoWorks NCM Core Gateways

You cannot configure redundant CiscoWorks NCM Core Gateways in the same CiscoWorks NCM Realm as a single CiscoWorks NCM Core.

Workaround: Edit the adjustable_options.rcx file and add the IP addresses of other CiscoWorks NCM Core Gateways.

Example:

<array name="rpc/allowed_ips">

<value>10.255.54.10</value>

</array>

Potential for Task Failure while Using Reserved CiscoWorks NCM Characters in Device Prompts

There are 11 characters that have special meaning in CiscoWorks NCM:

Opening square bracket ( [ )

Opening round bracket and the closing round bracket ( ( ) ).

Backslash ( \ )

Caret ( ^ )

Dollar sign ( $ )

Period or dot ( . )

Vertical bar or pipe symbol ( | )

Question mark ( ? )

Asterisk or star ( * )

Plus sign ( + )

If you use these characters in a device prompt, null pointer exception errors could occur during task execution. As a result, the task will fail. These characters should not be used while naming devices that interact with CiscoWorks NCM.

Oracle Database Errors Cause Failed Tasks and Other Issues

Oracle database errors causes tasks to fail and other issues due to a bug in the JDBC Oracle driver. You could get the following error message:

OALL8 is in an inconsistent state.

Workaround: Update your version of Oracle Database Server.

ACLs with the Same Name, but Different Case in CiscoWorks NCM, is Not Recommended

CiscoWorks NCM supports case-sensitivity in ACL names. Therefore, you can have two ACLs with the same name, but different case.

If you delete one of those ACLs, all ACLs with the same name are deleted, regardless of the case. Cisco does not recommend multiple ACLs with same name, but with differing case in CiscoWorks NCM.

Use of the Dollar Sign ($) in Perl Code

If you convert a Telnet/SSH Proxy session that contains a dollar sign ($) to Perl, CiscoWorks NCM does not properly interpret the dollar sign in the generated Perl code.

Workaround: Edit the script and add a backslash (\) in front of the dollar sign.

Downloading Software Images from Cisco.com

You can download software images from Cisco.com for devices that are not currently in your CiscoWorks NCM system. However, you may need to modify the driver or model information or both to successfully deploy the software image.

Workaround:

To successfully deploy the software image:


Step 1 Choose Devices > Device Tools > Software Images.

The Software Images page opens.

Step 2 In the Action column, click Edit next to the software image that you want to modify.

The Edit Software Image page opens.

Step 3 In the Image Set Requirements field, modify the driver and model information to be compatible with the device in CiscoWorks NCM.

Step 4 Click Save Software.


High Availability Distributed System: Importing Devices

If you import two devices with identical IP addresses into two separate CiscoWorks NCM Cores, at approximately the same time, you cannot detect if there is a duplicated device.

Workaround: Manually run the Deduplication task after importing devices. One device will be automatically de-duplicated and set to Inactive state. (See Chapter 7, Scheduling Tasks, in the User's Guide for CiscoWorks Network Compliance Manager, 1.5 for information on running the Deduplication task.)

High Availability Distributed System on SQL Server

If you see a conflict for which the reason_text field does not reference a constraint name, it is possible that CiscoWorks NCM automatically resolved the conflict. However, you might have to manually resolve the conflict. The following is an example of a reason_text field for a conflict that does not reference a constraint name:

reason_text A row insert at 'red-dalmssql102.ds2880db2' could not be propagated to 'RED-DALMSSQL101.ds2880db1'. This failure can be caused by a constraint violation. The merge process was unable to synchronize the row.

If the conflict is automatically resolved by the CiscoWorks NCM, simply delete the conflict. If the conflict is not automatically resolved, make the appropriate corrections and then delete the conflict.

Detect Network Devices Task

The CiscoWorks NCM prevents you from inadvertently running more than one Detect Network Devices task concurrently. Although the Detect Network Devices task generates only a minimal level of traffic, CiscoWorks NCM provides this protection to minimize additional traffic while running duplicate or additional Detect Network Devices tasks simultaneously.

If a second or third Detect Network Devices task is scheduled while an earlier Detect Network Devices task is running, CiscoWorks NCM will place the new tasks in the Waiting state. The tasks will be run individually after the first Detect Network Devices task has completed.

Batch Editing Parent Device Groups or Device Groups with No Devices Results in Invalid Error Message

When you batch edit parent device groups or partitions that have no devices, the following error message is displayed:

You do not have Modify Device Permission for any of the devices you selected.

Workaround: To batch edit all devices in a parent device group, do a batch edit against each child group in the parent device group.

Diagramming

CiscoWorks NCM applies an absolute value for the text height attribute of interface and port labels shown in Visio diagrams.

When the Visio VDX file is loaded, Visio assigns an incorrect formula to the text height attribute. As a result, when you have more than two lines of annotated text, for example, a label for an interface or port and you attempt to copy and paste the label, the label of the new interface or port is not properly displayed.

Workaround: Click the Text Tool option on the Visio tool bar and move the label to expose the interface or port icon.

Passing Your CiscoWorks NCM Password to Advanced Scripts

While using advanced scripts, $tc_user_password$ does not work.

Workaround: Use $Password$ instead of $tc_user_password. $Password$ can only be used in the Parameters part of the advanced script. You need to add the code to your script to get the password from the command line arguments when the script runs.

High Availability Distributed System Performance

While running a Distributed System, if you are deleting many objects simultaneously, the system may take a while to process the transactions for large delete operations.

High Availability Distributed System External Authentication

While using external authentication in a High Availability Distributed System environment, the External Authentication Type, for example, TACACS+ or Active Directory, is global (shared between all CiscoWorks NCM Cores). Authentication server information is CiscoWorks NCM Core specific.

Workaround: Set the External Authentication Type to None in the User Authentication page. Configure each CiscoWorks NCM Core individually with authentication server information or Active Directory setup. After all CiscoWorks NCM Cores have been configured, set the External Authentication Type on any CiscoWorks NCM Core. The External Authentication Type setting is replicated on all CiscoWorks NCM Cores.

RADIUS External Authentication

When a user tries to authenticate using RADIUS, if the RADIUS server does not respond, CiscoWorks NCM still authenticates the user against the CiscoWorks NCM local password. This happens even if you configure CiscoWorks NCM to not to fail-over on external authentication.

Scripts: Output Results in HTML Format

While executing an advanced script or a Run External Application task, any text that the advanced script or external application writes to stdout stream is stored in CiscoWorks NCM as the task result. If your script output begins with anything other than <html>, the script results will be treated as plaintext.

Nmap Scanning

Careful consideration should be taken while identifying the network range you are going to scan. Some network topologies can result in very long scans.

In addition, it is recommended that you do not scan Internet addresses. If you think your Nmap scan will take more than a few minutes, you can use the following Nmap options to limit the scanning time:

max_scan_delay milliseconds

where milliseconds is a value between 1 and 1000. .

Nmap settings can be changed by using the Administrative Settings option. See the Nmap documentation at www.insecure.org for detailed Nmap information.

SecurID Software Token Software, Version 3.x

If the CiscoWorks NCM server is installed with the 3.x SecurID token software, turn off copy protection while exporting SecurID software token keys on the RSA server. Otherwise, CiscoWorks NCM reports an error while accessing SecurID software tokens.

A patched version of the SecurID software is available at RSA's website http://www.rsasecurity.com.

Canceling or Deleting Tasks

Some CiscoWorks NCM tasks will spawn external processes to run PERL or Expect scripts, or to run user-provided executables or shell scripts. Under certain circumstances, CiscoWorks NCM may not be able to kill these external processes, when the spawning task is cancelled or deleted.

Workaround: Manually stop the external process on the CiscoWorks NCM server.

Deploy to Startup Config and Reboot not Supported via SNMP

CiscoWorks NCM can deploy a configuration file to the startup configuration and reboot the device via command line only. If the device is configured for only SNMP access, deploy startup and reboot will fail.

Tasks: Running External Application Tasks Presents a Possible Security Risk

All Run External Application tasks run the application with root (UNIX) or system (Windows) privileges. This is a potential security risk that should be acknowledged by the system administrator before using the Run External Application feature.

Tasks: A Task Scheduled for the 31st Might Run on the 1st

If you schedule a monthly recurring task for the 31st of every month and that task runs during a month that has less than 31 days, CiscoWorks NCM will run the task on the 1st, 2nd, or 3rd day of the next month depending on the number of days in the previous month. For example, if you schedule a task in February (with 28 days) for the 30th, the task will actually run on March 2nd.

Workaround: If you want to run the task on the last day of the month, you must set the date correctly.

Inventory: Data from Device Overwrites Manually Entered Values

Certain data on the Device Details page is auto-populated. If you manually change the data, CiscoWorks NCM overwrites the values when the next snapshot occurs.

The automatically populated data includes:

Domain Name

Host Name

Model

Serial Number

Location

Vendor

Console Server: SSH Access is not Supported

CiscoWorks NCM does not support console server access via SSH. If you use a console server to access a device, you must use the Telnet connectivity.

If you select the Use To Access Device option in the New Device page or Edit Device page, you should also select the Telnet option in the Connection Information section.

Sending Reports to External Email Addresses

Sometimes, the SMTP server will be configured to reject messages from the CiscoWorks NCM server address. In this case, the CiscoWorks NCM messages would not be delivered and you would see the following error message:

Error occurred when sending email. Please check the email address and/or your SMTP server settings.

If this occurs, you need to configure the SMTP server to enable the CiscoWorks NCM server to relay email messages through it.

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 Cisco.com 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.



Note The Docs tab provided in the CiscoWorks NCM UI might not include links to the latest documents.


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.

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].