None

WhatsUp Gold should be running when you import devices into Resource Manager Essentials (Essentials).

To launch WhatsUp Gold from CD One and import devices into Essentials, WhatsUp Gold should be running on the CiscoWorks SNMS server.

Workaround:

None.

None

Reinstalling individual components is not supported using Autorun.

You cannot reinstall individual components in CiscoWorks SNMS using Autorun. However, you can uninstall the individual components and reinstall CiscoWorks SNMS.

Workaround:

1. Uninstall all the installed components.

a. Select Start > Programs >
CiscoWorks 2000 > Uninstall CiscoWorks 2000.

The Uninstallation dialog box appears.

b. Click Uninstall All.

• If you have installed the CD One and WhatsUp Gold components of CiscoWorks SNMS:

a. Select Start > Programs > CiscoWorks Small Network Management Solution > Uninstall CiscoWorks Small Network Management Solution.

The Remove CiscoWorks SNMS dialog box appears.

b. Click OK.

• If you have installed all the components of CiscoWorks SNMS, uninstall them. Refer to the Install Guide for CiscoWorks SNMS for details.

2. Install CiscoWorks SNMS.

CSCdt22462
(2)

CiscoWorks Small Network Management Solution is slow while downloading Java applets on Windows 2000 systems.

On some Windows 2000 machines, the initial download of large Java applets, or their subsequent downloads (if not cached locally), may take longer than expected. In some cases, this may take up to 6 minutes. After the applets are loaded and cached locally, downloads are quicker.

The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. This consumes a lot of memory and results in disk paging on most machines. Downloading is therefore slower than expected. The effect is reduced on machines with large RAM and virtual memory.

Workaround:

or

Instructions will vary depending on the specific virus scanner you use.

CSCin08781
(2)

WhatsUp Gold crashes if the default map is opened again.

When the WhatsUp Gold console is launched, the default map WhatsUp1.wup is opened, if it is present. If you try to reopen the map when it is already open, WhatsUp Gold crashes.

Workaround:

Do not try to reopen the map if it is open.

CSCin00102
(2)

If you install CD One, 4th Edition over an existing CiscoWorks SNMS installation, it may overwrite some of the CiscoWorks SNMS components.

CiscoWorks SNMS does not prevent you from installing other CiscoWorks 2000 products that include CD One, 4th Edition.

Installation of CD One may overwrite some CiscoWorks SNMS components and cause the product to work improperly.

Workaround:

None.

CSCdw04615
(2)

Launch of device web interface from Essentials fails.

If the device user manager is configured not to allow connection without authentication, Essentials Device Center will not launch the device web interface.

Workaround:

or

CSCdv89187
(2)

SWIM upgrade job on
Catalyst 6000 series devices running IOS fails with the following error message:

This occurs if a catalyst device type has IOS software running on it and CISCO-FLASH-MIB is used for copying the image onto the flash.

Workaround:

None.

CSCin02042
(2)

Media convergence servers are not imported from WhatsUp Gold.

Import from WhatsUp Gold imports devices that return Cisco sysobjectids and devices supported by Essentials. Since Media Convergence Server (MCS) returns a Windows server's sysobjectid, these devices will not be imported from
WhatsUp Gold.

Workaround:

Manage the media convergence servers using Resource Manager Essentials > Administration > Inventory > Add Devices.

CSCin08988
(2)

Cannot launch WhatsUp Gold from the CiscoWorks SNMS desktop, after changing the CiscoWorks SNMS server's hostname.

After installing CiscoWorks SNMS, if you change the server's hostname, you cannot launch WhatsUp Gold from the CiscoWorks SNMS desktop.

Also, you will not be able to launch other applications such as, CiscoView, Essentials, CMS/VSM, and AccessPoint from WhatsUp Gold

Workaround:

None.

CSCdw37950
(2)

If the MSFC card is running version 12.1(7a), distribution fails when you delete the files.

If the bootflash has images in it, and you try to erase the bootflash using CISCO-FLASH-MIB, it fails.

