Resource Manager Essentials 3.0 Release Notes (Solaris)

None

Browsers running on remote X servers

Browsers running on remote X servers are not supported.

None

Cisco Voice Manager

Cisco Voice Manager must be installed on a different machine than Essentials.

None

Printing from a browser does not work reliably

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

CSCdp07512

The VM of Netscape version 4.6.1 leaks memory

The virtual memory (VM) in Navigator 4.6.1 leaks memory in proportion to the number of classes loaded by the applet being used.

To work around this problem, close your browser to free all memory claimed by the VM.

CSCdk44743

Netscape Navigator 4.x: Under certain conditions, requesting more records causes an internal error message

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

• When you use Navigator to view the report

• When you select all days of the week to generate the report

To work around this problem:

• Select an option other than all days of the week to generate the report

• Resize the window, which removes the error message

CSCdm94172

Report hang-up when waiting for a device attributes check

When you are waiting for a report to be displayed, you can cause the browser to freeze, or quit responding, by repeatedly clicking Update Status.

To avoid this problem, click Update Status less frequently. Wait a few minutes until all results have been collected, then click the button.

If the screen freezes, you can wait approximately 15 minutes and you will regain control, or use the Task Manager to close the application and restart it.

CSCdp13723

Netsys report generation fails

During the Netsys application setup, you cannot enter the local host IP address or its equivalent DNS name as the Netsys host in the remote UNIX (remote NT) option, or Netsys reports are not generated.

To work around this problem, do not use the local host IP address or its equivalent DNS name for the Netsys host in the UNIX (remote NT) option.

CSCdp13935

NetConfig exit in conjuction with device-search applets can crash browser

If you use the NetConfig application extensively and also use the device-selection applets on the desktop at the same time, a browser crash might occur when you exit NetConfig.

CSCdp31816

Login fails and existing login sessions do not respond

The Essentials Check Device Attributes operation triggers a memory leak. Device attribute checking is performed automatically every time you run an inventory update, but can also be performed manually by selecting Essentials > Administration > Inventory > Check Device Attributes. Whether you run a device attribute check or it occurs automatically, it causes a portion of the memory available to CiscoWorks2000 servlets to become unavailable.

After about 25 device attribute checks, all servlets quit operating. Logins do not work and running sessions cannot launch applications. If you allow the inventory collection period to remain on default (once per week) and do not perform device attribute checks frequently, the system displays this behavior only once every four to six months. If you increase the frequency of inventory collections or device attribute checking, this condition occurs sooner than four to six months.

To work around this problem, use one of the following methods:

1) Every four months, the CiscoWorks2000 system administrator must stop and start the CiscoWorks2000 server components using the /etc/init.d/dmgtd stop and /etc/init.d/dmgtd start commands. A complete reboot of the CiscoWorks2000 server also does this, but is not required. Or

2) Instead of performing the stop/start operations at four-month intervals, you can monitor the growth of the servlet process yourself, then perform the operation in method 1. Using the UCB version of ps, execute:

%/usr/ucb/ps-axww | grep servlet.jar

Using the process id of this process, run:

%/usr/ucb/ps-alx | grep <process id>

When the SZ field of this process is 50MB or more, stop and start the CiscoWorks2000 server components as described in method 1.

CSCdp25390

RIGEL:Dbl clk on title bar or clk on maxi btn brings up Ani Srv

If you maximize, restore, or resize your Navigator browser, the browser reloads all frames. This action leads to multiple instances of some applications being invoked, which uses a lot of memory.

To work around this problem, avoid maximizing, restoring, or resizing the screen. Close any extra instances of applications.

CSCdk89921

Essentials screen appears without the login applet

Do not change the default file ownership and permissions for the /var/sadm directory. If you do, bin will not be able to read files in this directory.

CSCdp40189

Attempts to use the CD One installation script to save data from an existing RME 2.x installation might fail if the existing RME 2.x is installed on a Solaris 2.5.1 or a Solaris 2.6 system that lacks the patches required for a full CD One installation

To migrate data from an existing RME 2.x installation to RME 3.0 installed on a different machine, insert the CD One CD-ROM in the RME 2.x machine. Run the setup.sh script to save your existing data. Then exit the installation script BEFORE beginning the installation process.

