System information

Troubleshooting CiscoWorks
Book Title
23-468
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, as shown in the following example:
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
CiscoWorks: Locked Out of Security Manager
Symptom: When you try to use the Administer, a CW-Security menu selection, regardless of the
name and password you enter on the User Identification screen, you receive a “Sybase login failed”
error. When you try entering the sa user ID and password, the message returned is “Sorry, the
username [sa] is reserved to the CiscoWorks system.”
Table 23-4 outlines the problem that might cause this symptom and describes solutions to that
problem.
Table 23-4 CiscoWorks: Locked Out of Security Manager
Configuration Management: Device-to-Database or
Database-to-Device Does Not Run
Symptom: The device-to-database or the database-to-device operation in the Configuration
Management application does not work.
Table 23-5 outlines the problems that might cause this symptom and describes solutions to those
problems.
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.