Guest

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager 1.7.03

  • Viewing Options

  • PDF (229.7 KB)
  • Feedback
Release Notes for CiscoWorks Network Compliance Manager 1.7.03

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.7.03

Contents

Introduction

Installing the CiscoWorks NCM 1.7.03 Patch

Post-Installation Steps

Uninstalling the CiscoWorks NCM 1.7.03 Patch

What's Been Fixed in CiscoWorks NCM 1.7.03

Additional Information

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


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

CiscoWorks NCM 1.7.03 is a patch release that you can install on top of CiscoWorks NCM 1.7,1.7.01 and 1.7.02.


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.7.03 Patch

Uninstalling the CiscoWorks NCM 1.7.03 Patch

What's Been Fixed in CiscoWorks NCM 1.7.03

Additional Information

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.

Installing the CiscoWorks NCM 1.7.03 Patch

On a standalone NCM core, install the NCM patch as follows:


Step 1 On the NCM server, unzip the patch bundle.

Step 2 From the command line, run the patch script.

For Windows, run the following command:

     patch.bat 
 
   

For Linux or Solaris, run one of the following commands:

     sh patch.sh
     ./patch.sh

Note The patch process creates a patch.log file in the NCM_HOME>/server/log directory. In the event of an error during the patch installation process, the error is logged to this file.


Step 3 Complete the Post-Installation Steps, below.

In a Multimaster or Horizontal Scalability environment, install the NCM patch as follows:


Step 1 On each NCM server in the environment, stop all NCM services.

Step 2 Apply this patch to each NCM server.

a. On the NCM server, unzip the patch bundle.

b. From the command line, run the patch script.

For Windows, run the following command:

        patch.bat
 
   

For Linux or Solaris, run one of the following commands:

        sh patch.sh
        ./patch.sh

Note The patch process creates a patch.log file in the <NCM_HOME>/server/log directory. In the event of an error during the patch installation process, the error is logged to this file.


Step 3 In a Horizontal Scalability environment, complete the steps for Fix QCCR1D95740.

Step 4 On all NCM servers, restart the NCM services.

Step 5 Complete the Post-Installation Steps, below.

Post-Installation Steps

After installing the patch, do the following:

Clear the web browser cache for each user.

Redeploy the NCM satellite agent to each NCM satellite (remote gateway).

Uninstalling the CiscoWorks NCM 1.7.03 Patch

The root of the NCM installation directory contains a subdirectory named patch_backups that was created by the patch installer. In the patch_backups directory is a subdirectory named with the patch build number. This subdirectory contains a backup of all critical files changed by the patch installer. The backup.log file lists the files that were backed up and the original location of the files.

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


Step 1 Stop the NCM services.

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 as described in "Upgrading to Java JDK Version 6 Update 29" in the NCM Administration Guide.

Step 5 Restart the NCM services.


What's Been Fixed in CiscoWorks NCM 1.7.03

Table 1 describes the issues fixed in CiscoWorks NCM 1.7.03.

Table 1 Issues Fixed in CiscoWorks NCM 1.7.03

Bug ID
Bug Summary

QCCR1D90952

Device configuration comparison does not work for large configurations. See Fix QCCR1D90952 for more details.

QCCR1D95740

Provide NCM core failover for Horizontal Scalability environments (includes QCCR1B89039 and QCCR1B99448). See Fix QCCR1D95740 for more details.

QCCR1D100822

Cancelling a parent task does not cancel the child tasks

QCCR1D108098

The CLI is case-sensitive for hostnames

QCCR1D120216

Track how long a device has been out of compliance

QCCR1B86926

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

QCCR1B89802

Very high memory usage

QCCR1B90798

Performance problems with topology queries (MySQL)

QCCR1B91836

Task Information page for an Auto-Remediation script contains HTML tags in the Comments area

QCCR1B93540

Exception thrown when checking "list active policies only"

QCCR1B93693

Unable to run command script from Event Notification and Response Rules

QCCR1B94014

Add the NCM Core designation to all Task pages in the NCM console