Workaround:

Manually delete the bootflash, update the inventory, and then try the operation again.

CSCdt71704
(2)

crmtftp.exe fails at system startup.

The CMF tftp service fails to start, and displays the following error:

Workaround:

Restart the service manually. To do so:

1. From the Windows Taskbar, select Start > Programs > Administrative Tools > Services.

The Services window appears.

2. Right-click on the CMF tftp service entry and select Start.

3. Close the Services window.

CSCdp47503
(3)

NMS integration fails.

NMS integration fails if the directory name, where the nmidb.jar file is stored, contains multiple spaces.

Workaround:

Rename the directory using a single space or no spaces.

CSCdv72484

CSCdv72485

CSCin01337
(3)

Launching of CiscoView, Essentials, CMS, and VSM from WhatsUp Gold browser fails.

If the CiscoWorks SNMS server name cannot be resolved, the launch of CiscoView, Essentials, CSM, and VSM fails.

Workaround:

Enable the resolution of CiscoWorks SNMS server and device names from the client browser by:

or

CSCdv50840
(3)

Cannot launch Cisco Cluster Management Suite on some devices using Java 1.3.1 Plug-in.

If Java 1.3.1 Plug-in is installed on the client system, Cisco Cluster Management Suite (CMS) and Cisco Visual Switch Manager (VSM) might not launch from CiscoView or WhatsUp Gold for certain devices.

Workaround:

VSM/Cluster Manager/Cluster Builder applets must be launched on a separate client computer that has Java Plug-in 1.2.2 installed.

A client computer cannot have both
Java Plug-in 1.2.2 and 1.3.x installed at the same time. You can download Java Plug-in 1.2.2 at the following URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java

CSCdv66331
(3)

Launch of WhatsUp Gold from Device Manager fails.

If the CiscoWorks SNMS server name is not resolved from the client, the launch of
WhatsUp Gold from Device Manager fails.

Workaround:

Enable the resolution of the server name by configuring DNS for the CiscoWorks SNMS server.

CSCdv81149
(3)

Device aliasing fails after the device limit of 20 is reached.

When the managed device limit of 20 is reached, aliasing will not work.

Workaround:

To check for all aliases, delete some devices from the managed state, and import the devices again.

CSCdw04187
(3)

Aironet device AP340 with sysobjectid1.3.6.1.4.1.522.2.1.76 is not supported by Essentials.

Aironet device AP340, with
sysobjectid 1.3.6.1.4.1.522.2.1.76 is not managed as an Aironet device. Instead it is managed as a generic SNMP device. Since Essentials does not support this device, you cannot launch Essentials from WhatsUp Gold.

Workaround:

Upgrade the device to 11.08T or a higher version.

CSCdw34481
(3)

Inventory custom report for RAM size may show incorrect values.

Devices that support memory pool may show incorrect values.

Workaround:

Use Resource Manager Essentials > Inventory > Detailed Device Report.

CSCdw56876
(3)

SWIM CCO support is unavailable for 2950 and 3550 series of devices.

SWIM CCO support for features, such as addition and recommendation of images from CCO, are not present for the 2950 and 3550 series of devices.

Workaround:

Add the required images by manually downloading them from CCO and importing them into the SWIM image library from the file system.

CSCin09092
(3)

Cannot launch Essentials and CiscoView from the WhatsUp Gold web map.

If the device is discovered through the WhatsUp Gold web interface by using only the IP address and not the hostname, you cannot launch Essentials or CiscoView from the web map.

Workaround:

Enter the hostname value in the Hostname field. If the device does not have a hostname, enter the IP address in the Hostname field.

CSCin00560
(3)

The feature, Add Images from CCO does not work for Aironet devices.

CiscoWorks SNMS displays an error message when you do the following:

1. Select Resource Manager Essentials > Software Management > Library > Images.

2. Select CCO as the source.

3. Select any Aironet device and continue downloading the image.

Workaround:

Manually download the images from CCO, extract them, and add them to your file system using Library > Add Images.

