User Guide for CiscoWorks2000 Server (CD One, 5th Edition)
Diagnosing Problems with the CiscoWorks2000 Server
Downloads: This chapterpdf (PDF - 326.0KB) The complete bookPDF (PDF - 1.48MB) | Feedback

Diagnosing Problems with the CiscoWorks2000 Server

Table Of Contents

Diagnosing Problems with the CiscoWorks2000 Server

Verifying Server Status

Testing Device Connectivity

Troubleshooting the CiscoWorks2000 Server

Frequently Asked Questions

Troubleshooting Suggestions


Diagnosing Problems with the CiscoWorks2000 Server


Use these tools and suggestions to diagnose problems with the CiscoWorks2000 Server:

Verifying Server Status

Testing Device Connectivity

Troubleshooting the CiscoWorks2000 Server

Verifying Server Status

Server tools enable you to gather and analyze information about your CiscoWorks2000 Server (see Table 5-1).

Table 5-1 Server Tools Tasks 

Task
Purpose
Action
Administrative Tasks

Collect server information.

Provides system information, environment, configuration, logs, and web server information

Server Configuration > Diagnostics >
Collect Server Info

or

Enter the following command:

On Windows 2000:

%NMSROOT%\bin\collect.info

On Solaris:

$NMSROOT/bin/collect.info

where %NMSROOT% and $NMSROOT are the directories where you installed CiscoWorks2000, in Windows 2000 and Solaris respectively.

Perform self test.

Runs self-tests and generates a report with the results

Server Configuration > Diagnostics >
Self Test

Check process failures.

Displays the failed process and time failure occurred

Server Configuration > Diagnostics >
Process Failures

Obtain detailed status of ANI Server.

Displays detailed system configuration and settings for ANI Server

Server Configuration > Diagnostics >
Analyze ANI Server

Enhance ANI discovery performance.

Enables you to view and enhance discovery performance through tuning and metrics.

Server Configuration >Diagnostics >
Discovery Metrics

All Users

Verify installed applications and versions.

Lists date, state, and version of currently installed CiscoWorks2000 applications and packages and whether any patches have been applied

Server Configuration > About the Server  > 
Applications and Versions

Check process status.

Checks whether back-end processes are in an interim state

Server Configuration > Administration  >
Process Management > Process Status


Testing Device Connectivity

The connectivity tools enable you to test device connectivity and reachability and troubleshoot nonresponsive devices. Some connectivity tools require system administrative-level privileges (see Table 5-2).

Table 5-2 Connectivity Tools Tasks 

Task
Purpose
Action
Administrative Tasks

Check device connectivity.

Verifies that the CiscoWorks2000 server can communicate with the device

Server Configuration > Diagnostics > Connectivity Tools > Management Station to Device

Check SSH connectivity to the device

Verifies that the CiscoWorks2000 server can communicate with the device using SSH.

Server Configuration > Diagnostics > Connectivity Tools > Management Station to Device

Select the SSH check box.

All Users

Look up host or device.

Provides device or host information via the name server

Server Configuration > Diagnostics > Connectivity Tools > NSLookup

Check device traceroute.

Detects routing errors between the network management station and a target device

Server Configuration > Diagnostics > Connectivity Tools > Traceroute

Ping a device.

Tests device reachability using an ICMP echo message and its reply

Server Configuration > Diagnostics > Connectivity Tools > Ping


Troubleshooting the CiscoWorks2000 Server

This section provides information on frequently asked questions (FAQs) and suggestions for troubleshooting the CiscoWorks2000 Server components. If the suggestions do not resolve the error, check the release notes supporting your platform for possible workarounds, or contact the Cisco TAC or your customer support.

Frequently Asked Questions

I have CiscoWorks2000 2.1 release installed on my computer running Windows 2000, and just finished installing a CiscoWorks2000 application from the 2.0 release. After installation, the daemon manager does not start, and displays the error message, The Service is not responding to the control function. What is wrong? How do I correct this problem?

While invoking CiscoWorks2000, the browser displays the exception error SSL Initializer class not found. How do I correct this error?

While invoking CiscoWorks2000, the browser displays the message, Could not connect to JRun Connector Proxy . Please contact the system administrator for this web site. Why does this happen, and how do I correct this?

When I invoke CiscoWorks2000, the browser displays the message "The Server is not yet ready to accept requests. Please try connecting after sometime. If the problem persists, please contact your System Administrator."

When I connect to the CiscoWorks2000 Server in the secure mode (HTTPS) using Netscape Navigator, the browser returns I/O errors and displays the message Netscape has encountered bad data from the server. Why does this happen?

When I invoke CiscoWorks2000 in the secure mode (HTTPS), there are too many dialogs making the process tedious. Is there a way to reduce the number of dialogs and steps?

While invoking CiscoWorks2000, the SSL Initialization window displays Permission Denied errors at the time of downloading JSSE jar files. Why does this happen?

