System information

ManualsBrandsDestination Audio ManualsComputer equipmentCS500C

451

452

453

454

455

456

457

458

459

460

Troubleshooting CiscoWorks Problems 23-465

Troubleshooting CiscoWorks

This section discusses troubleshooting procedures for connectivity problems related to CiscoWorks.

It describes speciﬁc CiscoWorks symptoms, the problems that are likely to cause each symptom, and

the solutions to those problems.

CiscoWorks: No Devices in Application Window

Symptom: No devices appear in the windows of CiscoWorks applications (such as Conﬁguration

Management or Conﬁguration Snap-In Manager).

Table 23-1 outlines the problem that might cause this symptom and describes the solution to that

problem.

Table 23-1 CiscoWorks: No Devices in Application Window

CiscoWorks: Sync with Sybase Fails

Symptom: Attempts to run Sync with Sybase in CiscoWorks fail.

Table 23-2 outlines the problems that might cause this symptom and describes solutions to those

problems.

Table 23-2 CiscoWorks: Sync with Sybase Fails

CiscoWorks: Sybase Login Fails

Symptom: When attempting to use CiscoWorks applications that involve the use of Sybase, you

receive a “Sybase login failed” error message.

Table 23-3 outlines the problems that might cause this symptom and describes solutions to those

problems.

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[-ndevice] [-rcommstring] [-w rw_commstring]

[-ttimeout]

Use a process of elimination to isolate the speciﬁc problem.