Guest

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager 1.7.02

  • Viewing Options

  • PDF (154.3 KB)
  • Feedback
Release Notes for CiscoWorks Network Compliance Manager 1.7.02

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.7.02

Contents

Introduction

Installing the CiscoWorks NCM 1.7.02 Patch

What's Been Fixed in CiscoWorks NCM 1.7.02

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


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

CiscoWorks NCM 1.7.02 is a patch release that you can install on top of CiscoWorks NCM 1.7 or 1.7.1


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

What's Been Fixed in CiscoWorks NCM 1.7.02

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Additional Required Applications

Hardware Requirements

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

Introduction

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

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

Installing the CiscoWorks NCM 1.7.02 Patch

To install the CiscoWorks NCM 1.7.02 patch:


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

Step 2 Run the patch script.

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

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

% sh patch.sh

or

% ./patch.sh


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

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

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

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


Step 1 Stop the NCM Management Engine.

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

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

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

Step 5 Restart the NCM Management Engine.


What's Been Fixed in CiscoWorks NCM 1.7.02

Table 1 describes the issues fixed in CiscoWorks NCM 1.7.02.

Table 1 Issues Fixed in CiscoWorks NCM 1.7.02

Bug ID
Bug Summary
Fix Description

QCCR1D115581

Violations should be highlightes in the policy non-compliance email messages.

This problem has been resolved.

QCCR1D118702

Out-of-memory errors.

This problem has been resolved.

QCCR1B85988

Satellite monitoring fails with com/rendition/service/UserManager error

The satellite agent on the core site is updated. After installing the patch, re-deploy the satellite.

QCCR1B86526

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

This problem has been resolved.

QCCR1B89606

Import Diagnostics, Policies & Command Scripts issue

This problem has been resolved.

QCCR1B91014

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

This problem has been resolved.

QCCR1B91254

List of command scripts does not include site information

This problem has been resolved.

QCCR1B91466

The limits of custom data field extensions not stated correctly in the help.

This problem has been resolved.

QCCR1B91615

The group list performance is poor when the number of groups exceeds 500.

This problem has been resolved.

QCCR1B91670

Creating a New Event Notification & Response Rule does not save the subsystem information.

This problem has been resolved.

QCCR1B91786

Session processing problems.

This fix is required for safe session processing. However after a session times out, users can no longer return to the last page viewed before the session timeout.

QCCR1B92137

HTTP Method Processing Errors.

This problem has been resolved.

QCCR1B92142

Policy based on dynamic criteria creates a database problem.

This problem has been resolved.

QCCR1B92189

Running a show command changes the device configuration.

NCM does not send the write memory command to devices while running diagnostic tasks, including custom diagnostic tasks.

To enable sending the write memory command to devices while running diagnostic tasks:

1. Add the following text to the adjustable_options.rcx file: <option name="DeviceInteraction/EnforceConfigurationSave/RunDiagnostics">true</option>

2. Restart the management engine.

QCCR1B92302

Telnet client converts CR to CR+LF.

In compliance with the telnet RFC, the NCM third-party telnet client converts each CR (Carriage Return) to CR + LF(Line Feed). Some telnet servers treat the LF as a CR, which causes the session to become unsynchronized.

This fix creates an option to disable the CR to CR+LF conversion.

To disable the CR to CR+LF conversion, follow these steps:

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

<option name="TelnetClient/OutputStream/ConvertCRtoCRLF">false</option>

2. Do one of the following:

Restart the NCM management engine.

or

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

or

Run the reload server options command from the NCM proxy.

QCCR1B92803

Authentication failover description in the online help is incorrect.

This problem has been resolved.

QCCR1B93054

The initial configuration in the device template is not readable.

This fix prevents future device templates from containing corrupted configurations. However it does not correct current device templates with corrupted configurations.

QCCR1B93055

Html tags are displayed in the recent, running and scheduled comments field.

This problem has been resolved.

QCCR1B93263

Enabling the NCM 1.7.1 cross site scripting feature affects policy related user report.

This problem has been resolved.

QCCR1B93365

NCM is slow to execute scheduled child tasks from parent tasks.

This problem has been resolved.

QCCR1B93619

Search results are in the missing comments field.

This problem has been resolved.

QCCR1B93677

The export or import of command scripts truncates trailing whitespace which causes errors.

This problem has been resolved.

QCCR1B93688

Data on user pages is not aligned correctly.

This problem has been resolved.

QCCR1B93864

Adobe Flash is not required to use the user interface.

To enable this fix, disable the use of Adobe Flash in the NCM console as follows:

1. In the appserver.rcx file, disable the use of Flash by modifying <option name="flexui/devicechooser">true</option> to <option name="flexui/devicechooser">false</option>

2. Add <option name="flexui/devicechooser/return_count">12</option> to the adjustable_options.rcx file to control the number of items returned by the search box.

or

Change the default value to 12 in this line.


Note To reduce the number of search results, narrow the search pattern.


QCCR1B93965

There is a mismatch in the User ID while performing device configuration comparisons.

This problem has been resolved.

QCCR1B94029

Estimate space is required for full text index and improvements to full text index addition.

This problem has been resolved.

QCCR1B94031

Device access error occurs in a batch snapshot task but not in an individual snapshot task.

This problem has been resolved.

QCCR1B94116

The compliance report displays policy compliance instead of the rule compliance.