While invoking CiscoWorks2000, the browser displays the exception error message java.security.AccessControlException: access denied. What is wrong?

When invoked in the secure mode (HTTPS), the CiscoWorks2000 Login Manager displays the exception error message javax.net.ssl.SSLException: untrusted server cert chain. What is wrong? How do I correct this problem?

During SSL initialization, the browser displays the error message, The Server Certificate is not valid before date though I have a self-signed certificate created the same day. What is wrong?

My server certificate for CiscoWorks2000 has expired. What should I do?

While invoking CiscoWorks2000, my browser stops responding, and I am not able to get the CiscoWorks2000 Login Manager. What should I do?

I installed CD One and got an error message that EDS wasn't registered with the daemon manager. Did I do anything wrong?

The Java Plug-in does not get enabled in the client browser. How do I enable the Plug-in?

I have enabled the Java Plug-in in the control panel. But the Plug-in does not get enabled. What else should I do?

Which version of the Java Plug-in should I use for CiscoWorks2000 to function properly?

Is there anything I should do before I invoke Netscape Navigator sessions in UNIX systems to run CiscoWorks2000?

Why do some CiscoWorks2000 applications not appear in the product?

Why can't I start my CiscoWorks2000 application?

What kind of directory structure does CiscoWorks2000 use when backing up data?

What does "cmf" stand for in the database path?

I'm locked out of the CiscoWorks2000 Server. Why did this happen, and how do I regain access?

How can I check the status of the ANI Server?

How can I verify whether the ANI discovery is complete or almost complete?

How can I verify whether the ANI Server is fully functional?

What if the database is inaccessible?

How do I change the port for osagent in Windows?

How do I change port for osagent in Solaris?

How do I change the ESS port in Solaris?

How do I change ESS port in Windows?

I have CiscoWorks2000 2.1 release installed on my computer running Windows 2000, and just finished installing a CiscoWorks2000 application from the 2.0 release. After installation, the daemon manager does not start, and displays the error message, The Service is not responding to the control function. What is wrong? How do I correct this problem?

CiscoWorks2000 applications from Release 2.0 do not support SSL, and use an old install framework. This install framework does not recognize the SSL support provided in CiscoWorks2000 release 2.1, and proceed with the installation. But after installation, the daemon manager in CiscoWorks2000 cannot start if you have enabled SSL in CiscoWorks2000 Server. This is because, SSL compliant applications cannot co-exist with non-SSL applications in CiscoWorks2000 Server in the SSL enabled mode.

On Windows 2000, you can find the details of the error in Event Viewer and syslog.log file.

To correct this problem, you have to disable SSL in CiscoWorks2000 Server. For more information, see the "Disabling SSL" section.

While invoking CiscoWorks2000, the browser displays the exception error SSL Initializer class not found. How do I correct this error?

To correct this error:


Step 1 Verify Java Plug-in 1.3.1 is installed and enabled.

Step 2 Clear the browser cache.

Step 3 Clear the Java Plug-in cache:

On Windows:

a. Go to Start > Settings > Control Panel > Java Plug-in 1.3.1.

b. In the Java Plug-in Control Panel, select the Cache tab.

c. Click the Clear JAR Cache button.

In Solaris:

a. To invoke the Java Plug-in Control Panel, enter the following at the shell prompt:

/usr/j2se/bin/ControlPanel

b. In the Java Plug-in Control Panel, select the Cache tab.

c. Click the Clear JAR Cache button.

Step 4 Uninstall any other version of Java Plug-in, if they are present, and install Java Plug-in 1.3.1. For more information, see the "Installing the Java Plug-in" section.


Note It is recommended that you use the tar file or autoinstall file downloaded from CiscoWorks2000 Server to install Java Plug-in 1.3.1.



While invoking CiscoWorks2000, the browser displays the message, Could not connect to JRun Connector Proxy . Please contact the system administrator for this web site. Why does this happen, and how do I correct this?

The browser displays this error, if you invoke CiscoWorks2000 immediately after restarting the daemon manager in CiscoWorks2000 Server.

To correct this problem:


Step 1 In the CiscoWorks2000 Server CLI, enter the following command to verify whether all processes are running:

$NMSROOT/bin/pdshow

Step 2 Wait for sometime for the JRun Servlet engine to come up and then invoke CiscoWorks2000 again.


When I invoke CiscoWorks2000, the browser displays the message "The Server is not yet ready to accept requests. Please try connecting after sometime. If the problem persists, please contact your System Administrator."

This error message is displayed, when all the processes are not up and running on the Ciscoworks2000 Server. Typically it occurs when the user starts the daemon Manager and immediately invokes the CiscoWorks2000 Server.

To correct this problem, check whether all the processes are running on the server and invoke Ciscoworks2000 after sometime.