QCCR1B94062

Distributed round-robin task scheduling does not work as documented

QCCR1B94556

The storage used by the "RN_DEVICE_DATA" table is growing much faster expected (VLAN text)

QCCR1B94763

audit_log.txt file grows without bounds with syslog messages; NCM cannot process any tasks

QCCR1B94918

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

QCCR1B94964

Command scripts run in enable mode execute the write mem command

QCCR1B95710

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

QCCR1B95956

Uptime report is inaccurate

QCCR1B96076

Syslog Change Detection DNS Lookup. See Fix QCCR1B96076 for more details.

QCCR1B96788

Diagnostic Import does not appear to be working

QCCR1B96789

Excessive RMI exceptions when the remote NCM core is not responsive

QCCR1B96817

Advanced Perl script converted from telnet session does not work for devices that use a JavaScript driver

QCCR1B96967

Application performance increasingly slow, requiring daily reboot

QCCR1B97059

Provide case-insensitive search for an Oracle database (includes QCCR1D112101, QCCR1B92143, and QCCR1B102817). See Fix QCCR1B97059 for more details.

QCCR1B97129

Diagramming does not work correctly

QCCR1B97183

CiscoCatNative: the snapshot failover from SCP to TFTP does not work correctly. See Fix QCCR1B97183 for more details.

QCCR1B97378

Diagrams do not show links or connections for Layer 1, Layer 2, or Layer 3. See fix Fix QCCR1B97378 for more details.

QCCR1B97470

Automatically cancel a task that has been running for a particular time frame

QCCR1B97530

truecontrol-client.jar throws local class incompatible: stream. See Fix QCCR1B97530 for more details.

QCCR1B97575

Policy rule conditions evaluated unnecessarily

QCCR1B97638

Provide a way to print compliance policies and rules. See Fix QCCR1B97638 for more details.

QCCR1B97785

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

QCCR1B97850

Compliance checks for new diagnostic policy do not give the expected results

QCCR1B97866

Dynamic Group Updates failing intermittently

QCCR1B97910

Missing deviceID input from WSDL APIs

QCCR1B98753

Last Access Time and Last Snapshot Result show wrong values. See Fix QCCR1B98753 for more details.

QCCR1B98835

Update SWIM library

QCCR1B98947

Scheduled tasks run too long without completion

QCCR1B99061

Scheduled tasks deleted unexpectedly

QCCR1B99464

Link for "Other End" shows incorrect data

QCCR1B99618

Script text box does not display after searching devices/groups

QCCR1B99700

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

QCCR1B99740

Expect does not set timeout

QCCR1B99755

Update Device Software task cannot be saved when the software to load includes a file with the .bin extension

QCCR1B99974

VLAN search results are not predictable

QCCR1B100040

NNMi-NCM integration: NCM device name is set to the IP address after export from NNMi to NCM. See Fix QCCR1B100040 for more details.

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)

QCCR1B100359

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

QCCR1B100592

Rule Exception Expire Date field needs to include future years

QCCR1B100711

Perl script fails on JavaScript driver EXT_CheckPointJS

QCCR1B100856

Command script run by a user with custom permissions throws NPE

QCCR1B100967

Very large number of error messages filling jboss_wrapper.log when running large Diagnostic tasks

QCCR1B101286

A subset of NCM users should be able to connect to devices using the AAA password only, not the device-specific and password rule passwords stored in NCM. See Fix QCCR1B101286 for more details.

QCCR1B101416

Policy export fails when too many policies are selected

QCCR1B101426

Reports > Search For > Interfaces displays incorrect "Negotiated Duplex" information

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

QCCR1B101600

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

QCCR1B101701

User permission denial throws a Java exception

QCCR1B102133

Horizontal Scalability: Child tasks are not cancelled when the parent task never completes

QCCR1B102147

Advanced script does not use the last used password

QCCR1B102225

jboss issues

QCCR1B102226

WSDL operation show_device missing Site Name as output

QCCR1B102230

Cannot edit partition

QCCR1B102302

