Guest

CiscoWorks Network Compliance Manager

Release Notes for CiscoWorks Network Compliance Manager 1.8.02

  • Viewing Options

  • PDF (333.3 KB)
  • Feedback
Release Notes for CiscoWorks Network Compliance Manager 1.8.02

Table Of Contents

Release Notes for CiscoWorks Network Compliance Manager 1.8.02

Contents

Introduction

Installing the CiscoWorks NCM 1.8.02 Patch

Post-Installation Steps

Uninstalling the CiscoWorks NCM 1.8.02 Patch

What's Been Fixed in CiscoWorks NCM 1.8.02

Additional Information

Supported Platforms

Supported Databases

Additional CiscoWorks NCM Configurations

Virtual Environments

Performance Issues

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


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

CiscoWorks NCM 1.8.02 is a patch release that you can install on top of CiscoWorks NCM 1.8 and 1.8.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.8.02 Patch

Uninstalling the CiscoWorks NCM 1.8.02 Patch

What's Been Fixed in CiscoWorks NCM 1.8.02

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.8.02 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.8.02 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 Restart the NCM services.


What's Been Fixed in CiscoWorks NCM 1.8.02

Table 1 describes the issues fixed in CiscoWorks NCM 1.8.02.

Table 1 Issues Fixed in CiscoWorks NCM 1.8.02

Bug ID
Bug Summary

QCCR1D90952

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

QCCR1D95740

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

QCCR1D100822

Cancelling a parent task does not cancel the child tasks

QCCR1B93693

Unable to run command script from Event Notification and Response Rules

QCCR1B94062

Distributed round-robin task scheduling does not work as documented

QCCR1B97470

Automatically cancel a task that has been running for a particular time frame (includes QCCR1B109774)

QCCR1B99830

Raw data stored in the RN_DEVICE_DATA table for snapshots

QCCR1B102133

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

QCCR1B105381

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

QCCR1B106474

Some command script tasks create extra child tasks on devices not included in the task

QCCR1B106691

Add all condition fields from an advanced search to a policy rule condition. See FIX QCCR1B106691 for details.

QCCR1B106699

Can add only one child context device to a device group using the non_flexui searchForm

QCCR1B106800

CLI discovery is failing because of inconsistent responses from the device. See Fix QCCR1B106800 for details.

QCCR1B106843

Horizontal Scalability: NCM core runs tasks even though it is configured not to

QCCR1B106895

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

QCCR1B107121

The Non-Compliant with Selected Policies field of the Device Search page should be sorted alphabetically

QCCR1B107125

Provide stronger encryption of the a.da file. See Fix QCCR1B107125 for details.

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. For details, see Fix QCCR1B107274.

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

QCCR1B107581

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

QCCR1B107727

Support tags for task templates and tasks. See Fix QCCR1B107727 for details.

QCCR1B107799

UpdatePolicy tag does not work using CLI/API calls

QCCR1B107877

Policy system accepts a logic condition it cannot parse

QCCR1B108028

The command task re-orders the variables in the original script

QCCR1B108089

Cannot run a compliance report CSV export without a failure

QCCR1B108200

Perl API connected through SSH is stuck on exit. See Fix QCCR1B108200 for details.

QCCR1B108275

Provide a way to specify protocol for the show device credentials API/CLI command

QCCR1B108367

Add missing columns to the device search and dynamic group filter. See Fix QCCR1B108367 for details.

QCCR1B108565

NCM Satellite Agent deployment and undeployment: unexpected password promptresults in an Expect script error

QCCR1B108569

The Software Levels page does not display the software levels added through the HP Live Network connector. See Fix QCCR1B108569 for details.

QCCR1B108644

The Software Levels page does not include the navigator and number of records per page fields

QCCR1B109101

print > in a diagnostic converts > to &gt;

QCCR1B109184

When the device reservation system is disabled, cannot add a new sub task to a multi-task project

QCCR1B109372

NCM task status documentation incomplete; API returns unknown status value

QCCR1B109429

CLI discovery is failing; permit adjustment of SSH buffer size

QCCR1B109589

Provide a way to assign non-administrative users the ability to manage partitions. See Fix QCCR1B109589 for details.

QCCR1B109661

Cannot download summary report using Microsoft Internet Explorer 8

QCCR1B109700

Detect Network Devices task does not use credentials from device password rules


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 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 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 QCCR1B106691

