CiscoWorks 1.0(3) Release Note

Running the $NMSROOT/etc/fixpolls Script

To run the $NMSROOT/etc/fixpolls script after upgrading from CiscoWorks Release 1.0 to 1.0(3), perform the following steps:

Step 1 Make sure you know the password for nmsuper or the password of a CiscoWorks Release 1.0 user. (Do not use the Sybase SA password.)

Step 2 Enter the following command at the UNIX prompt (%):

% $NMSROOT/etc/fixpolls -Uuser -P password

For example, if your user name is kwilson and your password is casey2, you would enter the following command:

% $NMSROOT/etc/fixpolls -Ukwilson -Pcasey2

Output similar to the following will appear:

Fixing poll template table... Done.

Running the $NMSROOT/etc/fixpolltable Script

To run the $NMSROOT/etc/fixpolltable script for each polling table, perform the following steps:

Step 1 To identify the names of the polling tables, select the Tools menu on the SNM console and pull down to Device Polling.

The Device Polling window appears.

Step 2 Select the Poll Group field and pull down the pick menu to display the existing poll group names for polling tables.

Step 3 Note the names of the polling tables.

Step 4 Make sure you know the password for nmsuper or the password of a CiscoWorks user. (Do not use the Sybase SA password.)

Step 5 Enter the following command at the UNIX prompt, substituting the name of the polling table:

% $NMSROOT/etc/fixpolltable -Uuser -Ppassword polling_table_name

For example, if your user name is kwilson, your password is casey2, and the name of the polling table is sample, you would enter the following command:

% $NMSROOT/etc/fixpolltable -Ukwilson -Pcasey2 sample

Output similar to the following will display:

Fixing poll table sample
All done fixing test1

Step 6 Repeat step 5 for each polling group.

Removing Log Manager Messages

Messages in the Log Manager window are stored in a Sybase table called ciscolog. These messages can accumulate quickly, and the database can consume large amounts of hard disk space; therefore, you should delete unwanted Log Manager messages to prevent your database from consuming too much disk space.

You can delete log messages from the Log Manager window in two ways:

• Delete the log messages from the Log Manager window as described in the CiscoWorks User Guide.
  

• Use the isql utility to remove all log messages as described in this section.
  

Use the isql utility in the following situations:

• The Sybase transaction log runs out of space when you try to delete all messages in the Log Manager window.
  

• You need more flexibility in specifying which records to delete.
  

• You want to use a shell script to delete the log messages efficiently. A script can be run with cron to ensure that the log messages are removed at regular intervals.
  

If the Sybase transaction log is filled up during the deletion of messages from the Log Manager window, you can resolve the problem by using the $NMSROOT/etc/enlarge_nms script to enlarge the transaction log. Instructions for using this script are provided in the CiscoWorks User Guide.

Using the Truncate Table Command

You also can use the isql truncate table command to remove the log messages from the Log Manager window and the records from the Sybase table. The truncate table command uses less space in the transaction log.

Caution The following procedure deletes all messages in the Log Manager window. Do not follow these steps if you want to delete the messages selectively.

Follow these steps to delete all log messages from the Log Manager window and the ciscolog file:

Step 1 Enter the following command at the UNIX prompt (%):

% isql -Unmsuper -P passwd

Step 2 Enter the following commands in a sequence to clean the ciscolog file:

> truncate table ciscolog
> go
> quit

The isql utility allows you to specify clauses for deleting the data in the ciscolog file. If you want to delete log records that are older than 3 days, perform the following steps:

Step 1 Enter the following command at the UNIX prompt (%):

% isql -Unmsuper -P passwd

Step 2 Enter the following commands to delete log records that are older than 3 days:

> delete ciscolog where datediff(day, timestamp, getdate()) > 3
> go
> quit

To automate the deletion of the log records, you can add these lines to a shell script that can be run manually or from cron. Refer to the manual pages on cron and crontab commands for more information.

