CiscoWorks Campus Manager

Document ID: 19000

Contents

Introduction

Prerequisites

Please 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.

Hardware and Software Versions

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

• Campus Manager 3.2
• Campus Manager 3.3

Troubleshooting Connection Problems

If you are unable to connect to your ANI server verify the following:

Order of File Entry

Verify that your first entry in the file, /etc/hosts, 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 you put in the URL locator to connect to CiscoWorks through the browser.

Current Java Virtual Machine

Verify that you have the latest compatible Java Virtual Machine (JVM) loaded on your client machine. To verify, follow these steps:

1. Enable JVM console logging from the web browser:
   1. Go to: IE-->Tools-->Internet Options--->Advanced Tab-->Microsoft VM
   2. Check all the boxes.
   3. Save the changes.
   4. Log out of CiscoWorks.
   5. Close the browser.
   6. Restart the browser.
2. Check the JVM version:
   1. Go to: IE-->View-->Java Console and the javaconsole window appears.
      
   2. Verify from the first line in the java console window the version of JVM is Microsoft (R) VM for Java, 5.0 Release 5.0.0.3309 or later.
      
   3. If the JVM is not latest, download the latest JVM fix from the Microsoft site.
      Choose product name--> Virtual Machine
      Choose your Operating system--> Win95/98/NT/Windows2000
      Download/ Install the latest version.
3. Relaunch the application.      

CampusManager and MS Internet Explorer

If you are using the MS Internet Explorer (IE) browser to access and launch CampusManager, do not install Client Application Manager (CAM).  If you already have CAM installed, uninstall it. To verify, do one of the following:

• 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, do the following:
  1. Under Temporary Internet Files, click Settings and the Settings window appears.
  2. Click View Objects. CamRegistry is listed in the new window, under Program File.
  3. If CAM Registry is installed, right click and select Remove.
  4. Clear the browser cache, by going to the General tab and selecting Delete files and Clear history.
  5. Restart the browser.

Restart the Server

Sometimes you can rectify the problem by stopping and restarting the ANI server process from the screen. Follow these steps:

1. Stop the server: CW2000Server/Server Configuration-->Administration-->Process Management-->Stop Process.
2. Restart: CW2000Server/Server Configuration-->Administration-->Process Management-->Start Process.
3. Launch the Campus Manager again.

Corrupt Database Tables

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

1. From the command line/dos prompt, log in as root/local admin.
2. Issue the following command for your operating system:
   • Unix:

      cd CSCOpx/bin/
      ./reinitdb.pl 

   • NT:

      cd CSCOpx/bin/
      perl reinitdb.pl
       

3. The command, reinitdb.pl displays the following prompt:

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

4. Type y
5. Presst 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, do the following:
   1. Stop the CiscoWorks Daemon Manager
   2. Re-type the reinitdb.pl command with -restore option.
      • Unix:

        cd CSCOpx/bin 
        ./reinitdb.pl -restore

      • NT/Windows2000:

        cd CSCOpx/bin/ 
        perl reinitdb.pl -restore 

   3. 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 .

SNMP Setting

Improper SNMP settings data, as defined in the format, can cause connection problems. Verify your setting by going to:

CiscoWorks2000 Server/Server Configuration->setup->ANI 
  Server Admin->SNMP Settings

target:read_community:UNUSED:timeout:retries:UNUSED:UNUSED:write_community

The target is the IP address/IP network that you want to discover using the SNMP strings indicated. An asterisk '*' represents a wildcard, therefore everything in that octet(0-255) is discovered.

For example, you can use the asterisk in any or all octets:

172.22.2.*:public::6:2:::private:

198.126.241.2:public::6:2:::public:

*.*.*.*:public::6:2:::private:

Verify Processes

1. From the CiscoWorks 2000 Server, issue the following commands:
   • UNIX CLI mode:

     
     cd /opt/CSCOpx/bin/ 
     pdshow ANIServer 

   • NT/Windows2000 command mode:

     
     cd $NMSRoot/CSCOpx/bin 
     pdshow ANIServer. 

2. Ensure that the following information is displayed:

   Process= ANIServer 
   State  = Running but busy flag set 
   Pid    = 1204 
   RC     = 0 
   Signo  = 0 
   Stop   = Not applicable 
   Core   = Not applicable 
   Info   = ANIServer started. 

3. Repeat the above steps for the ANIDbEngine and EDS. The ANIServer depends on these processes to be up and running.

Multi-Homed Server

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.

To ensure Campus Manager runs properly on multi-homed machines, follow these steps:

1. Open the gatekeeper configuration file (gatekeeper.cfg).
   • 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 the above file or stop/start CW2000 processes.

2. Go to the section that begins with the following line:

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

3. By default, the above lines are commented with #. Uncomment the property by removing the # character.

4. Enter the appropriate IP address in the following fields:
   • vbroker.gatekeeper.backcompat.callback.host=<external-IP-address>
   • vbroker.se.exterior.host=<external-IP-address>
   • vbroker.se.iiop_tp.host=<external-IP-address>
   • vbroker.se.interior.host=<external-IP-address>
5. Save the file.

6. Stop the CW2000 processes by issueing the following command from a DOS window CLI:
   • Solaris: /etc/init.d/dmgtd stop
   • Windows: net stop crmdmgtd

7. Delete the gatekeeper.ior file, located in the following directory:
   • Solaris: /opt/CSCOpx/www/classpath
   • Windows: $NMSROOT\CSCOpx\www\classpath

8. Start the CW2000 processes by issueing the following command from a DOS window CLI:
   • Solaris: /etc/init.d/dmgtd start
   • Windows: net start crmdmgtd

Related Information

• CD One
• Troubleshooting the ANI Discovery Used by Campus Manager and UserTracking