This document provides troubleshooting assistance when you are unable
to connect to an Asynchronous Network Interface (ANI) server when selecting
Campus Manager applications from CiscoWorks 2000 Interface.
Review the client and server prerequisites provided by the Installation
Guide of your associated edition of CiscoWorks2000 bundle. All command line
references require ROOT id (UNIX) or Local Administrator (Windows) access,
according to your operating system platform.
The information in this document is based on these software and
Campus Manager 3.2
Campus Manager 3.3
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
If you are unable to connect to your ANI server verify this:
Verify that your first entry in the file, /etc/hosts in Solaris or
C:\WINDOWS\system32\drivers\etc in Windows, is the actual IP address and
hostname of the CiscoWorks server machine and not the loopback address
127.0.0.1. The actual IP address or hostname is the address that you put in the
URL locator to connect to CiscoWorks through the browser.
Verify that you have the latest compatible Java Virtual Machine (JVM)
loaded on your client machine. In order to verify, follow these steps:
Enable JVM console logging from the web
Go to: IE > Tools > Internet Options > Advanced
Tab > Microsoft VM.
Check all the boxes.
Save the changes.
Log out of CiscoWorks.
Close the browser.
Restart the browser.
Check the JVM version:
Go to IE > View > Java Console, and the
Java console window appears.
Verify from the first line in the Java console window that the
version of JVM is Microsoft ®) VM for Java, 5.0 Release 220.127.116.1109 or
If the JVM is not latest, download the latest JVM fix from
Choose product name > Virtual
Choose your Operating System >
Download/Install the latest version.
Relaunch the application.
If you use the MS Internet Explorer (IE) browser to access and launch
Campus Manager, do not install Client Application Manager (CAM). If you already
have CAM installed, uninstall it. In order to verify, do one of
From the CiscoWorks 2000 GUI, go to CW2000Server/Server
Configuration > Setup > Client Manager Admin, and the CAM
install/uninstall screen appears.
From IE browser go to Tools > Internet Options >
General tab, and do this:
Under Temporary Internet Files, click Settings,
and the Settings window appears.
Click View Objects. CamRegistry is listed in the
new window, under Program File.
If CAM Registry is installed, right-click and choose
Clear the browser cache; go to the General tab and choose
Delete Files and Clear History.
Restart the browser.
Sometimes you can rectify the problem if you stop and restart the ANI
server process from the screen. Follow these steps:
Stop the server: CW2000Server/Server Configuration >
Administration > Process Management > Stop Process.
Restart: CW2000Server/Server Configuration >
Administration > Process Management >S tart Process.
Launch the Campus Manager again.
A corruption in the database tables can cause connection problems.
Reinitialize the database tables:
From the command line/dos prompt, log in as root/local
Issue this command for your operating system:
The command, reinitdb.pl displays this
This will erase all data from the database. Are you sure [y/n]:
Press the ENTER/RETURN key, and the ANI
information in regard to Network Discovery (Wbu tables) is erased from the
database, a new ANI Server connection is established, and network discovery is
If you are still unable to connect to the ANI Server, do
Stop the CiscoWorks Daemon Manager.
Re-type the reinitdb.pl command with
the -restore option.
perl reinitdb.pl -restore
Restart the CiscoWorks Daemon Manager if no errors are returned
from the reinitdb.pl command. The
-restore option deletes the existent ANI database,
not just the contents, and a new ANI database is created.
Improper SNMP settings data, as defined in the format, can cause
connection problems. In order to verify your setting, go to:
CiscoWorks2000 Server/Server Configuration->setup->ANI
Server Admin->SNMP Settings
Note: There are 6 colons between the SNMP read only string and the SNMP
The target is the IP address/IP network that you want to discover with
the SNMP strings indicated. An asterisk '*' represents a wildcard, so
everything in that octet (0-255) is discovered.
For example, you can use the asterisk in any or all octets:
Verify that these CiscoWorks2000 processes are running:
From the CiscoWorks 2000 Server, issue these commands:
* UNIX CLI mode:
* NT/Windows2000 command mode:
Ensure that this information is displayed:
State = Running but busy flag set
Pid = 1204
RC = 0
Signo = 0
Stop = Not applicable
Core = Not applicable
Info = ANIServer started.
Repeat these steps for the ANIDbEngine and
EDS. The ANIServer depends on these processes to run.
A multi-home machine is one with multiple NIC cards, each configured
with different IP addresses. Although Campus Manager 3.1 is supported by
multi-homed machines, you must modify the gatekeeper configuration file to run
it on multi-homed machines. Because of CORBA restrictions, only one IP address
can be used by a client to access CiscoWorks2000 Server.
In order to ensure that Campus Manager runs properly on multi-homed
machines, follow these steps:
Open the gatekeeper configuration file
# Solaris: Located under the /opt/CSCOpx/lib/vbroker directory.
Note: /opt is the default install location for Solaris
# Windows: Located under the $NMSROOT\CSCOpx\lib\vbroker directory.
Note: $NMSROOT is the default install location for Windows.
Note: You must be Administrator/root in order to modify this file or
stop/start CW2000 processes.
Go to the section that begins with this line:
#************ BEGIN MULTI-HOME PROPERTIES **********************
By default, these lines are commented with #. In order to uncomment
the property, remove the # character.
Enter the appropriate IP address in these fields:
Save the file.
In order to stop the CW2000 processes, issue this command from a
DOS window CLI:
# Solaris: /etc/init.d/dmgtd stop
# Windows: net stop crmdmgtd
Delete the gatekeeper.ior file, located in this
# Solaris: /opt/CSCOpx/www/classpath
# Windows: $NMSROOT\CSCOpx\www\classpath
In order to start the CW2000 processes, issue this command from a
DOS window CLI:
# Solaris: /etc/init.d/dmgtd start
# Windows: net start crmdmgtd