Cisco CiscoWorks Network Compliance Manager 1.7 Release Notes

Add the following line to the adjustable_options.rcx file: 

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

 

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.

 shows the supported platforms for CiscoWorks NCM 1.7.x.

The following operating systems are no longer supported:

Windows 2000

Solaris 9

Red Hat AS3

SuSE 9

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.

Windows Server 2008 R2

2

2.

 NCM 1.7 on the Windows Server 2008 R2 operating system requires SP1.

x86_64

X

Windows Server 2003 SP2

X86_32

X

Solaris 10 SPARC

3,4

3.

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

4.

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

Sun4u, Sun4v

X

RedHat RH AS 4

5

5.

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

x86_32

X

RedHat RHEL Server 5

x86_64

X

SuSE Enterprise Linux Server 10

x86_64

X