This problem has been resolved.

QCCR1B94258

Device Groups page takes a long time to load.

This problem has been resolved.

QCCR1B94263

Tasks scheduled through a CSV file do not retain their configuration.

This problem has been resolved.

QCCR1B94363

Oracle queries cannot process a large number of partitions

This problem has been resolved.

QCCR1B94371

Running diagnostic on Cisco firewalls yields many failures.

This problem has been resolved.

QCCR1B94377

No device discovery hints sent from NCM to NNMi for existing NCM devices.

This problem has been resolved.

QCCR1B94492

The software level violations do not show in Best Practices report.

This problem has been resolved.

QCCR1B94740

There should be a way to resize the proxy window.

To enable alternate settings for the proxy window size:

1. Edit the appserver.rcx file by locating "administration/User Interface/section_order" section and adding <value>Proxy Window</value> before "Miscellaneous".

2. Add the following text to the site_options.rcx file:

<!-- 500_600_12_80_24 = window size: height=500, width=600, font=12, column=80, row=24 --> <option name="webui/proxy_window/config">500_600_12_80_24 <title>Dimension of proxy window</title> <section>Proxy Window</section> <type>RadioButtons</type> <domain>500_600_12_80_24</domain> <number_500_600_12_80_24>Window size: 500 x 600, font: 12, column: 80, row: 24</number_500_600_12_80_24> <domain>600_700_13_90_28</domain> <number_600_700_13_90_28>Window size: 600 x 700, font: 13, column: 90, row: 28</number_600_700_13_90_28> <domain>700_800_14_100_32</domain> <number_700_800_14_100_32>Window size: 700 x 800, font: 14, column: 100, row: 32</number_700_800_14_100_32> </option>

3. On the NCM application server, clean out the cached files and browser cache by deleting all files in the following folders:

<NCM_HOME>\server\ext\jboss\server\default\tmp

<NCM_HOME>\server\ext\jboss\server\default\work\jboss.web

4. Restart the NCM management engine.

5. Update the proxy window setting as follows:

In the NCM console, navigate to Admin > Administrative Settings > User Interface.

Under Miscellaneous, set the Proxy Window setting to a different value.

Verify the change by opening a new proxy window.

QCCR1B94963

Data pruning task fails.

This fix improves the algorithm for database pruning. To enable this fix, verify that the Data Pruning task is

scheduled to run at least weekly.

After installing the patch, the first several runs of the

Data Pruning task might exceed the configured maximum task time. In this case, you will see the following warning message:

com.rendition.pruner.ConfigPruner: The task thread was interrupted. Pruning partially completed.

This message indicates that additional records can be

pruned. No action is necessary; subsequent runs of the Data Pruning task will clear the additional records.


Tip If the database configuration includes redo logs, ensure that adequate disk space is available for these logs, especially while the warning message appears. The required size depends on the database configuration and the size of the NCM database.


To complete database cleanup faster, you can any or both of the following steps:

1. Temporarily increase the value of Max Task Length to bigger value such as 18000 (5 hours). This setting is under Tasks on the Admin > Administrative Settings > Server page in the NCM console.


Tip After the warning message appears, reset the Max Task Length to the original value. The default value is 3600.


2. Run the Data Pruning task manually until the warning message disappears from the screen.


Note In a Multimaster or Horizontal Scalability environment, it is recommended to run the Data Pruning task manually on one NCM core until the warning message disappears. The Data Pruning task should be scheduled to run at least weekly on each core.


QCCR1B95133

Inconsistency between API cmds and WSDL cmds. There are missing input parameters like deviceid.

This problem has been resolved.

QCCR1B95184

Displayed search results for MAC address differ from the results in the saved csv file.

This problem has been resolved.

QCCR1B95297

Custom Actions Task fails. Device Status for device xyz java.lang.NumberFormatException: multiple points couldnot be updated.

This problem has been resolved.

QCCR1B95400

Java is not able to find toolbar.png file.

This problem has been resolved.

QCCR1B95510

NCM Proxy SSH session should not break when extended ASCII or multi-byte characters are entered in the terminal.

This problem has been resolved.

QCCR1B95518

Supported process for upgrading to Java 6 Upgrade 29 is required.

This problem has been resolved.

QCCR1B95629

SSH proxy doesnot connect automatically to devices.

The interceptor.jar file in the truecontrol.war file is replaced. The truecontrol.war file is availablein the truecontrol application EAR file.

The interceptor.jar files contains the JAVA applet code.

To enable this fix, use the Java Control Panel to delete the cached applets.

QCCR1B96014

Users with read-only permissions does not see policies and policy rules.

This problem has been resolved.

QCCR1B96067

Diagnostic task clears user attribution from Change Event Data

This problem has been resolved.


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 R2

x86_64

 

X

Windows Server 2003 SP2

X86_32

X

 

Solaris 10 SPARC2 ,3

Sun4u, Sun4v

 

X

RedHat RH AS 44

x86_32

X

 

RedHat RHEL Server 5

x86_64

 

X

SuSE Enterprise Linux Server 10

x86_64

 

X

1 CiscoWorks NCM 1.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 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).

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

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


The following operating systems are no longer supported:

Windows 2000

Solaris 9

Red Hat AS3

SuSE 9


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


Supported Databases

Table 3 shows the databases that are supported by CiscoWorks NCM 1.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