Note The user will get the CiscoWorks2000 desktop only if the web server and JRunProxyServer processes are up and running,


When I connect to the CiscoWorks2000 Server in the secure mode (HTTPS) using Netscape Navigator, the browser returns I/O errors and displays the message Netscape has encountered bad data from the server. Why does this happen?

This problem occurs when you do the following:

You create a new server certificate using the same hostname

You have set the browser to accept the old server certificate, till it expires

Typically, this problem is fixed when you clear the entry for your old server certificate from the browser.


Note The I/O errors in Netscape Navigator running in secure mode (HTTPS) is often caused by configured certificates in the client computer.


When I invoke CiscoWorks2000 in the secure mode (HTTPS), there are too many dialogs making the process tedious. Is there a way to reduce the number of dialogs and steps?

Yes. You have the following options:

If you are using self-signed certificates:

In Netscape Navigator, select the option Accept the Server Certificate forever (until it expires) in the New Site Certificate wizard, if you are confident about the identity of the server.

In Microsoft Internet Explorer, install the certificate in the browser's trusted certificate stores, if you are confident about the identity of the server.

Use a server certificate issued by a prominent third party certificate authority (CA).

Configure the hostname in your server certificate properly, and use the same hostname to invoke CiscoWorks2000.

Select the Grant Always option in Java Plug-in messages. If you do this, the Plug-in dialogs will not be displayed when you invoke CiscoWorks2000, until the certificate expires.

While invoking CiscoWorks2000, the SSL Initialization window displays Permission Denied errors at the time of downloading JSSE jar files. Why does this happen?

The SSL Initialization process downloads and installs the JSSE jar files inside a folder where the Java Plug-in is installed on your computer. (On Windows, this folder is typically located under C:\Program Files\Javasoft\) The SSL Initialization process displays Permission Denied when you do not have write permission in the Java Plug-in installation folder.

If you do not have write permission to the Java Plug-in installation folder, contact the system administrator and get the necessary permissions when you invoke CiscoWorks2000 for the first time.

All users should have sufficient permissions for Plug-in folders

You must have write access to the following directories:

PLUGIN_INSTALLATION\lib\ext—If you have to download JSSE jars

PLUGIN_INSTALLATION\lib\security\cacerts or PLUGIN_INSTALLATION\lib\security\cacerts.session files—If you decide to grant permission for the current session or grant always for the Server Certificate.

where PLUGIN_INSTALLATION is the directory where you have installed the Java Plug-in.


Note It is recommended to give write access to the users right from the parent directory of PLUGIN_INSTALLATION (Typically this is C:\Program Files\Javasoft\ in Windows 2000. If you installed the Java Plug-in in a custom path make the changes accordingly) and also ensure that all subdirectories have the required permissions.


While invoking CiscoWorks2000, the browser displays the exception error message java.security.AccessControlException: access denied. What is wrong?

The browser displays this error message if you deny permission to the signed applet to run while invoking CiscoWorks2000. For more information, see the "Invoking the CiscoWorks2000 Desktop" section.

When you invoke CiscoWorks2000, the browser displays a Java Plug-in Security Warning window, which prompts you to grant permission to run the signed applet. CiscoWorks2000 requires you to grant permission to run this applet. If you deny permission to run the applet, CiscoWorks2000 displays the error message java.security.AccessControlException: access denied.

To invoke CiscoWorks2000 again, do the following:


Step 1 Close all browser sessions.


Note Ensure that the Java Plug-in console is also closed.


Step 2 Clear the browser cache and Java Plug-in cache.

Step 3 Restart the browser and invoke CiscoWorks2000.


When invoked in the secure mode (HTTPS), the CiscoWorks2000 Login Manager displays the exception error message javax.net.ssl.SSLException: untrusted server cert chain. What is wrong? How do I correct this problem?

To invoke CiscoWorks2000 in the secure mode (HTTPS), you must enter the URL as follows:

https://server_name:port_number

where server_name is the name of the CiscoWorks2000 Server and port_number is the TCP port used by the CiscoWorks2000 Server, when SSL is enabled (secure mode).

This ensures that proper SSL initialization is done before CiscoWorks2000 launches the Login Manager. In the secure mode, you must go through the complete SSL initialization procedures before you log in to CiscoWorks2000. If you bypass these procedures, the Java Plug-in applications will not function properly.

When you get the exception error given above, close all the browser sessions, and invoke CiscoWorks2000 again. For more information, see the "Invoking CiscoWorks2000 Desktop in SSL Enabled Mode (HTTPS)" section.

During SSL initialization, the browser displays the error message, The Server Certificate is not valid before date though I have a self-signed certificate created the same day. What is wrong?

You may get this error if:

The date on CiscoWorks2000 Server and the client computer are not set properly or not set to current date

The time zone settings in CiscoWorks2000 Server and the client computer are not set properly or set to a different time zone