HPSA and TACACS+ authentication failover does not work when SA is unavailable

QCCR1B102338

Import deactivates device templates

QCCR1B102582

Connection through bastion host fails

QCCR1B102678

Search for device results in more devices when NNMiNodeUUID is selected than when it is not. See Fix QCCR1B102678 for more details.

QCCR1B103237

NCM import not updating console server port

QCCR1B103283

Problem exporting device passwords using tc_tools.sh

QCCR1B103347

Reroute to NCM logon page loses the target link. See Fix QCCR1B103347 for more details.

QCCR1B103620

Provide a monitor to detect tasks that have been running for a long time

QCCR1B103778

LDAP Setup Wizard should support Generic LDAP and SSL

QCCR1B103910

Issue with addins directory

QCCR1B103438

Process for creating the full-text search index takes too long. See Fix QCCR1B103438 for more details.

QCCR1B104046

Horizontal Scalability: Optimize the scheduler for task failover

QCCR1B104125

Issue with selecting device on run command script

QCCR1B104158

Compliance search "View Search Result as CSV File": unchecked policy rule displayed as 'Yes' for Rule Compliance, instead of "Not Checked Yet"

QCCR1B104783

WSDL operation list_task output generates too much data

QCCR1B104937

Perl script will not save as "Auto Remediation" task

QCCR1B105172

Any user can edit other user-defined reports, regardless of permissions

QCCR1B105179

Compliance report CSV export results in discrepancies

QCCR1B105277

Runtime exception error in jboss_wrapper for RN_DeviceLastUsed duplicate records

QCCR1B105285

Configuration change report with "include result details" formatted incorrectly in CSV output

QCCR1B105323

UI error when clicking on A10 interface detail

QCCR1B105381

CLI discovery is failing; PollRead variable must be set for discovery task only, not for all NCM tasks. See Fix QCCR1B105381 for more details.

QCCR1B105383

Incorrect checkmark behavior while importing scripts, diagnostics, or compliance policies

QCCR1B105406

Duplicate results when searching in diagnostics

QCCR1B105535

connect command should not be case-sensitive

QCCR1B105546

- Policy import should fail if dependency (diagnostics) is missing

QCCR1B105606

- CiscoNexus driver is not running a 'copy run start' in a command script. See Fix QCCR1B105606 for more details.

QCCR1B105705

Some non-administrator users are unable to view device configurations

QCCR1B105871

Event Notification Rule not updating

QCCR1B105931

Permit special characters in policy name and description

QCCR1B106020

Permissions problem when creating a command from the configuration templates for a specific partition

QCCR1B106037

Global "Change Detection and Polling" settings and Driver Discovery

QCCR1B106226

Unable to re-run auto-remediation command script

QCCR1B106240

Problem with compliance search export

QCCR1B106265

View > Current Configuration does not always show correct configuration. See Fix QCCR1B106265 for more details.

QCCR1B106381

Dynamic device group membership computation should be triggered when case-sensitivity is changed

QCCR1B106595

Check Configuration Compliance Report shows policy rule passed, but manual run fails

QCCR1B106652

Add To Favorites feature does not work correctly

QCCR1B106660

Permit special characters in policy detailed description and solution

QCCR1B106800

CLI discovery is failing because of inconsistent responses from the device

QCCR1B106895

Using the NCM console without Flash for the device selector leads to un-editable task templates

QCCR1B107153

Diagnostic text and Configuration text search results limit to 1000 valid records (Diagnostic text column shows: "No configuration found for this device")

QCCR1B107274

Replication errors related to RN_INTERCEPTOR_LOG. See Fix QCCR1B107274 for more details.

QCCR1B107433

"The SNMPv3 Username is not set" error while applying password rule which does contain SNMPv3 username/credential information

QCCR1B107557

- Interface search results export includes HTML in the CSV output file. See Fix QCCR1B107557 for more details.

QCCR1B107580

Search for Compliance is not case-insensitive when Oracle Case-Insensitive is enabled

QCCR1B107581