An example of the contents of a sample shell script follows:

#!/bin/sh

$SYBASE/bin/isql -Unmsuper -Ppasswd <<EOF

delete ciscolog where datediff (day, timestamp, getdate ()) > 3

go

quit

EOF

Retry Popup Window

A new retry popup window has been added to several CiscoWorks applications. This popup window indicates loss of connectivity to a device and enables you to retry the request or quit. The popup window displays the following message:

Device router_name not responding to SNMP

The retry popup window appears in the following CiscoWorks applications:

• Health Monitor---Restarts the timer and proceeds when the Cisco device is available.
  

• Path Tool---Skips a hop and proceeds normally until it completes its task. Path Tool reports devices that did not respond to SNMP.
  

• Show Commands---No timer is available, but the Show Commands application continues when the Cisco device is available.
  

• Environmental Monitor---Restarts the timer and proceeds when the Cisco device is available.
  

Enhancements to Configuration Management

The Configuration Management application includes the features described in this section.

Updating Devices in the Configuration Management Window

You can update the list of devices displayed in the Configuration Management window to reflect the current list of Cisco devices in the database, so the Cisco devices displayed in the Configuration Management window will be identical to the devices in the database.

Follow these steps to update the list of devices in the Configuration Management window:

Step 1 From the SNM Tools menu, select Config Management.

Step 2 Click on the Options button to display the pull-down menu.

Step 3 Select Refresh Device List.

The list of devices in the Configuration Management window are updated to reflect the current list of Cisco devices in the database.

Configuration File Size

The maximum size of a configuration file or a comments file is 128 KB.

Specifying the Write Community String for a Device

A new field called Write Community has been added to the Device window in the Device Management window. This field enables you to specify the ReadWrite (RW) community string for a device. The Security Manager application protects the RW community string specified in this field. In order to specify the RW community string in this field, you must have Write Password privilege assigned to your username in the Security Manager application. Otherwise, you cannot perform this task.

Edit Group or Edit User Window

The Security Manager application enables you to edit the name of an existing user or group. To perform either task, click on the Edit button for users or groups in the Users and Groups window to display the Edit User or Edit Group window. The CiscoWorks User Guide refers to the Edit User and Edit Group windows as Modify User and Modify Groups windows. This reference is incorrect.

Enlarging Disk Space Using a Command Sequence

Chapter 8, "Database Administration" in the CiscoWorks User Guide provides a procedure for expanding database space allocation. The steps in the procedure on page 8-10 were missing commas for some commands. The correct steps follow:

Step 1 Enter the following command at the UNIX prompt (%):

% $SYBASE/bin/isql -Usa -Ppasswd

Step 2 Enter the following command sequence to enlarge your disk space. The name must be a unique name each time the enlarge routine is run.

1> disk init
2> name = " nms2 ",

Step 3 Continue entering the following command sequence. Replace ../data/nms2 with any filename.

3> physname = "../data/nms2.dat ",

Step 4 Continue entering the following command sequence. Enter any unique number that is greater than one. This number must be incremented by one each time the enlarge routine is run.

4> vdevno = 3 ,

Step 5 Continue entering the following command sequence:

5> size = 4906

This is the size of disk space desired in 2-KB increment blocks, for example,
2 x 4096 = 8 MB.

Step 6 Start the sequence by entering the following:

6> go

Step 7 Now, alter the database by entering the following at the command line. In this example, you would create an 8-MB file.

1> alter database nms

Step 8 Continue entering the following command sequence. Enter size in megabytes. This number cannot exceed the size specified in the enlarge routine.

2> on nms2 = 8

Step 9 Start the sequence by entering the following command:

3> go

Step 10 Exit the command mode by entering the following command:

4> quit

Locations Information in the People Window

You can only modify location information in the People window for the Device Management application; you cannot add new location information in this window. To add new location information, use the Locations window.

nmslog Files