This fix adds the following conditions to the Rule Conditions field of a

policy rule:

Last Snapshot Attempt Status

Last Snapshot Attempt Date

Last Snapshot Date

Last Snapshot Success Date

Module Model

Module Description

Uptime

Because a device can have multiple modules, the module model field is presented to the criteria as a semi-colon (;) separated list of all module models for that device. If any of the module models matches the search string, the search results include the device. The module description field is handled in a similar manner. For example, a device containing five modules might present the following results for module model and module description:

N5K-C5010-FAN; N5K-C5010P-BF-SUP; N5K-C5010P-BF; N5K-M1600; N5K-PAC-550W

Chassis fan module;20x10GE/Supervisor;20x10GE/Supervisor; 6x10GE Ethernet Module;AC power supply

The uptime is reported as a decimal value. For example, uptime of 2 days 23 hours is displayed as 2.95.

To enable this fix, follow these steps:


Step 1 Stop all NCM services.

Step 2 Edit the appserver.rcx file as follows:

a. Locate the following block:

        <array name="policy/data_element/list">
          <value>ConfigText</value>
          <value>BlockText</value>
          <value>HostName</value>
          <value>DeviceModel</value>
          <value>SerialNumber</value>
          <value>AssetTag</value>
          <value>SoftwareVersion</value>
          <value>FirmwareVersion</value>
          <value>GeographicalLocation</value>
          <value>Memory</value>
          <value>FlashMemory</value>
          <value>DuplexMismatchDetected</value>
        </array>

b. Replace the located block with the following text:

        <array name="policy/data_element/list">
          <value>ConfigText</value>
          <value>BlockText</value>
          <value>HostName</value>
          <value>DeviceModel</value>
          <value>SerialNumber</value>
          <value>AssetTag</value>
          <value>SoftwareVersion</value>
          <value>FirmwareVersion</value>
          <value>GeographicalLocation</value>
          <value>Memory</value>
          <value>FlashMemory</value>
          <value>DuplexMismatchDetected</value>
          <value>LastSnapshotAttemptStatus</value>
          <value>LastSnapshotAttemptDate</value>
          <value>LastSnapshotDate</value>
          <value>LastSnapshotSuccessDate</value>
          <value>ModuleModel</value>
          <value>ModuleDescription</value>
          <value>Uptime</value>
        </array>
 
   

c. Locate the following block:

        <option 
name="policy/data_element/DuplexMismatchDetected/name">DuplexMismatchDetected</option>
        <option name="policy/data_element/DuplexMismatchDetected/type">Boolean</option>
        <option name="policy/data_element/DuplexMismatchDetected/label">Port 
Mismatch</option>
        <option 
name="policy/data_element/DuplexMismatchDetected/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/DuplexMismatchDetected/DeviceVOField">duplexMismatchDetected</op
tion>
        <array name="policy/data_element/DuplexMismatchDetected/operators">
          <value>equal</value>
        </array>

d. After the located block, APPEND the following text:

        <option 
name="policy/data_element/LastSnapshotAttemptStatus/name">LastSnapshotAttemptStatus</optio
n>
        <option name="policy/data_element/LastSnapshotAttemptStatus/type">String</option>
        <option name="policy/data_element/LastSnapshotAttemptStatus/label">Last Snapshot 
Status</option>
        <option 
name="policy/data_element/LastSnapshotAttemptStatus/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/LastSnapshotAttemptStatus/DeviceVOField">lastSnapshotAttemptStat
us</option>
        <array name="policy/data_element/LastSnapshotAttemptStatus/operators">
          <value>contain</value>
          <value>notContain</value>
          <value>containOnly</value>
        </array>
        <option 
name="policy/data_element/LastSnapshotAttemptDate/name">LastSnapshotAttemptDate</option>
        <option name="policy/data_element/LastSnapshotAttemptDate/type">Date</option>
        <option name="policy/data_element/LastSnapshotAttemptDate/label">Last Snapshot 
Attempt Date</option>
        <option 
name="policy/data_element/LastSnapshotAttemptDate/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/LastSnapshotAttemptDate/DeviceVOField">lastSnapshotAttemptDate</
option>
        <option 
name="policy/data_element/LastSnapshotSuccessDate/name">LastSnapshotSuccessDate</option>
        <option name="policy/data_element/LastSnapshotSuccessDate/type">Date</option>
        <option name="policy/data_element/LastSnapshotSuccessDate/label">Last Snapshot 