To fix the problem, set the date and time zone on CiscoWorks2000 Server and the client computer, restart the browser and invoke CiscoWorks2000 again.

My server certificate for CiscoWorks2000 has expired. What should I do?

If you are using a self-signed certificate, you can create a new certificate using the Create Self Signed Certificate option in CiscoWorks2000 Server. For more information, see the "Managing Security Certificates" section.

If you are using a third party issued certificate, you must contact the certificate authority (CA) and renew the certificate. You can use a self-signed certificate till you get the certificate renewed by the CA.


Note Before you perform any certificate management operations—creating or modifying certificates, back up the certificate files, the server private key in particular, and keep them in a safe location.


While invoking CiscoWorks2000, my browser stops responding, and I am not able to get the CiscoWorks2000 Login Manager. What should I do?

When you start CiscoWorks2000, a Java Plug-in dialog box is invoked, prompting you to grant permission for a signed applet to run. There is a chance that this dialog box goes behind your browser window, if you have several application or browser windows running.

On Windows, use ALT+tab to shift the focus to the Java Plug-in dialog box, and grant permission for the applet to run.

I installed CD One and got an error message that EDS wasn't registered with the daemon manager. Did I do anything wrong?

EDS is part of the CD One deliverable but is not enabled without Campus Manager or Resource Manager Essentials. If you are going to install either of these application suites, EDS will be automatically enabled after installation.

The Java Plug-in does not get enabled in the client browser. How do I enable the Plug-in?

To enable the Plug-in, do the following:

OS
Action
Windows

Start > Settings > Control Panel > Java Plug-in 1.3.1

In the Java Plug-in Control Panel:

1. Select Enable Java Plug-in in the Basic tab.

2. Click Apply.

Solaris

Execute /usr/j2se/bin/Control Panel.

In the Java Plug-in Control Panel:

1. Select Enable Java Plug-in in the Basic tab.

2. Click Apply.

AIX

Execute /usr/java131/jre/bin/JavaPluginControlPanel.

In the Java Plug-in Control Panel:

1. Select Enable Java Plug-in in the Basic tab.

2. Click Apply.

HP-UX

Execute /.netscape/java/ControlPanel

In the Java Plug-in Control Panel:

1. Select Enable Java Plug-in in the Basic tab.

2. Click Apply.


I have enabled the Java Plug-in in the control panel. But the Plug-in does not get enabled. What else should I do?

If you have installed the browser after installing the Java Plug-in, the Plug-in may not get enabled even after you enable it in the control panel.

Do the following:


Step 1 Uninstall the browser and Plug-in.

Step 2 Install the browser.

Step 3 Install the Java Plug-in.


Which version of the Java Plug-in should I use for CiscoWorks2000 to function properly?

CiscoWorks2000 supports Java Plug-in 1.3.1 only in all the supported clients and operating systems. It is advised not to install any other Plug-ins other than this one, for CiscoWorks2000 to function properly.

Is there anything I should do before I invoke Netscape Navigator sessions in UNIX systems to run CiscoWorks2000?

Yes. You must source the file /jpi.cshrc before invoking any Netscape session in UNIX systems, so that the environment is set for the browser to function properly on invoking CiscoWorks2000.

Why do some CiscoWorks2000 applications not appear in the product?

The CiscoWorks2000 Server represents a common set of management services which are shared by multiple network management applications. These services are enabled when a suite is installed and an application that relies on a particular service enables it.

If a particular suite of applications does not use a particular services, the services might not appear on the CiscoWorks2000 Server desktop. Applications and application suites may not use these features at all or to the fullest extent to which they are available. Refer to the user guide for your application suite to determine the extent to which these features are used.

Why can't I start my CiscoWorks2000 application?

If you cannot start your CiscoWorks2000 application and receive error messages complaining that the WebServer or ANIServer might not be running (even though pdshow indicates that those processes are up and running), you might need to check how your machine is resolving its server name and IP address.

The CiscoWorks2000 CORBA applications require name resolution to work properly. Choose Domain Name Service (DNS) or any other form of name resolution supported by both your client and server.

Configure the name resolution mechanism and restart the CiscoWorks2000 Server to access the application correctly.

What kind of directory structure does CiscoWorks2000 use when backing up data?

CiscoWorks2000 uses a standard database structure for backing up all suites and applications. See Table 5-3 for sample directory structure for the CiscoWorks2000 Server (represented by the cmf acronym). The cmf directory has two databases: cmf and ani.

Table 5-3 Sample CMF Backup Directory 

Directory path
Description
Usage Notes

/tmp/1

Number of backups

1, 2, 3...

/tmp/2/cmf

Application or suite

Backs up CiscoWorks2000 Server applications.

/tmp/1/cmf/filebackup.tar

CiscoWorks2000 server application tar files

Application data is stored in the datafiles.txt which are compiled into the tar file.

