Release Notes for CiscoWorks Network Compliance Manager 1.6.02 [CiscoWorks Network Compliance Manager]

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.6.02

Contents

Introduction

Installing the CiscoWorks NCM 1.6.02 Patch

What's Been Fixed in CiscoWorks NCM 1.6.02

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Additional Required Applications

Hardware Requirements

Caveats

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

Release Notes for CiscoWorks Network Compliance Manager 1.6.02

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

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

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

Contents

This document contains the following sections:

•Introduction

•Installing the CiscoWorks NCM 1.6.02 Patch

•What's Been Fixed in CiscoWorks NCM 1.6.02

•Supported Platforms

•Supported Databases

•Additional CiscoWorks NCM Configurations

•Virtual Environments

•Additional Required Applications

•Hardware Requirements

•Caveats

•Accessing the CiscoWorks NCM Documentation Set

•Obtaining Documentation and Submitting a Service Request

Introduction

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

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

Installing the CiscoWorks NCM 1.6.02 Patch

To install the CiscoWorks NCM 1.6.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.

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

Step 1 Stop the NCM Management Engine.

Step 2 Restore the files that are changed by the patch installer to their original locations.

Step 3 Restart the NCM Management Engine.

What's Been Fixed in CiscoWorks NCM 1.6.02

Table 1 describes the issues fixed in CiscoWorks NCM 1.6.02.

Table 1 Issues Fixed in CiscoWorks NCM 1.6.02

Bug ID

Bug Summary

Fix Description

QCCR1D72393

Provide pruning option for the RN_DEVICE_AUTH records

This problem has been resolved.

QCCR1D93293

The Replication Monitor needs to be updated for horizontally scaled cores.

This problem has been resolved.

QCCR1D99612

Device Search is extremely slow when config text is a criterion.

This fix enables the "contains (full text)" search of Configuration Text. The "contains (full text)" search is an indexed search. It requires that the database is enabled for full text search.

Being an indexed search, it returns results faster than the "contains" search. However, this search supports fewer options than the "contains" search. For descriptions of the supported options for "contains (full text)", see

Usage

in this section.

Enable Full Text Search On Oracle:

•Verify that Oracle Text is enabled and has the required privileges.

–The CTXSYS schema must be installed in the database instance.

–Grant EXECUTE privileges on CTX_DDL package to the CWNCM database user:

–GRANT EXECUTE ON CTX_DDL TO <na db user>;

For more information, see: http://download.oracle.com/docs/cd/B19306_01/text.102/b14217/admin.htm

•Generate the full text index:

–Verify that no Take Snapshot tasks are running.

–Verify that enough tablespace is available in the user schema, at least 30%-40% the size of RN_DEVICE_DATA table.

•Log on to the Ciscoworks Network Compliance Manager proxy with the credentials used to install CWNCM.

•Run the following command: run checkdb -fix -resolver addsearchindex -verbose

Note This command takes time to complete, depending on the size of the RN_DEVICE_DATA table. To avoid data corruption, do not interrupt this command. In the verbose output, verify that this run did not generate any SQL/ORACLE exceptions.

•Edit the adjustable_options.rcx file to set: <option name="fulltextsearch/enabled">true</option>

QCCR1D99612 contd.

On MSSQL:

•Verify that MSSQL Full Text Search service is installed and enabled by using one of the following approaches:

–Using MSSQL configuration Manager, determine whether the SQL Server FullText Search service is installed and started.

–Using SQL Management Studio, run the following select statement:

SELECT fulltextserviceproperty('IsFulltextInstalled) This statement returns 1 if the database is full-text enabled and 0 if not.

•Remove the MSSQL noise words. Follow the procedure for the MSSQL version:

MSSQL 2005

–Change to the NA_00012\Microsoft SQL Server\MSSQL.1\MSSQL\FTDATA\ directory.

–Create a backup copy of the noiseENU.txt file.

–Delete all entries in the noiseENU.txt file to leave an empty file.

For more information on how to edit noise words, see: http://msdn.microsoft.com/en-us/library/ms142551%28SQL.90%29.aspx

MSSQL 2008

By default no noise words are enabled.

•Generate the full text index:

–Log on to the Ciscoworks Network Compliance Manager proxy with the credentials used to install CWNCM.

–Run the command run checkdb -fix -resolver addsearchindex -verbose

Note On MSSQL this command returns immediately and starts full-text indexing. Wait some time before you start using the new search. In the verbose output, verify that this run did not generate any SQL exceptions.

•Edit the adjustable_options.rcx file to set: <option name="fulltextsearch/enabled">true</option>

QCCR1D99612 contd.

On MySql:

This feature is not supported.

Usage

After full text search is enabled, faster configuration text search is available for the following options:

•Reports > Search For > Devices > Configuration Text > contains (full text)

•Reports > Search For > Configurations > Configuration Text > contains (full text)

•Reports > Search For > Device Templates > Configuration Text > contains (full text)

•Reports > Advanced Search > Search Criteria > Configuration Text > contains (full text)

•Could also create Dynamic groups based on Search Criteria > Configuration Text > contains (full text)

Similarly, these searches also support searching for configuration text that "does not contain (full text)". The search is case insensitive for the "contains (full text)" and "does not contain (full text)" operators.

Specific search usage:

•Search for a single word (a sequence of characters containing no spaces):

•Valid examples: interface, telnet, snmp

•Search for a single word using the wildcard: The asterisk character (*) is the only supported wildcard; this wildcard must be at the end of the search phrase.

Valid examples: interf*, tel*

•Search for an IP address (same as searching for a single word): The asterisk character (*) is the only supported wildcard; this wildcard must be at the end of the search phrase.

•Search for an IPv4 address is supported and treated as single word.

Valid examples:

–- 10.11.12.13 results in exact match

–- 10.11.12.* results in all addresses that start with 10.11.12

–- 10.11.* results in all addresses that start with 10.11

QCCR1D99612 contd.

•Search for a phrase (a sequence of characters containing one or more white spaces):

Valid examples: set vlan, set vpn name

•Search for a phrase using the wildcard:

The asterisk character (*) is the only supported wildcard. This wildcard must represent one or more complete words within of the search phrase.

The * must NOT be at the end of the search phrase.

Use white space on either side of the *. If white space is absent, Ciscoworks Network Compliance Manager treats the search as a word using the wildcard.

Valid examples: set * name, telnet * table * settings

•Logical operators (AND, OR, NOT, ACCUM, EQUIV) are not supported nor considered as part of search string.

Known Issue

ORACLE only: If a Take Snapshot task is running during the generation of the full text index, you might see the following error:

java.sql.SQLException: ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE

Disable Full Text Search

•Edit the adjustable_options.rcx file to set: <option name="fulltextsearch/enabled">false</option> (Alternatively, delete this option from the file.)

•Remove the full text index:

–Verify that no Take Snapshot tasks are running.

–Log on to the CWNCM proxy, and then run the following command: run checkdb -fix -resolver removesearchindex

•If any dynamic groups are configured to use the "contains (full text)" or "does not contain (full text)" operator, edit or delete these dynamic group configurations.

QCCR1D103055

Running a multi-task project on IOS devices leads to a null pointer exception.

This problem has been resolved.

QCCR1D106083

Searching a CLOB using Like operator is very expensive.

This problem has been resolved.

QCCR1D111687

The device type is LoadBalancer instead of Load Balancer.

a. Update the appserver.rcx file as follows:

b. Locate the following line: <value>Load Balancer</value>

c. Change the line to: <value>LoadBalancer</value>

d. Save the file.

e. Restart the management engine.

QCCR1D114268

Run Diagnostics and OS Analysis tasks does not run across mesh servers.

Update the adjustable_options.rcx file to add the following options:

<option name="formatting/list port/stdout_table/header">ID,Port Name,Port Status,Port Running State,Port Type,Description,Comments,Last Modified,IP Addresses,Configure Duplex,Configured Speed, Negotiated Duplex,Negotiated Speed,MAC Address,VLAN ID</option> <option name="formatting/list port/stdout_table/body">

NA_00012.DevicePortID$,NA_00012.PortName$,NA_00012.PortStatus$,

NA_00012.PortState$,NA_00012.PortType$,NA_00012.Description$,

NA_00012.Comments$,NA_00012.LastModifiedDate$,NA_00012$,

NA_00012.ConfiguredDuplex$,NA_00012.ConfiguredSpeed$,

NA_00012.NegotiatedDuplex$,NA_00012.NegotiatedSpeed$,

NA_00012.MacAddress$,NA_00012.AssociatedVlanID$</option>

To back out this change, remove these two lines from the adjustable_options.rcx file.

QCCR1D116914

The CLI command show port gives inconsistent results.

This problem has been resolved.

QCCR1D117569

The failed logon attempts to the proxy replace the hostname with $3$.

This problem has been resolved.

QCCR1D117839

The list device API does not return the value for driver name.

This problem has been resolved.

QCCR1D118479

Support for parsing of ACS 5.x logs by CWNCM Syslog server to be provided.

This fix provides a mechanism for parsing Cisco Secure Access Control System (ACS) 5.x logs for change detection when those logs are forwarded by ACS 5.x to the CWNCM Syslog server.

Note TheCiscoworks Network Compliance Manager AAA Log Reader Agent cannot be used to process ACS 5.x logs because ACS 5.x uses a format different from that of standard RFC-compliant logs. Also, the Ciscoworks Network Compliance Manager AAA Log Reader Agent is a Windows application while ACS 5.x is installable on a CSACS appliance or VMware.

To enable the use of ACS 5.x logs for change detection, follow these steps:

1. Configure the ACS 5.x server to forward ACS logs to the CWNCM syslog

server:

a. On ACS 5.x, use System Administration > Log Configuration > Remote Log Targets > Create to set the IP address of the CWNCM Syslog server.

Use Advanced Syslog Options to verify that the Port and Facility Code values match the configuration of the CWNCM Syslog server.

b. On ACS 5.x, use System Administration > Log Configuration > Log Categories > Global (or Per Instance) to set the categories of logs to be forwarded (for example, AAA Audit).

For the selected categories, use the Remote Log Target tab to add the CWNCM Syslog server configured in the previous step as a target.

For more information, see http://www.cisco.com/en/US/products/ps9911/products_user_guide_list.html

2. On the Ciscoworks Network Compliance Manager server, update the appserver.rcx file:

a. Locate the following line <option name="syslog/process_other_treatments">false</option>

b. Change it to <option name="syslog/process_other_treatments">true</option>

c. Save the file

3. Restart Ciscoworks Network Compliance Manager

4. In CWNCM, go to Admin > Administrative Settings > Configuration Mgmt, and then add the pattern "CSCOacs" to the Syslog Detection Patterns list.

QCCR1D118677

Removing old diagnostic script does not delete all related information too.

This problem has been resolved.

QCCR1D119116

The workflow logic fails in certain scenarios with task command script.

This problem has been resolved.

QCCR1D119907

The changes made to Custom Service Types is not saved..

This problem has been resolved.

QCCR1D120534

The username and password values are not over written when using device-specific password rules with empty fields and AAA.

This problem has been resolved.

QCCR1D121720

The module information is not deleted after the diagnostic history is erased.

This problem has been resolved.

QCCR1B85299

The Edit Device page does not list the password.

This problem has been resolved.

QCCR1B85418

The SNMP community string is listed twice in the deploy password task.

This problem has been resolved.

QCCR1B85677

Policy rule exceptions are not applied to software policy rules.

This problem has been resolved.

QCCR1B85901

"list image" command needs site specified, even if CWNCM only has a single site.

This problem has been resolved.

QCCR1B86233

Policy tag feature does not work properly for full access users.

This problem has been resolved.

QCCR1B86318

There is no method to remove custom service type from multiple devices.

This problem has been resolved.

QCCR1B86996

Java API connect problems with multiple threads.

After installing the patch, update your custom application with the latest version of the truecontrol-client.jar file. This file is available in the

<NCM_HOME>/client/ directory.

QCCR1B87303

Garbage collection errors when running flows against CWNCM.

This problem has been resolved.

QCCR1B87821

Test policy can fail for rule condition "must not contain".

This problem has been resolved.

QCCR1B87842

Device IP addresses not updated after primary IP address change.

This problem has been resolved.

QCCR1B87935

Scripts cause a NullPointerException when run in a group but not when run individually.

This problem has been resolved.

QCCR1B87943

Dynamic device group calculation problem: system becomes non-responsive, requires restart to restore service; addresses the issue of multiple threads calculating dynamic groups simultaneously.

This problem has been resolved.

QCCR1B87944

ORA-00001: unique constraint (NA_ADMIN.RN_DEV_GRP_DEV_MAP_PK) violated when adding device to device group.

This problem has been resolved.

QCCR1B88152

The list device option shows vendor name as status.

This problem has been resolved.

QCCR1B88313

Update SWIM library.

This problem has been resolved.

QCCR1B88415

The pages are slow in loading when viewing configuration changes.

If you notice a large number of records in the RN_DEVICE_ACCESS_LOG table, run the following SQL command on the database:

Oracle:

DELETE FROM rn_device_access_log WHERE isConfigChange = 0

AND NoPrune = 0 AND ConfigID IS NULL

AND CreateDate < to_date('2011-03-26','yyyy-mm-dd')

AND NOT EXISTS (SELECT deviceaccesslogid FROM rn_diagnostic_data WHERE rn_device_access_log.deviceaccesslogid = rn_diagnostic_data.deviceaccesslogid)

AND NOT EXISTS (SELECT deviceaccesslogid FROM rn_device_data WHERE rn_device_access_log.deviceaccesslogid = rn_device_data.deviceaccesslogid);

On Microsoft SQL server or MySql:

DELETE FROM rn_device_access_log

WHERE isConfigChange = 0

AND NoPrune = 0

AND ConfigID IS NULL

AND CreateDate < '2011-03-26'

AND NOT EXISTS (SELECT deviceaccesslogid FROM rn_diagnostic_data WHERE rn_device_access_log.deviceaccesslogid = rn_diagnostic_data.deviceaccesslogid)

AND NOT EXISTS (SELECT deviceaccesslogid FROM rn_device_data WHERE rn_device_access_log.deviceaccesslogid = rn_device_data.deviceaccesslogid);

Note Modify the date ('2011-03-26' in this example) to match your pruning schedule.

QCCR1B88572

Merge SJK fixes and language file from CWNCM 9.0 SJK (includes QCCR1D116341, QCCR1D116345, and QCCR1D116400).

This problem has been resolved.

QCCR1B88573

The page times out when using View > Device > Single view.

This problem has been resolved.

QCCR1B88738

Virtual Context Firewalls not available a in reports and groups.

Update the appserver.rcx file as follows:

1. Locate the line <array name="devicetype/types">

2. After the above line, add the line <value>Virtual Firewall</value>

This portion of the file should now be:

<array name="devicetype/types">

<value>Virtual Firewall</value> <value>Router</value>

<value>Switch</value>

3. Save the file.

4. Restart the management engine or reload the configuration.

QCCR1B88962

Device Group navigation and editing is very slow.

This problem has been resolved.

QCCR1D116454

Provide a way to disable Dynamic Device Group

In a multi CWNCM cores mesh setup, dynamic group recalculation task does not need to run on all CWNCM cores in the mesh as the result of running it on one CWNCM core is replicated among all other CWNCM cores in the mesh. This fix provides the option to disable dynamic group recalculation on particular cores.

To disable dynamic group recalculation:

1. Add the following option to one of the .rcx files, preferably <NA_HOME>/jre/adjustable_options.rcx.

(Add the new option between "option" root elements.) <option name="dynamic_group/disable">true</option>

2. Reload the .rcx settings by running reload server options via the CLI or by restarting the CWNCM Management Engine.

QCCR1B89914

Satellite monitor fails with com/rendition/service/UserManager error.

This fix updates the satellite agent on the core side. After installing the patch, re-deploy the satellite.

Supported Platforms

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

Table 2 Supported Platforms for CiscoWorks NCM 1.6.x

Operating System

Architecture

32-bit

64-bit¹

Windows Server 2008 R2

x86_64

X

Windows Server 2003 SP2

X86_32

X

Solaris 10 SPARC²^,³

Sun4u, Sun4v

X

RedHat RH AS 4⁴

x86_32

X

RedHat RHEL Server 5

x86_64

X

SuSE Enterprise Linux Server 10

x86_64

X

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

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

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

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

The following operating systems are no longer supported:

•Windows 2000

•Solaris 9

•Red Hat AS3

•SuSE 9

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

Supported Databases

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

Table 3 Supported Databases for CiscoWorks NCM 1.6.x

Database

Notes

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

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

Oracle 11g (11.1.0.7.0) Standard and Enterprise Edition

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

Microsoft SQL Server 2005 and 2008 Standard and Enterprise Edition

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

MySQL 5.0.58

MySQL 5.0.58 ships with CiscoWorks NCM 1.6.

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

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

The following databases are no longer supported:

•Oracle 9i and Oracle 9.2

•Microsoft SQL Server 2000

•MySQL 3

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

Additional CiscoWorks NCM Configurations

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

Database

Restrictions

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

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

Oracle 11g Standard or Enterprise Edition (11.1.0.7.0)

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

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

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

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

Database

Restrictions

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

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

Oracle 11g Standard or Enterprise Edition (11.1.0.7.0)

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

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

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

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

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

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

Virtual Environments

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

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

•Use of Vmotion is not recommended.

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

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

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

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

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

If you 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

Caveats

This section contains information about the limitations and problems known to exist in CiscoWorks NCM 1.6.x.

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

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2010 Cisco Systems, Inc. All rights reserved.

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager 1.6.02

Hierarchical Navigation

Downloads

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.6.02

Contents

Introduction

Installing the CiscoWorks NCM 1.6.02 Patch

What's Been Fixed in CiscoWorks NCM 1.6.02

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Additional Required Applications

Hardware Requirements

Caveats

Accessing the CiscoWorks NCM Documentation Set

Obtaining Documentation and Submitting a Service Request

© 2010 Cisco Systems, Inc. All rights reserved.

Programs

Programs

Programs

Programs