Success Date</option>
        <option 
name="policy/data_element/LastSnapshotSuccessDate/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/LastSnapshotSuccessDate/DeviceVOField">lastSnapshotSuccessDate</
option>
        <option name="policy/data_element/LastSnapshotDate/name">LastSnapshotDate</option>
        <option name="policy/data_element/LastSnapshotDate/type">Date</option>
        <option name="policy/data_element/LastSnapshotDate/label">Last Snapshot 
Date</option>
        <option 
name="policy/data_element/LastSnapshotDate/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/LastSnapshotDate/DeviceVOField">lastSnapshotDate</option>
        <option name="policy/data_element/ModuleModel/name">ModuleModel</option>
        <option name="policy/data_element/ModuleModel/type">String</option>
        <option name="policy/data_element/ModuleModel/label">Module Model</option>
        <option 
name="policy/data_element/ModuleModel/object">BasicDataModelElement</option>
        <option name="policy/data_element/ModuleModel/DeviceVOField">ModuleModel</option>
        <array name="policy/data_element/ModuleModel/operators">
          <value>contain</value>
          <value>notContain</value>
          <value>containOnly</value>
        </array>
        <option 
name="policy/data_element/ModuleDescription/name">ModuleDescription</option>
        <option name="policy/data_element/ModuleDescription/type">String</option>
        <option name="policy/data_element/ModuleDescription/label">Module 
Description</option>
        <option 
name="policy/data_element/ModuleDescription/object">BasicDataModelElement</option>
        <option 
name="policy/data_element/ModuleDescription/DeviceVOField">ModuleDescription</option>
        <array name="policy/data_element/ModuleDescription/operators">
          <value>contain</value>
          <value>notContain</value>
          <value>containOnly</value>
        </array>
        <option name="policy/data_element/Uptime/name">Uptime</option>
        <option name="policy/data_element/Uptime/type">Integer</option>
        <option name="policy/data_element/Uptime/label">Uptime</option>
        <option name="policy/data_element/Uptime/object">BasicDataModelElement</option>
        <option name="policy/data_element/Uptime/DeviceVOField">uptime</option>
        <array name="policy/data_element/Uptime/operators">
          <value>equal</value>
          <value>lessThan</value>
          <value>greaterThan</value>
        </array>
 
   

Step 3 Save the appserver.rcx file.

Step 4 Delete all files in the following directories:

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

<NCM_HOME>/server/ext/jboss/server/default/work/

Step 5 Start all NCM services.

Step 6 Close any existing ncm console windows, and then clear the web browser cache.

Fix QCCR1B106800

This fix introduces the sshBufferSize device access variable for setting the size of the SSH buffer to be used for reading bytes from the underlying SSH stream. For a device with the sshBufferSize device access variable defined in NCM, NCM reads at one time the specified number of bytes from the SSH channel between that device and NCM.

This control supports devices that have a large (over 1 KB) banner that causes NCM discovery to fail. Consult with your Support representative before using this variable.

The default value of sshBufferSize is 1024 bytes. The value must be in the range 1024 to 10,000 bytes.

As part of this fix, if you modify any of the following RCX options, you can run the NCM Proxy CLI command 'reload server options' to activate the changes without restarting the NCM services:

Access/SSH/SshCloseOnReadTimeout

Access/SSH/TimeoutMultiplier

Access/SSH/ReadSleepTime

Access/SSH/DEBUG

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 QCCR1B107125

The a.da file stores the credentials for accessing the NCM database. By default, NCM encrypts the a.da file using TripleDES.

This fix provides a way to change the encryption algorithm for this file to AES256.

To enable this fix, follow these steps:


Step 1 Stop the NCM services on all NCM cores.

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

<option name="database/credentials/useAES256Encryption">true</option>

Step 3 Back up the <NCM_HOME>/a.da file to a location outside the NCM directory structure.

Step 4 Edit the a.da file as follows:

a. Locate the line that starts with the following string: U=

b. Edit that line to delete all characters after the equals sign (=).

c. Locate the line that starts with the following string: S=

d. Edit that line to delete all characters after the equals sign (=).

Step 5 Verify that the resulting a.da file is similar to the following example:

     ##generated, do not edit this file
     #Wed Jul 25 14:15:15 MDT 2012
     U=
     S=