/tmp/1/cmf/database

CiscoWorks2000 Server database directory

Includes files for each database:

xxx_DbVersion.txt

xxx.db database files

xxx.log database log files

xxx.txt database backup manifest file


What does "cmf" stand for in the database path?

The cmf acronym in the database structure represents the Common Management Foundation (CMF). This phrase describes the set of management services provided by the CiscoWorks2000 Server.

I'm locked out of the CiscoWorks2000 Server. Why did this happen, and how do I regain access?

There are several reasons why you might have been locked out. Most likely it is due to changes made using the Select Login Module option (see the "Understanding Fall Back Options" section). You will need to replace the incorrect login module with a default configuration, log into CiscoWorks2000, and return to the login module to correct one or more of the following:

Authentication service that does not exist

Authentication service that is not reachable

Incorrect host name

Incorrect port number

Incorrect configuration parameters


Note Do not alter the existing technologies in the default configuration file.


If all of the parameters listed are correct, see the "Troubleshooting Suggestions" section.

How can I check the status of the ANI Server?

To check the status of the ANI Server to determine if it is up and running properly:


Step 1 From the CiscoWorks2000 desktop, select Server Configuration > Administration > Process Management > Process Status.

Step 2 Use the information in Table 5-4 to verify the current status of the ANI Server.


Table 5-4 ANI Server Status 

State
Explanation
Solution

Administrator has shut down the server.

Administrator intentionally shut down the ANI Server.

Start the ANI Server to get it up-and-running again.

Administrator has shut down the server.

ANI Server has failed to come back up.

Might occur after stopping and restarting the ANI Server.

Failed to Run.

ANI Server could not start up initially.

Check the log for details:

On Solaris: /var/adm/CSCOpx/logs/daemons.log

On Windows 2000: %NMSROOT%\
log\ANIServer.log, where %NMSROOT% is the directory where you installed CiscoWorks2000.

Program started—No mgt msgs received.

ANI Server is in the process of starting up.

Wait a few minutes, and check the status again.

Running but busy flag set.

Normal state. ANI Server is up-and-running normally.

None. Everything is normal.

Can also appear when the ANI Server is hung or not responding.

If discovery does not appear to be completing, check the log for details:

On Solaris: /var/adm/CSCOpx/logs/daemons.log

On Windows 2000: %NMSROOT%\log\
ANIServer.log, where %NMSROOT% is the directory where you installed CiscoWorks2000.

The ANI Server cannot load the database. Run reinitdb.pl to reinitialize the database.

The ANI database is corrupted, and the ANI Server cannot run with a corrupted database.

Reinitialize the database:

From the command prompt or shell window, run:

On Solaris: $NMSRROOT/bin/reinitdb.pl

On Windows 2000: perl %NMSROOT%\bin\reinitdb.pl

where %NMSROOT% and $NMSROOT are the directories where you installed CiscoWorks2000, in Windows 2000 and Solaris respectively.


How can I verify whether the ANI discovery is complete or almost complete?

Use the Discovery Metrics task to check if discovery is in progress. From the CiscoWorks2000 desktop:


Step 1 Select Server Configuration > Diagnostics > Discovery Metrics.

Step 2 Use the "Percent Complete" column to determine if the discovery task is finished.


How can I verify whether the ANI Server is fully functional?

The CiscoWorks2000 Server includes several tools to verify varying functional states of the ANI Server. To progressively determine the cause of any problems:


Step 1 Select Server Configuration  > About the Server  > About ANI Server > Copyrights and Versions.

If this page appears, you have verified that the web server and its applets are working properly.

If this page does not appear, the problem is not related to the ANI Server. The CiscoWorks2000 web server is not running properly.

Step 2 Select Server Configuration  > About the Server  > About ANI Server > Devices Support.

If a list of icons, device names, and device OIDs appears, you have verified that the ANI Server is up-and-running.

If an error occurs, follow the suggestions appropriate to the reported state of the ANI Server (see Table 5-4).

Step 3 Select Server Configuration  > Diagnostics  > Analyze ANI Server.

If this page appears, verify that the name of the ANI Server and the host running it is correct.

If an error occurs, follow the suggestions appropriate to the reported state of the ANI Server (see Table 5-4).

Step 4 Select Server Configuration > Diagnostics >Discovery Metrics.

If this page appears, you have verified that the ANI Server is working.

If an error occurs, the ANI Server is not working properly.


What if the database is inaccessible?

If the server is not able to connect to the database, the database might be corrupt or inaccessible. This can occur if processes are not running. Try the following:


Step 1 Log in to CiscoWorks2000 as admin.

Step 2 Select Server Configuration > Diagnostics > Process Failures to get a list of CiscoWorks2000 back-end processes that have failed.

Step 3 Select Server Configuration > Diagnostics > Self Test.

Click Create to create a report.

Click Display to display the report.