Resolve FQDN task will not update already populated FQDN field. See Fix QCCR1B107581 for more details.

QCCR1B107585

NNMi-NCM integration: NNMi uses SNMP strings only from device-password rules

QCCR1B108089

Cannot run a compliance report CSV export without a failure

QCCR1B108341

CLI discovery is failing; permit adjustment of SSH buffer size


Additional Information

Some of the fixes detailed here require additional manual steps or .rcx file modifications. The .rcx files are located in the <NCM_HOME>/jre directory. Unless otherwise directed, it is recommend to make all changes to the adjustable_options.rcx file. Other files might be overwritten during an NCM upgrade.


Note Before modifying .rcx files, back up the current .rcx files to a location outside of the NCM directory structure. (NCM reads all .rcx files within the NCM directory structure.)


Fix QCCR1D90952

This fix provides a new configuration difference tool library.

To enable the new configuration difference tool, follow these steps:

1. Add the following line to the adjustable a_options.rcx file:

<option name="data/NewDiffTool">true</option>
 
   

2. Do one of the following:

a. Restart the NCM management engine.

b. Click [Save] on the Admin > Administrative Settings > User Interface page in the product console.

c. Run the "reload server options" command from the NCM proxy.

Fix QCCR1D95740

This fix provides NCM core failover in Horizontal Scalability environments. It includes revisions to the Task Load and Core List pages to display information about all NCM cores in the Horizontal Scalability environment. The information on the Core List page is dynamic and is recalculated each time the Core List page is opened or refreshed.


NoteBecause of this fix, if NCM runs in a Horizontal Scalability environment, you MUST complete the following configuration steps regardless of your intent to use the NCM core failover functionality.

NCM core failover is enabled by default. For information about disabling task failover, see the NCM1.7.03 Horizontal Scalability Guide. For information about obtaining the latest NCM Horizontal Scalability Guide, see Accessing the CiscoWorks NCM Documentation Set.


To re-enable Horizontal Scalability functionality after applying this patch, follow these steps:

1. Disable the JCS disk cache as described in the NCM1.7.03 Administration Guide.

For information about obtaining the latest NCM Horizontal Scalability Guide, see Accessing the CiscoWorks NCM Documentation Set.

2. On each NCM server, edit the distributed.rcx file as follows:

a. Add the following line:

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

b. If you want to enable distributed round robin, on each NCM server, add the following line:

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

3. On each NCM server, edit the site_options.rcx file as follows:

a. Locate the following option block:

<option name="distributed/run_tasks_locally">. . . <title>Allow this core to run 
all tasks created on it locally</title> . . . </option>
 
   

b. Immediately after the located option block, add the following lines:

<option name="distributed/round_robin_stop_task_running">false
       <title>Reserve this core for user interaction</title>
<section>Performance Tuning</section>
       <type>Checkbox</type>
       <comment>In a Horizontal Scalability environment that uses
       distributed round robin task assignment, do not run 
       regularly-scheduled or user-initiated device tasks on this
       core.</comment>
     </option>
 
   

4. On each NCM server, edit the appserver.rcx file as follows:

a. Locate the following line:

     <array name="distributed/core-specific-options">
 
   

b. Within the located array block, locate the following line:

<value>distributed/run_tasks_locally</value>
 
   

c. After the located line, add the follow value to the array block:

<value>distributed/round_robin_stop_task_running</value>
 
   

5. On all NCM servers, restart the NCM services.

Fix QCCR1B96076

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

To enable this fix, follow these steps:

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

<option name="syslog/hostname_colon_skip">true</option>
 
   

2. Do one of the following:

Restart the NCM management engine.

Click [Save] on the Admin > Administrative Settings >

User Interface page in the product console.

Run the "reload server options" command from the NCM proxy.

To verify the configuration change, set Device/Syslog to trace.

Fix QCCR1B97059

This fix provides case-insensitive search of many objects in the NCM database on Oracle only.

To enable this fix, follow the steps in "Enabling Case-Insensitive Search (Oracle)" in the NCM Administration Guide.