This procedure might fail if the existing RME 2.x is installed on either Solaris 2.5.1 or on a Solaris 2.6 system that lacks the patches required by the CD One installation. (The setup.sh script checks for the required OS version and patches needed to install CD One.) If running the setup.sh script fails, users cannot save their existing data.

To save your existing data, you need root or super-user privileges. Follow these steps:

Step 1 Mount the CD One media and change directory to the install directory:

# cd /cdrom/cdrom0

Step 2 Enter Bourne shell:

# /bin/sh

Step 3 Make the temporary setup directory:

# mkdir /tmp/setup

Step 4 Define and export these environment variables:

# SETUPDIR=. ; export SETUPDIR

# TOC=disk.toc ; export TOC

Step 5 Run the upgradebg.sh script:

# /bin/sh ./upgradebg.sh

CSCdp40189 cont.

Step 6 When the script prompts you to continue with installation and disable existing RME and CWSI, enter No.

You will receive the following message: Setup has detected the following product on the destination server:

-Resource Manager Essentials (RME) version 2.0 or higher

-CWSI Campus (Campus) version 2.2 or higher

-TrafficDirector (TD) version 5.3 or higher

(Other comments from the message are not shown here.)

Step 7 Enter Yes at the following prompt: Do you want to proceed? (y/n)?

Step 8 Enter <CR> to use the default /opt/CW2000/OldData directory at the following prompt: Please specify the path of the temporary directory where the data from the current products will be archived. You may also specify an alternate directory that does not contain any existing data.

The script saves the existing data, and setup uninstalls the other products.

Step 9 Enter No at the following prompt: Setup will now uninstall RME/CWSI and TD. Do you want to continue? (y/n)?

You will then receive the following message: Upgrade stopped at user's choice.

Step 10 Remove the temporary directory created in step 3:
# rm -rf /tmp/setup

Step 11 Move the saved data to the new RME 3.0 system (via tar, ftp, etc) or nfs-mount the directory where the data was saved. Then on the new system use the script bg2rigel.pl as described in Installing and Setting Up Resource Manager Essentials.

CSCdk18245

Clearing cache

When you upgrade your software, you might need to clear your browser cache file to display the login frame.

If you are running Navigator, select Edit > Preferences > Advanced > Cache, then select Clear Memory Cache.

If you are running Internet Explorer, select View > Internet Options > General > Temporary Internet File > Delete Files.

CSCdp06564

Upgrade to Essentials 3.0 causes administrator's password to be reset

When you upgrade from Essentials 2.x to 3.0, the system administrator's password is reset to "admin."

To work around this problem, after installing CD One but before installing Essentials 3.0, log in and change the admin password to that of Essentials 2.x. Then install Essentials 3.0.

None

Device package help

If you have intermittent problems with device package help, download the latest device package version from CCO.

CSCdp19474

Essentials unable to delete job after upgrade

Do not attempt an Essentials 2.x to 3.0 upgrade while any Software Management jobs are running or pending. Wait until the jobs are complete or cancel or remove these jobs before upgrading your system.

Software Management jobs that are running during the upgrade might not be completed correctly. Pending jobs will not be performed after the upgrade is finished and cannot be removed from your system.

CSCdp19747

Essentials 2.x to Essentials 3.0 upgrade

When you upgrade Essentials 2.x, the management data is automatically preserved and upgraded. The following procedure is necessary only if you have performed a new installation and want to manually upgrade your data from a previous 2.x installation.

To upgrade your data, run the bg2rigel.pl script from an upgrade installation or manually from the command line after a new installation of CD One plus Essentials 3.0. Refer to Installing and Setting Up Resource Manager Essentials on Solaris for further important instructions before proceeding.

To run the bg2rigel.pl script manually, enter: <NMSROOT>/conf/bg2rigel/scripts/bg2rigel.pl -I {BG data backup Dir} [-f]
You must insert a space between -I and the backup directory value where NMSROOT is the path to the CiscoWorks2000 installation.

If you run the script without the -I option, the program tries to install the incremental device support (IDS) information in the database, which causes failure and many errors if the IDS is already in the database. Also, failure and multiple errors occur if bg2rigel.pl is run without the -I option more than once.

If your upgrade fails, follow instructions in Installing and Setting Up Resource Manager Essentials on Solaris.

CSCdp24862

After uninstalling RME only, re-install of RME fails