This process removed the NCM database credentials from the a.da file. At this point, NCM cannot connect to the NCM database.

Step 6 Configure NCM with the credentials for accessing the NCM database.

a. From the <NCM_HOME>/client directory, run tc_tools.bat (Windows) or tc_tools.sh (UNIX).

b. At the tc_tools prompt, enter 1 to change the database connection information. When prompted, enter the user name and password of an NCM database user with permission to modify the NCM database.

c. From the tc_tools prompt, exit the tool.

Step 7 Repeat steps 2 through 8 on each NCM core.

Step 8 Start the NCM services on all NCM cores.

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.

Fix QCCR1B107727

This fix provides a way to add an identifying tag to a task template. If a tag has been added to a task template, any task run using that template includes the tag. These task templates and tasks can be filtered by tag on the following pages in the NCM console:

Task Templates

Scheduled Tasks

Running Tasks

Recent Tasks

Subtasks and re-run tasks include the related tag, if any.

If needed, create a new tag as part of creating a task template. Deleting all task templates and tasks for a given tag removes that tag from the NCM database.

Tags are meant for task templates only. NCM ignores a tag applied to a specific task.

To enable this fix, follow these steps:


Step 1 From one NCM core, update the NCM database schema to correctly store and index the task template tag:

a. From the <NCM_HOME>/client directory, run tc_tools.bat (Windows) or tc_tools.sh (UNIX).

b. At the tc_tools prompt, enter 4 to enable new product features, and then select the "Enable Tags for Task Templates and Tasks" option. When prompted, enter the user name and password of an NCMdatabase user with permission to modify the NCM database.

c. From the tc_tools prompt, exit the tool.

Step 2 Stop the NCM services on all NCM cores.

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

<option name="task/template/tagging/enabled">true</option>

Step 4 Start the NCM services on all NCM cores.

Fix QCCR1B108200

This fix delivers an updated Perl API library.

To install the updated library, follow these steps:


Step 1 Change to the <NCM_HOME>/client/perl_api/Opsware directory.

Step 2 Uncompress and untar the Opsware-NAS-Connect-0.6.8.tar.gz file.

Step 3 Change to the uncompressed Opsware-NAS-Connect-0.6.8 directory.

Step 4 In the Opsware-NAS-Connect-0.6.8 directory, run the following commands in order:

perl Makefile.PL

make

make test

make install

For more information, see the README file in the uncompressed Opsware-NAS-Connect-0.6.8 directory.

Fix QCCR1B108367

This fix adds the following fields to the Search for Device page and to the search criteria for building a dynamic device group:

Device ID

Last Successful Snapshot

Last Snapshot Attempt

Last Snapshot Result

Last Access Attempt

Last Access Success

Last Access Result

Change Detection and Polling

Device Family

Module Software/OS

Installing the patch enables this fix.

Fix QCCR1B108569

This fix displays policies obtained through the HP Live Network security and compliance service on the Software Levels page. To show only these policies, select the Service Defined Levels view.

Installing the patch enables this fix.

Fix QCCR1B109589

This fix adds the Manage Partition and Manage View commands to the New User Role and Edit User Role pages accessible from the User Roles & Partitions page.

The Manage Partition command gives access to the Security Partitions menu item.

The Manage View command enables the Rename function on the Partitions page. To enable this functionality, grant both Manage Partition and Manage View.

When this fix is disabled, only NCM users with the Administrator role can access the Partitions in page.

To enable this fix, follow these steps:


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

<option name="Administration/SecurityGroupsMgmt/Configurable">true</option>
 
   

Step 2 Restart the NCM services.

Supported Platforms

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

Table 2 Supported Platforms for CiscoWorks NCM 1.8

Operating System
NCM Application Supported Versions
NCM Satellite Supported Versions
Windows Server 2008:
 

x64 Datacenter Edition, SP2

X
None
 

R2 x64 Datacenter Edition, SP1

X
 

x64 Enterprise Edition, SP2

X
 

R2 x64 Enterprise Edition, SP1

X
 

x64 Standard Edition, SP2

X
 

R2 x64 Standard Edition, SP1

X
 

Note: RSA device authentication is not yet available on Windows Server 2008. If you run NCM on a Windows operating system require RSA device authentication, you cannot install or upgrade to NCM 1.8 at this time.