Fix QCCR1B97183

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, follow these steps:

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

     <option name="Access/SSH/SshCloseOnReadTimeout">true</option>
 
   

2. Restart the NCM services.

Fix QCCR1B97378

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 be reprocess existing records for cross referencing. This fix provides a way to force this cross referencing.

To enable this fix, follow these steps:

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

2. <!-- 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. -->

<option 
name="Diagnostics/Special/Topology/CrossReferenceExistingRecords">true</option>
 
   

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

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

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

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

Fix QCCR1B97530

This fix updates the <NCM_HOME>/client/truecontrol-client.jar file.

To enable this fix, copy the updated truecontrol-client.jar file for use in your external application.

Fix QCCR1B97638

This fix delivers a way to print policies from the NCM console. To use this functionaly, go to the Policies > Import/Export Policies page, select the policies to print, and then click [Print].

Fix QCCR1B98753

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, follow these steps:

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.

Fix QCCR1B100040

When the CiscoWorks NNMi-CiscoWorks NCM integration is enabled, synchronizing the NNMi topology with the NCM inventory populates the NCM hostname field with the device IP address. This fix corrects this problem for new devices added to the topology synchronization.

To update the NCM database with the actual hostname values for the previously synchronized devices, follow these steps:

1. Display the NNMi and NCM hostnames for devices in the NCM database by running the following command from the NCM proxy:

run checkdb -resolver nnmshow
 
   

2. Confirm that the NNMi hostnames are acceptable for all devices.

3. If all NNMi hostnames are acceptable, update the NCM hostnames with the NNMi hostnames by running the following command from the NCM proxy:

run checkdb -resolver nnmforce
 
   

This command modifies only those devices that have NNMi hostnames.

Fix QCCR1B101286

This fix adds the ability to limit some NCM users to using only their AAA credentials when connecting to devices from NCM. The affected users cannot use the device-specific passwords and the password rule passwords that are stored in NCM.

For information about enabling this functionality and configuring users with the limited access, see "Limiting Device Password Access" in the NCM Administration Guide.

Fix QCCR1B102678

When the CW NNMi-CW NCM integration is enabled, searching for devices in NCM might returned different numbers of devices with and without the inclusion of NNMiNodeUUID in the search. This fix prevents NCM from adding duplicate NNMiNodeUUID metadata records to the NCM database.

To remove existing duplicate NNMiNodeUUID metadata records from the NCM database, as the NCM database user, run the following command from the NCM proxy on one NCM server:

run checkdb -fix -resolver nnmuuid -verbose

Fix QCCR1B103347

After a user session has timed out, clicking a link in the NCM console redirects the user to the NCM log-on page. By default, logging on opens the NCM Home page, not the requested page.

With this fix, NCM loads the most recently requested page after a user successfully logs on in this scenario.

To enable this fix, follow these steps:


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

<option name="WebUI/RedirectToLastRequestedPage">true</option>
 
   

Step 2 Restart all NCM services.


Fix QCCR1B103438

This fix adds an option for running multiple threads while creating the full-text index of the NCM database on Oracle or SQL Server.

To enable this fix in preparation for enabling full-text search, follow these steps:


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

     <option name="fulltextsearch/parallel">T</option>

Step 2 Edit the newly-added line to replace T with the number of parallel threads. Possible values range from 1 to one less than the number of database server cores.

Step 3 Do one of the following:

Restart the NCM management engine.

Click [Save] on the Admin > Administrative Settings > User Interface page in the product console.

Run the "reload server options" command from the NCM proxy.


Note Enabling the database for full text search requires database downtime and available disk space. For information about estimating these requirements and enabling the "contains (full text)" search , see the NCM Administration Guide.


Fix QCCR1B105381

By default NCM does a blocking read on SSH connections for discovery tasks. This fix provides a configuration option that sets NCM to do polling-based reads on discovery task-related SSH connections.

To enable this fix, follow these steps:


Step 1 Consult with your Support representative to evaluate the impact of this change in your environment.

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

     <option name="Driver/Discovery/UsePollRead">true</option> 
 
   