If you uninstall RME 3.0, then install it again on a CD One installation, the second installation of RME 3.0 fails in the database update steps. This failure is due to a bug in the RME 3.0 uninstallation code, which removes files belonging to CD One. If you encounter this problem, log in as root, then:

Step 1 Stop the daemon manager if it is running, using /etc/init.d/dmgtd stop
Check to ensure that all processes have quit running. If ps -ef|grep CSCO does not list any processes, then none are running.

Step 2 If RME 3.0 was already installed and failed, uninstall it.

Step 3 This step MUST be performed before you install RME 3.0 again.
Install the missing CD One files to the correct directory and set its permissions properly.
cp <cdrom-dir>/patch.sh /opt/CSCOpx/lib/sh
chmod 755 /opt/CSCOpx/lib/sh/patch.sh
pkgadd -d <cdrom>/packages CSCOdb

Step 4 Install RME 3.0.

CSCdm68049

Inventory files left after uninstall

If you uninstall Essentials 3.0, make sure that all Essentials files have been removed from these two directories.

/opt/CSCOpx/IDS/logs

/opt/CSCOpx/conf/bg2rigel/rme

CSCdp05515

After an Essentials uninstall, JRM does not remove NetConfig jobs

If you uninstall Essentials 3.0, you might notice that NetConfig jobs are still being displayed under CiscoWorks2000 Server > Administration > Job Management.

To work around this problem, reinstall Essentials, then remove any residual jobs by selecting the unwanted job and clicking the remove button.

None

Starting Essentials as root

If you start Essentials by logging in as root and entering /etc/init.d/dmgtd start from a command-line, make sure you do not suspend the root session with the suspend command. If you suspend the root session after manually starting Essentials, other processes such as the Daemon Manager, DIServer, and IcServer are also suspended.

To resolve this issue, unsuspend the root session.

CSCdm05454

Protocol Distribution report shows 100% TCP/IP utilization for
Catalyst 5000 switches

If you launch the Protocol Distribution report from the Reachability Dashboard, and the option for availability polling for Reload & Protocol Distribution is off, the Protocol Distribution report shows 100% TCP/IP utilization for Catalyst 5000 family devices.

If you launch Protocol Distribution directly from the Availability menu, the application recognizes that no views are configured for Protocol Distribution monitoring.

None

TACACS with SecureID

The Essentials configuration archive does not support TACACS with SecureID. The configuration archive supports static passwords, which are defined when you add or import devices into the Essentials inventory.

None

Configuration Import Message

Cwconfig cannot validate the syntactic correctness of configuration files uploaded to the device via the import command. As a result, the import is reported successful even if the configuration file is invalid.The configuration update will not succeed on the device, but cwconfig cannot detect this failure.

None

Access restrictions and file permissions

Cwconfig is a set-userid program owned by root; it belongs in bin. However, as soon as the program starts, cwconfig sets the userid to bin. 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.

CSCdk12667

Command-line syntax errors

When a cwconfig session has multiple syntax errors, only the first detected error is reported. The others remain unlisted.

CSCdm83922

Editing a job just before scheduled execution

If you edit a job just before it is scheduled to run and do not complete the edit in time, the job will run in its pre-edited state. The desired edit can still be scheduled, but you cannot re-edit that job after the original edit is scheduled.

To work around this problem, make sure your edit is complete before a job is scheduled to run or delete the job and create a new one.

None

Standard device prompts required for Configuration Archive Telnet mechanism

The Telnet transport mechanism cannot retrieve or update device configurations if any remote devices have nonstandard device prompts. The accepted, standard device prompts on Cisco IOS devices are the device prompt strings ending with the greater than symbol or the pound symbol (number symbol) at the Telnet login and enable mode. The accepted, standard device prompts on Catalyst devices end with the keyword "enable" at the Telnet enable mode.

CSCdp21510

NetConfig job scheduled by Approver throws exception

If you have only Approver status in the NetConfig application, you cannot create a NetConfig job using the command line interface or run a NetConfig job using the GUI.

To work around this problem, you must also be designated a NetAdmin, NetOp, or SysAdmin in addition to being an Approver.

CSCdp20553

Null pointer exception using NetConfig

