|
|
![]() | Caution Make sure all applications are stopped before you upgrade Essentials. The upgrade process depends on having reasonable interaction times with the database. If this is not possible, the upgrade fails. |
![]() | Caution If the Y2K Compliance Assessment Tool is installed on your machine, you must uninstall it before installing this version. Otherwise the installation fails. |
![]() | Caution CWSI Campus and Essentials 3.0 cannot coexist on the same machine. |
These release notes describe the caveats for Resource Manager Essentials 3.0 running on the Windows NT 4.0 with Service Pack 5 (workstation and server.) This document contains the following sections:
Use these publications to learn how to install and use CiscoWorks2000:
For information about supported devices, go to the suggested URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/dev_sup/
e3_0.htm
Table 1 lists the time zone acronyms that are supported in the CiscoWorks2000 applications that use the time zone feature. These time zones can be configured on Essentials managed devices. Details in Table 1 are:
When configuring time zones on CiscoWorks2000 servers, use the supported value in Column 3. To make sure that time zones are translated correctly -- especially when your devices, servers, and clients are in different time zones -- follow these guidelines:
To help you understand the importance of setting time zones correctly, these steps illustrate how time zones are converted as they are passed from devices to servers to clients in different time zones:
1. An event occurs on a managed device, and the application message (such as syslog) containing the device time zone is sent to the server.
2. An application daemon on the server reads the incoming message, converts the time zone to GMT, and stores it in the Essentials database.
3. When a client requests a report, the GMT stored in the Essentials database is converted to the CiscoWorks2000 server's time zone and is displayed in Essentials reports. Because Perl and Java process Essentials reports differently, the server time zone is displayed as either an acronym or a GMT offset (as shown in Column 4).
1 Offset from GMT | 2 Area Covered (Country/City) | 3 Time Zone Setting on Server | 4 Output in Report | |
|---|---|---|---|---|
| GMT | Acronym | |||
+10:00, +11:00 | Australia | Brisbane, Melbourne | GMT + Offset | AEST, AET, or EAST |
+9:30 | Australia | Adelaide |
| ACT |
+9:00 | Japan/Tokyo | Tokyo |
| JST |
+8:00 | China | Beijing |
| CST |
+3:00, +4:00 (DST1) | Russia/Moscow | Moscow | GMT +3:00, |
|
+2:00, +3:00 (DST) | Cairo, Helsinki | Cairo, Helsinki |
| GMT +2:00, |
+2:00 | Israel | Israel |
| IDT |
+1:00, +2:00 (DST) | Germany, Italy | Berlin, Rome | GMT +1:00, |
|
+1:00, +2:00 (DST) | France, Spain | Paris, Madrid | GMT +1:00, | CEST |
0 | Africa, Great Britain/ London | Greenwich Mean Time | GMT | GMT |
-5:00, -4:00 (DST) | Eastern Canada | Atlantic |
| ADT |
-5:00, -4:00 (DST) | U.S./New York | Eastern Time |
| EST, |
-6:00, -5:00 (DST) | U.S./Chicago | Central Time |
| CST, |
-7:00, -6:00 (DST) | U.S./Denver | Mountain Time |
| MST, |
-8:00, -7:00 (DST) | U.S./Los Angeles | Pacific Time |
| PST, |
-10:00 | Hawaii/Honolulu | Hawaii |
| HST |
| 1DST = Daylight Savings Time |
Table 2 shows time zone settings and their acronyms for your Cisco network devices. Using Table 2 ensures that Syslog Analysis and the CiscoWorks2000 server function correctly. Make sure that the time zone information is correct on your devices. To set time zones on your devices, use a command-line interface (refer to your device-specific command reference manual.)
Syslog Analysis depends on receiving correct time zone information from your network devices. As a message is parsed by Syslog Analysis, the time zone acronym in the message is read and compared with a standard table within Essentials. If the time zone settings on your network devices are not configured properly, the comparison fails. Syslog Analysis defaults to PDT/PST, resulting in the wrong time conversion.
When Syslog Analysis parses and writes data to the database, the application converts all time zone settings to GMT and stores a message time zone in the database as GMT. If the acronym on your device is set properly, correct conversion occurs, and the GMT is calculated correctly. (See page 4 for a step-by-step description of time zone conversion between devices, servers, and clients in different time zones.)
1 Offset from GMT | 2 Time Zone Acronym Setting on Device | 3 Area Covered (Country/City) |
|---|---|---|
+12:00 | IDLE | International Date Line East |
+12:00 | NST, NZST, NZT | New Zealand/Wellington |
+11:00 | EADT | Australia/Queensland |
+11:00 | SST | Pacific/Guadalcanal, Solomon Islands |
+10:00, +11:00 | AEST, AET, EAST | Australia/Melbourne, Sydney |
+10:00 | GST | Mariana Islands/Guam |
+9:30 | ACT | Australia/Darwin |
+9:00 | JST | Asia/Tokyo |
+8:00 | CCT, CTT | Asia/Beijing, Shanghai, Taiwan |
+7:00 | VST | Asia/Bangkok |
+7:00, +8:00 (DST1) | WAST, WADT (DST) | Australia/Perth |
+6:00 | BST | Asia/Dacca |
+5:30 | IST | Asia/Calcutta |
+5:00 | PLT | Asia/Karachi |
+4:00 | NET | Asia/Yerevan |
+4:00 | ZP4 | Russia/Moscow |
+3:00 | ADT, EAT | Asia/Riyadh |
+3:00 | BT | Asia/Baghdad |
+2:00 | ART | Africa/Cairo |
+2:00, +3:00 (DST) | EET | Europe/Istanbul |
+1:00 | CAT | Atlantic/Cape Verde |
+1:00 | CET, ECT, FWT, MET, MEWT, | Paris/Madrid |
+1:00, +2:00 (DST) | SWT | Sweden/Stockholm |
0 | GMT, UTC2 | Africa, Great Britain/London |
-1:00 | WAT | Cape Verde Islands |
-2:00 | AT | Azores Islands |
-2:00 | FST | Finland |
-2:00 | MEST, MESZ | Mid-Europe |
-3:00 | AGT | South America/Buenos Aires |
-3:00 | BET | South America/Sao Paulo |
-3:30 | CNT | Canada/St. Johns |
-4:00 | PRT | South America/Caracas |
-5:00, -4:00 (DST) | EST, EDT (DST) | U.S./New York |
-5:00 | IET | U.S./Indianapolis |
-5:00 | ZP5 | U.S./Chesapeake Bay |
-6:00, -5:00 (DST) | CST, CDT (DST) | U.S./Chicago |
-6:00 | ZP6 | U.S./Chesapeake Bay |
-7:00, -6:00 (DST) | MST, MDT (DST) | U.S./Denver |
-7:00 | PNT | Pacific/Pitcairn |
-8:00, -7:00 (DST) | PST, PDT (DST) | U.S./Los Angeles |
-9:00, -8:00 (DST) | AST | U.S./Anchorage |
-9:00, -8:00 (DST) | YST, YDT (DST) | Canada/Yukon |
-10:00 | AHST, HDT, HST | Hawaii/Honolulu |
-11:00 | MIT | Pacific/Asia |
-11:00 | NT | Alaska/Nome |
-12:00 | IDLW | International Date Line West |
-13:00 | NZDT | New Zealand/Wellington |
| 1DST = Daylight Savings Time 2UCT = Coordinated Universal Time |
The section contains notes and caveats for Resource Manager Essentials, as follows:
| ID | Summary | Explanation |
|---|---|---|
None | Cisco Voice Manager | Cisco Voice Manager cannot coexist with Essentials on one machine. Install Cisco Voice Manager on a different machine. |
None | Printing from a browser does not work | 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 on NT and Sol | In Navigator 4.6.1, the VM leaks memory in proportion to the number of classes loaded by an applet. To work around this problem, close your browser. |
CSCdk18245 | Clearing cache | If you are upgrading your software, it might be necessary for you to clear your browser cache file to display the login frame. If you are running Netscape Navigator on a PC, select Edit > Preferences > Advanced > Cache. From the Cache window, choose the option to clear your cache memory. If you are running Internet Explorer on a PC, select View > Internet Options > General > Temporary Internet File > Delete Files. |
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. |
CSCdp00679 | The time in Who Is Logged On? menu does not reflect the user's setting | To make sure that the CiscoWorks2000 system recognizes date and time zone changes, restart the system. Procedure Step 1 Click Start > Settings > Control Panel Step 2 Double-click Services Step 3 Highlight the CiscoWorks2000 Daemon Manager and click Stop, then highlight the Daemon Manager and click Start. |
CSCdp08278 | Tasks may fail if server is not 100% up | At the beginning of a CiscoWorks2000 session, if you select a task from the CiscoWorks2000 navigation tree before the server is running fully, the task might fail. To work around this problem, try selecting the task again. If this does not help, then restart the system by one of these two methods:
|
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 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. |
| ID | Summary | Explanation |
|---|---|---|
CSCdp05515 | After Essentials uninstall, JRM does not remove NetConfig jobs | If you uninstall Essentials, jobs from the NetConfig application might still be displayed under CiscoWorks2000 Server > Administration > Job Management. To work around this problem, after reinstalling or uninstalling Essentials, remove any residual jobs by selecting the unwanted job and clicking Remove. |
CSCdp19747 | Essentials 2.x to 3.0 upgrade | When you upgrade Essentials 2.x to 3.0, 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. Refer to Installing and Setting Up Resource Manager Essentials on Windows NT for further important instructions before proceeding. To upgrade your Essentials 2.x 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. To run the script manually, enter: \set NMSROOT={your CiscoWorks2000 install directory} %NMSROOT%\bin\perl%NMSROOT%\conf You must insert a space between -I and the backup directory value. If you run bg2rigel.pl without the -I option, the program tries to install the information about incremental device support (IDS) in the database, which causes failure and many errors if the IDS is already in the database. Also, failure and multiple errors occur if you run the script without the -I option more than once. If your upgrade fails, follow instructions in Installing and Setting Up Resource Manager Essentials on Windows NT. |
| ID | Summary | Explanation |
|---|---|---|
None | Error message during restore: | This problem is an error from the .tar file in the restore log. You can ignore this message only if the error is reported against the subdirectories that the .tar file creates during restore. This error is valid if the .tar file reports an error for the files it is restoring. The working directory should be the _root_ directory on the drive where CiscoWorks2000 is installed, not the CiscoWorks2000 directory itself. The default directory for CiscoWorks2000 is To work around this problem, enter the following command at the DOS prompt: perl c:\Program Files\CSCOpx\bin\ |
CSCdm82725 | Error Message in Delete Change History: The Job Scheduler failed to schedule the requested job | If you schedule a job with an option other than Immediate, you get an error message. The job is not scheduled. |
CSCdm83547 | Restore function is not working | To work around this problem, look at the restorebackup.log file and look for the file that indicates a permission denied error. Either change the property of this file to be writable by deselecting the read-only box in the file properties, or simply delete the file. You can then restore the database. |
| ID | Summary | Explanation |
|---|---|---|
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 report shows 100% TCP/IP use for Catalyst 500 switches. To work around this problem, launch the Protocol Distribution report directly from under the Availability menu. The application recognizes that no views are configured for Protocol Distribution monitoring. |
| ID | Summary | Explanation |
|---|---|---|
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 to the Essentials inventory. |
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" sign (>) or the pound sign (#.) The accepted, standard device prompts on Catalyst devices end with the keyword "enable" at the Telnet enable mode. |
None | Devices with multiple IP addresses | If you use the hostname in the inventory database for device management, the TFTP transport mechanism might not work for devices with multiple IP addresses. The SNMP library used by the TFTP transport mechanism queries for only one IP address for a given hostname while performing hostname resolution with the corresponding domain name server. For a device having more than one IP address, the hostname resolution might not always return the IP address of the interface running the SNMP agent. In such cases, the TFTP mechanism fails with an SNMP Time Out Error message. To work around this problem, import devices using the IP address in the inventory database. |
CSCdp10476 | CMLogger/Corba exception if config tasks can't write messages | If you try to write debug messages to the log file, Essentials tasks might fail. To work around this problem, perform the action again. In rare cases, you might have to restart the Daemon Manager. |
| ID | Summary | Explanation |
|---|---|---|
None | 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 in the database. To preserve this support: Step 1 Stop Essentials. Install a backup database, if you have one; otherwise, install the basic database, px.db, over your corrupt database.
Step 2 Back up or rename the corrupted database files:
Step 3 Install the basic database files: |
CSCdk35153 | Chassis modem table is not polled correctly | Inventory reports show only configured modems. An interval exists between the time that a modem is physically installed in a chassis and the time that it is configured for use. During this interval, the Essentials Inventory application might detect only one modem. Additionally, log messages might display database integrity violations. These messages can be ignored. To work around this problem, go to the device and configure the modem for use, then reacquire the inventory data for the device. |
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 being 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. |
CSCdm18668 | Inventory change filter incorrectly shows the serial number field twice in the "Stack Module" and "Cisco Stack" tables | If you select both serial number field entries, the applet generates an exception and the inventory change filter will not work. To work around this problem, select only one serial number entry. The applet is slow to load. Sometimes it takes more than 60 seconds for the GUI to appear. |
None | IP address may change between reboots | 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, and the IP address might change between reboots. |
None | PIX Firewall device | To configure the PIX Firewall device on your SNMP server host so Essentials can manage it, enter the server name and IP address of your Essentials workstation. |
CSCdm18668 | Inv Change Filter GUI fails if both serial number items checked | If you select both serial number entry fields, the applet generates an exception. Then the inventory change filters do not work. To work around this problem, select only one serial number entry. The applet is slow to load---sometimes it takes more than 60 seconds for the GUI to appear. |
CSCdm75952 | User Field is not saved when apostrophe is used | After selecting Essentials > Administration > Inventory > Change Device Attributes, then selecting a device and clicking, select User Fields. Do not use special characters such as apostrophes, semicolons, or parentheses in these fields. |
CSCdp28565 | Scan history shows in neg. number when Daylight Saving occurs | If you select Essentials > Inventory > Scan History to view the duration record for an inventory collection during the change to either Daylight Savings Time or Standard Time, the time it takes to complete the inventory collection is displayed incorrectly. However, the inventory collection works correctly. |
| ID | Summary | Explanation |
|---|---|---|
CSCdm79181 | DOS prompt window appears | If you are using a Windows NT as client and server, a DOS prompt window might flash on the screen after the system is installed or restarted. You can ignore this prompt. |
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 be designated a NetAdmin, NetOp, or SysAdmin in addition to being an Approver. |
| ID | Summary | Explanation |
|---|---|---|
None | MultiSwitch Feature Card for Catalyst 6000 and RouterSwitch Feature Card for Catalyst 5000 | Backup of current images during image distribution fails for MultiSwitch Feature Card for Catalyst 6000 devices and RouterSwitch Feature Card for Catalyst 5000 devices. Images running on these devices cannot be imported using 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 Cisco 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 include 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 device fails | When a Cisco IOS image is downloaded to the slot0 flashcard 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 Cisco IOS image. |
CSCdm78469 | CCO Upgrade Analysis task might 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. |
CSCdp19474 | Essentials unable to delete job after upgrade | Do not attempt an upgrade from Essentials 2.x to 3.0 if you have any Software Image Management jobs running or pending in Essentials 2.x. Wait for the jobs to be completed or cancel them before upgrading your system. |
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 Essentials > Software Management > Library > Add Images. PVC Traffic Shaping image file names follow the c5atm-wbpvc.* file format. These images are not available using the Add Images option. 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. |
| ATM Module upgrades on Catalyst switches (continued) | Token Ring LANE software image version umbers start from 70.1(1) and the image filenames 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.) |
|
| LANE ATM software on these modules include Ethernet LANE, Token Ring LANE and PVC Traffic Shaping features. While importing these software images to the library from the File System/Device, enter 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 the 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. See Table 3 for further information. |
| Filename | Software Management | Show Module Command Version |
|---|---|---|
c5atm-wtall_113-2_WA4_3.bin | 4(3) | 11.3(2)WA4(3) |
c5atm-wtall_113-2a_WA4_4b.bin | 4(4b) | 11.3(2a)WA4(4b) |
c5atm-wtall_113-3a_WA4_5.bin | 4(5) | 11.3(3a)WA4(5) |
c5atm-wtall_113-4_WA4_7a.bin | 4(7a) | 11.3(4)WA4(7a) |
| ID | Summary | Explanation |
|---|---|---|
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. |
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:
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: Tue Feb 29 15:57:01 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.