Step 4 Select Server Configuration >Diagnostics >Collect Server Info.

Step 5 Click the Product Database Status link to get detailed database status.

Step 6 Contact the Cisco TAC or your customer support to get the information you need to access the database and find out details about the problem. After you have the required information, perform the following tasks for detecting and fixing database errors.


Depending upon the degree of corruption, the database engine may or may not start. For certain corruptions, such as bad indexes, the database can function normally until the corrupt index is accessed.

Database corruptions, such as index corruptions, can be detected by the dbvalid utility, which requires the database engine to be running.

To detect database corruption:


Step 1 Log on as root (UNIX) or with administrator privileges (Microsoft Windows).

Step 2 Stop the Daemon manager if it is already running:

UNIX—/etc/init.d/dmgtd stop

Microsoft Windows—net stop crmdmgtd (enter command in an MS-DOS window)

Step 3 Make sure no database processes are running and there is no database log file. For example, if the database file is /opt/CSCOpx/databases/rme/rme.db, the database log file is /opt/CSCOpx/databases/rme/rme.log. This file is not present if the database process shuts down cleanly.

Step 4 (UNIX only) Check if the database files(s) and the transaction log file (*.log) are owned by user casuser. If not, change the ownership of these files to user casuser and group casusers.

Step 5 (UNIX only) Set environment variables (K-Shell syntax):

export SATMP=/tmp/.SQLAnywhere

export LD_LIBRARY_PATH=/opt/CSCOpx/lib (Solaris only)

export SQLANY=/opt/CSCOpx/objects/db

Step 6 Start the database engine:

UNIX—start it in the foreground:

$SQLANY/bin/dbeng7 -c 16M -m -n validateEng {database file name} -n validateDb

Microsoft Windows—start it in an MS-DOS window. For example, if CiscoWorks2000 is installed in d:\cw2000:

d:\cw2000\objects\db\win32\dbeng7 -c 16M -n testEng {database file name} -n testDb

If the database engine starts, it displays messages like this (in Microsoft Windows, message appears in a new window):

16384K of memory used for caching 
Transaction log: xxx.log 
Starting checkpoint 
Finished checkpoint 
Database: xxx.db started 
Press 'q' to quit

If this message does not appear, the database has a fatal corruption, but can sometimes be recovered.

Step 7 (UNIX only) If there was no error in step 5, Restart the engine as a daemon:

$SQLANY/bin/dbeng7 -ud -c 16M -m -n validateEng {database file name} -n validateDb

Step 8 Run dbvalid to detect any other errors such as corrupt indexes:

UNIX syntax—$SQLANY/bin/dbvalid -c "uid={dba user id for the database};pwd={dba password for the database}; eng=validateEng;dbn=validateDb"

Windows syntax—d:\cw2000\objects\db\win32\dbvalid -c "uid={dba user id for the database};pwd={dba password for the database};eng=validateEng;dbn=validateD"

The dbvalid command displays a list of tables being validated. The Validation utility scans the entire table, and looks up each record in every index and key defined on the table. If there are errors, the utility displays something like:

Validating DBA.xxxx 
run time SQL error -- Foreign key parent_is has invalid or duplicate 
index 
entries 1 error reported

On UNIX, the command also returns a non-zero return code, that is, $? = 1.


To fix database errors:

Fatal errors may be due to a corrupt database or a corrupt or missing database transaction log file. If the transaction log is missing or corrupt, the database can be recovered at the cost of a few missing transactions. This can be done by forcibly starting the database without a transaction log; for example:

$SQLANY/bin/dbeng7 -f -n rmeTst /opt/CSCOpx/databases/rme/rme.db

This starts the database engine in recovery mode, recovers the database, and immediately terminates the engine. Messages similar to the following appear during the recovery process:

2648K of memory used for caching
Database recovery in progress
Last checkpoint on Mon Dec 06 1999 03:06 pm
Checkpoint log...
Transaction log: px.log...
Forcing recovery without transaction log
Rollback log...
Checkpointing...
Starting checkpoint
Finished checkpoint
Recovery complete
Recovered to last checkpoint

If the corruption is due to bad indexes, the indexes must be dropped and then recreated:


Step 1 Start the engine as in step 6 for Microsoft Windows or step 7 for UNIX.

Step 2 Run the isql utility to fix the bad indexes:

UNIX syntax—$SQLANY/bin/isql -c "uid={dba user id};pwd={dba password};eng=validateEng;dba=validateDb"

Microsoft Windows syntax (run in an MS-DOS window). For example, if CiscoWorks2000 is installed in d:\cw2000: d:\cw2000\objects\db\win32\isql-c "uid={dba user id};pwd={dba password};eng=validateEng;dbn=validateDb"

Step 3 Run the following isql commands to delete and add the indexes. This could take a while to run depending upon the number of rows in the table.

