Table Of Contents
Diagnosing Problems with the CiscoWorks Server
Verifying Server Status
Testing Device Connectivity
Troubleshooting the CiscoWorks Server
Frequently Asked Questions
Troubleshooting Suggestions
Diagnosing Problems with the CiscoWorks Server
Use these tools and suggestions to diagnose problems with the CiscoWorks Server:
•
Verifying Server Status
•Testing Device Connectivity
•Troubleshooting the CiscoWorks Server
•Troubleshooting Suggestions
Verifying Server Status
Server tools enable you to gather and analyze information about your CiscoWorks Server (see Table 6-1).
Table 6-1 Server Tools Tasks
Task
|
Purpose
|
Action
|
Administrative Tasks
|
Collect server information.
|
Provides system information, environment, configuration, logs, and web server information
|
Select
Server Configuration > Diagnostics >
Collect Server Info
or
Enter the following command:
•On Windows:
NMSROOT\bin\collect.info
•On Solaris:
$NMSROOT/bin/collect.info
where NMSROOT and $NMSROOT are the directories where you installed CiscoWorks, in Windows and Solaris respectively.
|
Perform self test.
|
Runs self-tests and generates a report with the results
|
Select
Server Configuration > Diagnostics >
Self Test
|
Check process failures.
|
Displays the failed process and time failure occurred
|
Select
Server Configuration > Diagnostics >
Process Failures
|
All Users
|
Verify installed applications and versions.
|
Lists date, state, and version of currently installed CiscoWorks applications and packages and whether any patches have been applied
|
Select
Server Configuration > About the Server >
Applications and Versions
|
Check process status.
|
Checks whether back-end processes are in an interim state
|
Select
Server Configuration > Administration >
Process Management > Process Status
|
MDC Support
|
The MDC Support utility collects log files, configuration settings, memory info, complete system related info, process status and host environment information.
It also collects any other relevant data, into a deliverable tar (compressed form ) file to support the MDC's installed.
The MDC Support utility also queries CCR for any other support utilities registered, and run them. Other MDCs need to register their own support utilities that will collect their relevant data.
|
For Windows go to,
NMSROOT\MDC\bin and execute the command:
For Solaris,
/opt/CSCOpx/MDC/bin and execute the command:
|
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 Connectivity Tools Tasks Table 6-2).
Table 6-2 Connectivity Tools Tasks
Task
|
Purpose
|
Action
|
Administrative Tasks
|
Check device connectivity.
|
Verifies that the CiscoWorks server can communicate with the device
|
Select
Server Configuration > Diagnostics > Connectivity Tools > Management Station to Device
|
Check SSH connectivity to the device
|
Verifies that the CiscoWorks server can communicate with the device using SSH.
|
Select
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 using the name server
|
Select
Server Configuration > Diagnostics > Connectivity Tools > NSLookup
|
Check device traceroute.
|
Detects routing errors between the network management station and a target device
|
Select
Server Configuration > Diagnostics > Connectivity Tools > Traceroute
|
Ping a device.
|
Tests device reachability using an ICMP echo message and its reply
|
Select
Server Configuration > Diagnostics > Connectivity Tools > Ping
|
Check Management Station to Device
|
This tool checks the connectivity between the CiscoWorks server and a device
|
Select
Server Configuration > Diagnostics > Connectivity Tools > Management Station to Device
|
Troubleshooting the CiscoWorks Server
This section provides information on frequently asked questions (FAQs) and suggestions for troubleshooting the CiscoWorks 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
•While invoking CiscoWorks, the browser displays the exception error SSL Initializer class not found. How do I correct this error?
•While invoking CiscoWorks, 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 connect to the CiscoWorks 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 CiscoWorks in the secure mode (HTTPS), there are too many dialog boxes. This makes the process tedious. Is there a way to reduce the number of dialog boxes and steps?
•While invoking CiscoWorks, the SSL Initialization window displays Permission Denied errors at the time of downloading JSSE jar files. Why does this happen?
•While invoking CiscoWorks, the browser displays the exception error message java.security.AccessControlException: access denied. What is wrong?
•When invoked in the secure mode (HTTPS), the CiscoWorks 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 CiscoWorks has expired. What should I do?
•While invoking CiscoWorks, my browser stops responding, and I am not able to get the CiscoWorks 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 CiscoWorks to function properly?
•Is there anything I should do before I invoke Netscape Navigator sessions in UNIX systems to run CiscoWorks?
•Why do some CiscoWorks applications not appear in the product?
•Why can't I start my CiscoWorks application?
•What kind of directory structure does CiscoWorks use when backing up data?
•What does "cmf" stand for in the database path?
•I'm logged out of the CiscoWorks Server. Why did this happen, and how do I regain access?
•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 configured the Active Directory Login Module but it does not work. How can I analyse the problem ?
•How do I change the IP Address of the CiscoWorks Server after installing it, or after running it for a while?
•How do I change the Hostname of the CiscoWorks Server after installing it, or after running it for a while?
•How do I find out which devices are supported by a particular application?
•How do I enable or disable Java plug-in?
•How do I verify if SSH is enabled or disabled on my device using CiscoWorks Server?
•How to verify which version of SSH is running on my system?
Q. While invoking CiscoWorks, the browser displays the exception error SSL Initializer class not found.
How do I correct this error?
A. 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 on page 3-7.
Note It is recommended that you use the tar file or autoinstall file downloaded from CiscoWorks Server to install Java Plug-in 1.3.1.
Q. While invoking CiscoWorks, 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?
A. This error message is displayed, when all the processes are not up and running on the CiscoWorks Server. Typically it occures when you invoke CiscoWorks immediately after restarting the daemon manager in CiscoWorks Server.
To correct this problem:
Step 1 In the CiscoWorks 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 CiscoWorks again.
Note CiscoWorks desktop is displayed only if the web server and JRunProxyServer processes are up and running,
Q. When I connect to the CiscoWorks 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?
A. 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.
Q. When I invoke CiscoWorks in the secure mode (HTTPS), there are too many dialog boxes. This makes the process tedious. Is there a way to reduce the number of dialog boxes and steps?
A. 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 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 CiscoWorks.
•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 CiscoWorks, until the certificate expires.
Q. While invoking CiscoWorks, the SSL Initialization window displays Permission Denied errors at the time of downloading JSSE jar files. Why does this happen?
A. 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 CiscoWorks 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. 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.
Q. While invoking CiscoWorks, the browser displays the exception error message java.security.AccessControlException: access denied. What is wrong?
A. The browser displays this error message if you deny permission to the signed applet to run while invoking CiscoWorks. For more information, see the "Invoking the CiscoWorks Desktop" section on page 2-2.
When you invoke CiscoWorks, the browser displays a Java Plug-in Security Warning window, which prompts you to grant permission to run the signed applet. CiscoWorks requires you to grant permission to run this applet. If you deny permission to run the applet, CiscoWorks displays the error message java.security.AccessControlException: access denied.
To invoke CiscoWorks 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 CiscoWorks.
Q. When invoked in the secure mode (HTTPS), the CiscoWorks Login Manager displays the exception error message javax.net.ssl.SSLException: untrusted server cert chain. What is wrong? How do I correct this problem?
A. To invoke CiscoWorks 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 CiscoWorks Server and port_number is the TCP port used by the CiscoWorks Server, when SSL is enabled (secure mode).
This ensures that proper SSL initialization is done before CiscoWorks launches the Login Manager. In the secure mode, you must perform all the SSL initialization procedures before you log in to CiscoWorks. 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 CiscoWorks again. For more information, see the "Invoking CiscoWorks Desktop in SSL Enabled Mode (HTTPS)" section on page 2-3.
Q. 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?
A. You may get this error if:
•The date on CiscoWorks Server and the client computer are not set properly or not set to current date
•The time zone settings in CiscoWorks 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 CiscoWorks Server and the client computer, restart the browser and invoke CiscoWorks again.
Q. My server certificate for CiscoWorks has expired. What should I do?
A. If you are using a self-signed certificate, you can create a new certificate using the Create Self Signed Certificate option in CiscoWorks Server. For more information, see the "Managing Security Certificates" section on page 4-14.
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.
Q. While invoking CiscoWorks, my browser stops responding, and I am not able to get the CiscoWorks Login Manager. What should I do?
A. When you start CiscoWorks, 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.
Q. I installed CD One and got an error message that EDS wasn't registered with the daemon manager. Did I do anything wrong?
A. 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.
Q. The Java Plug-in does not get enabled in the client browser. How do I enable the Plug-in?
A. To enable the Plug-in, do the following:
OS
|
Action
|
Windows
|
Select
Start > Settings > Control Panel > Java Plug-in
In the Java Plug-in Control Panel:
1. Select Enable Java Plug-in in the Basic tab.
2. Click Apply.
|
Solaris
|
Run /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.
|
Q. I have enabled the Java Plug-in in the control panel. But the Plug-in does not get enabled. What else should I do?
A. 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.
Q. Which version of the Java Plug-in should I use for CiscoWorks to function properly?
A. CiscoWorks 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 CiscoWorks to function properly.
Q. Is there anything I should do before I invoke Netscape Navigator sessions in UNIX systems to run CiscoWorks?
A. 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 CiscoWorks.
Q. Why do some CiscoWorks applications not appear in the product?
A. The CiscoWorks 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 CiscoWorks Server desktop. Applications and application suites may not use these features at all, or to the fullest extent. See the User Guide for your application suite to determine the extent to which these features are used.
Q. Why can't I start my CiscoWorks application?
A. If you cannot start your CiscoWorks 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 CiscoWorks CORBA applications require name resolution to work properly. DNS is a must for CiscoWorks CORBA applications to work properly.
Configure the name resolution mechanism and restart the CiscoWorks Server to access the application correctly.
Q. What kind of directory structure does CiscoWorks use when backing up data?
A. CiscoWorks uses a standard database structure for backing up all suites and applications. See Table 6-3 for sample directory structure for the CiscoWorks Server .
Table 6-3 Sample CiscoWorks Common Services Backup Directory
Directory path
|
Description
|
Usage Notes
|
/tmp/1
|
Number of backups
|
1, 2, 3...
|
/tmp/2/cmf
|
Application or suite
|
Backs up CiscoWorks Server applications.
|
/tmp/1/cmf/filebackup.tar
|
CiscoWorks server application tar files
|
Application data is stored in the datafiles.txt which are compiled into the tar file.
|
/tmp/1/cmf/database
|
CiscoWorks 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
|
Q. What does "cmf" stand for in the database path?
A. The cmf acronym in the database structure represents the Common Management Foundation (CMF). This phrase describes the set of management services provided by the CiscoWorks Server.
Q. I'm logged out of the CiscoWorks Server. Why did this happen, and how do I regain access?
A. There are several reasons why you might have been logged out. Most likely it is due to changes made using the Select Login Module option (see the "Understanding Fall Back Options" section on page 3-5). You will need to replace the incorrect login module with a default configuration, log into CiscoWorks, and return to the login module to correct one or more of the following:
–Session Time out
–Change from SSL mode to non-SSL mode
–Change from non-SSL mode to SSL mode
–Log out from any other CiscoWorks application
–Visit other sites and then return to CiscoWorks
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.
Q. What if the database is inaccessible?
A. 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 CiscoWorks as admin.
Step 2 Select Server Configuration > Diagnostics > Process Failures to get a list of CiscoWorks 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 (Windows).
Step 2 Stop the Daemon manager if it is already running:
•UNIX—/etc/init.d/dmgtd stop
•Windows—net stop crmdmgtd (enter this 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
For Korn and Bourne Shell:
SATMP=/tmp/.SQLAnywhere ; export SATMP
LD_LIBRARY_PATH=/opt/CSCOpx/lib:/opt/CSCOpx/objects/db/lib ; export LD_LIBRARY_PATH
ASANY=/opt/CSCOpx/objects/db ; export ASANY
PATH=${PATH}:/opt/CSCOpx/objects/db/bin ; export PATH
For C Shell:
setenv SATMP /tmp/.SQLAnywhere
setenv LD_LIBRARY_PATH /opt/CSCOpx/lib:/opt/CSCOpx/objects/db/lib
setenv ASANY /opt/CSCOpx/objects/db
setenv PATH ${PATH}:/opt/CSCOpx/objects/db/bin
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
•Windows—start it in an MS-DOS window. For example, if CiscoWorks 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 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 caused by 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 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"
•Windows syntax (run in an MS-DOS window). For example, if CiscoWorks 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},...
Q. How do I ensure that jrm is running fine?
A. To check whether jrm is working on Windows, at the command prompt enter:
cwjava -cw NMSROOT\com.cisco.nm.cmf.jrm.jobcli
To check whether jrm is working on Solaris, at the command prompt enter
cwjava -cw $NMSROOT/com.cisco.nm.cmf.jrm.jobcli
If you get a message "Established connection with JRM", then EDS, EDS-GCF and jrm are running.
If you do not get the above message, contact the technical assistance center with the error message.
Q. How do I change the port for osagent in Windows?
A. To change the port for osagent in Windows:
Step 1 Backup 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=<NMSROOT> -DORBagentPort=42342 com.visigenic.vbroker.gatekeeper.GateKeeper -props <NMSROOT>\lib\visigenics\gatekeeper.cfg
to
-DNMSROOT=<NMSROOT> -DORBagentPort=44444 com.visigenic.vbroker.gatekeeper.GateKeeper -props <NMSROOT>\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 <NMSROOT>\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.
<NMSROOT> is the installation directory for CiscoWorks server.
Q. 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 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 5 Back up $NMSROOT/objects/dmgt/dmgtd.conf file.
Step 6 Edit the file dmgtd.conf using a text editor.
a. Change the line RmeOrb y - $NMSROOT/lib/vbroker/bin/osagent -p 42342 to RmeOrb y - $NMSROOT/lib/vbroker/bin/osagent -p 44444
b. Change the port number for RmeGatekeeper from RmeGatekeeper y RmeOrb $NMSROOT/lib/vbroker/bin/rungk.sh 42342 to RmeGatekeeper y RmeOrb $NMSROOT/lib/vbroker/bin/rungk.sh 44444
Step 7 Open the file /etc/services in a plain text editor such as vi.
Step 8 Comment out the entry for CSCOsa port and add the following entry:
cscoosa 44444/udp # CSCO NM osagent
Note The change is for the port number only.
Step 9 Open /var/sadm/pkg/CSCOmd/pkginfo in a plain text editor, such as vi.
•Change the entry for OSAGENT_PORT= 42342 to the following:
OSAGENT_PORT=44444
•Change the entry PX_OSA_PORT=42342 as follows:
PX_OSA_PORT=44444
Step 10 Restart the daemons. It is recommended that you reboot the server.
Q. How do I change the ESS port in Solaris?
A. There are 4 ports related to ESS:
•ESS Service Port: 42350/udp
•ESS listening port: 42351/tcp
•ESS HTTP Port: 42352/tcp
•ESS Routing Port: 42353/tcp
The ports mentioned above are default ports. The alternative ports defined for these in CiscoWorks are 44350, 44351, 44352, 44353 respectively.
To change the ports:
Step 1 Open the file $NMSROOT/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.
Q. 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 <NMSROOT>\objects\ess\conf\rvrd.conf -logfile <NMSROOT>\log\ess.log -listen 42351 -no-http
to
-store <NMSROOT>\objects\ess\conf\rvrd.conf -logfile <NMSROOT>\log\ess.log -listen 44351 -no-http
Step 4 Change the corresponding entry in NMSROOT\objects\ess\conf\essproperties.conf.
Step 5 Reboot the server.
Q. I have configured the Active Directory Login Module but it does not work. How can I analyse the problem ?
A. To analyse the problem, enable the Debug mode for the Active Directory Login module. To do this:
Step 1 Login as Admin.
Step 2 Go to Server Configuration -> Setup -> Security -> Select Login Module.
The Select Login Module dialog box appears.
Step 3 Select a login module from the Available Login Modules list box and Click on Edit Options.
The Login Module Options dialog box appears.
Step 4 Select the radio button True and click on Finish.
This enables the Debug option. Enabling debug mode allows the login module to add the detailed progress and failure information to log files. The log files are located at:
For Windows:
CSCOpx\lib\jrun\jsm-cw2000\logs\stdout.log
For Solaris:
CSCOpx/objects/jrun/jsm-cw2000/logs/stdout.log
For all failed login attempts, the log files contain LDAP error messages, which specify the reason for the failure. These messages are self-explanatory. For example if the "Usersroot" configuration is incorrect, then the login module cannot match the complete DN string with any entries in the Active Directory database. It indicates which portion of the DN matched and which portion did not match. You can then check up your Active Directory setup and verify the entries for the Usersroot.
In some cases, the log file contains error messages with NameError. This indicates that either you entered a wrong user Id or there is some splelling error in the Usersroot configurtion.
Q. How do I change the IP Address of the CiscoWorks Server after installing it, or after running it for a while?
A. You can change the IP address on the server, and then access it using the new IP address.
To change the IP address on Windows:
Step 1 Click Start > Settings > Network and Dial-up Connections > Local Area Connection.
The Local Area Connection Status dialog box appears.
Step 2 Click Properties.
The Local Area Connection Properties dialog box appears.
Step 3 Select Internet Protocol (TCP/IP) and click Properties.
The Internet Protocol (TCP/IP) Properties dialog box appears.
Step 4 Select the radio button Use the following IP address.
Step 5 Change the IP address as required, in the IP Address field.
For the subnet mask and default gateway values, use the command ipconfig at the command prompt.
The subnet mask and default gateway values will be displayed.
Step 6 Enter these values in the Subnet mask and default gateway fields.
Step 7 Click OK.
Step 8 Restart the server.
To change the IP address on Solaris, use the command ifconfig at the command prompt to change the IP address of the required interface.
For example, at the command prompt, you can enter:
ifconfig interfacename inet ipv4address
where the variable interfacename represents the name of the interface and ipv4address represents the new IP address.
Q. How do I change the Hostname of the CiscoWorks Server after installing it, or after running it for a while?
A. To change the hostname of the CiscoWorks Server, you need to update several files, and reboot the server:
Step 1 Change the hostname in all the following files:
Table 6-4 Changing Hostname in CoscoWorks Common Services 2.2 Server
Bundle
|
Solaris
|
Windows
|
LMS Bundle
|
•/etc/hosts
Modify loghost to the new hostname.
•/etc/hostname.hm0 or the appropriate interface file.
Modify the file to the new hostname.
•/etc/nodename or the appropriate interface file.
Modify nodename to the new hostname.
Note Reboot the server after these steps.
•/var/sadm/pkg/CSCOmd/pkginfo
Change the "PX_HOST" to your new hostname.
•NMSROOT/lib/classpath/md.properties.
NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•If you are usingCampus Manager: NMSROOT/campus/etc/cwsi/ANIServer.properties. Change the "AniName=ANIServer4.2-XXX" where XXX will be your new hostname.
|
•Identification tab in the Network window: My Computer > Properties > Network Identification > Properties
Modify it to your new hostname.
•Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\Tcpip\
Parameters
Modify the hostname to new hostname.
Note Restart the server after these steps.
•md.properties file:
NMSROOT/lib/classpath/md.properties. NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•ANIServer.properties NMSROOT/campus/etc/cwsi/ANIServer.properties. Change the "AniName=ANIServer4.2-XXX" where XXX will be your new hostname.
•Change HostName entry in the CCR.
For this do the following:
Navigate to NMSROOT/MDC/bin
|
| |
•Change HostName entry in the CCR.
For this do the following:
setenv LD_LIBRARY_PATH NMSROOT/MDC/lib
Navigate to NMSROOT/MDC/bin
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
RWAN Bundle
|
•/etc/hosts
Modify loghost to the new hostname.
•/etc/hostname.hm0 or the appropriate interface file.
Modify the file to the new hostname.
•/etc/nodename or the appropriate interface file.
Modify nodename to the new hostname.
Note Reboot the server after these steps.
•/var/sadm/pkg/CSCOmd/pkginfo
Change the "PX_HOST" to your new hostname.
•NMSROOT/lib/classpath/md.properties.NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•For aclm.properties, /opt/CSCOpx/objects/aclm/etc/
aclm/aclm.properties.
Change the "ORBAgentAddr" value to your new hostname.
|
•Identification tab in the Network window: My Computer > Properties > Network Identification > Properties
Modify it to your new hostname.
•Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\Tcpip\
Parameters
Modify the hostname to new hostname.
Note Restart the server after these steps.
•md.properties file:
NMSROOT/lib/classpath/md.properties. NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•For aclm.properties, /opt/CSCOpx/objects/aclm/etc/aclm/
aclm.properties.
Change the "ORBAgentAddr" value to your new hostname.
•Change HostName entry in the CCR.
For this do the following:
Navigate to NMSROOT/MDC/bin
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
|
| |
•Change HostName entry in the CCR.
For this do the following:
setenv LD_LIBRARY_PATH NMSROOT/MDC/lib
Navigate to NMSROOT/MDC/bin
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
LMS and RWAN Bundles
|
•/etc/hosts
Modify loghost to the new hostname.
•/etc/hostname.hm0 or the appropriate interface file.
Modify the file to the new hostname.
•/etc/nodename or the appropriate interface file.
Modify nodename to the new hostname.
Note Reboot the server after these steps.
•/var/sadm/pkg/CSCOmd/pkginfo
Change the "PX_HOST" to your new hostname.
•NMSROOT/lib/classpath/
md.properties.
NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•If you are usingCampus Manager: NMSROOT/campus/etc/cwsi/ANIServer.properties. Change the "AniName=ANIServer4.2-XXX" where XXX will be your new hostname.
|
•Identification tab in the Network window: My Computer > Properties > Network Identification > Properties
Modify it to your new hostname.
•Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\Tcpip\
Parameters
Modify the hostname to new hostname.
Note Restart the server after these steps.
•md.properties file:
NMSROOT/lib/classpath/md.properties. NMSROOT is the location of CiscoWorks.
Change the "PX_HOST" to your new hostname.
•ANIServer.properties NMSROOT/campus/etc/cwsi/ANIServer.properties. Change the "AniName=ANIServer4.2-XXX"where XXX will be your new hostname.
|
| |
•For aclm.properties, /opt/CSCOpx/objects/aclm/etc/
aclm/aclm.properties.
Change the "ORBAgentAddr" value to your new hostname.
•Change HostName entry in the CCR.
For this do the following:
setenv LD_LIBRARY_PATH NMSROOT/MDC/lib
Navigate to NMSROOT/MDC/bin
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
•For aclm.properties, /opt/CSCOpx/objects/aclm/etc/aclm/
aclm.properties.
Change the "ORBAgentAddr" value to your new hostname.
•Change HostName entry in the CCR.
For this do the following:
Navigate to NMSROOT/MDC/bin
Remove HostName containing old host name by entering:
ccraccess -removeResource Core Custom Custom " " " " HostName
Add new Host Name entry with new host name by entering:
ccraccess -addResource Core Custom Custom NewHostName " " HostName
Check the new HostName entry from CCR:
ccraccess -getResource Core Custom Custom " " " " HostName
|
Note For Solaris, the sys-unconfig command erases the hostname and IP addresses pertaining to the Solaris system (not the LMS or SNMS software) and guides you through the server-renaming process. You also do this when you change the hostname in the hosts, hostname.hm0, and nodename files in the /etc directory.
Step 2 Stop and restart the ANI server.
On Solaris:
a. Enter /etc/init.d/dmgtd stop to stop the Daemons (server).
b. Delete gatekeeper.ior file under /opt/CSCOpx/www/classpath/gatekeeper.ior.
c. Enter/etc/init.d/dmgtd start to start the Daemons (server).
A new gatekeeper.ior file should be created.
On Windows:
a. On the Windows desktop, select Start >Run.
b. Enter cmd, and then click OK. This will open up a DOS Window.
c. At the prompt, enter net stop crmdmgtd to stop theDaemons (server).
d. Delete the gatekeeper.ior file under NMSROOT\www\classpath/gatekeeper.ior, the default install location for CiscoWorks.
e. At the prompt, enter net start crmdmgtd to start the Daemons (server).
Note You must have Administrator privileges to execute these commands.
Q. How do I find out which devices are supported by a particular application?
A. Select Server Configuration > About the Server > Applications and Versions. Under Applications Installed, click the application name to see a list of the supported devices.
Q. How do I enable or disable Java plug-in?
A. For applications for which the plug-in is optional, you can either enable or disable Java plug-in.
To enable or disable Java Plug-in:
Step 1 Select Server Configuration > Setup > Java Plug-in Use.
Step 2 Click Enable or Disable.
Step 3 Click Finish.
Q. How do I verify if SSH is enabled or disabled on my device using CiscoWorks Server?
A. To verify whether SSH is enabled or disabled using the CiscoWorks Server:
Step 1 Logon to the CiscoWorks desktop.
Step 2 Select Server Configuration > Diagnostics > Connectivity Tools > Management Station to Device.
Step 3 In the Check Connectivity dialog box, enter the device name and select the SSH check box.
If SSH enabled on the device, you will see:
If SSH is not enabled on the device, you will see:
Q. How to verify which version of SSH is running on my system?
A. You can verify the SSH version that is running on your system using the commands:
From the Command Line Interface, enter:
or
Troubleshooting Suggestions
Use the suggestions in Table 6-5 to resolve errors or other problems with the CiscoWorks Server.
Table 6-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. (Windows only.)
|
ODBC resource.dll and ODBC driver manager are different versions.
|
Install ODBC from 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 CiscoWorks 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.
|
Common Services cannot recover forgotten passwords.
|
A system administrator-level user must either change the password or delete and then add the user again.
|
Administration
|
You are locked out of the CiscoWorks 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, /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 Windows:
1. Remove the changed login module,
C:\Program Files\CSCOpx\www\classpath\
com\cisco\nm\cmf\security\jaas\
JaasConfigModule.
2. Restart JRunProxyServer by either of the following methods:
–Access the Windows Service Control dialog and stop and start JRUN Proxy Server for CiscoWorks
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 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 on page 4-10.
|
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 on page 4-10.
|
Feedback