CSCin01313
(3)

Page Not Found error from User Guide Home button.

In Online Help if you select Resource Manager Essentials > User Guide and click on the Home button, a Page Not Found error occurs.

Workaround:

In the Location or Address field of your browser, enter the URL:
http:// server_name:1741/help/index.html

where server_name is the name of the server on which CiscoWorks SNMS is installed.

CSCin01355
(3)

The Backup current running image option for distribution to Aironet devices is not supported.

When you select Resource Manager Essentials > Software Management > Library > Browse Images and select an Aironet device, CiscoWorks SNMS displays the following error:

Workaround:

Copy the image from the device using
Library > Add Images and select the Aironet device to which distribution is made.

CSCin01458
(3)

Import from WhatsUp Gold, cross launch of CiscoView, and Resource Manager Essentials fails because of name resolution.

When you discover devices in WhatsUp Gold with the Resolve Host Names option checked, Cisco ICS 7700 devices appear with a host name that CiscoView and Resource Manager Essentials cannot resolve.

Workaround:

Discover Cisco ICS 7700 using the IP address.

CSCin01794
(3)

Existing version of the
Java Plug-in has not been uninstalled, before installing the new version.

You have not uninstalled the existing version of the Java Plug-in, before installing the new version.

Workaround:

Before installing Java Plug-in 1.3.1 on a client machine, uninstall the previous version of the plug-in.

CSCin01889
(3)

Netscape crashes if CiscoView is invoked without a plug-in installation on Solaris Netscape client 4.77.

When you click on the CiscoView link from Device Manager and if there is no plug-in installed on the machine, Netscape crashes.

Workaround:

Install Java Plug-in when you login to
CiscoWorks SNMS for the first time.

CSCin02576
(3)

Distribution to Aironet devices fails if the flash size is small.

Distribution to Aironet devices fails if the flash size is smaller than 2 MB.

Workaround:

None.

CSCin04286
(3)

Installation is improper when performed from a remote shared CD drive, if the sharename has a space.

If you install CiscoWorks SNMS from a remote shared CD drive and if the sharename has a space, the installation will be improper.

Workaround:

Map the remote shared CD drive.

CSCin04204
(3)

Installation of WhatsUp Gold as a service fails when the WhatsUp Gold console is running.

If you run the wugsvc -install command while the WhatsUp Gold console is running, the message,
Service installed and started
appears, although the service has not started.

Workaround:

Close the WhatsUp Gold console and then install the service.

CSCin04208
(3)

Without removing the
WhatsUp Gold service, you cannot uninstall
CiscoWorks SNMS completely.

If you install WhatsUp Gold as a service, and then uninstall CiscoWorks SNMS, the uninstallation will not be complete. WhatsUp Gold remains active and can be used.

Workaround:

Remove the WhatsUp Gold service before uninstalling CiscoWorks SNMS.

CSCin04443
(3)

Unable to launch applications from WhatsUp Gold for devices that run on Windows.

You cannot launch applications like Essentials and CiscoView for some devices that run on Windows. This happens because Windows machines are generally configured for WINS and not DNS.

Workaround:

or

CSCin04077
(3)

Import from WhatsUp Gold fails if a device is added using Add Device in the WhatsUp Gold web Map.

This happens because you have not entered the device SysObjectID while adding a device using the Add Host link in a WhatsUp Gold web map.

Workaround:

Enter the device SysObjectID.

CSCin09093
(3)

Cannot save the map that was created using the WhatsUp Gold web interface.

You cannot save the maps in WhatsUp Gold, if you created them using the WhatsUp Gold web interface.

Workaround:

Create maps using the WhatsUp Gold console on the CiscoWorks SNMS server.

CSCin04448
(3)

Unable to start WhatsUp Gold Syslog service.

When you start the WhatsUp Gold Syslog service from the WhatsUp Gold console (Configure>Logging), the message,
Unable to open socket
appears.

This is because another Syslog service is already running on the system.

