Table of Contents

System Requirements for CW2000

Essentials System Recommendations

Determining Minimum System Configuration
Improving Essentials Server Performance
Improving Essentials User Report Response Time

CWSI Campus System Recommendations

Installation Notes

Prerequisites for Mounting the CW2000 CD-ROM
Mounting the CW2000 CD-ROM on the Local Machine
Accessing the CW2000 CD-ROM From a Remote Machine
Downloading a Patch to Correct EssentialsDbMonitor Process
Essentials Installation Notes

Installation Requirement for /opt Directory or Link
Aborting Essentials Installation Procedure
Package Failures During Installing and Uninstalling
Uninstalling Does Not Remove Packages If It Fails to Terminate dmgtd
Uninstalling Does Not Remove All Configuration Directories
Files Deleted After Uninstalling
Unable to Log In After Stopping System
Reinstall Unable to Lock Root Directory
Software List Shows Wrong Version for CW2000 Packages

CWSI Campus Installation Notes

Reinstalling CWSI Campus 2.2
Starting CWSI Campus 2.2

Uninstalling CWSI Campus

Resource Manager Essentials

Supported Device Import Software
Essentials Supported Devices
Using Essentials with Token Ring Switching Products

Catalyst Software Versions Supported
Cisco IOS Versions Supported

Essentials Release Notes and Caveats

Server Caveats
Browser Caveats
Desktop Caveats
Administrator Caveats
Inventory Caveats
Device Configuration Caveats
cwconfig Command Caveats
Import Caveats
Software Management Caveats
Syslog Analysis Caveats
Case Management Caveats
Device Navigator Caveats

CWSI Campus

CWSI Campus Application Compatibility
Startup Information
Browser Support for CWSI Campus Online Help
Online Help
CWSI Campus Error Messages
CWSI Campus Network Map

ANI Becomes Inaccessible After Learning Large Number of Devices
New Features for CWSI Campus Network Map
Unable to Open CWSI Campus in HP-UX 11.0
CWSI Campus 2.2 Topology Does Not Show Device Icons
Important Notes and Caveats for CWSI Campus Network Map

VlanDirector

New Features for VlanDirector
Important Notes and Caveats for VlanDirector

UserTracking

New Features in UserTracking
Important Notes and Caveats for UserTracking

TrafficDirector

New Features
New Standards Supported
New Monitoring Applications
Trend Reporting Enhancements
Monitoring Enhancements
Configuration Enhancements
Monitoring Application Enhancements
Important Notes and Caveats

Documentation Updates

Chapter 6---Working with Properties
Chapter 19---Displaying History Information
Appendix A---Troubleshooting
Appendix F---Integrating the TrafficDirector Application with Other Managers

AtmDirector

New Features for AtmDirector
Important Notes and Caveats for AtmDirector

CiscoView

New Features in CiscoView
Cisco IOS Information
Incrementally Installing Device Packages
Caveats Fixed in This Release
Troubleshooting
Installation Notes and Caveats
General Notes and Caveats

Troubleshooting

Asynchronous Network Interface (ANI)
Database Engine
CORBA Agent
RTPoller
Event Channel
Stopping and Starting CWSI Campus Daemons
When CWSI Campus Cannot Log Into AniServer

Documentation and Additional Resources
Service and Support
Cisco Connection Online

Release Notes for CW2000 (HP-UX)

These release notes describe the new features and caveats for the components of the CiscoWorks2000 (CW2000) family of products:

• Cisco Resource Manager Essentials

• CWSI Campus

This document contains the following sections:

• System Requirements for CW2000 on page 2

• Installation Notes on page 6

• Resource Manager Essentials on page 14

• CWSI Campus on page 44

• Documentation and Additional Resources on page 97

• Service and Support on page 98

• Cisco Connection Online on page 98

System Requirements for CW2000

The system requirements for Essentials and Essentials and CWSI Campus combined products are listed in Table 1.

• No browser is required for the Essentials server system. Client systems must have a supported browser installed. Refer to Installing Resource Manager Essentials and CWSI Campus on HP-UX for more information.

• Set your browser with "accept all cookies" enabled.

• For browsers running on a PC, set your desktop to use small fonts and set your desktop color map to 256, 32768, or 65536 colors.

• Netscape Navigator version 4.05 can be downloaded from CCO at http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000.
  You can also access ftp://archive:oldies@archive.netscape.com/archive/index.html.

• Essentials is supported on the browsers shown in Table 2.

Essentials System Recommendations

This section provides further information to help you choose a system that will best meet your specific needs.

Determining Minimum System Configuration

Three major considerations can help you to determine your minimum system configuration requirements:

1. Consider the number of managed devices to be polled by Availability.

2. Consider the number of Syslog messages expected daily.

3. Consider the number of managed devices expected in Inventory and
Device Configuration.

Availability is the primary consideration, after which you can then consider syslog messages and managed device expectations and determine your needs accordingly.

Improving Essentials Server Performance

To improve system performance for Essentials, consider the following options:

• Reduce the number of managed devices polled by Availability.

• Increase the interval used by Availability to poll managed devices.

• Reduce the number of syslog messages saved to the CW2000 database.

• Increase the interval used by Device Configuration to collect information for managed devices.

Improving Essentials User Report Response Time

Table 3 lists system recommendations for HP-UX systems running Essentials only.

CWSI Campus System Recommendations

For CWSI Campus, use a system configuration that will support the number of devices you want to manage using CWSI Campus and the number of end hosts you plan to manage using UserTracking. Select a configuration that will support the application with the higher requirement. For example, if you have 200 devices and 5,000 end hosts, choose the dual processor.

Table 4 lists CWSI Campus recommended system configurations.

Installation Notes

Follow these instructions for mounting the CiscoWorks2000 family of products CD-ROM instead of the instructions included in Installing Resource Manager Essentials and CWSI Campus on HP-UX.

Caution You must use this CD-ROM mounting procedure to successfully install the product.

Consider the following when you are installing CW2000:

• If you use the standard UNIX mount command to mount the CD-ROM, the software installation will fail.

• The Portable File System (PFS), which is used to mount the CD-ROM in this procedure, allows access to a variety of CD-ROM file systems.

• You must use this procedure to mount the CD-ROM for both CWSI Campus and Essentials.

• You can install CW2000 from a CD-ROM that is mounted on the local machine or from a CD-ROM that is mounted on a remote HP-UX machine.

Prerequisites for Mounting the CW2000 CD-ROM

The following are prerequisites for mounting the CW2000 CD-ROM:

• You must install patch number PHCO_15453 or any superseding patch from HP prior to running PFS on an HP-UX 10.20 system, or you might not be able to eject the CD-ROM after unmounting it.

• You must have network loopback and networking in general configured before running PFS on HP-UX.

The command netstat -rn shows the network routing tables; the entry lo0 is for the loopback interface.

Mounting the CW2000 CD-ROM on the Local Machine

Caution You must use this CD-ROM mounting procedure to successfully install the product.

To mount the CW2000 CD-ROM on the local machine, follow these steps while logged on as superuser:

Step 1 If you are running HP-UX 10.20, ensure that HP patch PHCO_15453 (or any superseding patch) is installed.

Step 2 Ensure that the path /usr/sbin is in the path environment variable.

Step 3 For HP-UX 10.xx systems, enable network loopback (if it is not already enabled) by adding the entry LOOPBACK_ADDRESS=127.0.0.1 to the file /etc/rc.config.d/netconf.

Step 4 Verify that network loopback is enabled by entering the following command:

netstat -rn.
 

Output similar to the following is displayed:

Routing tables
Destination     Gateway         Flags   Refs     Use  Interface  Pmtu PmtuTime
127.0.0.1       127.0.0.1       UH         0    2897  lo0        4608
171.69.217.60   127.0.0.1       UH         1    2299  lo0        4608
default         171.69.217.254  UG         5   86356  lan0       1500
171.69.217.0    171.69.217.60   U          0    7702  lan0       1500
 

The entry lo0 is for the loopback interface.

Step 5 Start the PFS daemons to allow network access on server and client by entering the following commands:

# nohup /usr/sbin/pfs_mountd &
# nohup /usr/sbin/pfsd 4 &
 

Step 6 Verify the processes running on the system by entering the following command:

# ps -ef|grep pfs
 

Output similar to the following is displayed:

root  1196  1195  0 14:07:28 ttyp1     0:00 pfs_mountd.rpc
root  1224  1208  0 14:07:47 ttyp1     0:00 pfsd.rpc
root  1210  1208  0 14:07:41 ttyp1     0:00 pfsd.rpc
root  1217  1208  0 14:07:44 ttyp1     0:00 pfsd.rpc
root  8669  7686  0 15:49:25 ttyp3     0:00 /usr/sbin/pfsd 4
root  8670  8669  0 15:49:25 ttyp3     0:00 pfsd.rpc
root  8617  7686  0 15:48:33 ttyp3     0:00 /usr/sbin/pfs_mountd
root  8739  7686  1 15:50:49 ttyp3     0:00 grep pfs

Step 7 Mount the CD-ROM by entering the following command:

# pfs_mount devicefile mount_point
 

where devicefile is the device filename of the CD-ROM drive and mount_point is the directory on which you want to mount the CD-ROM.

For example, the following command mounts the device /dev/dsk/c1t2d0 to the /cdrom directory:

# pfs_mount /dev/dsk/c1t2d0 /cdrom
 

Step 8 After you install the software, enter the following command to unmount the CD-ROM:

#pfs_umount/cdrom
 

Accessing the CW2000 CD-ROM From a Remote Machine

Caution You must use this CD-ROM mounting procedure to successfully install the product.

To access the CW2000 CD-ROM from a remote machine, follow these steps:

Step 1 Perform the following steps on the remote machine while logged on as superuser:

(a) Mount the CD-ROM on the remote machine as described in the section "Accessing the CW2000 CD-ROM From a Remote Machine."

(b) Add the following entry to file /etc/pfs_exports (create the file if it does not already exist):

/cdrom -access=client
 

where client is the name of the host on which you want the install the software.

(c) Enter the following command to export the directory that you just mounted:

# /usr/sbin/pfs_exportfs-a
 

Step 2 Perform the following steps on the local machine (the machine on which you want to install the software) while logged on as superuser:

(a) Start the pfs_mountd daemon by entering the following command:

# nohup pfs_mountd &
 

(b) Mount the CD-ROM by entering the following command:

# pfs_mount serverhost:remote_mount_point local_mount_point
 

where serverhost is the name of the remote machine, remote_mount_point is the name of the CD-ROM mount point on the remote machine, and local_mount_point is the name of the CD-ROM mount point on the local machine.

For example, the command

# pfs_mount server:/cdrom1 /cdrom2
 

mounts the /cdrom1 directory of the remote machine named server to the /cdrom2 directory of the local machine.

Downloading a Patch to Correct EssentialsDbMonitor Process

In some situations, the EssentialsDbMonitor process does not start within the specified time, causing all CW2000 database-related processes to quit. The output of the command

/opt/CSCOpx/bin/pdshow EssentialsDbMonitor

will show that the state of EssentialsDbMonitor is not running normally. The DbServer process, however, can run normally even though the EssentialsDbMonitor process has failed.

If this situation occurs, you can download the needed patch from the following URL:

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000

Follow these steps to correct this situation:

Step 1 Download the dmgt-tune1.0-hpux-rme2.0.sh script to the /tmp directory.

Step 2 Shut down the CW2000 system using the following command:

/sbin/init.d/dmgtd stop
 

Step 3 Run the script using the following command:

sh /tmp/dmgt-tune1.0-hpux-rme2.0.sh
 

Step 4 Restart the CW2000 system using the following command:

/sbin/init.d/dmgtd start
 

This procedure modifies the necessary parameters for EssentialsDbMonitor to start successfully. The script dmgt-tune1.0-hpux-rme2.0.sh will report if the modifications were successful.

[CSCdk92403]

Essentials Installation Notes

In most of the HP-UX machines, the values of nfile (kernel parameter for maximum number of open files) and ninode (parameter for maximum number of open inodes) are low by default. When CW2000 is started without tuning these parameters, the file table gets full and the system must be rebooted.

CW2000 might also misbehave due to insufficient kernel resources such as semaphores or shared-memory segments. As a result, before starting CW2000, the kernel must be properly tuned.

At the end of a successful install, the install script checks the kernel parameter values to ensure proper kernel tuning. If the parameters are found to be low, you are notified with the following message:

INFO: Needs to tune the kernel.This will require a reboot
Proceed with kernel rebuilding? [Y]
 

Upon confirmation, the script builds the kernel as per the requirements. Before overwriting the kernel, you are again prompted with the following message:

INFO: Kernel build completed.
Overwrite /stand/system and Reboot with new kernel ? [Y]
 

Upon confirmation, the script completes the installation and reboots the machine from the newly built kernel.

If the kernel build is unsuccessful, daemons will not be started. You will be asked to tune the kernel and start the daemons.[CSCdk62037]

Installation Requirement for /opt Directory or Link

Essentials must either install itself or a link to itself in the /opt directory. Without write access to the /opt directory, you cannot install Essentials. [CSCdk03648]

Aborting Essentials Installation Procedure

If you abort the Essentials installation procedure before it completes, not all required components are installed, and Essentials will not operate successfully.

To recover from an aborted installation, run uninstall.sh, and remove the already installed packages, then start the Essentials installation procedure from the beginning. [CSCdj64037]

Package Failures During Installing and Uninstalling

If you send any signal to setup.sh, the default signal handler (exit) is invoked. This behavior is intended to allow you to terminate the install at any time. If a CNTL-C (SIGINT) or other signal is sent to setup.sh during the package install phase, some packages do not install properly. It is recommended that you terminate the installation before the packages are added or after the packages are added. [CSCdk52988]

Uninstalling Does Not Remove Packages If It Fails to Terminate dmgtd

If you run /opt/CSCOpx/bin/unintall.sh, the script exits quickly and a message is displayed that indicates dmgtd is terminated with SIGKILL.

The workaround is to run uninstall.sh again. [CSCdk48753]

Uninstalling Does Not Remove All Configuration Directories

Uninstalling Essentials does not remove all Device Configuration related directories in /var/adm/CSCOpx/files. To remove all Device Configuration related files, remove the /var/adm/CSCOpx/files/archive directory. [CSCdk50635]

Files Deleted After Uninstalling

If you move the configuration archive directory to a new location, for example, newDir, the Essentials uninstallation script deletes all files with the following extensions:

newDir/config/any_subdirectory/*running.cfg

newDir/config/any_subdirectory/*startup.cfg

newDir/config/any_subdirectory/*running.dfr

newDir/config/any_subdirectory/*running.dfc

newDir/config/any_subdirectory/*running.cmt

If you created your own files with these extensions, you must move them to a different directory before uninstalling Essentials.

Unable to Log In After Stopping System

After performing a "stop system" request from the web, the browser disables the system to the point where you cannot restart the system using the browser.

You must log in to the server, and at the command prompt, enter the pdsys start command to restart the Essentials system. [CSCdk26767]

Reinstall Unable to Lock Root Directory

During installation/reinstallation of Essentials on HP-UX, the installation log might show the following errors:

ERROR: Cannot lock "/" because another command holds a conflicting lock.

ERROR: Cannot read the target "/".

You can ignore these error messages, as the installation will complete successfully. [CSCdk45889]

Software List Shows Wrong Version for CW2000 Packages

If you use "swlist" to find out the version of a CW2000 package, you might not get current information.

The workaround is to select Home > About Resource Manager Essentials >
Copyright and Versions to find out package version information. [CSCdk90748]

CWSI Campus Installation Notes

The following sections contain information about installing the CWSI Campus product. Review the following information before installing CWSI Campus 2.2.

Reinstalling CWSI Campus 2.2

If you have installed CWSI Campus 2.2, and you must reinstall it, you must close all CWSI Campus applications, then reinstall CWSI Campus 2.2.

Starting CWSI Campus 2.2

After installing CWSI Campus 2.2, wait approximately 5 minutes before starting the product. If you attempt to start the product too soon, the following error message is displayed:

osagent could not find the object object_name.
ANI server
 

Click OK, wait a few minutes, and then start the product again. This error does not affect product operation.

Uninstalling CWSI Campus

Note the following caveats:

• Before uninstalling CWSI Campus, close all CWSI Campus windows.

• After uninstalling CWSI Campus, some directories and files might remain. In this case, delete these directories and files manually. If you are unable to delete them, and the message "the file is in use" appears, reboot your machine, then manually delete the remaining files.

• Although TrafficDirector and CiscoView are stand-alone products, they cannot be uninstalled separately from the CWSI campus package because they share components with CWSI Campus.

You can uninstall CWSI Campus, if necessary, by entering the following commands:

cd /<CWSIROOT>/bin
./uninstall.sh
 

Resource Manager Essentials

This section contains information, notes, and caveats for Resource Manager Essentials.

Supported Device Import Software

Essentials lets you import device information from both local and remote network management databases identified in Table 5.

Table 5: Supported Software for Device Import from Local and Remote Network Databases

Software	Version
HP OpenView Network Node Manager	4.11, 5.0, and 5.01
CiscoWorks	3.2 and 4.0
CiscoWorks for Switched Internetworks (CWSI)	2.1
CWSI Campus	2.2

Essentials Supported Devices

Essentials supports the devices listed in Table 6 through Table 10. See the "Cisco IOS Versions Supported" section for information on the supported Cisco IOS versions. See the "Using Essentials with Token Ring Switching Products" section for the devices the Essentials Software Management module supports.

It is possible to insert an ATM Signal Processor (ASP) card into slot 13 of a Catalyst 5500 chassis. Other LS1010 cards might also be inserted in the chassis. Due to hardware limitations, the supervisor card in the Catalyst 5500 cannot accurately detect the presence or status of these cards. As a result, Essentials inventory will not display this hardware correctly in certain reports, and available slots might be inaccurate. Hardware enhancements have been proposed to address this problem.

Table 6: Inventory Manager Supported Devices

Product Family	Devices Supported
Cisco CS500	CS500
Cisco/CiscoPro 7xx	751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776
Cisco/CiscoPro 10xx	1000, 1003, 1004, 1005, 1020
Cisco/CiscoPro 16xx	1601, 1602, 1603, 1604, 1605
Cisco 2xxx	2000, 2102, 2202
Cisco/CiscoPro 25xx	2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF
Cisco 26xx	2601, 2610, 2611
Cisco/CiscoPro 3xxx	3000, 3101, 3102, 3103, 3104, 3202, 3204, 3620, 3640,
Cisco switching access concentrator	MC3810
Cisco/CiscoPro 4xxx	4000, 4000-M, 4500, 4500-M, 4700, 4700-M
Cisco 25xx access servers	2509RJ, 2511RJ
Cisco AS5xxx access servers	AS5200, AS5300, AS5800
Cisco 7xxx	7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513
Viper Switch	CPW16, ESP2015
Catalyst	1220, 1600, 1700, 1800, 1900, 1912, 2200, 2600, 2800, 2820, 2828, 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 2926, 3000, 3001, 3011, 3011 router, 3100, 3200, 3500, 3600, 3900, 3920, 5000, 5002, 5500, 5505, 5509, 5CRSM, 8510
CiscoPro EtherSwitch	10/100, 1100, 1200, 1220,1220&L, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1601, Pro 16, 1900, 1900L, 2200
ATM switch	LightStream 1010, 1015, 2020
Multiservice switch	BPX 8620, BPX 8650, IGX 8410, IGX 8420, IGX 8430, MGX 8220, IPX 8xxx
SwitchProbe	WS-PB7-4ETH-32, WS-PB7-8ETH-32, WS-PB7-12ETH-64, WS-PB6-1ETH-8, WS-PB6-1ETH-16, WS-PB6-2ETH-16, WS-PB6-1TR-8, WS-PB6-1TR-16, WS-PB6-2TR-16, WS-PB6-ETHTR-16, WS-PB6-1WANETH-8, WS-PB6-1WANETH-16, WS-PB6-1WANTR-8, WS-PB6-1WANTR-16, WS-PB7-2WANTR-32, WS-PB7-3WANTR-32, WS-PB7-4WANTR-32, WS-PB7-HSSIETH-32, WS-PB8-DFDDIETH-32, WS-PB8-ATM3ETH-32, WS-PB8-1FEHD-TX-32, WS-PB8-1FEFD-TX-32, WS-PB8-2FEHD-TX-32, WS-PB8-1FEHD-FX-32, WS-PB8-1FEFD-FX-32, WS-PB8-2FEHD-FX-32
Workgroup concentrator	1000, 1100, 1400
FastHub	300, 100+, 316T, 3116, 316C, 2116, 216T, 116T, 116C, 1116
MicroHub	1502, 1503, 1516
General SNMP devices	Most MIB II compliant

Table 10: Software Management Supported Devices

Product Family	Devices Supported
Cisco/CiscoPro 7xx	760 series, 770 series
Cisco/CiscoPro 10xx	1000, 1003, 1004, 1005
Cisco/CiscoPro 16xx1	1601, 1602, 1603, 1604
Cisco/CiscoPro 25xx2	2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF
Cisco 26xx	2601, 2610, 2611
Cisco/CiscoPro 3xxx	3620, 36403
Cisco switching access concentrator	MC3810
Cisco/CiscoPro 4xxx	4000, 4000-M, 4500, 4500-M, 4700, 4700-M
Cisco 25xx access servers4	2509RJ, 2511RJ
Cisco AS5xxx access servers5	AS5200, AS5300, AS5800
Cisco 7xxx, 7500 RSP series routers6	7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513, including CIPs
Catalyst7	29008, 2926, 5000, 5002, 5005, 5500, 5505, 5509, 8500, 8510, C5RSM, Catalyst 5000 modules supported: NMP, TR, FDDI, CDDI, ATM
ATM switch	LightStream 1010, 1015

1Dual Flash bank and single Flash bank. 2Dual Flash bank and single Flash bank. 3MICA modem upgrades supported. 4Dual Flash bank and single Flash bank supported. 5Dual Flash bank and single Flash bank on AS5200 supported; MICA modem upgrades on AS5200 and AS5300 supported; Microcom 56K firmware upgrade on AS5200 and AS5300 supported. 6Cisco 7000 series; 7200 series router upgrades supported; no slave RSP upgrade available; CIP card microcode upgrades supported on 7000 and 7500 series devices running Cisco IOS Version 11.1(1) or later. 7Supervisor I, II, III, ATM, FDDI, CDDI, and Token Ring switch modules on Catalyst 5000 and 5500 series devices. 8Catalyst 2900XL devices are not supported.

Using Essentials with Token Ring Switching Products

When using Essentials with Token Ring switching products, verify you have installed the firmware revisions as noted in Table 11.

Catalyst Software Versions Supported

Table 12 lists platform-specific software supported when using Essentials on Catalyst devices.

Cisco IOS Versions Supported

Support is provided for devices running Cisco IOS Versions 10.3 to 11.3 only. Unless your devices are running Cisco IOS Version 10.3 or later, some MIB values might not be supported. As a result, devices running versions of Cisco IOS earlier than 10.3 might not provide all device details in the inventory reports.

Essentials Release Notes and Caveats

This section contains the notes and general caveats that apply to Essentials on the HP-UX operating systems. It consists of the following sections:

• Server Caveats on page 22

• Browser Caveats on page 23

• Desktop Caveats on page 26

• Administrator Caveats on page 27

• Inventory Caveats on page 29

• Device Configuration Caveats on page 31

• cwconfig Command Caveats on page 33

• Import Caveats on page 33

• Software Management Caveats on page 34

• Syslog Analysis Caveats on page 41

• Case Management Caveats on page 42

• Device Navigator Caveats on page 43

Server Caveats

Using the Apache http server to support software not installed by Essentials is not supported.

Browser Caveats

If a graph looks awkward, or if text scrolls off a screen, reload or refresh the browser page. Usually, if you reload or refresh the page, the problem corrects itself.

Some e-mail sent to users contains URL links that wrap to more than one line. The workaround is to log in to Essentials, then use the Essentials tree control to perform the operation.

Printing Does Not Work Reliably

To print an exact copy of an Essentials screen, use the Print Screen or Capture Screen function on your machine.

Browser Accepts Only Certain Cookies

When using Netscape Navigator or Internet Explorer, you might encounter a situation in which Essentials returns you to the login screen when you select an option. If this occurs, configure your browser to accept all cookies (Netscape: Edit > Preferences >
Advanced > Accept all cookies; Internet Explorer: View > Internet Options > Advanced, select Cookies). [CSCdk17516]

The login dialog is not shown after you upgrade your version of Internet Explorer. The workaround is to flush your browser cache. [CSCdk18245]

The following administrator options have been found to sometimes cause the Internet Explorer browser to hang:

• Admin > Device Configuration > General Setup > Netsys Setup > Schedule

• Admin > Device Configuration > General Setup > Change Probe Setup >
  Config Retrieval Schedule

Installing the Internet Explorer 4.0 Service Pack 1 eases the problem, but the browser still might hang occasionally. [CSCdk32462]

When trying to print Device Configuration or Syslog (Java-based) reports from Internet Explorer running on Windows 95, you get a system error.

The workaround is to save the HTML version of the report to your local disk, then print the report from your local machine. [CSCdk26130]

Essentials depends on cookies to transmit permission-related information. If multiple copies of Internet Explorer are opened for use with Essentials on the same desktop by launching them from the Start > Programs > Internet Explorer interface or from an icon on the desktop, Internet Explorer generates incorrect authorization failures when you are correctly logged in.

The workaround is to start new browser windows using the New option from within the browser. [CSCdk33035]

Using Internet Explorer 4.x on a machine with an installation of Microsoft Visual J++ might cause some Admin > Device Configuration tasks to fail with a NullPointerException or a InvalidClassException. Installation of Microsoft Visual J++ installs different versions of the Java JDK 1.1 class files which are used by Internet Explorer. [CSCdk31703]

A server error message is displayed on the lower frame of the Exceptions Summary Report in Change Audit > Exceptions Summary, but only under the following conditions:

• When using the Netscape browser to view the reports

• When you select all days of the week to generate the Exceptions Summary Report

The workarounds include:

• Using Internet Explorer to view the Exceptions Summary Report

• Selecting an option other than all days of the week to generate the Exceptions Summary Report

If you are using Netscape and you select all days of the week to generate the report, after the server error message is displayed, you can resize the report window or the lower frame of the report. This removes the error message and display the report successfully. [CSCdk44743]

Netscape 4.0x does not display the correct month and day for GMT time zones containing offset minutes [CSCdk34547]

Netscape does not always display the date in the correct time zone or with the correct date on the Collect Server Info and Self Test pages.

The workaround is to use Microsoft Internet Explorer 4.01. [CSCdk44551]

The Navigator 4.05 right mouse button pop-up menu offers the Open Frame in New Window option. If you select this option while in Essentials, the right frame of the Essentials desktop appears, but the navigation tree does not.

The workaround is to complete all tasks in Essentials windows. [CSCdj50947]

On Solaris, HP-UX, and AIX, Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state.

The workaround is to click the Navigator Reload button. [CSCdj55007]

If you access the Glossary (Help > Glossary) with Navigator 4.05, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section.

The workaround is to click Glossary. [CSCdj57449]

For Netscape browsers, the "All Syslog Messages" report from the Device Center does not work. You get a null pointer exception message when you try to obtain this report. [CSCdk52585]

Desktop Caveats

JavaScript Error When Clicking Back from CCO Web Site

When using the online help file Help > Contents > CCO and Device Management > Case Management > Cisco Web Site link, if you select the Back button, an error message appears. [CSCdk27845]

When the device selector is shown on some of the Essential screens, if the Finish button is clicked before the applet code has finished initializing, a java script popup error displays. Ignore this message. [CSCdk07201]

Administrator Caveats

HP-UX Needs Patch (Server Requirements)

The following patches are required for Essentials to run on HP-UX:

• PHSS_15043 or superseding patch for HPUX 10.20

• PHSS_14577 or superseding patch for HPUX 11.0

DCE-Core software needed for both HP-UX 10.20 and HP-UX 11.0 is available on the operating system installation CD. The abovementioned patches can be downloaded from http://us-support.external.hp.com. These are patches for aCC runtime components (dld.sl). [CSCdk32911]

The workaround is to edit the filtered file and remove the incorrect prefix to the NM header line after the filtering is complete. [CSCdk51413]

When the database is down, if you click Admin > Inventory > Schedule Collection, a blank page is displayed. [CSCdj60419]

# /sbin/init.d/dmgtd start
 

Click Admin > Troubleshooting > Collect Server Info link to collect server information, then call your technical support representative. [CSCdk37124]

If the Event Channel Admin screen hangs or reports the system is down, verify the EDS process is running using the Process Status screen (Admin > System Admin >
Process Status). If running, check the daemons log (/var/adm/CSCOpx/log/daemons.log) for process failures or errors in EDS, SyslogAnalyzer, or ChangeAudit. EDS and the dependent processes might need to be restarted if failures are found. [CSCdk09614]

Some proxy or firewall products require users to be authenticated before accepting or forwarding connections. The Essentials proxy function does not provide authentication information to these proxy servers and requires per-user authentication information itself. [CSCdk05720]

[CSCdk12362]

When you add or import a device or change device information, avoid using angle brackets (< or >) in the User or Serial Number fields. When some browsers encounter these characters, they might interpret the information incorrectly. [CSCdj24567]

Inventory Caveats

Export to File Can Overwrite Existing System Files

When you select Admin > Inventory > Export to File and specify the filename to which the device information is to be exported, if the filename already exists, the system overwrites the existing file and no warning or reconfirmation message appears. Use caution when specifying a filename, as it could potentially overwrite important files. [CSCdk48937]

In the Chassis Slot Details reports for Access devices (AS5200s and AS5300s) and RSMs, the number of available slots displays a negative number; however, the same information is displayed correctly in the Detailed Device Report. [CSCdk52231]

For Year 2000 compliance and Software Version Reports generated by Resource Manager 1.1, the EPROM revision is blank for software version 5.3(5) or greater; however, versions less than 5.3(5) are in the report. [CSCdj91789]

The workaround is to go to the device and configure the modem for use, then reacquire the inventory data for the device. [CSCdk35153]

The workaround is to run the Detailed Device Report, which shows details about each Flash partition that was discovered when the router was added to inventory. [CSCdk10221]

The workaround is to remove any unwanted commas that might cause data to be placed in separate fields when they should be placed in a single field. [CSCdk25851]

Device Configuration Caveats

In order for the configuration archive to successfully gather the ATM and RSM module configurations, these modules must have the same Telnet passwords as that of the supervisors for the Catalyst 5000 family of devices.

JRunProxyServer Leaks File Handles Due to Configuration Archive CORBA

If Tasks > Device Configuration > Update Archive is used frequently, or if running or startup configuration files are retrieved frequently from the configuration reports that provide access to these configuration files, after weeks or months of use, the Essentials product stops working correctly because it has run out of file descriptors.

The workaround is to enter kill -HUP WebServer pid. (To determine the pid on the WebServer, run the command /opt/CSCOpx/bin/pdshow WebServer.) [CSCdk54194]

The workaround is to change the permission of the log files. [CSCdk52137]

If you delete a device from the Essentials inventory, the corresponding Netsys report for that device is not removed. The old report remains, but is not updated. [CSCdk51481]

http://<RME_server_hostname>/CSCOnm/servlet/JSServlet

Click the Unload All Clients option. The page will be refreshed after the clients are unloaded. Then click the Load All Clients option. [CSCdk52938]

The workaround is to check the archived configuration file. [CSCdk50736]

Partial failure for getting module configurations for Catalyst devices results in error strings being shown as part of the raw configuration, as well as raw diff. [CSCdk49749]

cwconfig Command Caveats

Access Restrictions and File Permissions

On UNIX, cwconfig is a set-userid program owned by root and belongs in the bin group. However, as soon as the program is launched, (internally) cwconfig sets userid to bin. The groupid of the process remains the same as the invoking user's groupid. Consequently, all files created by cwconfig---exported configurations and log files--- are owned by bin and belong in the same group as the invoking user. The files have Read-Write permissions for both owner and group. [CSCdk44589]

[CSCdk50007]

Command-Line Syntax Errors

When a cwconfig session has multiple syntax errors, only the first error detected by the tool is reported; the others remain unlisted. There is currently no workaround. [CSCdk12667]

Currently, cwconfig cannot validate the syntax of configuration files uploaded to the device via the import command. Consequently, the cwconfig import process reports success even if a configuration file with invalid contents is attempted to be written to the device. The configuration update does not succeed on the device, but cwconfig cannot detect this failure. [CSCdk18495]

The workaround is to change the operating system configuration to increase the number of open file descriptors allowed per process. [CSCdk53421]

Import Caveats

Import from Local NMS is Not Supported on HP-UX 11.0

Import from local NMS on HP-UX 11.0 is not supported on Essentials because HP OpenView and CiscoWorks are not supported on this operating system. [CSCdk57643]

[CSCdk01464]

The workaround is to upgrade Cisco IOS to 11.2(14)P or higher. Cisco IOS versions 11.3(2) and 11.2(9) also exhibit bug symptoms; Cisco IOS versions 11.3(3) and 11.2(13) contain fixes. [CSCdj60284]

The workaround is to verify that TACACS information is properly configured, or delete TACACS information completely for such devices. [CSCdk31318]

Software Management Caveats

Supervisor III History Is Not Showing Correct Data Under Image Entity

In the Browse History Report page for Catalyst devices, the Image Entity column displays extra text after the image name as in Supervisor.1/system SW.

This extra text after the "/" character is incorrect and should be ignored. [CSCdk50175]

If you are not upgrading the Supervisor module in a Catalyst distribution job, but upgrading some other modules, do not select the "Backup current running image" job option. Selecting this option, which upgrades Catalyst modules other than Supervisor, can cause the Software Management application to incorrectly import the current running Supervisor image as the module (ATM, FDDI, CDDI, Token Ring) image in the software library. [CSCdk51236]

When you are importing images from L2 and L3 Catalyst switches to the Software Management library, you might get a warning message stating "Either there is no image present in the Flash or Flash MIB is not supported by this device," in addition to the list of images on that device. Ignore this message. [CSCdk52400]

The Work Order Report displayed during the Distribute Images job creation process for Catalyst switches incorrectly displays that the image will be copied to the software library at the time of distribution for ATM, FDDI, and Token Ring modules. Ignore this message. [CSCdk51176]

Before proceeding with module software upgrades, manually verify that the Catalyst switch is running a compatible Supervisor software version. [CSCdk50317]

In the Recommend Image Upgrade screen, verify from the software version numbers whether the new target image supports all the features you wish to deploy. Software Management does not check if all current configured features in the ATM module are present in the new image. [CSCdk40327]

If the 4.2(x) image is selected as the target image during Image Distribution from CCO, use the Browse Library > Edit Image Attributes screen to edit the version number. [CSCdk50101]

Software Management supports only the combined format files (for example, mcom-modem-code-xx.bin) but it does not support the separate firmware and dsp code files. These files cannot be imported to the software library. [CSCdk27380]

Step 5 Add the image to the library using the "Add Image to Library" option. [CSCdk22546]

The workaround is to select less than 50 devices if they have a slower link to the Internet. [CSCdk32490]

If you import images that require more than 20 minutes to complete, the browser might time out and display the message "Document contains no data." Decrease the number of images you import at one time to ensure the import process requires less than 20 minutes. [CSCdj25733]

If you import an image from CCO when the temporary directory file system is full, you might receive server errors when running other Essentials functions. To avoid these errors, keep the temporary directory clear of unneeded files. [CSCdj44161]

For Supervisor III modules on Catalyst 5000 and 2900 devices, the baseline and synchronization options are supported only when the modules are running software version 4.1 or later. [CSCdk06556]

Syslog Analysis Caveats

NullPointerException Error

For all Netscape browsers, the "All Syslog Messages" report from Device Center does not work. You will get a null pointer exception message. The internal cause of this is due to the "title" not being set for this report. There is currently no workaround. [CSCdk52585]

Click Advance, then double-click on each 6 and replace it with *, then press Enter. [CSCdk49695]

Syslog reports do not have Cisco IOS explanations for some messages. Refer to the latest Cisco IOS reference manual for additional information on reported messages. [CSCdj61218]

..%CIP4-6-MSG: %MSG802-6-LLC.START: Starting LLC-2...
 

%MSG802 6 LLC_START Starting LLC-2...
 

where MSG802 is the facility, 6 is the severity, LLC_START is the mnemonic, and the remaining text is the description. The first part (CIP4-6-MSG) is not used. Only the second part of the CIP message is stored. [CSCdj16580]

The workaround is to again generate the syslog report. [CSCdk33214]

Case Management Caveats

Case Management Query Does Not Show All Open Cases

Case Management Query (Tools > Case Management > Case Query/Update) might not show all open cases. This occurs when there is more than one contract associated with your CCO User ID because CCO uses the contract number as the validation key for the Case Query operation.

The workaround is to request via e-mail to cco-team@cisco.com that all contracts be added to the Additional Contracts field in your CCO user profile. [CSCdj50287]

If you open a case with CCO via e-mail after unsuccessfully trying to open a case using Essentials (Tools > Case Management > Case Open), processing of the e-mail might take a while. The Technical Assistance Center (TAC) is usually able to process these requests within an hour, but it could take longer. Until the case is processed, the case is not available via Case Query/Update (Tools > Case Management > Case Query/Update). [CSCdj50294]

The workaround is to enter the enable password in the Enable Secret Password field for the device (Admin > Inventory > Change Device Attributes). [CSCdj82514]

Internet Explorer does not open a second window with collection details when you click on the Pass or Fail link in the "Inventory and Telnet Collection Status" window. [CSCdk32038]

Continue incrementing this value until the process completes. [CSCdk50702]

Device Navigator Caveats

Catalyst 1924EN Software Version 8.0.4 Supports Web Browsing

Catalyst 1900 devices are not supported by Device Navigator in this release. [CSCdk43726]

The workaround is to close the help window and view that help topic manually through the Help Contents window. [CSCdk11625]

CWSI Campus

The CWSI Campus components are as follows:

• CWSI Campus Network Map

• VlanDirector

• UserTracking

• TrafficDirector

• AtmDirector

• CiscoView

This section contains information that applies to all of these components. Notes and caveats for the individual components are described in these release notes in the sections about the specific component.

CWSI Campus Application Compatibility

Table 14 shows the Cisco devices that CWSI Campus applications support and the minimum software version required on the device.

Table 14: CWSI Campus Application and Cisco Device Compatibility Matrix

Device Family	Cisco Devices	Network Topology	Device Mgmt	Traffic Mgmt (RMON)	VLAN Mgmt	LANE Mgmt	ATM Mgmt	User Tracking	Minimum Software
Catalyst Switches
Catalyst 1200	1201, 1202, 1211, 1212	X	X	X	-	-	-	-	4.29
Catalyst 1900	1912, 1924	X	X	X	X	-	-	-1	8.0 (Enterprise)
Catalyst 2820	2822, 2828	X	X	X	X	X2	X	-1	8.0 (Enterprise)
Catalyst 2900XL	2908XL, 2916XL/ MXL, 2924XL/CXL	X	X	X3	-4	-5	-5	-4	IOS 11.2(8) SA
Catalyst 2900	2901, 2902, 2926	X	X	X	X	-	-	X	2.4.3
Catalyst 3000	3000, 3100, 3200	X	X	X	X	X	X	X1	2.2.2
Catalyst 3900	3900, 3920	X	X	X	X	-6	X	X7	3.0(2)
Catalyst 5000	5000, 5002	X	X	X	X	X8	X	X	2.4.3
Catalyst 5500	5500, 5505, 5509	X	X	X	X	X8	X	X7	2.4.3
Catalyst 8500 CSR	8510	X	X	X	-	-	-	X9	IOS 11.3
ATM Switches
LightStream	LightStream 1010 (with Frame Card 1)	X	X	X10	-	X	X	-	IOS 11.2 (8.0.1) FWA4.1
Catalyst 8500 MSR	Catalyst 8510 (with PFQ feature card)	X	X	X10	-	X	X	-	IOS 11.2 (8.0.1) FWA4.1
Routers
Route Switch Module	Catalyst 5000	X	X	X11 12	-	-	-	X12	IOS 11.2
C7200	7202, 7204, 7206	X	X	X11	-	-	-	X12	IOS 11.1
C7500	7513, 7507, 7505	X	X	X11	-	-	X	X12	IOS 11.1
C4000	4500, -M, 4700, -M	X	X	X11	-	-	X	X12	IOS 10.3
C3600	3620, 3640	X	X	X11	-	-	X	X12	IOS 11.3
C2600	2610, 2611, 2612	X	X	X11	-	-	-	X12	IOS 11.3
C2500 (LAN/ WAN)	C2501- C2504, C2513- C2515	X	X	X11	-	-	-	X12	IOS 10.3
C2500 (hub/ routers)	C2505, 2507, 2516, 2519, 2524, 2525	X	X	X11	-	-	-	X12	IOS 10.3
C2500 (Frame Relay)	C2520-C2523	X	X	X11	-	-	-	X12	IOS 11.0
C1600	1601-1605	X	X	X11	-	-	-	X12	IOS 11.2
C1000	1000, 1003-1005, 1020	X	X	X11	-	-	-	X12	IOS 10.3
Probes and Analysis Modules
-	LAN SwitchProbes (Ethernet, Token Ring, FDDI, Fast Ethernet)	-	X13	X	-	-	-	-	4.21
-	WAN SwitchProbes (FR, ATM, HSSI)	-	X13	X	-	-	-14	-	4.2.1
-	WAN SwitchProbes (Multiport T1/E1)	-	X13	X	-	-	-	-	4.2.2
-	Network Analysis Modules (NAM) (Catalyst 5X00 module)	-	X	X	-	-	-	-	4.3 (Catalyst)

1Acquires MAC table data and supports VMPS client functionality, but not VMPS server functionality. 2LAN Emulation Client support only. 3Roving is not supported. Acquires MAC table data, but does not support VMPS client or VMPS server functionality. 4The Catalyst 2900XL series switches will support VTP and ISL switching technologies in CY Q4 1998. Management of these switches through VlanDirector and UserTracking will follow. 5The Catalyst 2900XL series switches will support ATM modules in CY Q4 1998. Management of these ATM up links and services will follow. 6Token Ring LANE functionality is not currently provided within the Catalyst 3900 and Catalyst 5000 series (TR module) switches, but will be available in future product releases. 7Acquires MAC table data, but does not support VMPS client or VMPS server functionality. 8Requires Supervisor software version 2.4.3 and ATM line card software version 3.2.5. 9Cisco Catalyst 8500 CSR series switches support the UserTracking application with ARP table information. 10The Catalyst 8500 MSR series ATM switches support ATM RMON and are managed by AtmDirector within CWSI Campus. 11The TrafficDirector update scheduled for CY Q4 1998 will provide support for Cisco-IOS-based RMON devices. Two group RMON support (that is, Alarms and Events) is provided in all IOS versions 11.1 and above. Full RMON support (all 9 groups) is provided as an option in the IOS 11.1 Plus and greater images for the 2500 family routers and the AS5200 and AS5300 access servers. 12Cisco routers support the UserTracking application with ARP table information and Alarm and Event groups in TrafficDirector. 13Can be configured using TrafficDirector. 14The AtmDirector application does not manage ATM SwitchProbes. These SwitchProbes are managed using the TrafficDirector (RMON-based) application within the CWSI Campus suite.

Startup Information

You can select and start up CiscoView from HP OpenView (HP-OV) manager. The additional CWSI Campus functions, including the CWSI Campus topology mapping services, VlanDirector, AtmDirector, and UserTracking applications, must be started from the main CWSI Campus interface, which is started from HP-UX as part of the normal start-up procedures for CWSI Campus.

CiscoView is a device-focused application and is easily started from HP-OV based upon the device discovery process within HP-OV. The additional CWSI Campus functions require more detailed network-wide topology data than HP-OV can provide. The CWSI Campus discovery and database services must be running for these additional applications to function. Therefore, you must start these services from the CWSI Campus Network Map window.

Browser Support for CWSI Campus Online Help

If you decide to use Netscape as your browser, and it has not already been installed, you can install it at any time. Starting CWSI Campus Help does not provide the interaction for you to view and accept the Netscape licensing information. You must start Netscape at least once before starting CWSI Campus help so that you can accept the Netscape licensing information. If you do not start Netscape before starting CWSI Campus help, CWSI Campus help will not start.

Online Help

To run CWSI Campus redirected to another system (setting $DISPLAY to redirect the output to a different system) and have online help available, you must install the help files on each system where CWSI Campus will be used. [CSCdk49311]

CWSI Campus Error Messages

Some of the error messages do not have online help. The Help button on the error message window is unavailable (grayed-out).

CWSI Campus Network Map

This section describes new features and provides important notes and caveats for the CWSI Campus network map.

The ANI server might become inaccessible when discovering a large network resulting from a lack of heap memory. You can modify the last line in CSCOcwsi/bin/cwsi script and change the javaVM option -mx to a larger number.

ANI Becomes Inaccessible After Learning Large Number of Devices

If you are running CWSI Campus topology for more than one day, ANI becomes inaccessible after learning a large number of devices.

The workaround is to change the kernel parameter maxdsiz to a high value (preferably 256 MB), then reboot the machine. [CSCdk92025]

New Features for CWSI Campus Network Map

CWSI Campus Network Map provides the following new features:

• Support for the Netflow Feature Card (NFFC) on Catalyst 5000 switches. The CWSI Campus Network map shows the NFFC on Catalyst 5000 switches. The attributes report also has new fields that describe this card.

• Display of Multi-Layer Switches (MLS) and components (Switch Engines and Route Processors) with the ability to highlight logical relationships between devices such as flow masks and shortcuts.

• Topology discovery and display for Catalyst 8510 switches.

Unable to Open CWSI Campus in HP-UX 11.0

CWSI dumps core on HP-UX 11.0 when invoked on Solaris-CDE when using specific font settings.

The workaround is to run xrdb -merge <CWSIROOT>/etc/cwsi/hpfonts.properties. [CSCdk59880]

CWSI Campus 2.2 Topology Does Not Show Device Icons

CWSI Campus 2.2 topology does not show device icons on the CWSI Campus Network map when CWSI is being run on a remote console. This condition occurs only with remote Solaris and HP desktop console displays.

The workaround is to change the device icons in Options > Properties > Map Dialog to Vector instead of Bitmap. [CSCdk56686]

Important Notes and Caveats for CWSI Campus Network Map

Right Click on the Device in Topology Displays Blank in HP-VUE

On the CWSI Campus network map, popup menus are displayed as the result of right-clicking the mouse on a device icon or link or on the map itself. The menu items in these popup menus are displayed as blank on HP-VUE Display.

The workaround is to change the CWSI Campus topology map background color to any color other than white using Options > Properties > Map Dialog. [CSCdk60057]

The workaround is to resize the window to display the topology map. [CSCdk65353]

Not all modules are shown in the Node Attributes window. You can access the Node Attributes window by selecting the device and clicking the right mouse button. [CSCdj40028] [CSCdj40030]

• On Catalyst 3000 switches, LANE client (LEC) and LANE server/Broadcast and Unknown server (LES/BUS) components that do not bind with VLANs will not be discovered by CWSI Campus. As a result, ATM VLANs consisting of these LANE components will not be discovered. [CSCdj28689] [CSCdj06709]

• Because of the agent inconsistency (lecsLesConfigTable MIB walk skips LES instances) that exists in Cisco IOS Release 11.1(X) and Catalyst 5000 ATM image 3.2(4) (and earlier), CWSI Campus is not able to discover some emulated LANs (ELANs). This inconsistency has been resolved in Cisco IOS Release 11.2 and Catalyst 5000 ATM image 3.2(5). [CSCdj24857]

• If a Catalyst 5000 switch appears as an ATM cloud on the CWSI Campus Network map, ensure that the switch has sufficient memory. The Catalyst 5000 switch includes 16 MB of memory; however this might be insufficient, depending on the number of protocols the switch is running. Insufficient memory might prevent the supervisor agent and the LANE card from being connected. Without the connection, the ifEntries related to the LANE card will be missing from the ifTable and the device will show up as an ATM cloud on the topology.

"Error accessing agent domain rmon while retrieving ETSTATS error: entry or group not present in agent"
 

"invalid command name "Sess0"
"bad window path name ".en"
 

The workaround is to acknowledge these error messages by clicking the OK button. No functionality is affected. [CSCdk29907]

The discovery process is unable to discover Catalyst 5505 switches with OC-12 dual port modules running release 4.12. This problem also occurs with the release that supports MPOA. [CSCdk23407]

VlanDirector

New Features for VlanDirector

• Support for Token Ring VLANs on Catalyst 3900 and Catalyst 3920 switches

• VLAN configuration and display for Catalyst 1912 and 1924 switches

Important Notes and Caveats for VlanDirector

• The topology map and Vlan Director windows hang when you try to create a VLAN when running CWSI in the background.

The workaround is to run the stty -tostop command in the shell where you started CWSI. [CSCdk79031]

The workaround is to stop the server using the stopcwsiserver command, then start it again using the startcwsiserver command. [CSCdj59620]

The workaround is to create only one configuration server at a time. [CSCdj63616]

Failed to assign auto ATM address of LE config server on port <port name> of device <ip Address>. <snmp error message: COM.cisco.nm.mojo.comm.snmp.SnmpValueException: SnmpResponseBadValue
on <ipAddress> > 
 

The following are possible causes:

• Wrong community strings

• Wrong device image

• Command already exists in the running configuration file of the LANE module (lane config auto-config-atm-address or lane config config-atm-address)

The workaround is to remove the line from the configuration file and remove the database association from the particular interface (remove the line that says "lane config database xxx") and try again. [CSCdk31419]

The workaround is to enter the clear config all command on the device to return the device to its working state. [CSCdk27572]

• Deleting a backup LES deletes ATM-VLAN. The workaround is to rediscover the network after deleting the LE server. This should discover the ELAN again (provided the master LES is operational). [CSCdk32280]

• Deleting the master LECS results in deleting all ATM-VLANs from CWSI Campus.

The workaround is to ensure that there is a backup LECS before deleting the master LECS. The backup LECS will become the master. After rediscovery, all ATM-VLANs are found and displayed. [CSCdk32372]

• Selecting Map Highlighting > VTP Trunks from the CWSI Campus Network Map might not reflect the actual trunking links. To see the actual trunking links, select View > Refresh Map, then click on the VTP Trunks. [CSCdk31351]

UserTracking

New Features in UserTracking

• Discovery and display of Token Ring NIC addresses in the table.

• Replicating cells. You can replicate a single cell in a single column into one or more contiguous cells adjoining the cell being replicated. You might use this feature to replicate the VTP Domain name or VLAN name into one or more cells. When replicating cells, note the following:

  • You can replicate cells only in columns where cells can be edited. To select the cells to replicate, highlight the desired cells by pressing the left mouse button while dragging the cursor in the column over the cells you want to replicate. You can also make an initial selection of the cells you want to replicate and then while holding down the Shift key, single click the furthest cell into which you want to replicate. To replicate the cell, select Edit > Replicate.

  • You can replicate cells only in one column at a time. The UserTracking application reports an error if you have cells in more than one column selected when you select Replicate.

  • You can replicate cells only in columns that can be edited, such as Mac Address, VLAN, VTP Domain, User Name, Notes, and Port State. The source value is written only into cells in rows whose VLAN type is Ethernet. If you replicate cells in the VTP Domain column, the UserTracking application sets the cells in the corresponding VLAN column to blanks. When the UserTracking application completes the replication, you must set the VLAN names for those cells. You can set the names by doing another replication. When you replicate in the VLAN column, UserTracking does not ensure that the VLAN being stored is a VLAN in the VTP domain for that row.

• Support for Token-Ring networks. The UserTracking application provides the capability to locate end-users on Token-Ring networks.

• Three new columns (VLAN Type, Ring, and trBRF VLAN) have been added to the UserTracking screen display.

Important Notes and Caveats for UserTracking

UserTracking Table

• In some cases when you delete rows in the UserTracking application, the application terminates with a thread dump. There is currently no workaround. You must restart the UserTracking application. (When this occurs, the CWSI client is not affected, even if you started the UserTracking client from CWSI.) [CSCdk41893]

• In some cases when you click on a cell in the VLAN, VTP Domain, or Port State columns in UserTracking, the UserTracking client might become inaccessible. You must terminate the UserTracking client and restart it. [CSCdk42144]

• If you change the IP address of a TFTP server in a VMPS server's environment (through CiscoView or through the CLI), UserTracking discovers the new IP address of the TFTP server (as part of the next ANI discovery), but UserTracking does not delete the old entry. Subsequent downloads of the TFTP file for that VTP domain from UserTracking will download to the old TFTP server, as well as to the new one. [CSCdk35147]

• If you change the IP address of a TFTP server in a VMPS server's environment (through CiscoView or through the CLI) to an unreachable destination might cause the UserTracking client to hang for an extended period of time. [CSCdk30396]

• In the TFTP Configuration window, do not modify the entry that specifies the VTP domain serviced by this VMPS server (vmps domain DomainName). If you change this line, the VMPS server might no longer be recognized by UserTracking.

TrafficDirector

New Features

Release 5.5.1 includes major new features and enhancements described in the following sections:

• New Standards Supported

• New Monitoring Applications

• Trend Reporting Enhancements

• Monitoring Enhancements

• Configuration Enhancements

• Monitoring Application Enhancements

New Standards Supported

To support the widest range of topologies and standards possible, Release 5.5.1 provides a variety of features for the new MIB definitions and other important standards, as follows:

• ATM RMON MIB---This release fully supports the ATM RMON MIB as implemented in Cisco ATM SwitchProbe devices. You can collect native ATM statistics for specific port groups.

• Switch Monitoring (SMON) standard---This release supports the emerging SMON standard (RMON MIB extensions for switched networks) so you can view switch traffic by VLANs or priorities as discovered by an agent or switches that embed SMON reporting. Both ISL and Token Ring-ISL protocols and the 802.1Q standard (Ethernet Tag---ETPID without RIF support) are supported to monitor communications between switches. Snap tag and Null tagging under the 802.1Q standard are not supported.

• Application Response Time (ART) MIB---This release introduces extensions to RMON to track application response time for the ART MIB. You can examine statistics for application retries, traffic load, and response time to receive an up-to-date picture of application load on the network.

• High-Capacity RMON (HCRMON)---To provide added support for data captured from high-speed SwitchProbe devices, applications can now graphically display 64-bit counters as implemented in the HCRMON draft standard. This reduces the chance for losing data if a counter wraps between polling intervals. The overall polling frequency is also minimized.

• Extensions for RMON2 groups---All RMON2 groups (including User History, Probe Config, and TopN Conversations) are fully supported on selected SwitchProbe devices. Third-party applications can also use the Probe Config features for help with configuration.

• Extended NetFlow Support---Up to eight Cisco routers or interfaces on multi-interface routers can be accommodated on Fast Ethernet SwitchProbe devices to track router statistics using NetFlow conventions (in addition to the single aggregate NetFlow interface). The device can receive IP address and interface port number group information when the NetFlow option is enabled on the device and configured in the hardware.

• SNMPv2 Bulk Retrieval---Third-party applications can now take advantage of improved performance when using SNMPv2 messaging for communication with a SwitchProbe device. The following applications now display switch ports, hosts, conversations, and logging more quickly:

  • TrafficMonitor

  • Protocol Monitor

  • Application Monitor

  • Protocol Zoom

  • All host- and conversation based applications, domain discovery, and logging daemons.

New Monitoring Applications

Table 15 lists the new monitoring applications that provide support for the extended RMON standard.

Table 15: New Monitoring Applications That Support Extended RMON Standards

This New Application...	Supports
Custom History	RMON2 User History group
ATM Monitor	ATM RMON MIB
ART Monitor	ART MIB
VLAN Monitor	SMON draft standard
TopN Conversations	Viewing of statistics for the most active conversation pairs for a single RMON2 or ATM RMON agent.

Trend Reporting Enhancements

The following usability and functional improvements have been made to the Trend Reporter subsystem:

• GUI enhancements

  • Improved ASCII report viewing

  • Configurable daily reports

  • Easy navigation of multisegment reports

• New reports---The following reports provide reporting capabilities for the new applications and expand features to supply data aggregation and baseline capabilities:

  • Baselines

  • Proxy SNMP

  • Application Response Time

  • TopN AL/NL Hosts and Conversations

  • Network Volume Summary

Monitoring Enhancements

The following new extensions are provided for monitoring switches, Frame Relay agents, and ATM virtual channels (VCs):

• Switch Monitoring---The following enhancements have been made to switch monitoring:

  • Fast EtherChannel/multiport roving.
    Added to Catalyst 5000-series switches, you can view traffic from several ports simultaneously.

  • VLAN interface monitoring.
    With the new VLAN agent options, you can monitor Cisco ISL and 802.1Q VLANs on full-duplex links as though they were individual links.

  • Enhanced switch configuration.
    To ease the switch configuration process, you can create a master switch properties file that you can apply to identical switches. Using the switching file, the TrafficDirector application can automatically assign port files to specific port numbers. You can create port properties files for user, server, and trunk ports, so different properties can be applied per port.

• ATM Monitoring---The following enhancements have been made to ATM monitoring:

  • ATM RMON MIB support.
    Native ATM evaluation can now be achieved in various applications so you can monitor using the ATM NSAP address.

  • ATM data captures.
    Now supports raw mode for examining ATM headers in addition to WAN headers. This feature helps you troubleshoot complex ATM problems at their source.

  • ATM virtual channel as an interface.
    With the new ATM RMON support, you can monitor each VPI/VCI pair from ATM SwitchProbe devices in TrafficDirector applications.

  • Generic domains for LAN Emulation (LANE) types.
    With ATM RMON support, you can monitor by ATM LAN emulation type, including LANE, and Multiprotocol over ATM/Classical IP (MPOA/CIP).

Configuration Enhancements

The following configuration enhancements have been made:

• Autodiscovery of multiport SwitchProbe interfaces---To ease the agent configuration process, the configuration subsystem can extract the names of monitoring interfaces and their topology from the SwitchProbe device automatically.

Monitoring Application Enhancements

Several existing real-time monitoring applications have been improved to increase ease of use and provide extensions for other new features:

• Data Capture---Allows you to save Ethernet, Token Ring, and FDDI packets in Sniffer 5.0 format. You can also filter traffic based on protocol definitions and those filters defined with the Filter Editor.

• New Protocol Decodes---To support a greater number of industry-standard, and most widely used protocols, definitions for the following decodes have been added:

  • HTTP, for greater insight into web traffic.

  • SNMP enhancements to support SNMP v2, extensions for the RMON2 groups, HCRMON, ATM RMON, and SMON.

• Traffic Monitor---Increased ease of use in viewing data can now be achieved through:

  • Paging (with stepping arrows) to show more ports (maximum of 32 simultaneously).

  • Port speed display for 10/100 switches and CIR on DLCIs.

• Alarm Discovery---You can view all currently configured domains and existing alarms in the enhanced Domain/Alarm Discovery application.

Important Notes and Caveats

Interpreting Some Reports

• For some reports, the Utilization% displayed may differ from that shown on Segment Details. [CSCdk57767] [CSCdk55659]

• The Network Analysis Module supports only one roving port; therefore, adding a port to a list of roved ports is not supported.

• When you rove to a different port using the Network Analysis Module, only the replace operation is supported; the Add operation results in an error.

• Running Domain Discovery a switch port, VLAN, or FEC that is roved to a Network Analysis Module results in a error retrieving alarm entries.

• Running Data Capture against a switch port, VLAN, or FEC that is roved to a Network Analysis Module may result in the Running For field showing an incorrect value. [CSCdk87967]

• You must define the analyzer port precisely as listed in the Interface box; otherwise, roving will fail.

• Starting All Conversations against a NetFlow interface might result in the Destination Host Name being displayed incorrectly. [CSCdk62230]

• The multiport roving feature on the Network Analysis Module is not supported Network Analysis Modules running Release 4.3(1a) and higher.

• You can enable and install logging for ports that are roved to the Network Analysis Module. However, the logging daemons are not started, and therefore no actual data is logged to the database. Generating a report against this data results in an error stating that there is no data available for that report. [CSCdk84504]

• The TrafficDirector application roves to the specified port when you select Data Capture from the main TrafficDirector screen. For other applications such as All Talkers, you must perform roving manually from Configuration Manager or start the application from Traffic Monitor. [CSCdj62108]

• Before roving multiple ports, verify that the ports are all in the same VLAN and that one of the ports is not a trunk port. [CSCdk49058]

• If any changes are made to the SPAN port or the analyzer port without using TrafficDirector (for example, using the switch command-line interface), the TrafficDirector application will not reflect these changes. [CSCdk44815]

• An error message is displayed when you attempt to rove a port or a group of ports that contains a port that has already been roved. [CSCdk60830]

• To apply a new properties file to a roved port, you must click Rove OFF before you can perform a rove operation to the same port again.

• TopN Conversations is not supported for the ALLAL and ALLNL domains.

• Disabling the host-conv-getbulk option in the default.dvp configuration file results in duplicate entries appearing in the ATALK All Talkers display. [CSCdj89834]

• Logging information cannot be generated for more than 100 DLCIs. [CSCdk26525]

• VLANs are only learned on Catalyst 5000-series devices. [CSCdk29981]

• To log data and run Trend Reports on an individual VLAN, you must enable logging on the specific interface for that VLAN.

• The RMON II probeConfig group is supported only on a limited number of SwitchProbe devices. [CSCdk47296]

• The maximum number of History buckets supported on a Catalyst 1900 series or Catalyst 2820 series device running release 8.X is 20.

• You cannot rove a VLAN using the Network Analysis Module and run a mini-RMON application (such as Traffic Monitor, Short- and Long-Term History, Segment Details, Segment Zoom, and so on) against a roved VLAN with the Network Analysis Module.

• On the Catalyst 19xx and 28xx families of switches, the TrafficDirector IP address or host name must be defined as one of the four WRITE Managers in the Network Management (SNMP) Configuration. If it is not defined, write operations to the switch will fail.

• The TrafficDirector application does not recognize gigabit modules in the Catalyst 8510 switch.

• When running Segment Details against an ATM SwitchProbe device, the total cell count might be incorrect. Rollovers of the counter are not included. [CSCdk41385]

• The View > Show MAC option for All Talkers and All Conversations does not map the network address as required. [CSCdk45224]

• In the Add Agent window, if you select View, the managed interface of the SwitchProbe device is displayed. You must deselect this agent before saving any of the entries as agents. [CSCdk40368]

• Running the All Talkers application for the ATALK domain may result in duplicate entries being displayed. [CSCdj89834]

• Shutting down the TrafficDirector application does not always shut down all of the daemons. [CSCdk50319]

Documentation Updates

The following updates apply to the Using the Campus TrafficDirector Application publication.

Chapter 6---Working with Properties

The following information was inadvertently omitted from the sections "Enabling Domains for Monitoring" on page 6-8, and "Defining Individual Properties" on page 6-23:

If, when adding or editing a domain in a properties file with Property Editor, you cannot see all domains defined in that properties file, follow these steps:

Step 1 Shut down the TrafficDirector application.

Step 2 Restart the TrafficDirector application.

Step 3 Restart Property Editor.

You will then be able to see all domains in the properties file.

Chapter 19---Displaying History Information

The following information was inadvertently omitted from the subsection "Creating .udh Files" on page 19-15, Step 4:

To identify the OID string, refer to the appropriate MIB docuemnt or a MIB browser that shows both the OID name and value.

For example, to indicate ifInOctets, you would specify 1.3.6.1.2.1.2.2.1.10.

To identify which variable instance to use, you must specify the interface on the SwitchProbe device for which you want to track the OID you specified. You can identify this using either the IFINDEX, DLCI #, or CONTROL INDEX of that interface.

For example, to track ifInOctets for interface 3, you would specify 1.3.6.1.2.1.2.2.1.10@IFN.3; to track ifInOctets for DLCI 57, you would specify 1.3.6.1.2.1.2.2.1.10@DLCI.57.

Appendix A---Troubleshooting

The following note was inadvertently omitted from the section "Testing Agents, Switches, and Frame Relay Agents" on page A-4:

Appendix F---Integrating the TrafficDirector Application with Other Managers

The HP OpenView-related information in the subsection, "Integrating with HP OpenView or IBM NetView/6000," should be replaced with the information in this section:

Integrating with HP OpenView

[CSCdk53964]

AtmDirector

New Features for AtmDirector

• ATM-RMON feature in fabric and ATM-VLAN maps is now available.

• Discovery and display of unknown UNI devices.

• Enhancement to SPVC-provisioning capability.

• Tooltip support in AtmDirector maps.

Important Notes and Caveats for AtmDirector

Main Window

While editing the fabric name on the tree structure in the main window, the old name is not completely cleared from the display when the new name is being entered. The new name is displayed clearly after you press Return.

Online Help

If you launch and close the Netscape browser many times, sometimes AtmDirector help cannot be launched. If this occurs, close Netscape (and AtmDirector if necessary) and wait for few seconds, then try again.

ATM Fabric Map

The following caveats apply to the ATM fabric map:

• During SPVP/SPVC setup using Advanced Parameters, selecting an incorrectly configured ABR table displays the following message:

Traffic Type not understood 
 

The workaround is to add a new row for the ABR traffic with the appropriate traffic parameters and apply it towards the SPVP/SPVC setup.

• If AtmDirector displays unknown devices that are no longer present in the network, complete the following steps to remove them from the map.

  (a) Reset the interface on the LS1010 switch to which the unknown device is connected. This will clear the unknown device entry in the CISCO-ATM-ADDR-REG table.

  (b) Delete the link between the LS1010 switch and the unknown device, after it appears as a broken line on the ATM fabric map. The unknown device is deleted from the ATM fabric map after the link is deleted.

• AtmDirector might display more than one fabric (for one single physical ATM fabric) in cases where 1483 encapsulation is being used. [CSCdj67021]

ORB DB Error. 
 

[CSCdk28870]

• After deleting and adding the PNNI summary address, you must exit from the AtmDirector application for those addresses to be updated on the database on the client.

• On the PNNI topology map, sometimes there are no links displayed between the PNNI nodes. This situation was introduced in the LS1010 release 11.2(8)WA03(03). The fix will be included in the next LS1010 maintenance release. [CSCdk47194]

CiscoView

New Features in CiscoView

• Expanded community string management and functionality.

  • You can more conveniently manage all your devices' community strings: You can enter, modify, or delete community strings for all your devices before you manage any of the devices.

  • You can optionally save defined community strings for future CiscoView sessions.

  • You can specify community strings for submodule hosts (for example, for a board within a router).

  • If you attempt to access a submodule device when its community string is not defined, CiscoView uses the parent device's community string instead (if known). If the parent's community string is not known or does not work, CiscoView uses the default community strings, "public" and "private." If these strings fail, you are prompted to enter the correct strings.

  • If you attempt to access any device when its community string is not defined, CiscoView uses the default community strings "public" and "private" instead. If the default strings fail, you are prompted to enter the correct strings.

• Full support for 64-bit counters. If you are running CiscoView over an NMS, contact your NMS vendor to determine if your NMS also supports 64-bit counters.

• User preferences (as defined in the Options > Properties dialog) saved across CiscoView sessions.

• The CVSecurity patch (previously released as a PSMU for CiscoView 4.0) fully integrated into CiscoView. Now you can easily install CVSecurity as part of the CiscoView installation.

CVSecurity takes effect only when CiscoView and CiscoWorks are installed on the same UNIX machine. (CVSecurity is not available for PC platforms.) When installing CiscoView on a UNIX machine, if CiscoWorks is already present, you are prompted to specify whether or not to install CVSecurity.

CVSecurity allows you to restrict CiscoView functionality for specified groups of users. When you attempt to launch CiscoView from CiscoWorks, you must enter a username/password, which determines your level of CiscoView access. There are three levels of access:

• You cannot launch CiscoView.

• You can launch CiscoView and use it to view device configuration and to monitor devices, but cannot use CiscoView to configure any device.

• You have full CiscoView privileges---you can launch CiscoView and use it to both monitor and configure devices.

• Support for the following upgrade paths:

  • Upgrade from CiscoView 3.2, 4.0, and 4.1

  • Coexistence with CiscoWorks 3.2 and 4.0

  • Upgrade CiscoView within CiscoWorks for Switched Internetworks 1.3 (CWSI 1.3)

• Support of HP OpenView 4.11, 5.0, and 5.01

• Availability of CiscoView as part of the WAN Manager 9.1 (formerly StrataView+) bill of materials. WAN Manager 9.1 launches CiscoView as a device management application for the BPX/IGX/MGX devices.

Because WAN Manager currently runs with HP OpenView on the Sun/Solaris, the BPX, IGX, and MGX (formerly AXIS) package files have been tested only on these platforms. Refer to the BPX, IGX, or MGX device package release notes for the most current information on the operating system versions supported, as versions will vary from release to release.

For additional information about WAN Manager platform availability and support, see the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/ and click the "What's Hot for CiscoView and CiscoWorks Windows" link.

• Support for the devices listed in Table 16.

Table 16: Supported Devices

Small to Medium Business Products	Mid-Range Enterprise Products1	High-End Enterprise Products
Cisco 761, 762, 765, 766, 771, 772, 775, 776	Catalyst switch models2 1200, 1400, 1600, 1601, 1700, 1800, 1900, 2100, 2600, 2800, 2820, 2900, 2900XL, 2926, 3000, 3100, 3200, 3900, 5002, and CPW2200	Catalyst 5000, 5500, 5505, and 5509; and 8510
Cisco 1003, 1004, and 1005	EtherSwitch Pro16, EPS2015, 1200, 1220, 1400, 1420	Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers
Cisco 1601, 1602, 1603, 1604, 1605	EtherSwitches: Pro16 and CPW16	LS1010
Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525	Workgroup concentrators 1400
Cisco 3600 series (includes 3620 and 3640) and 3800 series	Fasthub 216T
Cisco 4000 series3 (includes 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M)		Cisco uBR7246 and uBR904
AS5200 Access Server	AS2509-RJ AS2511-RJ	AS5300 Access Server AS5800 Access Server
Cisco 1501, 1502, 1503, 1516
Fasthub 300 and Fasthub 100+ Series
EPS-500, EPS-1500, EPS2115, CPW-500, CPW-2115, and CPW-16
MWEB200

1Adapters WA-C301TA, WA-C303TA, WA-C308TA, WA-C306TA, WA-C321T-PC, WA-C321T-UX, WA-C323T-PC, WA-C323T-UX, WA-C326T-PC, WAC326T-UX, WA-C328T-PC, WA-C328T-UX are no longer supported. 2Catalyst 1000 and 1100 are no longer supported. 3Due to a fix made for the BRI port problem, the Cisco 4000 series devices now support Cisco IOS 10.3 or later.

Support for other applications are listed in Table 17.

• The CiscoView devices packages included in this release are shown in Table 18.

Note that there are additional device packages not included on the CiscoView CD-ROM, but which are available for download from CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/.

In particular, device packages for the multi-service switching devices BPX 8600, IGX 8400, and MGX 8220 (formerly AXIS) are available only from CCO.

Refer to the package readme files for details on the supported versions. Readme files are available at the same location on CCO as the device packages. For more information about selecting and downloading device packages, see the section "Incrementally Installing Device Packages."

.
Table 18: CiscoView Device Packages

Device Package	Version
1000.pkg	4.0(1.2)
1500.pkg	4.0(1.2)
1600.pkg	4.0(5.0)
2500.pkg	4.0(4.0)
2600.pkg	4.0(3.0)
3600.pkg	4.0(11.0)
3800.pkg	4.0(1.02)
4000.pkg	4.0(3.1)
700.pkg	4.0(1.4)
7000.pkg	4.0(5.0)
AS5200.pkg	4.0(5.0)
AS5300.pkg	4.0(3.1)
AS5800.pkg	4.1(2.0)
CPW10_100.pkg	4.0(1.4)
CPW1200.pkg	4.0(1.4)
CPW1220.pkg	4.0(1.5)
CPW1400.pkg	4.0(1.4)
CPW1420.pkg	4.0(1.5)
CPW16.pkg	4.0(1.1)
CPW2115.pkg	4.0(1.1)
CPW2200.pkg	4.0(2.1)
CPW316.pkg	4.0(1.4)
CPW500.pkg	4.0(1.1)
Cat116.pkg	4.0(1.4)
Cat1200.pkg	4.0(1.4)
Cat1600.pkg	4.0(1.3)
Cat1700.pkg	4.0(1.4)
Cat1800.pkg	4.0(1.1)
Cat1900.pkg	4.0(2.0)
Cat2100.pkg	4.0(1.4)
Cat216.pkg	4.0(1.4)
Cat2600.pkg	4.0(1.3)
Cat2800.pkg	4.0(1.4)
Cat2820.pkg	4.0(2.1)
Cat2900.pkg	4.0(2.1)
Cat2900XL.pkg	4.0(2.0)
Cat3000.pkg	4.0(1.6)
Cat3900.pkg	4.0(1.5)
Cat5000.pkg	4.1(2.6)
Cat5500.pkg	4.1(2.6)
Cat8510.pkg	4.1(1.1)
Cisco1516.pkg	4.0(1.2)
EPS2015.pkg	4.0(1.1)
LS1010.pkg	4.0(2.3)
MWEB200.pkg	4.0(1.1)
ubr7200.pkg	4.0(1.1)
ubr900.pkg	4.0(1.0)
TD_INTG.pkg	4.1(1.6)
TN3270/TN3270_AIX.pkg	4.1(1.2)
TN3270/TN3270_HPUX.pkg	4.1(1.2)
TN3270/TN3270_SOL.pkg	4.1(1.2)
WG_Concentrator.pkg	4.0(1.3)
stackmkr.pkg	4.0(1.1)
Threshold_AIX.pkg	4.0(1.1.3)
Threshold_HP10.pkg	4.0(1.1.3)
Threshold_WIN.pkg	4.0(1.1.3)
Threshold_SOL.pkg	4.0(1.1.3)

Cisco IOS Information

This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing.

CiscoView supports Cisco IOS software Releases 10.0 through 11.3. Note the following restrictions:

• Access servers require a minimum of Cisco IOS software Release 10.2.

• Cisco 3600 devices require Cisco IOS software Release 11.1 or later.

• Cisco 4000 series devices require Cisco IOS software Release 10.3 or later.

• Cisco AS5800 devices require Cisco IOS software Release 11.3(3)AA.

• Cisco uBR7246 devices require Cisco IOS software Release 11.3(2)XA.

• Not all device packages support all Cisco IOS versions. If you are uncertain which Cisco IOS version is supported, you can check your device package readme file.

New devices and further specifics on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:

• Cisco Connection Online (CCO) in the Cisco Connection Documentation section (continually updated)

• Cisco Connection Documentation, Enterprise Series CD (formerly called UniverCD)

Incrementally Installing Device Packages

There are several ways to add (or incrementally install) support for new devices to CiscoView 4.2(1). Direct customers should refer to the section "Cisco Connection Online" at the end of this release note for information about accessing CCO. Partner-initiated customers should refer to the section "Partner Initiated Customer Accounts."

Downloading Device Packages from CCO

You can add new devices to CiscoView from the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/. On this page, go to the section "Download CiscoView Software Updates" and click "CiscoView 4.x Packages." From the "CiscoView 4.x Packages" page, you can download packages for all supported devices. For more information, refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView. A quick reference version exists in the CiscoView CD Installation Instructions booklet.

Determining Which Package to Download

In general, multiple devices within the same product family share a single device package. If you have a specific device in mind, look for the device package for the device's family.

To determine if your particular device is supported, look at the readme for the device package (available on the same webpage listed in the previous section).

Partner Initiated Customer Accounts

http://www.cisco.com/acs/info/pica.html

You can also refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView.

Caveats Fixed in This Release

Table 19 lists caveats in CiscoView 4.1(1) that are fixed in CiscoView 4.2(1). Only the most serious caveats resolved in CiscoView 4.2(1) are listed.

Applet and device package caveats that have been fixed since the previous release are described in the respective applet and device package readme files. These readme files are available from the CiscoView Upgrade Planner:

http://www.cisco.com/kobayashi/library/netmanage/cview

Table 19: Caveats Fixed in CiscoView 4.2(1)

CSCdi51665	Users preferences such as timeout are not persistent across CiscoView sessions.
CSCdi62739	When saving new policies for a host, they will not match if IP is in use.
CSCdj38584	Sometimes CiscoView cannot be configured due to missing fonts.
CSCdj39055	CiscoView does not support workgroup concentrator WS-X1434.
CSCdj43438	CiscoView does not properly convert the Timeticks SYNTAX.
CSCdj50382	A wrong instance might be used for subclass discovery.
CSCdj58682	Running CiscoView dumps core when a device package is incrementally installed.
CSCdj59472	Newly created rows might not be added to table.
CSCdj60605	CiscoView might fail to open a device if both the Catalyst 5000 and Yosemite card are set to the same community strings.
CSCdj61077	CiscoView package for the Cisco 7000 has typo for feip-f.
CSCdj64545	TCL script interprets address as exponent ex. 1e550.
CSCdj68522	CiscoView port monitor default polling fails.
CSCdj72051	CiscoView is not unable to work with AS5300.
CSCdj75454	Cisco 7000 package corrupts the Memory Used graph.
CSCdj75485	Need enhancement in engine for StackView support for AS5300.
CSCdj90331	CV4.1(1) integration with HPOV/SNM fails.
CSCdj92755	CiscoView crashes when going to PVC Configuration menu.
CSCdk03414	Catalyst 5000 always uses default 6 sec snmp timeouts.
CSCdk03853	MIB files for the imported module SNMPV2-SMI are missing.
CSCdk05042	CiscoView installation may fail if $OV_BIN env. var. is defined on AI.
CSCdk05800	Change in the Wr.Com.Str When Opening a device does not change Op.
CSCdk05801	CV security patch is not invoked in AI.
CSCdk10541	Default telephone text box accepting junk values.
CSCdk11370	Cancel option adds entries in phone book.

Troubleshooting

If you cannot open a device in CiscoView 4.2(1), a message appears indicating that the device is unmanageable for one of the following reasons:

• The Simple Network Management Protocol (SNMP) agent is not running in the device.

You can still ping the device from the management station.

• You have entered an incorrect community string in the File > Open Device window.

• The management station cannot access or successfully ping the device. This could be caused because the request timed out or because there was a noSuchName condition.

If the request timed out, you can try increasing the timeout period, verifying the write community string, or checking that the device is reachable.

If there was a noSuchName condition, verify the write community string.

• You are missing the device package.

If you try to access a device when the device package is not installed in CiscoView, CiscoView displays the following error message:

CiscoView is unable to open devicename because you do not have the appropriate device package installed on your machine. You can download the latest device package from the CiscoView Upgrade Planner:

http://www.cisco.com/kobayashi/library/netmanage/cview

If you receive this error message, you should access the specified URL, and download and install the correct device package.

• You have an obsolete version of a device package.

Check your device package and compare the date with the version on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview. Upgrade your device package to the latest version, if required.

Installation Notes and Caveats

  line 46: syntax error
  line 49: syntax error
  failed in loading /opt/SUNWconn/snm/struct/Cat3900.schema
 

The workaround is to manually remove the referenced Cat3900.schema file. [CSCdk12506]

General Notes and Caveats

This section contains general notes and caveats. They are divided into five sections:

• Notes and Caveats for Enterprise Network Management Products

• Notes and Caveats for Workgroup Products

• Notes and Caveats for Access Products

• Notes and Caveats for High-End Business Products

• Notes and Caveats for WanBU/NSMBU Devices

• Notes and Caveats for Online Help

Notes and Caveats for Enterprise Network Management Products

• Dragging Ports. On UNIX platforms, for this release, use the middle mouse button to drag. Only certain devices (such as the CAT1200, CAT1600, CAT5000, CPW16) have defined their ports for dragging across devices.

• Erroneous Command Windows. When CiscoView is invoked from an NNM, whenever you open a device, one or more command windows momentarily pop up then disappear. [CSCdk14010]

• MGX (Formerly AXIS) Errors. When CiscoView is using an AXIS device package, if the AXIS agent cannot process packets sent by CiscoView (generating tooBig errors), CiscoView core dumps. [CSCdk24025]

• HP OpenView. If a switch is configured as two or more domains, HP OpenView discovery might not work properly and might discover only one of the domains. If this occurs, use CiscoView to manage the domain directly rather than launching the switch from the map.

With HP OpenView, the grapher does not graph with v2c agents, especially 64-bit counters values. The HP OpenView bug ID is 4701401398. To work around this problem, use the Data Collector to collect and to then graph the desired data. [CSCdk08824]

• Open Look. Popup menus might be out of focus. To correct the focus, move your pointer out of the window and back into the menu.

• Printing to LaserJet III. CiscoView might fail to print to a LaserJet III printer, especially in the "LaserJet" format, because of this printer's limited memory.

• StackMaker.

  • Internal Debugging---When the StackMaker Debug option is set to On, debug messages print to the StackMaker Debug Log file. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is /tmp/.smDebugLog.

  • Internal Debugging---When the StackMaker Debug SNMP option is set to On, SNMP debug messages print to the StackMaker Debug Log file on the UNIX platform. The messages show the SNMP packets that have been sent and received. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is /tmp/.smDebugLog.

  • Log File from Apply Operations---The StackMaker log file stores the results of a saved stack configuration (Actions > Apply Stack Configuration). The log file is /tmp/stackmkr/sm.log. When the log file exceeds 1 MB, it automatically resets to 0 bytes.

  When StackMaker runs on Catalyst 1900 devices, some debug output is printed to the console. Ignore this output.
  

  StackMaker does not work with devices that have different community strings. (By default, stacked devices use the same community strings.) [CSCdj00349]
  

  You might get error messages when invoking StackView for a device, particularly if you just changed the "seed" device or if you previously opened and closed the stack. If you get error messages when invoking StackView, exit the current CiscoView session and launch a new CiscoView session. [CSCdk12100]
  

• Threshold Manager. Some agents, most notably the Catalyst switches, impose a limit on the number of alarm and event entries that can be created. Applying a large number of thresholds to these devices will likely fail. In this case, some alarm entries might be successfully created but their associated event entries are not.

Notes and Caveats for Workgroup Products

• Catalyst 1700. Version 4.0(1.4) of the Cat1700.pkg device package does not work properly if either of the following device packages are installed: Cat1900.pkg, Version 4.0(2.0); or Cat2820.pkg, Version 4.0(2.1). [CSCdk48245]

• Catalyst 1800. The device agent does not update the IP address table of MIB-II properly and does not reflect the correct IP address information of all the device interfaces. You cannot view the correct IP address information of the device by selecting Device > Configure > IP Address Table.

CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820---The General Bridge window shows the bridge information for VLAN1 only. Bridge information for other VLANs is not available.

CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820---The Spanning Tree Protocol Window for switched ports is available for ports in VLAN1 only. This window does not show valid information for ports that are not in VLAN1.

VLAN colors are not displayed in CiscoView for a Catalyst 1900 when a VLAN is highlighted in VLAN Director. [CSCdk40128]

• Catalyst 1924. If you launch a Catalyst 1924 with Firmware V8.00.04(03), you cannot access the Port Zoom or Switch Zoom applications from Rmon Options. [CSCdk24862]

• CPW 1420 and Catalyst 2820. On the front panel display of the device, the Connect and Disabled LEDs on FDDI modules do not reflect the appropriate status.

The Configure > Module option is supported only for one module type, even though it can be invoked for multiple module types.

There is a dependency between the CPW1420 and Catalyst 2820. The CPW1420 device package will not run unless the Catalyst 2820 package is installed. [CSCdj64496]

• Catalyst 1900, Catalyst 2820, CPW 1220, and CPW 1420.To delete an entry from the Set Managers configuration, enter an IP address of 0.0.0.0. The agent on the devices do not accept a blank entry for an IP address. [CSCdj03444]

• Catalyst 116 and CPW 316. To delete an entry from the Set Managers configuration, enter a blank field. The IP address of 0.0.0.0 does not remove the entry from the Set Manager Table.

• Catalyst 2600. The Catalyst 2600 device package contains two versions of the Enterprise MIBs for the Catalyst 2600 switch:

  • C2600_cisco.my---This MIB file is installed to support devices with image versions prior to 2.2.1.

  • C2600.my ---This MIB file is installed to support devices with image version 2.2.1 or later.

• Catalyst 2900XL. CiscoView is missing the Rmon Option menu for the Catalyst 2900XL, so there is no access to Traffic Director, Switch Zoom, Port Zoom. [CSCdk15743]

• Catalyst 3000 Series. When you access a stack with six or more devices, there might be some significant performance problems. You can improve performance by increasing the SNMP timeout settings.

The workaround is to run xnmsmpconf and set the global default "set" value to "private." [CSCdk14013]

When a Catalyst 5000 is open in CiscoView, if you change the community strings, the changes will become the default community strings used by CiscoView for devices with unknown community strings.

The workaround is to close and reopen CiscoView, then change the default community strings by selecting Options > Properties from the menu. [CSCdk14111]

ATM, FDDI, and CDDI do not support Broadcast Suppression.

Do not use the Grapher in the CiscoView Monitor 10BaseT Group Switching Ethernet window. Use the Monitor or TrafficDirector tools (if TrafficDirector is installed) to see graphical views of the selected repeater ports.

When you use the Switch Zoom menu (if TrafficDirector is installed) from CiscoView to view multiple switch ports, the default configuration for the Catalyst 5000 is to configure Statistics only. To see the Short-Term or Long-Term history from Traffic Monitor, use the Domain Manager to configure the Short-Term and Long-Term groups manually or use Segment Zoom to view the port first.

When you use the Segment Zoom menu from CiscoView to view the port segment, the default configuration for the Catalyst 5000 is Statistics, Short-Term history, and Long-Term history.

If you see the message "Error: Entry or Group not present in Agent" when starting Segment Zoom, Switch Zoom, or Data Capture, the write community string may not match the device. If the community string matches but the problem still occurs, use the CiscoView Configure Device menu to see whether the RMON capability is enabled.

When you select the repeater module port on a Catalyst 5000, it always uses the first port of the selected segment to create the RMON agent group.

If all Catalyst 5500 slots are populated with modules and you experience timeouts, increase the SNMP timeout value to 15 seconds.

The WS-X5213 and WS-X5213A modules show the 100 Mbps speed LED lit only if the speed is configured at 100 Mbps and the port is connected.

Opening the FDDI/Ethernet Bridge category under Configure > Device can display an "unknown error." This is because of a problem with the device software.

If a general error (genErr) is displayed when you change vlanPortIslStatus, the selected port might not support ISL.

The values of ifAdminStatus and ifLinkUpDownEnable cannot be changed on an ATM port.

Port duplex settings cannot be changed on ATM and FDDI ports.

The value portSpanTreeFastStart cannot be changed on ATM and FDDI ports.

Configuring ports to unsupported speeds returns a general error (genErr). This is because of a problem in the device software.

If you run CiscoView from CWSI, and CWSI is integrated with SNM 2.3 on Solaris 2.5.1, if you try to disable all ports on different modules at once on a Catalyst 5500, the LANE module resets.

This problem occurs with the ATM LANE module WS-X5158. This problem occurs only on Catalyst 5500s with LECS functions. To avoid this problem, disable ports individually. [CSCdk40179]

• CDP and CGMP Protocols Unsupported. The CPW 1200/1400 and Cat 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these will return errors.

• Community String Mismatching. When you enter values for the read-only, write-only, and read-writeId with the Command Line Interface (CLI) commands, these values must match. A mismatch results in noSuchName or timeout errors. To avoid these error conditions, use identical community strings in CiscoView and corresponding agents.

• Duplicate Categories. When multiple ports of different types are selected,
  Port > Config might show duplicate categories.

• Switch Firmware. Table 20 lists firmware versions that must be used in the switches.

Table 20: Switch Firmware

Switch	Firmware Version
Catalyst 2100 and 2800	3.63 or later
EtherSwitch 1200 and 2800	3.63 or later
EtherSwitch 10/100	1.38 or later
Catalyst 1700	1.38 or later
Grand Junction FastSwitch 10/100	1.37 or later
Grand Junction FastSwitch 2100 and 2800	3.62 or later

Notes and Caveats for Access Products

• Logical View and Channel Modem View Not Available in Stack View. The Logical view and Channel Modem Mapping view are not available for stacked Cisco 3600 series routers. This support is scheduled for a future release. However, Logical View is available on individual or stacked Cisco 3600 routers if a digital modem carrier card and a T1/ E1 card is present.

• With Cisco IOS Versions Below 11.1(7), Table Misses Interfaces. The fix for defect CSCdi69480 (PRI/E1 interfaces missing in cardIfIndex table) is integrated into Cisco IOS Release 011.001(007) and later. The Cisco 3600 4.0(6.1) device package incorporates the fix and may not work properly with Cisco 3600 series routers running Cisco IOS versions below 011.001(007).

• Cisco AS5800 Universal Access Servers

  • Hot swap works inconsistently.

  After the hot swap, the dial shelf physical view alone gets redrawn.
  

  The workaround is to exit CiscoView and re-open the device. [CSCdk11818]
  

  • Cannot monitor PRI channels in AS5800 CE1/CT1 card.

  Monitor of individual channels of trunk ports in CE1/CT1 card is not available. Only the configuration information is displayed. [CSCdk11819]
  

  • Help for compression card is incorrect.

  Incorrect help information displayed for sa-compression card. [CSCdk11820]
  

  • HealthMon Status shows wrong values for ShelfId and ShelfAddress.

  In device configuration dialog of the SC3640, the values displayed for ShelfId and ShelfAddress are wrong. [CSCdk11823]
  

  • Pixel and mask of size 38 is shown bigger.

  The pixel and mask of size 38 is shown bigger for AS5800 and SC3640. The relevant files contain size of 48 pixels for width and height. [CSCdk11854]
  

Notes and Caveats for High-End Business Products

• LightStream1010. To configure an LECS address for LS1010 from CiscoView, ServiceId needs to be the following: 10.1.3.6.1.4.1.353.1.5.1.<Index>, where Index is the row differentiator for configuring multiple LECS addresses. Index is an integer.

• Power Supply Display. By default, CiscoView 3.1(1) displays two power supplies for a Cisco 7000 router running Cisco IOS Release 10.2 and earlier. With Cisco IOS Release 10.3 and later, power supplies are displayed based on ciscoEnvMonSupplyState values.

• Cisco 7000 Series

  • View menu for Cisco 7000 series is inconsistent.

  The view menu for the 7204, 7206 has front view too but all the other 7000 series routers have just the rear view. [CSCdj86030]
  

  • CiscoView with the Cisco 7000 package 4.0(4.0) fails on Token Ring Modules.

  Selecting Category "TokenRing Errors" generates an error: "The MIBs are not supported by the device." However, launching CiscoView 4.0 with 7000 package 4.0(1.0) on the same router it does not generate any errors. [CSCdk13389]
  

  • Mismatch of formula in help for buffer failure in 7000pkg.

  Device monitor shows the wrong help context. [CSCdk08747]
  

  • Ciscoview does not display pa-a8t.

  CV fails to display a 7206 with pa-8b-st, pa-a8t-x21, c7200-io1fe and cpu-7200 cards correctly. [CSCdk03826]
  

  • x25CircuitCalledDteAddress in ascii value.

  The variables x25CircuitCalledDteAddress and 25CircuitCallingDteAddress are displayed in ascii. It is better to show these in numeric form. [CSCdj40816]
  

  • Cisco IOS less than 11.1 cause FSIP dialogs in CV for mip ports.

  An invalid port level FSIP configuration category appears for devices with MIP cards running less than 11.1. The dialog just displays N/A for variables displayed in it as these are not applicable to it. [CSCdj23970]
  

  • Delta values appear as absolute values.

  When using CV to monitor multiple ports, the delta value does not change relative to the 2 polling points, but is simply a dump of the raw SNMP value. [CSCdj93913]
  

• Cisco uBR7200 Series

  • RFC1595-SONET-MIB support:

  The RFC1595-SONET-MIB is not supported in ubr7200 device package version 1.1.
  

  • Downstream Channel MIB Variable Settings:

  The downstream channel frequency (docsIfDownChannelFrequency) setting in the rport configuration dialog box accepts only values between 54 and 1000 Mhz (54,000,000 - 1,000,000,000). The standard MIB range for this variable is 0 to 1000 Mhz (0 - 1,000,000,000).
  

  The downstream channel width (docsIfDownChannelWidth) setting in the report configuration dialog box accepts only a value of 6 Mhz (6,000,000). The standard MIB range for this variable is 0 to 16 Mhz (0 - 16,000,000).
  

  The downstream channel modulation (docsIfDownChannelModulation) setting in the rport configuration dialog box accepts only values of 3 or 4. The standard MIB values for this variable are 1,2,3,4. 1 indicates unknown; 2 indicates other.
  

  The administration status of the channel cannot be changed from the Admin Status field in the rport dialog box.
  

  • Upstream Channel MIB Variable Settings:

  The upstream channel frequency (docsIfUpChannelFrequency) setting in the rport configuration dialog box accepts only values from 5 to 42 Mhz (5,000,000 - 42,000,000) and the value of 0 Mhz. If 0Mhz is specified, the Administration Status automatically changes to down. The standard MIB range for this variable is 0 to 1000 Mhz (0 - 1,000,000,000).
  

  The upstream channel width (docsIfDownChannelWidth) setting in the report configuration dialog box accepts only 1.6 Mhz (1,600,000). The standard MIB range for this variable is 0 to 16 Mhz (0 - 16,000,000).
  

  The administration status of the channel cannot be changed from the Admin Status field in the rport dialog box.
  

  • Fast Serial MIB Variable Display Values:

  The Fast Serial rport configuration dialog box for HSSI interface displays N/A for status of flow control signals (locIfFSIPrts,locIfFSIPcts, locIfFSIPdtr,locIfFSIPdcd,locIfFSIPdsr). The agent returns 0 instead of the acceptable values 1-3. (1 - Not Available, 2- Up, 3-Down).
  

Notes and Caveats for WanBU/NSMBU Devices

WanBU/NSMBU device packages are available to be downloaded from CCO.

If you run CiscoView from HP OpenView and use WAN package files, and you are not using WAN Manager, CiscoView has the following limitations:

• CiscoView will not launch from topology maps or pull-down menus.

• Ciscoview does not support topology discovery with automatic icon identification.

• CiscoView does not support MIB and Trap integration.

These limitations exist because WAN Manager will eventually replace the existing Equipment Manager GUI with CiscoView, and the WAN package files have been designed to integrate with WAN Manager.

For additional information about platform availability and support, see the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/, and click the "What's Hot for CiscoView and CiscoWorks Windows" link.

Notes and Caveats for Online Help

• Find Tab. Because of the way a master CiscoView contents file is used by the software when multiple CiscoView device package help files are present, the list of files to include when setting up a customized find operation contains multiple items called CiscoView. [CSCdj62089]

• Online Help Intermittent Display Problem. There is a problem with the online help viewer, HyperHelp, intermittently displaying the Help topic window when opening Help > Contents.

When you first open a help topic using Help > Contents and click the Back button, the HyperHelp viewer might display a blank window. This is a HyperHelp bug. [CSCdi04758]

The workaround is to increase the kernel configuration parameter "number of open file descriptors per process" to approximately 90 or more. [CSCdk49538]

Troubleshooting

Before providing troubleshooting procedures, this section describes the CWSI Campus daemons and their interactions with clients.

Asynchronous Network Interface (ANI)

Asynchronous Network Interface (ANI or AniServer) is a multithreaded Java program. ANI is responsible for the discovery of the network for both devices and users. ANI is also responsible for all communication with the clients.

Database Engine

The database engine (dbeng50) is responsible for checkpointing all ANI information into the database and for storing historical data for the UserTracking application. For ANI, this is a checkpoint only. ANI performs all of its operations from the data stored in memory. The database stores user-entered information and allows ANI to load its data model quickly into memory upon a subsequent restart. (The Cisco Resource Manager database engine has the same name, so your system should be running two processes with this name.)

CORBA Agent

The CORBA agent (osagent) is responsible for interprocess communication messages. All servers must register with the osagent. All clients looking for service can find it with the help of the osagent. The CWSI Campus login window is used to indicate the name of the ANI server that the osagent should locate.

You can enter a command to view all servers registered with CORBA. However, before executing this command, you must make sure that the environment variable for the OSAGENT_PORT is set to 42342. To do this, enter the following command:

setenv OSAGENT_PORT 42342
 

Then to see all servers registered with CORBA, and where they are located, enter:

/opt/CSCOpx/lib/visigenics/bin/osfind
 

RTPoller

RTPoller is used to obtain real-time data for graphing in the AtmDirector application.

Event Channel

The event channel (EventChannel) is used to send events to all servers and clients who have registered with it.

Stopping and Starting CWSI Campus Daemons

The following command-line scripts control the CWSI Campus daemons:

• stopcwsiserver stops the CWSI Campus daemons.

• startcwsiserver starts the CWSI Campus daemons.

To use these scripts:

Step 1 Log in as Super User, and enter the <CWSIROOT>/bin directory.

Step 2 Open a shell window Command Prompt window.

Step 3 Enter stopcwsiserver to stop the CWSI Campus server processes.

When the shell prompt returns, all the daemons have been stopped. Wait a few moments for all processes to stop before restarting.

To restart the processes:

Step 1 Enter startcwsiserver and wait until the shell prompt returns.

Wait a few minutes to allow the processes to start and get into a steady state before starting CWSI Campus.

Step 2 Run osfind.

After running osfind, if you see that the AniServer or one of the other servers is missing, or you see in the processes lookup that your database engine is missing, stop the CWSI Campus servers and start them again.

When CWSI Campus Cannot Log Into AniServer

If you have just rebooted your machine and are unable to log in to AniServer, ANI may not yet be ready to receive messages. Wait 5 minutes, then try again.

If you are still unable to log in, run the osfind program to verify that AniServer has registered with the OSAgent. If so, verify that the name of AniServer in the login box is the same name as the name registered with OsAgent.

If you do not find AniServer, run the stopcwsiserver script (see "Stopping and Starting CWSI Daemons," earlier in this section), and then run the startcwsiserver script. Run osfind again. If AniServer is there, log into CWSI. If AniServer is still not registered, you might have a corrupt database.

You will need to reinitialize the corrupt database, which will delete all current data in the database. To do this, complete the following steps:

Step 1 Log in as Super User.

Step 2 Go to the <CWSIROOT>/bin directory.

Step 3 Run reinitdb.

Documentation and Additional Resources

In addition to these release notes and online help, the CWSI Campus documentation set includes the following documents:

• Installing Resource Manager Essentials and CWSI Campus on HP-UX

• Getting Started with Resource Manager Essentials

• Getting Started with CWSI Campus

• Using the Campus VlanDirector Application

• Using the Campus UserTracking Application

• Using the Campus TrafficDirector Application

• Using the Campus AtmDirector Application

• Getting Started with CiscoView

• Manual pages for Essentials located in the /opt/CSCOpx/man/man1 directory

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

A CCO web page for Essentials contains links to marketing and technical documentation and includes the latest downloadable Essentials packages. To find the latest Essentials information, point your web browser to the following location:

http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the Information Packet that shipped with your product.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

• WWW:  http://www.cisco.com

• WWW:  http://www-europe.cisco.com

• WWW:  http://www-china.cisco.com

• Telnet:  cco.cisco.com

• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

Posted: Thu Sep 30 12:25:32 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.