Linux:
 

Red Hat Enterprise Linux Server AS 4.0 or later minor version

 
X
 

Red Hat Enterprise Linux Server 5.4 or later minor version through 5.6

X
X
 

Red Hat Enterprise Linux Server 6.0 or later minor version

X
 
 

SUSE Linux Enterprise Server 9

 
X
 

SUSE Linux Enterprise Server 11 SP1

X
 
 
Tip: Red Hat does not support direct upgrades from Red Hat Enterprise Linux Server 5.x to 6.0.
Solaris:
 

Oracle Solaris 10 SPARC

X
X
 
Note:
· Before installing NCM on a Solaris platform, reconfigure the Syslog server to not listen for remote Syslog messages.
· NCM on a Solaris system requires a large amount of swap space because of the way the fork() system call works. For example, forking a 24 GB process allocates 24 GB in the swap file, which guarantees space to swap out the new process if necessary. If the 24 GB is not available in swap, the fork() system call fails.

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

Table 3 Supported Databases for CiscoWorks NCM 1.8

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


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.8.x 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:

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

Table 4 lists the virtual servers NCM supports.

Table 4 NCM-Supported Virtual Servers 

Virtual Server
Supported Operating System Types
Notes

VMware:

ESX Server 3.5

ESX 4.0 or later minor version

ESXi 4.1 or later minor version

ESXi 5.0 or later minor version

Host OS:

— Windows
— Linux

Guest OS: Any of the operating systems listed in Table 2

The virtual environment must meet the x86-64 or AMD64 hardware requirements listed in Table 5.

Microsoft® Hyper-V R2

· Host OS: Windows Server 2008 R2 x64
· Guest OS: Any of the Windows operating systems listed in Table 2
 

Oracle Solaris Zones

Oracle Solaris
 

If you are running NCM in a virtual environment, review the follow guidelines:

Because NCM can be network intensive, many virtual machines sharing a virtual switch and network interface card could result in unexpected behavior, including time-outs and failed tasks.

Each virtual environment is different and could function differently under loads with shared VM guests.

On a virtual server, it is recommended that the Disk I/O be split. The virtual server must have two arrays:

One array for the host operating system

One array for the virtual machines

Live migration (for example, using Vmotion) of the NCM application server is not recommended.

If you plan to use virtual machines for both the NCM application and the NCM database, ensure that they are running on different guests. It is recommended to host the database virtual machine on a different array to avoid conflicting I/O on the array. Verify that the database is supported in a virtual environment.

When configuring NCM on virtual machines in a Multimaster Distributed System environment or a Horizontal Scalability environment, the maximum number of NCM application servers is two.

Some virtual guests time drift, which can be an issue and should be corrected. Synchronizing the guests to an external time source can solve this issue.

Each NCM guest system must be configured with a set reservation for CPU and memory. These reservations should be at least 125% of the standalone server requirements listed in Table 5 and Table 6. Ensure that the resource pool containing the NCM guest system has adequate resources to consistently deliver the CPU and memory reservations to the NCM guest system.

Performance Issues

To counter performance issues while running NCM in a virtual environment, do the following:

Increase hardware resources on the physical host.

Ensure resources are dedicated to the NCM application server guest.

Decrease the number of guests running simultaneously.

Add a network interface card dedicated to NCM to the virtual server.

A large number of concurrent tasks increases NCM resource demand. If performance issues arise, reduce the number of concurrent tasks or provide more resources to the NCM virtual server. (This suggestion also applies to physical servers.)

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 5 Application Server Requirements

Application Server

CPU

Intel 64-bit (x86-64), AMD 64-bit (AMD64), 3.0+ GHz (Windows, Linux), Minimum of 2.5GHz, 1 physical CPU with 6 cores and 12 logical processors with hyper-threading

Oracle SPARC64 VI or later (M-Series), Oracle SPARC T4 or later (T-Series) (Oracle Solaris), Minimum of 2.5GHz, 1 physical CPU with 6 cores and 12 virtual processors

Memory

16 GB RAM

Swap Space

16 GB

Disk

40 GB, Fast SCSI

Network

100 Mbps Fast Ethernet, full duplex


Table 6 Database Server Requirements

Database Server

CPU

Intel Xeon or equivalent, 3.0+ GHz

Memory

16 GB RAM

Swap Space

16 GB

Disk

512 GB, 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