When you use the ls -l command to list the nmslog files in a directory, the list includes names of the nmslog files and the dates they were created. Following is a sample listing displayed by the ls -l command:

-rw-r--r--  1 root         4187 Mar  5 07:32 nmslog
-rw-r--r--  1 root        13108 Mar  4 18:48 nmslog.Fri
-rw-rw-rw-  1 root          226 Mar  3 14:26 nmslog.Thu

The date indicates the day when the file was created, and the name of the file (nmslog.Fri) indicates the day when that nmslog file was closed.

Path Tool Link

A black link in a path displayed in the Path Tool window indicates that the device did not respond to SNMP.

Running Data Workbench Reports

The section "Running Reports from UNIX" in Chapter 4 in the CiscoWorks User Guide explains how you can use the runrpt command to run reports that were created and saved by the Data Workbench.

The correct name of this command is runrw. It is located in the $SYBASE/bin directory. The correct command syntax for the sample report called storm_report follows:

runrw storm_report -Uyourname -Ppassword

For more information about the runrw command, enter the following command:

syman runrw

Show Command Support for Flash Memory

To display information about Flash memory on a Cisco device, click on the
Show Flash button in the Show Commands window. If the device is a Cisco 7000 router, information similar to the following displays:

4096K bytes of flash memory on embedded flash (in RP1).

file     offset     length        name
  0     0x80        53364       eip1-0
  [4140812/4194304 bytes free]

For CiscoWorks Release 1.0(3) caveat information on this feature, refer to "CiscoWorks Release 1.0(3)Modifications" on page 33.

Troubleshooting Configuration Management

If the Configuration Management application fails or you are unable to use commands in this application, verify the following:

• You have a ReadWrite (RW) community string for the device.
  

Log on to the device and check the device configuration file. Ensure that a line similar to the following exists in the file:

snmp-server community your_community_string RW

• The device is running.
  

• The TFTP server is running.
  

• The /tftpboot directory is readable and writable to all.
  

• The router has Software Release 8.2 or later.
  

• The device specification in your name resolution software (for example, NIS, DNS or the /etc/hosts file) is correct.
  

• The configuration file that you download does not have syntax errors in it. If you suspect that it does, log on to the router console and initiate a TFTP session from the router. The errors will be displayed on your console screen. Or, log on to the router before you download the file, and check to see if any error messages exist.
  

• You have not deleted lines when editing configuration command scripts. Instead change parameters. For example, if you do not want debugging on, do not delete the lines containing the parameter. Instead, modify the parameter from debugging on to debugging off.
  

Using the nmsanms Program

The CiscoWorks User Guide provides instructions on how to run the nmsamns program. Run the nmsamns program when you are not using the Security Manager application. If you run the nmsamns program when Security Manager is being used, you will need to restart the Security Manager application. Otherwise, Security Manager will be unable to access any Sybase database records.

Writing SQL Reports for Custom Polling Tables

To write SQL-based reports for analyzing data collected in polling tables, you must be familiar with CiscoWorks polling applications, Simple Network Management Protocol (SNMP), and structured query language (SQL).

Table 1 shows the columns that are always present in a polling table. The remaining columns are user-defined and contain the values of the polled MIB objects.

Table 1 : Columns in a Polling Table

Field Name	Field Size	Field Type
timestamp	datetime	Timestamp for each row of data polled
device_id	int	Join to devices table
sysUpTime	int	System up time in 100ths of a second
inst	char (255)	Index into MIB object table
rec_type	tinyint	0 = normal record, 1 = start record, 2 = not used, 3 = restart record, 4= irregular records

If the polled MIB objects are indexed by ifIndex, the inst column contains the appropriate value (for example, ifIndex or locIfxxx). This inst column can be used to join with the interface_id column in the Interfaces table. To join the inst column with the interface_id column, add the following to the SQL WHERE clause:

select ...
where ...
and convert(int, inst) = interfaces.interface_id

When you start polling a device, CiscoWorks creates a record with rec_type = 1. All the values in this record are absolute. All other records have rec_type = 0 and contain a mix of delta and absolute values. When you stop polling a device, you do not get any additional rows. A new rec_type value of 4 has been added to account for any anomalies or irregularities, which includes absolute values instead of delta values.

You can determine whether a MIB object will contain an absolute or delta value by getting its data type from the $SNMHOME/agents/cisco.schema file and identifying the value for each type. For example, sysUpTime uses timeticks as its record type, so the data value will be displayed as a delta value (the difference in value between the current poll and the last poll) if rec_type = 0.

For information on identifying the value for a data type, refer to Table 2.

Table 2 : Values for Types of Records

Record Type	Value
timeticks	delta
counter	delta
gauge	absolute
int	absolute

Using genmibview

In a custom polling table, the columns containing the polled object values are labeled var[1-n], where n is the number of polled MIB objects. The genmibview script in the $NMSROOT/etc directory enables you to create a view of the polling table that uses the MIB variable names. Use the following command to create a table with meaningful column names:

$NMSROOT/etc/genmibview -Uuser -Ppassword tablename

The command creates a view called tablename_view. For example, to generate a view for a polling table named traffic, a user named netman and a password cisco, use the following command:

$NMSROOT/etc/genmibview -Unetman -Pcisco traffic

This command creates a view of the traffic table called traffic_view, with columns named after the MIB object names.

Specifying MIB Object Values

When you create a polling table in Device Polling, you specify the MIB object values that you want to collect. These values are collected by the poller and added to the database as the values are received. When polled values arrive at the poller in different packets, the values are written to the database in different records. Therefore, you might find that the data for a given poll is spread over two or more records, with NULL appearing where data was not available.

The following example shows how polling data is received over time and added to the database:

Polling:
                time    sysUpTime       var1    var2    inst
                 x         100           10               1
                 x+1       101                   15       1
                 x+2       102           10               2
                 x+10      110           20               1
                 x+11      111           25               2
Database storage:
                rec_type sysUpTime      var1    var2    inst
1  100  10    1
  1  101    15  1
  1  102  10    2
  0   8  10   1
  0   1  15    2

You cannot perform row operations without first grouping and aggregating your data. You might want to use the timestamp column to perform groupings and then use the AVG or MAX (for absolute values) or SUM (for delta values) to aggregate. You can use the following GROUP BY clause to group by device, inst, and 15-minute intervals:

select ...
group by device_id, convert(int, inst), datepart(dd, timestamp),
datepart(hh, timestamp), convert(int, datepart(mi, timestamp)/15)

Computing sysUpTime Over a Polling Interval

To calculate time-dependent statistics for a device, calculate the total device uptime during the polling period. Create a temporary table containing the uptime for each polled device by using the following SQL commands:

select device_id, sum(sysUpTime)/100 uptime into #t1 from <table>
where rec_type = 0 group by device_id

The SQL commands create a temporary table called #t1 that contains device IDs and the uptime values for each device. The value is divided by 100 so that uptime will be in seconds (sysUpTime is in 100ths of a second).

Using ifOperStatus and ifAdminStatus

If you are polling interface values, include ifOperStatus and ifAdminStatus in your polling values to determine whether a given interface is operational. If you are using a GROUP BY clause in your SQL, add a HAVING condition to the group to check whether the interface was operational. Add the following commands to the group:

select ...
group by ...
having max(ifOperStatus) = 1 and max(ifAdminStatus) = 1

The possible values for ifAdminStatus are listed in Table 3.

Table 3 : Values for ifAdminStatus

Value	Meaning
1	up
2	down
3	testing

These values are also described in RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.

Calculating Traffic Values on Serial Lines

Because serial lines are full duplex, there is no single way to perform a traffic calculation. The following calculation provides the best view:

traffic = max(ifInOctets, ifOutOctets)
utilization = traffic/line bandwidth

In general, however, it is often less complex and more direct to look at traffic as the amount of data transmitted by a given device onto a line. This is consistent with the router calculation that obtains a load value. In this case, use the following calculation (where the utilization is a function of which end of the serial line that you are measuring):

traffic = ifOutOctets
utilization = traffic/line bandwidth

If you use ifInOctets+ifOutOctets as a traffic measure for serial lines, your utilization levels appear to be greater than 100 percent.

To determine whether you have a serial line, check the interface_type column in the Interfaces table. Table 4 lists the serial interface types and the protocols associated with each interface. For detailed information on interfaces and protocols, refer to RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II.

Table 4 : Serial Interface and Protocol Type

Serial Interface Type	Protocol Type
2	1822
3	1822
4	ddnx25
5	RFC 877-x25
16	lapb
17	sdlc
18	ds1
19	e1
20	ISDN
22	serial
23	PPP

To select serial interfaces, use the following with the WHERE clause:

select ...
where ...
and interfaces.interface_type in (2,3,4,5,16,17,18,19,20,21,22,23)

Additional Files in the $NMSROOT/contrib Directory

The following utilities have been added to the $NMSROOT/contrib directory. For more detailed information, refer to the individual README files also located in the directory.

• nmlogclean---Cleans out nmslog messages.
  

• nmpolldump---Dumps polling data to a file that can be imported to a spreadsheet.
  

• nmpollpurge---Helps with deletion of old polling data without destroying the poll table.
  

Shutting Down the CiscoWorks Daemons

If you are unable to shut down the CiscoWorks daemons (including nmpolld, nmlogd, nmeventd, or nmdevmond) by clicking on the Off button in the Process Manager window, perform the following steps as a superuser. Do not attempt to turn off the Sybase dataserver.