You can access NetConfig by selecting Resource Manager Essentials > Configuration Management > NetConfig or Resource Manager Essentials > Administration > Approve or Reject Jobs. Do not open a NetConfig job in Resource Manager Essentials > Configuration Management > NetConfig and Resource Manager Essentials > Administration > Approve or Reject Jobs. If you do, do not exit the first instance of NetConfig until all tasks are finished. Then exit both instances of NetConfig.

None

Devices with multiple IP addresses

The TFTP transport mechanism might not work for devices with multiple IP addresses when a given device is managed by using the host name in the Inventory database. The SNMP library used by TFTP queries for only one IP address for a given hostname while performing hostname resolution with the corresponding domain name server. For a device with more than one IP address, hostname resolution might not return the IP address of the interface running the SNMP agent. In such cases, TFTP fails and displays SNMP Time Out Error.

To work around this problem, import devices using the IP address in the inventory database.

CSCdp11661

Server error when attempting to open Inventory report

If you install TrafficDirector after Essentials and select /opt/CSCOpx for TrafficDirector's installation (or the subdirectory where Essentials is installed), TrafficDirector could corrupt Essentials.

If the problem occurs, you must uninstall both Essentials and TrafficDirector and re-install both products. Uninstalling only TrafficDirector does not clear the problem in Essentials.

CSCdm87814

Essentials' Check Contract Status tool generates information for routers only.

If you select Resource Manager Essentials > Contract Connection > Check Contract Status, information is generated for routers only.

Use a web browser to obtain information from the CCO URL:

http://www.cisco.com/cgi-bin/front.x/
csadispatch?AppName=ContractAgent

Then, under View Contracts, select the link By Contract > Serial > Purchase Order > Service Order Number (Contract Lookup) and find the contract information.

CSCdm01805

Adding devices to Essentials fails

Adding devices to Essentials fails if case-insensitive community strings already exist in the database. If you add a device to the Essentials database with community strings similar to those already present in the ACCESS_DATA table (the only difference is the use of upper and lower case), the import fails.

Because community strings are not removed from the database, this problem also applies to devices removed from the database.

CSCdm75952

Do not use special characters such as apostrophes, semicolons, or parentheses in the Change Device Attributes window

If you select Resource Manager Essentials > Administration > Inventory > Change Device Attributes, then select a device and click, you must select User Fields. Do not use special characters such as apostrophes, semicolons, or parentheses in these fields.

CSCdm62904

Fixing a corrupt database

The troubleshooting procedure documented in Using Resource Manager Essentials explains how to install the px.db database over your corrupt database. This procedure overwrites all incremental device support (IDS) in the database. To preserve the IDS, perform the following procedure:

Step 1 Stop the Essentials 3.0 daemon manager. Install a backup database if you have one; otherwise, install the basic database, px.db, over your corrupt database.
a. Back up or rename the corrupted database files: CSCOpx/databases/rme/rme.db
CSCOpx/databases/rme/syslog.db
b. Install the basic database files:
From CSCOpx/databases/rme/orig/rme.dborig to CSCOpx/databases/rme/rm.db
From CSCOpx/databases/rme/orig/syslog.dborig to CSCOpx/databases/rme/syslog.db
c. You must copy both files in the database location. These must be owned by user bin and group bin on both Windows NT and UNIX systems.

Step 2 Run the following scripts to preserve all IDS information:
$NMSROOT/dbupdate/dbupdate.pl $NMSROOT/IDS/inventory/invIds.txt
$NMSROOT/dbupdate/dbupdate.pl $NMSROOT/IDS/config/cfgIds.txt

Step 3 Start the Essentials 3.0 daemon manager.

None

IP address may change between reboots

You must import cable modems ubr904 and ubr924 using the fully qualified pathname. These devices get the IP address of the cable interface using DHCP from the head-end cable router; the IP address might change between reboots.

None

PIX Firewall device

Configure the PIX Firewall device on your SNMP server host so Essentials can manage it: Enter the server and IP address of your Essentials workstation.

CSCdp06531

RME 3.0 Beta: Inventory reports get error on sort

If you try to sort columns in an inventory report such as hardware or software, you might see one of several error messages, including a 500 internal server error message.

CSCdp25706

2 user defined templates for IOS. 1 enable mode, 1 config mode

For Cisco IOS and FastSwitch, you cannot create a NetConfig job containing both the enable mode (user-defined templates) and config mode (system-defined templates.) Instead, create different jobs.

None