Delete an index with the SQL statement:

DROP INDEX {the index in question}

Add an index with the SQL statement:

CREATE [UNIQUE] INDEX xyz on {your table pqr} column_name {ASC|DESC},...


How do I change the port for osagent in Windows?

To change the port for osagent in Windows:


Step 1 Back up your Windows registry.

Step 2 In the Registry Editor, navigate to HKEY_LOCAL_MACHINE >
SOFTWARE > Cisco > Resource Manager > Current Version > Daemon > RmeOrb

Step 3 Change the value of Args from -p 42342 to an unused port number, for example -p 44444.

Step 4 Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Cisco > Resource Manager > Current Version > Daemon > RmeGatekeeper

Step 5 Change the value of Args from

-DNMSROOT=C:\PROGRA~1\CSCOpx -DORBagentPort=42342 com.visigenic.vbroker.gatekeeper.GateKeeper -props D:\PROGRA~1\CSCOpx\lib\visigenics\gatekeeper.cfg

to

-DNMSROOT=C:\PROGRA~1\CSCOpx -DORBagentPort=44444 com.visigenic.vbroker.gatekeeper.GateKeeper -props D:\PROGRA~1\CSCOpx\lib\visigenics\gatekeeper.cfg

Step 6 Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Cisco > Resource Manager > Current Version > Environment:

Step 7 Change the value of OSAGENT_PORT and PX_OSA_PORT from 42342 to 44444.

Step 8 Open the file C:\PROGRA~1\CSCOpx\lib\classpath\md.properties, in any plain text editor, such as Notepad.

Step 9 Change the value of OSAGENT_PORT and PX_OSA_PORT from 42342 to 44444.

Step 10 Reboot the server.


How do I change port for osagent in Solaris?


Step 1 Stop daemons.

Step 2 Make sure that no CSCO processes are running.

Step 3 Make sure all ports used by CW2K are freed.

You can do this as follows:

netstat -na | grep 423

netstat -na | grep 174

If these ports are free, you will not see any output.

Step 4 Back up /opt/CSCOpx/objects/dmgt/dmgtd.conf file.

Step 5 Verify whether the port 44444 is free, using the following command:

netstat -na | grep 44444

If the port is free, you will not see any output.

Step 6 Change the port for RmeOrb from, -p 42342 to -p 44444.

Step 7 Change the port number for RmeGatekeeper from 42342 to 44444.

Step 8 Open the file /etc/services in a plain text editor such as Vi.

Step 9 Comment out the entry for CSCOsa port and add the following entry:

cscoosa 4444/udp # CSCO NM osagent


Note The change is for the port number only.


Step 10 Open /opt/CSCOpx/lib/classpath/md.properties, in a plain text editor, such as Vi.

Step 11 Change the entry for OSAGENT_PORT= 42342 to the following:

OSAGENT_PORT=44444

Step 12 Change the entry PX_OSA_PORT=42342 as follows:

PX_OSA_PORT=44444

Step 13 Restart the daemons. It is recommended that you reboot the server.


How do I change the ESS port in Solaris?

There are 4 ports related to ESS:

ESS Service Port:7500/udp

ESS listening port:7500/tcp

ESS HTTP Port:7580/tcp

ESS Routing Port:7588/tcp

The ports mentioned above are default ports. The alternative ports defined for these in CiscoWorks2000 are 42350,42351,42352,42353 respectively.

To change the ports:


Step 1 Open the file /opt/CSCOpx/objects/ess/conf/essproperties.conf in a plain text editor, such as Vi.

Step 2 Change the port numbers as required.

Step 3 Reboot the system.


How do I change ESS port in Windows?


Step 1 Back up your Windows registry.

Step 2 In the Registry Editor, navigate to HKEY_LOCAL_MACHINE >
SOFTWARE > Cisco > Resource Manager > Current Version > Daemon > ESS

Step 3 Change the value of Args from

-store d:\PROGRA~1\CSCOpx\objects\ess\conf\rvrd.conf -logfile d:/PROGRA~1/CSCOpx/log\ess.log -listen 7500 -no-http

to

-store d:\PROGRA~1\CSCOpx\objects\ess\conf\rvrd.conf -logfile d:/PROGRA~1/CSCOpx/log\ess.log -listen 42350 -no-http

Step 4 Change the corresponding entry in $NMSROOT\objects\ess\conf\essproperties.conf.

Step 5 Reboot the server.


Troubleshooting Suggestions

Use the suggestions in Table 5-5 to resolve errors or other problems with the CiscoWorks2000 Server.

Table 5-5 Troubleshooting Suggestions 

Symptom
Probable Cause
Possible Solutions
Desktop

Authorization required. Please log in with your username and password.

Incompatible browser causing cookie failure (unable to retrieve cookie).

Refer to the installation documentation for supported Internet Explorer/Navigator software.