Step 1 At the UNIX prompt (#), enter the ps command to identity the process identification number (PID) for nmpolld:

# ps vax | grep nmpolld

The PID for nmpolld displays.

Step 2 Enter the following command to remove the process

# kill process-id-number

You may have to wait several minutes for the Polling daemon to shutdown.

Step 3 At the UNIX prompt (#), enter the ps command to ensure that the displayed processes do not include the process you just removed.

# ps vax | grep nmpolld

Step 4 If the process is still running, remove the nmpolld daemon:

hostname# kill -9 process-id-number

CiscoWorks Error Messages

This section describes undocumented error messages that do not appear in the CiscoWorks User Guide. They are arranged in alphabetical order.

Error Message

Bad poll rate: <string>, for poll group <string> (id=<string>)

Explanation The poll rate is invalid.

Recommended Action Ensure that the poll rate for this poll group is an unsigned number between 0 and 2684354 seconds (maximum valid poll rate). Use the Device Polling application to check the poll rate.

Error Message

Cannot find an IP address for the specified device.

Explanation The IP address for the device that you are trying to find is unavailable.

Recommended Action Check the /etc/hosts file, the Domain Name System (DNS) server, or the NIS server (whichever is applicable) to find out if the IP address is listed for the device.

Error Message

Cannot find data repository table <tablename>

Explanation The specified table does not exist in the Sybase directory.

Recommended Action Use Device Polling to recreate the poll group.

Error Message

Cannot open snm+lock file: path: permission denied.

Explanation This message appears if you try to launch SunNet Manager (SNM) when you are logged in as a user, and the directory with the snm+lock file and other files are owned by the superuser.

Recommended Action To transfer the ownership of the directory and the files that belong to the superuser to a user, enter the following command at the UNIX prompt (#):

# chown -R username directory name

Remove the snm+lock file:

# rm snm+lock

The snm+lock file is created when you launch SNM.

Error Message

Cannot poll this variable - do not know what it is.

Explanation The specified variable could not be identified.

Recommended Action Ensure that an entry for this variable exists in a .oid file in the $SNMHOME/agents directory.

Error Message

Cannot touch nmstartup.

Explanation If your system is running CiscoWorks, and you change the host name for your system, Sybase might not function because it continues to use the old host name.

Recommended Action Add the new host name to the $NMSROOT/sybase/interfaces file and restart Sybase. For example, if the new host name for your system is tassle, the entries in the interfaces file should be as follows:

SYBASE
        query tcp sun-ether tassle 8000
        master tcp sun-ether tassle 8000
        console tcp sun-ether tassle 8001



 Error Message 
Cannot write to <directory path>!

Explanation The permissions for the specified directory are read-only.

Recommended Action Using the chmod command, change the permissions for the specified directory to RW (read/write) or specify a different directory.

Error Message

Could not send Data Report to SunNet Manager Console.

Explanation The Real-Time Graphs application could not send a Data Report on the SNM Console.

Recommended Action Make sure the SNM Console is running. Also, check the shell where the SNM Console was started for additional Sun error messages.

Error Message

Data type mismatch for <string> (id=<string>) : database claims <string>

while mib claims <string>

Explanation The CiscoWorks MIB database (mib.bin) claims one data type, while the SNM schema claims another. The data type claimed by SNM will be assumed to be the correct one.

Recommended Action Correct the CiscoWorks MIB database or the SNM schema file, whichever is in error.

Error Message

Database is full - cannot store any more records.

Explanation The system might have inadequate disk space for storing database records.

Recommended Action Use the $NMSROOT/etc/enlarge_nms script to enlarge your database. For instructions, refer to Chapter 8, in the section "Enlarging the Database" in the CiscoWorks User Guide.

Error Message

Database server has disappeared.

Explanation The database server might have stopped working.

Recommended Action Access the Process Manager application and check to see if the On button for the database server is grayed out. If it is not, run the $NMSROOT/etc/nmstartup script to start all processes required for CiscoWorks.

Error Message

Delete doesn't delete data from the database.

Explanation When you delete a vendor from the Vendors table, the vendor is deleted from the Vendors window, but the information continues to exist in the People window.

Recommended Action Access the People window and delete the information for the appropriate vendor.

Error Message

Device Poll <string> (id=<string>) cannot find device id in database.

Explanation The specified device no longer exists within the Devices table in Sybase.

Recommended Action Use the Device Management application to ensure that the device still exists. If not, create it. Use Device Polling to recreate the poll group that was polling this device.

Error Message

Device Poll <string> (id=<string>) can't find previous stop record to 
update it - disabling itself.

Explanation There is a consistency problem in the start_stop table in Sybase.

Recommended Action Use the Process Manager window to restart Device Polling, or obtain the process ID number for the nmpolld process and send it a HUP signal.

Step 1 To obtain the process ID number for nmpolld, enter the following command:

hostname% ps -aux

Identity the process ID number for nmpolld.

Step 2 Send the HUP signal by entering the following command:

hostname% kill -HUP process ID number

---

Error Message

Device poll: desired poll rate: secs, actual poll rate:

Explanation Device Polling is unable to maintain polling at the desired poll rate.

Recommended Action Adjust your desired poll rate to a reasonable poll rate between 0 and 2684354 seconds.

Error Message

<directory> does not contain a valid CiscoWorks 1.0 or NetCentral 1.3!

Explanation During an upgrade installation, you are asked for the directory path for the old software. This error message indicates that the software in the specified directory path cannot be upgraded.

Recommended Action You can correct this error in one of two ways. You can specify the directory path that contains a valid CiscoWorks or NetCentral installation. You can also exit the installation process and reinstall the software, selecting new when prompted to specify the type of installation by the script.

Error Message

<directory path> is not a directory!

Explanation The specified directory is either a file or it does not exist.

Recommended Action Specify a valid directory path.

Error Message

File: File table is full.

Explanation This message appears if the number of open files on your system exceeds the limit defined in the system kernel.

Recommended Action To solve this problem, close some open files or shut down applications that might have open files. Or you can increase the limit for open files by building a new kernel and changing the allowed number of open files. For information on building a new kernel, refer to your Sun documentation.

Error Message

Fork failed: <string>.

Explanation Your system might have inadequate process quota or swap space, or you have a full process table.

Recommended Action Check the process quota for your system to find out if it is sufficient. If the process quota is inadequate, either shut down some applications or add more swap space to your system.

If your system swap space is inadequate, shut down some applications and rebuild the kernel with a larger process table.

Error Message

Invalid variable name: <string> - <string>

Explanation The specified variable cannot be identified or polled.

Recommended Action Ensure that an entry for this variable exists in a .oid file in the $SNMHOME/agents directory.

Error Message

Scrollbar - Bad proportion Length resource value, set to default.

Explanation When using the Log Manager application, this error message might display repeatedly.

Recommended Action None. Ignore the error message.

Error Message

Sybase error: This location is currently being referenced by one or more 
devices.

Explanation You are attempting to delete a location that is used by another device.

Recommended Action Delete references to this location for all devices that use this location and try again.

Error Message

System error: Unable to verify session ID.

Explanation This error message might appear when you login through the CW-Login application.

Recommended Action Follow these steps to verify the problem caused by error message and eliminate the problem:

Step 1 To verify if the error message is associated with a core dump caused by the
ps -ajx command, enter the following command at the UNIX prompt (%):

% ps -ajx

Determine if a core dump occurred. Also contact Sun Microsystems and report this error message.

Step 2 If the ps -ajx command caused a core dump, quit from all applications in SNM and CiscoWorks and enter the following command again:

% ps -ajx

A core dump might not occur now. If it does, report the problem to Sun.

Step 3 If a core dump did not occur a second time, restart the SNM and CiscoWorks applications.

The error message will not appear the next time you login using the CW-Login application.

To receive the SunOS patch (ID 100981) to fix this error, contact Sun Microsystems, Inc.

Error Message

Unable to find agents directory in <directory path> directory!

Explanation The configuration has attempted to find the directory path where the new CiscoWorks schema files can be merged with the existing SNM schema files. The specified directory does not have the appropriate subdirectory structure for SNM schema files.

Recommended Action Specify a directory with a valid subdirectory structure for SNM schema files. The default directory is $SNMHOME.

Error Message

Unable to obtain grapher port number.

Explanation The SNM grapher is not currently running.

Recommended Action Start the grapher again from the SNM Tools menu.

CiscoWorks Release 1.0(3) Caveats

This section lists notes and restrictions that apply to the CiscoWorks Release 1.0(3). If a caveat applies only to CiscoWorks Release 1.0 or 1.0(2), it is noted in the description of the caveat.

These caveats are arranged within sections by CiscoWorks applications. General caveats are presented first, followed by CiscoWorks applications, which are presented in an alphabetical order.

Nmlogd: Sybase error_handler: General SQL server error: Check messages from SQL error.

IP address went from 0.0.0.0. to 130.109.22.5

IP address went from 130.109.22.5 to 0.0.0.0

ranlib /usr/sys/sun4m/libprom.a

/usr/tmp/unbundled/ncskernel

OPEN LOOK Toolkit Warning in application "nmlogman":
    Scrollbar - Bad proportion Length resource value, set to default

Path Source is an unknown host
Path Destination is an unknown host

localhost: RPC: Unable to receive errno = Connection reset by peer.

ERROR: Unknown host <FQDN> displays. 

ld.so: warning: /usr/lib/libc.so.x.y has older revision than expected 8

# ln -s /usr/lib/libc.so.x.y /usr/lib/libc.so.1.8
# ln -s /usr/lib/libc.sa.x.y /usr/lib/libc.sa.1.8

X Error of failed request