Step 3 3. Restart all NCM services.


Note The option Access/SSH/ReadSleepTime is related to the Driver/Discovery/UsePollRead option as it determines the frequency of the polling. Access/SSH/ReadSleepTime is specified in milliseconds and defaults to 1000 ms (1 second).


Fix 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, do the following:


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

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

-->

   <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>
   <option name="DeviceInteraction/EnforceConfigurationSave/Port Scan">disabled</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/Add Device 
Context">true</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/Remove Device 
Context">true</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/OS Analysis">disabled</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/Provision 
Device">false</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/Batch Insert ACL 
Line">true</option>
   <option name="DeviceInteraction/EnforceConfigurationSave/Batch Remove ACL 
Line">true</option>

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

Step 3 Install the latest NCM driver pack, which is available from Network Compliance Manager (NCM) Driver Updates.

For more information, see "Configuring the Default Setting of the Enforce Save Check Box for New Tasks" in the NCM Administration Guide.

Fix QCCR1B106265

This fix updates the algorithm for determining which device configuration is the current configuration.

To ensure that the current configuration is correctly marked for each device in the NCM database, run the following command from the NCM proxy.

run checkdb -resolver currentconfig -verbose
 
   

The duration of this command is proportional to the number of devices in the NCM database.

Fix QCCR1B107274

Disconnecting from the NCM proxy immediately after connecting can cause replication errors in a Multimaster Distributed System environment. This problem is caused by a limitation with the Oracle database. This fix introduces a date offset to the end-date column in the RN_INTERCEPTOR_LOG table.

To enable this fix, follow these steps:


Step 1 On each NCM core, add the following line to the adjustable_options.rcx file:

<option name="proxy/mm_log_offset">1000</option>
 
   

This setting adds 1000ms (1 second) to the end date.

Step 2 Do one of the following:

Restart the NCM management engine.

Click [Save] on the Admin > Administrative Settings > User Interface page in the product console.

Run the "reload server options" command from the NCM proxy.


Fix QCCR1B107557

This fix updates the process for exporting interface search results to remove the <span> HTML tags from the CSV output file.

To enable this fix, follow these steps:


Step 1 In the adjustable_options.rcx file, locate the following line:

<option name="driver/perl_wait_timeout">0</option>

Step 2 After the line located in step 1, add the following line:

<option name="csv/remove/html">true</option>

Step 3 Do one of the following:

Restart the NCM management engine.

Click [Save] on the Admin > Administrative Settings > User Interface page in the product console.

Run the "reload server options" command from the NCM proxy.


Fix QCCR1B107581

This fix introduces a configuration option that changes the behavior of the Resolve FQDN task. When this fix is enabled, the Resolve FQDN task always overrides the FQDN field for each device. Unlike the Overwrite Existing Domain Names check box on the Administrative Settings - Server page, this fix does not impact the contents of the device hostname field.

To enable this fix, follow these steps:


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

     <option name="dnslookup/always_override_existing_fqdn">true</option> 

Step 2 Do one of the following:

Restart the NCM management engine.

Click [Save] on the Admin > Administrative Settings > User Interface page in the product console.

Run the "reload server options" command from the NCM proxy.


Supported Platforms

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

Table 2 Supported Platforms for CiscoWorks NCM 1.7.x

Operating System
Architecture
32-bit
64-bit 1

Windows Server 2008 R22

x86_64

 

X

Windows Server 2003 SP2

X86_32

X

 

Solaris 10 SPARC3 ,4

Sun4u, Sun4v

 

X

RedHat RH AS 45

x86_32

X

 

RedHat RHEL Server 5

x86_64

 

X

SuSE Enterprise Linux Server 10

x86_64

 

X

1 CiscoWorks NCM 1.7 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 NCM 1.7 on the Windows Server 2008 R2 operating system requires SP1.

3 Before installing CiscoWorks NCM 1.7 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).

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

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

Table 3 Supported Databases for CiscoWorks NCM 1.7.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.7 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.7 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.7.


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