Troubleshooting CiscoWorks Problems

Step 5 Try a Management Information Base (MIB) browse of the device from the base platform. On Netview/6000, choose Tools, MIB-Browser, SNMP. On HP OpenView, choose Monitor, MIB Values, Browse MIB: SNMP. On SunNetManager, choose the device and then select a Quick Dump of SNMP.

If MIB values are not returned for the device, check the documentation for your base platform and re-check the snmp-server information in the router.

Step 1 Check whether the inetd daemon is running on the UNIX workstation. On AIX, HPUX, or Solaris, enter ps -ef | grep inetd. On Sun, enter ps -aux | grep inetd. If the inetd daemon is not running, start it. For information on starting the inetd daemon, refer to your operating system manual.

Step 2 Use the netstat -a | grep tftp command to see whether the TFTP daemon is running on the UNIX workstation. If the TFTP daemon is not running, start it. For instructions on starting the TFTP daemon, refer to the CiscoWorks Installation and Reference Guide.

Step 3 Test TFTP functionality from the router to the UNIX workstation. On the UNIX workstation, enter the command cd /tftpboot and then the command ls -l filename to check for the presence of a scratch configuration file for the router (the default is router_name-confg).

If there is not a configuration file for the router, create one by entering the command touch filename and then the command chmod 777 filename.

Step 4 Open a Telnet session to the router, enter privileged mode (to enter privileged exec mode, use the enable exec command), and enter the copy running-config tftp command. Specify the TFTP server and the file you just created (filename) to overwrite the file on the TFTP server. If the file transfer fails, check connectivity between the router and the host and refer to your operating system manual to troubleshoot TFTP server problems.

• NMSROOT---/usr/nms

• SYBASE---/usr/nms/sybase

• PATH---$NMSROOT/bin, /$NMSROOT/etc, $SYBASE/bin

• DSQUERY---CW_SYBASE

If you did not load your software in the default directories, your values should point to the locations you chose.

Use the printenv UNIX command to see the current environment variable settings.

• NMSROOT---/opt/CSCOcw

• SYBASE---/opt/CSCOcw/sybase

• PATH---$NMSROOT/bin, /$NMSROOT/etc, $SYBASE/bin

• DSQUERY---CW_SYBASE

If you did not load your software in the default directories, your values should point to the locations you chose.

Use the printenv UNIX command to see the current environment variable settings.

export NMSROOT=/usr/nms

Possible Problem	Solution
Sync with Sybase has not been run	You must run Sync with Sybase to populate the CiscoWorks application windows. With Netview/6000 and HP OpenView, choose a Sync entry under Misc. On SunNetManager, choose a Sync entry under Tools. For more information on running Sync with Sybase, refer to the CiscoWorks User Guide.

Possible Problem	Solution
Basic connectivity or setup problem	Follow the steps outlined in the section "Testing Basic Connectivity and Setup" earlier in this chapter.
Community string, name resolution, or timeout problem	Run nmadd from the command line to determine whether the problem is related to community string, name resolution, or timing out. The nmadd syntax is nmadd [-n device] [-r commstring] [-w rw_commstring] [-t timeout] Use a process of elimination to isolate the specific problem.

Possible Problem	Solution
Misconfigured environment	Step 1 Check the environment settings for your CiscoWorks installation using the printenv command. Make sure the settings shown point to the directories where you installed CiscoWorks. Step 2 If any of these variables point at the wrong location, Sybase logins fail. Set any incorrect variables to the proper value and attempt to use the CiscoWorks application again. For more information about the default values, descriptions, or locations of the CiscoWorks environment variables, see the section "CiscoWorks Environment Variables" earlier in this chapter.
Dataserver is not running	Check whether the dataserver is running. On HP-UX, Solaris, and AIX use the command ps -ef | grep dataserver. On SunOS, use the command ps -auxww | grep dataserver. On any of these systems, executing $NMSROOT/etc/isalive also returns status.
nscpwd file is corrupted	Step 1 Check to see whether the nscpwd file is corrupted. Enter the command ls -al $NMSROOT/etc/ncspwd and check the output for the following: 4 (date) (year) (time) ncspwd Step 2 If the output begins with anything other than 4, run the following command, answering the prompts as shown: $NMSROOT/bin/nmsanms Name: sa Password: sybasesa Key: beta
$SYBASE interfaces file has been modified	Step 1 Check to make sure that the $SYBASE interfaces file is present in the $SYBASE directory and that $SYBASE and the path to $SYBASE are defined in the environment variables. If you are using Solaris and the IP address of the management station has changed, you must recalculate the decimal-to-hexadecimal IP address specification. See the section "The $SYBASE Interfaces File Format" later in this chapter. Step 2 Make sure the DSQUERY environment variable correctly specifies the Sybase server name indicated in the $SYBASE interfaces file (the default is CW_SYBASE). For more information, see the section "CiscoWorks Environment Variables" earlier in this chapter. To find out the proper format for the $SYBASE interfaces file on your platform, see the section "The $SYBASE Interfaces File Format" later in this chapter.