CiscoWorks SNMS comes with two Syslog services, CMF Syslog service and WhatsUp Gold Syslog service. (We recommend that you keep the WhatsUp Gold Syslog service turned off at all times.)

As the Essentials Syslog Analyzer uses the data collected by CMF Syslog service, it is mandatory to run the CMF Syslog service.

Workaround:

None

CSCdv68683
(3)

Redundant links in WhatsUp Gold maps after unintegration of WhatsUp Gold or after uninstalling CiscoWorks 2000.

WhatsUp Gold maps that were saved earlier will show redundant links. These links may not work after unintegration of WhatsUp Gold with Cisco devices or after you uninstall CiscoWorks 2000.

Workaround:

Recreate the maps.

CSCin04285
(3)

wugsvc -remove fails while removing the WhatsUp Gold service.

This happens because you have not stopped the WhatsUp Gold service before executing the wugsvc -remove command.

1. Workaround:
Stop the WhatsUp Gold service.

2. If you still see the WhatsUp Gold service entry in the Services window, close the window and open it again.

3. After this entry is removed from the Services window, execute the wugsvc -remove command.

CSCin04717
(3)

Duplicate entries are seen for a device family.

In the WhatsUp Gold console, when you select Configure > Device types, you see duplicate entries for a device family.

Workaround:

1. Click OK to close the Device types dialog box.

2. Select Configure > Device types and reopen the dialog box.

CSCin08936
(3)

Certificate Expiry warning message is seen when certain CiscoView applications are invoked.

Owing to a bug in Java Plugin version 1.3.0, Certificate Expiry warning messages are displayed when certain signed certificates used to communicate between the client browser and the CiscoWorks SNMS server are accessed.

Workaround:

None. These are informational messages. Ignore these messages and continue to use CiscoWorks SNMS.

CSCin04971
(3)

Installation of CiscoWorks SNMS is very slow.

The delay is caused by filtering mechanisms such as virus scanners. Some virus scanners are configured to automatically scan contents. The scanning takes up a lot of memory and results in paging to the disk on most machines, because of which the machine becomes significantly slower than expected. The effect is reduced on machines with large RAM and virtual memory.

Workaround:

1. Disable your machine's virus scanner. This will improve Java applet download times, considerably.

or

Disable automatic scanning of all downloaded files, and instead, enable scanning of only program files (specified by extension).

Instructions will vary depending on the specific virus scanner you use.

2. Restart the virus scanner after installation is complete.

CSCdt24701
(4)

No error message is displayed after an unsuccessful attempt to uninstall nmidb packages.

After an unsuccessful attempt to uninstall nmidb packages, no error message appears stating that the process failed. Furthermore, the View History window displays a message that the download has completed successfully.

Workaround:

None.

CSCin04854
(4)

Changes are not reflected in WhatsUp Gold.

Changes are not reflected in WhatsUp Gold even after integrating the newer version of nmidb.

Workaround:

After integrating a newer version of nmidb, you should restart the WhatsUp Gold console and service to ensure that the changes are reflected in WhatsUp Gold.

CSCin09055
(4)

Chassis Card Type is shown as -1 for Aironet devices.

Select

or

The Chassis Card Type is shown as -1 for Aironet devices.

This happens because the Cardtype MIB variable of OLD-CISCO-CHASSIS-MIB is not properly populated for Aironet devices.

Workaround:

None.

CSCin04099
(4)

Uninstallation of
CiscoWorks SNMS takes a long time.

The delay is caused by filtering mechanisms such as virus scanners. Some virus scanners are configured to automatically scan contents. The scanning takes up a lot of memory and results in paging to the disk on most machines, because of which the machine becomes significantly slower than expected. The effect is reduced on machines with large RAM and virtual memory.

Workaround:

1. Disable your machine's virus scanner. This will improve Java applet download times, considerably.

or

Disable automatic scanning of all downloaded files, and instead, enable scanning of only program files (specified by extension).

Instructions will vary depending on the specific virus scanner you use.

2. Restart the virus scanner after uninstallation is complete.