CiscoWorks Campus Manager

Troubleshooting ANI Server Issues in Campus Manager 5.x

Document ID: 110195

Updated: Jul 13, 2009



This document provides information on how to troubleshoot Asynchronous Network Interface (ANI) server issues encountered in the CiscoWorks Campus Manager application. Campus Manager uses the ANI server to build a layer 2 topology of the network based on the devices present in Device Credential Repository (DCR).



There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Campus Manager 5.1

  • Campus Manager 5.2

For troubleshooting ANI server issues with Campus Manager 3.2 or 3.3, refer to Troubleshooting ANI Server Connection Problems.


Refer to Cisco Technical Tips Conventions for more information on document conventions.

Cannot Connect to ANI Server

While accessing the admin page or any other pages in the CiscoWorks Campus Manager application, the Cannot connect to ANI Server error message appears.


When you find the Cannot connect to ANI Server error, any one of the solutions described in this section can help you to resolve the problem.

ANI server process status

You might have to check if ANI server is up and running fine. Log in to the CiscoWorks server and issue the pdshow ANIServer command to check the ANI server status. The healthy state of ANI server status looks like this:

 Process= ANIServer
 State  = Running with busy flag set
 Pid    = 24437
 RC     = 0
 Signo  = 0
 Start  = 06/15/09 11:00:26
 Stop   = Not applicable
 Core   = Not applicable
 Info   = ANIServer started.


Check whether you are using supported java plugins on the client machine. The supported java plugins for Campus 5.1 and 5.2 are jre1.6.0_5 and jre1.6.0_11, respectively.

Browser restart

You can close all the browsers in the client machine and launch the CiscoWorks application again. This will resolve client specific issues.

Applet cache

Sometimes cleaning up all cache files can solve the problem. In order to clean up cache files, perform this on the client machine:

Settings -> Control Panel -> Java -> General -> Temporary Internet Files -> Settings -> Delete Files

Reachability issues

You can check ani.log for any CORBA related issues; ani.log is available under NMSRoot/log in Windows and /var/adm/CSCOpx/log in Solaris.

You can also check whether the CiscoWorks server has any reachability issues, and make sure that both the CiscoWorks hostname and IP are reachable from the client.


It is required that the CiscoWorks server hostname must be in DNS, and make sure the hostname is reachable from the client machine.

If you want to access the CiscoWorks server with the IP address alone and not with hostname, complete these steps:

  1. Set jacorb.dns.enable=off in NMSRoot/lib/classpath/

  2. Re-generate the server certificate with the IP address (not with hostname).

  3. Restart CiscoWorks daemons:

    net stop crmdmgtd and net start crmdmgtd for Windows

    /etc/init.d/dmgtd stop and /etc/init.d/dmgtd start for Solaris

In order to generate a server certificate, launch the CiscoWorks application and invoke this:

CS->Server ->Security ->Single-Server Management -> Certificate Setup

Console logs

If the console window closes too fast when you are launching the CiscoWorks application and is unable to go through the exceptions in console, then go to the java console log at the respective location.

In order to enable console debugging in the client machine, go to Settings -> Control Panel -> Java -> Advanced -> Debugging -> Enable Tracing and Enable logging.

Note: The location of the console log file is C:\Documents and Settings\<username>\Application Data\Sun\Java\Deployment\log. The file name has the extension of trace (.trace).

Cannot launch Topology Services

You cannot launch the Topology Services in Campus Manager when this error is seen in the console log:

org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to <lms-server>:42342

In order to resolve this problem, complete these steps:

  1. Go to the client machine and open 'hosts' file available under C:\WINDOWS\system32\drivers\etc.

  2. Add an entry with hostname and IP address: lms-server

    Note: Where '' is the IP address and 'lms-server' is the hostname of LMS Server.

  3. Restart Topology Services.

Jars in client machine

If you find CORBA related exceptions in the client machine, then the issue might be related to client jars. This occurs when you launch CM4.X and CM5.X one after one.

Jars cleanup is required whenever such CORBA exceptions are seen. For cleaning jars, you must delete the vbroker.jar file if it is present under <JreLocation>/lib/endorsed in the client machine. The default JreLocation is available in C:\Program Files\Java\jre1.6.0_11. Refer to Cisco bug ID CSCsm82212 (registered customers only) for more information on this issue.

Presence of IOR files

The IOR file is created or recreated whenever the NameService process is started or restarted. Make sure the IOR file is present under these locations: /NMSRoot/lib/csorb/NS_Ref and NMSRoot/campus/www/classpath/NS_Ref.


You can check when the IOR file is updated using timestamp. If the IOR file is not updated recently, then you might need to check the status of the NameServiceMonitor and NameServer process. In order to update the IOR file, you need to restart the NameServer process or daemons.

Issue the pdterm NameServer and pdexec NameServer commands in order to restart the NameServer process.

IOR accessibility

  • Check if you can access the IOR file from the client browser. In order to check this, use this link: http://<server>:<port>/CSCOcm/classpath/NS_Ref.

    For example:

  • The IOR file will be displayed in the browser as a sequence of HEX numbers.

Content of the IOR file

  • Copy the NS_Ref file, which is available in NMSroot/lib/csorb from the CiscoWorks server.

  • Paste the NS_Ref file in the client machine (for example, D:\NS-Ref).

  • Install JacORB software (open source) from jacorb website in the client machine.

  • Perform dior utility to display the server name and port number. In order to perform dior utility: D:\JacORB\bin>dior -f D:\NS_Ref.

    Note: D:\JacORB is the jacORB installed location. Make sure to use the proper install path if jacORB is in different location.

  • Ensure the server name and port number fields are embedded properly in the IOR file (NS_Ref).

Change attributes of IOR

Perform fixior utility in order to change the CiscoWorks hostname or IP address for debugging purposes.

D:\JacORB\bin>fixior lms-server1 42342 NS_Ref

Note: D:\JacORB is the jacORB installed location. Make sure to use the proper install path if jacORB is in different location.

CORBA Services

  • Perform nmg utility and ensure Orb LoginService and callback services are registered properly.

    D:\JacORB\bin>nmg -ORBInitRef 
  • Check the port numbers of the services.

  • Get the IOR file (NS_Ref) from the CiscoWorks server if those services are not registered properly.


JacORB Debug

If you still cannot get the root cause of the problem, then increase the debugging level for CORBA.

  • Change the property jacorb.log.default.verbosity=4 in the file: /opt/CSCOpx/lib/classpath/

  • You can see more JacORB related debugging statements in logs and in the console.

Note: For more information on JacORB, refer to

CiscoWorks with Firewall?

CiscoWorks with NAT?

If the CiscoWorks server is inside NAT environment, you only have to use the hostname to access the server via browser. Ensure the IOR file has the hostname alone (not IP address).

Related Information

Updated: Jul 13, 2009
Document ID: 110195