Cisco CiscoWorks Network Compliance Manager 1.7 Release Notes

Page of 22
   
2
Release Notes for CiscoWorks Network Compliance Manager 1.7.01
OL-25586-01
  Introduction
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.01 Patch
To install the CiscoWorks NCM 1.7.01 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
Restart the NCM Management Engine.