Database: ODBC error with Essentials. (Microsoft Windows only.)

ODBC resource.dll and ODBC driver manager are different versions.

Install ODBC from Microsoft Windows CD (selecting SQL server).

Display: applet cannot start: class browserServer not found. (Solaris only).

The server name is not in the httpd.conf file.

Add the server name in the httpd.conf file in the $NMSROOT\lib\web\conf directory.

Display: only right side of desktop displayed.

Incompatible browser software.

Refer to the installation documentation for supported Internet Explorer/Navigator software.

Desktop is not registered in DNS.

Register desktop in DNS.

Setup

Authorization required. Please log in with your username and password.

Incompatible browser causing cookie failure (unable to retrieve cookie).

Verify that you have Accept all cookies enabled. Refer to the installation documentation for supported Internet Explorer and Netscape Navigator software and setup procedures.

Daemon Manager could not start. The port is in use.

The operating system has not yet reallocated the port.

Make sure all CiscoWorks2000 processes are terminated (/usr/ucb/ps -auxww | grep CSCO). Wait five to ten minutes, then try to restart the Daemon Manager.

User has forgotten his password.

CiscoWorks2000 cannot recover forgotten passwords.

A system administrator-level user must either change the password or delete and then add the user again.

The ANI Server cannot load the database. Run reinitdb.pl to reinitialize the database.

The ANI database is corrupted, and the ANI Server cannot run with a corrupted database.

Reinitialize the database:

From the command prompt or shell window, where $NMSROOT is the root directory where you installed CiscoWorks2000, run:

On Solaris: $NMSRROOT/bin/reinitdb.pl

On Windows 2000: perl %NMSROOT%\bin\
reinitdb.pl

Cannot access the ANI supported devices.

ANI may have restarted since you last connected.

Log out of CiscoWorks2000 and log in again:

1. Click Logout.

2. Enter your user name and password.

3. Click Connect and attempt to use the Campus Manager application again.

Unable to analyze the ANI Server because a message states that you are not authorized.

When using a Campus Manager application, a error occurs: Cannot connect to ANI Server.

Administration

You are locked out of the CiscoWorks2000 Server.

Changes in the login module configuration file might not be correct.

Authentication server might be down and there were no fallback logins set.

On UNIX:

1. Log on as root.

2. Remove the changed login module override, /opt/CSCOpx/www/classpath/
com/cisco/nm/cmf/security/jaas/
JaasConfigModule.

3. Restart JRunProxyServer by entering:

/opt/CSCOpx/bin/pdterm JRunProxyServer

/opt/CSCOpx/bin//pdexec JRunProxyServer

4. Reload the browser.

   

On Microsoft Windows:

1. Remove the changed login module override, C:\Program Files\CSCOpx\www\classpath\
com\cisco\nm\cmf\security\jaas\
JaasConfigModule.

2. Restart JRunProxyServer by either of the following methods:

Access the Microsoft Windows Service Control dialog and stop and start JRUN Proxy Server for CW2000

or

In an MS-DOS window, change to C:\Program Files\CSCOpx\bin (this drive and path are the defaults for installation; use the actual installation drive and path). Run the following:

.\pdterm JRunProxyServer

.\pdexec JRunProxyServer

3. Reload the browser.

The Log File Status window displays files that exceed their limit.

Files need to be backed up so that file size will be reset to zero.

1. Stop all processes.

2. Enter the log file maintenance command:

a. On UNIX: $NMSROOT/cgi-bin/admin/

b. On Microsoft Windows: %NMSROOT%\
cgi-bin\admin\

3. Restart all processes.

For detailed instructions refer to the Maintaining Log Files online help (select Server Configuration > Administration > Log File Status, then click Help).

Error message in the logfile: Connection Refused. Check the Device is SSH supported or not.

Device is not SSH enabled or the server is not authorized to initiate SSH connection

1. Check whether the device is up or not.

2. Try connecting to the device with a commercial SSH client.

If you are able to connect, skip to step 3.

If you are not able to connect, check whether the device is running SSH enabled (K2 or K9) image.

If it is not the correct image, download the appropriate image to the device.

If you have the correct image, then see whether you have created RSA key pairs in the device. Creating RSA keys will enable SSH in the device.

3. Check whether your server or network is authorized to initiate SSH connections to device.

After installation, while starting the daemon manager, the following error message is displayed:

Found Non-SSL compliant Applications. Please disable SSL and then start the Daemon Manager

(Solaris only)

Found Non-SSL compliant products that do not function in SSL enabled mode.

Disable SSL from CLI and then start the daemon manager. For more information, see the "Disabling SSL" section.

After installation, while starting the daemon manager, the following error message is displayed:

Service Not responded in a timely fashion

Found Non-SSL compliant products that do not function in SSL enabled mode.

Disable SSL from CLI and then start the daemon manager. For more information, see the "Disabling SSL" section.