Campus Manager clients generate a Cannot connect to ANI Server error

[TCC_2]

Resolution

These are among the reasons the Asynchronous Networks Interface (ANI) Server does not respond to errors:

1. The ANI Server process does not run.

   Try restarting the ANIServer, as shown:

   # pdterm ANIServer
   # pdexec ANIServer

   Wait at least 10 minutes for the ANI server to start.

2. There is an incorrect browser setting.

   Try disabling all proxy settings on your browser, and access the server through the IP address instead of the hostname.

3. There are blocked ports between client and server.

   Make sure that there are no firewalls or Access Control Lists (ACLs) blocking the ANI ports between the client and ANI Server. Open Campus Manager from a browser on the server.

4. There is an incorrect configuration of gatekeeper on multi-homed servers.

   A multi-home machine is one with multiple Network Interface Cards (NICs), each configured with different IP addresses. Although Campus Manager supports 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 the CiscoWorks2000 server. To ensure Campus Manager runs properly on multi-homed machines, open the gatekeeper configuration file (gatekeeper.cfg).

   For Solaris, it is located under the /opt/CSCOpx/lib/vbroker directory. The /opt is the default install location for Solaris.

   For Windows, it is located under the $NMSROOT\CSCOpx\lib\vbroker directory. The $NMSROOT is the default install location for Windows.

   Note: You must be Administrator/root in order to modify the file or to stop and start the CW2000 processes.

To resolve this issue, perform these steps:

1. Go to the section that begins this way:

   #************ BEGIN MULTI-HOME PROPERTIES **********************

2. By default, the lines are commented with #. Uncomment the property by removing the # character.
3. Enter the appropriate IP address in these fields:

     vbroker.gatekeeper.backcompat.callback.host= 
     vbroker.se.exterior.host= 
     vbroker.se.iiop_tp.host= 
     vbroker.se.interior.host= 

4. Save the file.
5. Stop the CW2000 processes by issuing this command from a DOS window Command Line Interface (CLI):

       Solaris: /etc/init.d/dmgtd stop 
     Windows: net stop crmdmgtd 

6. Delete the gatekeeper.ior file, located here:

     Solaris: /opt/CSCOpx/www/classpath 
     Windows: $NMSROOT\CSCOpx\www\classpath 

7. Start the CW2000 processes by issuing this command from a DOS window    CLI:

     Solaris: /etc/init.d/dmgtd start 
     Windows: net start crmdmgtd 

• There are corrupt database tables.

  A corruption in the database tables may cause connection problems. Reinitialize the database tables as shown:

   
  1. From the command line/dos prompt, log in as root/local admin.
  2. Issue this command for your operating system:      Unix:    cd CSCOpx/campus/bin/   ./reinitdb.pl   NT:    cd CSCOpx/campus/bin/   perl reinitdb.pl 
  3. The reinitdb.pl command displays this prompt:

       This will erase all data from the database. Are you sure [y/n]:

  4. Type y
  5. Press the Enter/Return key, and the ANI information regarding Network Discovery (Wbu tables) is erased from the database. A new ANI Server connection is established, and network discovery is initiated.
  6. If you are still unable to connect to the ANI Server, perform these steps:
     1. Stop the CiscoWorks Daemon Manager.
     2. Re-type the reinitdb.pl command with -restore option, as shown:

       Unix: 
       cd CSCOpx/campus/bin
       ./reinitdb.pl -restore
       NT/Windows2000: 
       cd CSCOpx/campus/bin/ 
       perl reinitdb.pl -restore

• Restart the CiscoWorks Daemon Manager if no errors are returned from the reinitdb.pl command. The -restore option deletes the existing ANI database, not just the contents. A new ANI database is created.