MultiSwitch Feature Card for Catalyst 6000 and RouterSwitch Feature Card for Catalyst 5000

Backup of current images during image distribution fails for the MultiSwitch Feature Card for Catalyst 6000 devices and RouterSwitch Feature Card for Catalyst 5000 devices.

Images running on these devices cannot be imported by the image baseline or image synchronize task.

CSCdk66836

Not enough space available on Flash for software image upgrade

If the Flash memory does not have enough space, Software Management cannot recover the space because the squeeze operation through SNMP fails and leaves the Flash memory locked. This problem affects low-end IOS hardware platforms running the following Cisco IOS releases:12.0(4), 12.0(5), 12.0(4)P, 12.0(5)P, 12.0(4)T, 12.0(5)T.

Low-end platforms are Cisco 1000, 1600, 1700, 2500, 2600, 3600, 4000, 4500, and 4700 routers.

To work around this problem, erase the Flash memory manually and use Software Management to upgrade to the new software image.

CSCdk93048

Downloading IOS image to the slot0 flash card on 8510CSR fails

When a Cisco IOS image is downloaded to the slot0 Flash card on the 8510CSR device using SNMP, the copy operation fails with copyUnknownFailure, and the formatting information on the Flash card is erased.

To work around this problem, use slot1 instead of slot0 as the target location of the IOS image.

CSCdm78469

CCO Upgrade Analysis task may recommend incorrect flash upgrade requirements

If you select Resource Manager Essentials > Software Management > CCO Upgrade Analysis > Distribution, the upgrade might recommend a Flash upgrade for a device that already satisfies the Flash requirement. Some versions of Cisco IOS images report a Flash size that is less than the actual size, which causes the upgrade analysis to make incorrect conclusions about the Flash requirement.

To work around this problem, if the upgrade analysis recommends a Flash upgrade, make sure that a Flash upgrade is necessary.

None

ATM module upgrades on Catalyst switches

Software Management supports upgrade software on the following ATM modules for Catalyst 5000 series devices:

WS-X5153, WS-X5154, WS-X5155, WS-X5156, WS-X5157, WS-X5158, WS-X5161, WS-X5162, WS-X5167, WS-X5168.

These modules require different versions of ATM software images. Check the ATM module software release notes on CCO for compatibility between module types and software versions, and minimum supervisor software requirements.

WS-X5153 to WS-X5158 modules can run LANE ATM, PVC Traffic Shaping, or Token Ring LANE images.

LANE ATM image file names follow the cat5000-atm.* format. These modules run from 2.2 to 3.2(8) ATM module software releases. LANE ATM Software Images for these modules can be imported using Resource Manager Essentials > Software Management > Library > Add Images.

PVC Traffic Shaping image file names follow the c5atm-wbpvc.* file format. These images are not available using Add Image to Library from the CCO Interface. PVC Software Image version numbers range from 50.1(1) to 51.x at the time of releasing this document. Check the PVC Software Images release notes for version compatibility information.

Token Ring LANE software image version numbers start from 70.1(1) onwards and the image file names follow c5atm-trlane.* format.

To upgrade software images on WS-X5161, WS-X5162, WS-X5167, WS-X5168 modules, the Supervisor module must be running at least 4.1(1) software. These modules run software images whose file names follow the c5atm-wtall.* format. For example c5atm-wtall.113-2a_WA4_4b.bin is the file name for LANE ATM software.

ATM module upgrades on Catalyst switches (continued)

LANE ATM software on these modules include Ethernet LANE, Token Ring LANE and PVC Traffic Shaping features. While importing these software into the library from the File System/Device, input the part of the file name after WA as the software version number.

In Table 3, 4(4b) is the software version number. When you download this software to an ATM module, the ATM module version number from show module command is displayed as 11.3(2)WA4(4b). No problem results if the version numbers displayed using the show module command do not match Software Management version numbers. Refer to Table 3 for more examples.

CSCdk47488

Changing the default logging facility

Syslog messages are logged to a file. The file is configured to store local7.info messages from routers, but for the PIX devices, the default is not local7.

To work around this problem, set the PIX device to facility 23.

CSCdm14868

Catalyst 5000 does not support new message format

Catalyst 5000 image 4.4(1) has a new syslog message format. If the service timestamp is enabled, syslog analysis cannot parse it.

To work around this problem, disable the service timestamp.