On AIX, HP-UX, and SunOS, the $SYBASE interfaces file should resemble the following:

## CW_BACKUP_SERVER on Bamboo
##    Services:
##        query     tcp  (3000)
##        master    tcp  (3000)
 
CW_BACKUP_SERVER 5 5
     query tli tcp /dev/tcp \x00020bb8ab44766a0000000000000000
     master tli tcp /dev/tcp \x00020bb8ab44766a0000000000000000
 
## CW_SYBASE on Bamboo
##    Services:
##        query     tcp  (2002)
##        master    tcp  (2002)
 
CW_SYBASE 0 0
     query tli tcp /dev/tcp \x000207d2ab44766a0000000000000000
     master tli tcp /dev/tcp \x000207d2ab44766a0000000000000000
 

On the Solaris platform, the entries in the $SYBASE interfaces file take the following generic format, where P is the 5-digit port address converted to hex and the I is the IP address converted to hex on an octet-by-octet basis:

CW_SYBASE 0 0
     query tli tcp /dev/tcp \x000207d0ab44766a0000000000000000
     master tli tcp /dev/tcp \x000207d0ab44766a0000000000000000
##                                  7d0 = 2000 port number
##                                      ab = 171
##                                        44 = 68
##                                          76 = 118
##                                            6a = 106
##                         IP address = 171.68.118.106
 

Possible Problem

Solution

Security Manager on without an enabled group

If Security Manager is on without having a group enabled to use it, all users can be locked out of Security Manager. Step 1 Temporarily disable Security Manager to allow security administration. Enter the following commands from the command line: $SYBASE/bin/isql -Usa -Psybasesa 1> use nms 2> go 1> setuser "SAnms" 2> go 1> update applications set authority_ck = 0 2> where app_name = "nmadmin" 3> go 1> quit Step 2 All security is now removed from the CiscoWorks application. You must reconfigure Security Manager with a group enabled to use it. For information on configuring Security Manager, refer to the CiscoWorks User Guide.

Possible Problem	Solution
Basic connectivity or setup problem	Perform the steps outlined in the section "Testing Basic Connectivity and Setup" earlier in this chapter.
TFTP problem	Perform the steps outlined in the section "Testing Basic TFTP Connectivity" earlier in this chapter.

Possible Problem	Solution
Basic connectivity or setup problem	Perform the steps outlined in the section "Testing Basic Connectivity and Setup" earlier in this chapter.
TFTP problem	Perform the steps outlined in the section "Testing Basic TFTP Connectivity" earlier in this chapter.

Possible Problem	Solution
Basic connectivity or setup problem	Perform the steps outlined in the section "Testing Basic Connectivity and Setup" earlier in this chapter.
Polling interval too low	Try increasing the polling interval. To increase the polling interval, select Options, then Properties, and increase the value in the Timeout (secs): field. If the polling interval is too low, CiscoView will time out.
Community string, name resolution, or timeout problem	If CiscoView still fails, try running nmcview from the command line to determine whether the problem is related to community string, name resolution, or timing out. The nmcview command syntax is nmcview [-h host] [-c | -rd read community] [-C | -rw write community] [-t timeout] [-r retries] [-P poll frequency] Use a process of elimination to isolate the specific problem.