|
|
These release notes describe the caveats for the Solaris version of the CiscoWorks2000 family of products. The supported versions are 2.6 and 2.5.1. This document contains the following sections:
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdm06596 | Changing time zones | Changes made to the system Time Zone from outside of Y2K Compliance Assessment Tool applications (for example, by changing the Time Zone in the Windows NT Date/Time control panel, or changing the information in the Unix /etc/TIMEZONE file) might not be reflected in already running Y2K Compliance Assessment Tool applications. After changing the system Time Zone, users should restart all Y2K Compliance Assessment Tool applications. |
The Y2K Compliance Assessment Tool utilizes the Java 1.1.6 Run-Time Environment and Perl 5.002 interpreter for report generation. There are several limitations with these subsystems that have been uncovered, related to timezone processing. These limitations include:
Because of these limitations, only a certain set of timezones will be supported on Solaris and Windows NT.
Table 1-1 represents the timezones that are supported by the Y2K Compliance Assessment Tool on Solaris.
The Y2K Compliance Assessment Tool supports the devices listed in Table 1-2.
| Routers | Devices Supported | Inventory Manager | Minimum Software |
Cisco Universal Broadband Routers | UBR7223, UBR7246 | Supported | IOS 11.03 |
Cisco 7000 Series1 | 7000, 7010, 7200, 7204, 7204VXR, 7206, 7206VXR, 7505, 7506, 7507, 7513, 7576 | Supported2 | IOS 11.1 |
Cisco 4000 Series | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M | Supported | IOS 11.03 |
Cisco switching access concentrator | MC3810 | Supported | IOS 11.03 |
Cisco 3600 Series | 3620, 3640 | Supported | IOS 11.3 |
Cisco 2600 Series | 2601, 2610, 2611, 2612 2620, 2621 | Supported | IOS 11.3 |
Cisco 2500 Series4 | 2500-2525, 2501CF, 2502CF, 2501LF, 2502LF | Supported | IOS 11.03 |
Cisco 1700 Series | 1720 VPN | Supported | IOS 12.0 |
Cisco 1600 Series4 | 1601, 1602, 1603, 1604, 1605 | Supported | IOS 11.2 |
Cisco 1000 Series | 1000, 1003, 1004, 1005, 1020 | Supported | IOS 11.03 |
Cisco 800 Series | 801, 802, 803, 804 | Supported | IOS 12.0 |
Cisco 700 Series | 761, 762, 765, 766, 771, 772, 775, 776 | Supported | 4.1 |
| Access Servers | Devices Supported | Inventory Manager | Minimum Software |
Cisco AS5000 Series Access Servers5 | AS5200, AS5300, AS5800 | Supported | IOS 11.03 |
Cisco 2500 Series Access Servers4 | 2509RJ, 2511RJ | Supported | IOS 11.03 |
| Switches | Devices Supported | Inventory Manager | Minimum Software |
Catalyst 8500 MSR Series | 8510 MSR, 8540 MSR | Supported: 8540 MSR | IOS 11.2 (8.0.1) FWA4.1 |
Lightstream Series | Light Stream 1010 | Supported | IOS 11.2 (8.0.1) FWA4.1 |
Multiservice switch | BPX 8620, BPX 8650, IGX 8410, IGX 8420, IGX 8430, MGX 8220, IPX 8xxx | Supported | 8.4 |
Catalyst 8500 CSR Series | 8510 CSR, 8540 CSR | Supported | IOS 11.3 |
Catalyst 6000 Series | 6006, 6009, 6506, 6509 | Supported | 5.1(1)CSX |
Catalyst 6000 Series | WS-X6302 | Supported | IOS 12.0 |
Catalyst 5000 Series6 | 5000, 5002, 5500, 5505, 5509 | Supported | 2.4.3 |
Catalyst 5000 Series | WS-X5302 | Supported | IOS 12.0 |
Catalyst 4000 Series | 4003, 4912G | Supported | 4.4(1) |
Catalyst 3900 Series | 3900, 3920 | Supported | 3.0(2) |
Catalyst 3000 | 3000, 3100, 3200 | Supported | 2.2.2 |
Catalyst 2900 Series | 2901, 2902, 2926, 2926G, 2948G | Supported | 2.4.3, [2926G 4.3(0.31)], [2948G 4.4(1)] |
Catalyst 2900XL Series | 2908XL, 2916M-XL, 2924XL-V, 2924C-XL-V, 2912XL, 2924M-XL, 2912MF-XL, 2924XL, 2924C-XL | Supported | IOS 11.2 (8) SA5 |
Catalyst 2800 Series | 2822, 2828 | Supported | 8.0 (Enterprise) |
Catalyst 1900 Series | 1912, 1924 | Supported | 8.0 (Enterprise) |
Catalyst 1200 Series | 1201, 1202, 1211, 1212, 1220 | Supported | 4.29 |
| SwitchProbe and Network Analysis Modules | Devices Supported | Inventory Manager | Minimum Software |
LAN SwitchProbes | Ethernet, Token Ring, FDDI, Fast Ethernet | Supported | 4.2.1 |
WAN SwitchProbes | FR, ATM, HSSI | Supported | 4.2.1 |
WAN SwitchProbes | Multi-port WAN | Supported | 4.2.2 |
Network Analysis Module | Catalyst 5000 module | Supported | 4.3 (Catalyst) |
| Hubs | Devices Supported | Inventory Manager | Minimum Software |
Workgroup concentrator | 1000, 1100, 1400 | Supported | Not Applicable |
FastHub | 300, 100+, 316T, 3116, 316C, 2116, 216T, 116T, 116C, 1116 | Supported | Not Applicable |
MicroHub | 1502, 1503, 1516 | Supported | Not Applicable |
General SNMP devices | Most MIB II compliant | Supported | Not Applicable |
| 1Software Management: Cisco 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. 2The Cisco 7576 router has not been tested for support. 3IOS 10.3 may work, however it is not Year 2000 compliant. 4Software Management: Dual Flash bank and single Flash bank. 5Software Management: Dual 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. 6Software Management: Supervisor I, II, III, ATM, FDDI, CDDI, and Token Ring Gigabit Ethernet Switch, Route Switch modules on Catalyst 5000 and 5500 series devices. |
This section contains notes and caveats for the Y2K Compliance Assessment Tool, as follows:
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | The Y2K Compliance Assessment Tool web server not supported | Using the web server to support software not installed by the Y2K Compliance Assessment Tool is not supported. |
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 the Y2K Compliance Assessment Tool. |
None | Printing from a browser does not work reliably | To print an exact copy of a screen, use the Print Screen or Capture Screen function on your machine. |
CSCdk17516 | Browser accepts only certain cookies | When using Netscape Navigator or Microsoft Internet Explorer, you might encounter a situation in which the Y2K Compliance Assessment Tool returns you to the Login screen when you select an option. If this occurs, configure your browser to accept all cookies.
|
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, select Edit > Preferences > Advanced > Cache. From the Cache window, you will see the option to clear your cache memory. If you are running Microsoft Internet Explorer, select View > Internet Options > General > Temporary Internet File > Delete Files. The login dialog is not shown after you upgrade your version of Internet Explorer. The workaround is to flush your browser cache. |
None | Microsoft Internet Explorer 4.01: Times out after 5 minutes. | Microsoft Internet Explorer times out after 5 minutes while performing Y2K Compliance Assessment Tool operations, especially those involving CCO transfers. Refer to article number Q181050 on the Microsoft support Web Site for the resolution. |
CSCdk33035 | Microsoft Internet Explorer 4.01: Cookie error if multiple Internet Explorer applications point to different Y2K Compliance Assessment Tool servers | The Y2K Compliance Assessment Tool depends on cookies to transmit permission-related information. If multiple copies of Microsoft Internet Explorer are opened for use with the Y2K Compliance Assessment Tool on the same desktop by launching them from the Start > Programs > Internet Explorer interface or from an icon on the desktop, Microsoft Internet Explorer generates incorrect authorization failures when you are correctly logged in. To work around this problem, start new browser windows using the New option from within the browser. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdj64037 | Aborting the Y2K Compliance Assessment Tool installation procedure | If you abort the installation procedure before it completes, not all required components are installed, and the Y2K Compliance Assessment Tool will not operate successfully. To recover from an aborted installation, start the installation procedure from the beginning. |
None | The Y2K Compliance Assessment Tool installation is unsuccessful. | The Y2K Compliance Assessment Tool will not install correctly if the gzip command as it is described in the Readme file is used. The workaround is to use the UNIX gzip command to unzip the file. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Starting the Y2K Compliance Assessment Tool as root | If you start the Y2K Compliance Assessment Tool by logging in as root and entering the following command at a command-line prompt # /etc/init.d/dmgtd start
Make sure that you do not suspend the root session using the suspend command. If you suspend the root session after manually starting the Y2K Compliance Assessment Tool, other processes such as the Daemon Manager, DIServer, and IcServer are also suspended. To resolve this issue, unsuspend the root session, and the processes restart normally. |
CSCdm18493 | Database move script does not check directory | The database move script, To work around this problem, make sure that the new path to the database files is different from the current location. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk35153 | Chassis modem table is not polled correctly | For devices that support the CISCO-MODEM-MGMT-MIB (for instance, AS5x00 access servers), there is a time interval between the time when a modem is physically installed in a chassis and the time that the modem is configured for use. During this time interval, Y2K Compliance Assessment Tool Inventory might detect only one of the modems. Additionally, log messages might display database integrity violations; however, 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. |
CSCdk10221 | Incorrect flash memory value in hardware report | When devices such as the Cisco 2500 series routers are configured to partition Flash memory into two Flash partitions, the Y2K Compliance Assessment Tool might report the value of the first partition as the value of both partitions added together, then place that value in the Flash memory field. Check the router running configuration file using the show run command from the enable prompt (Router#) to verify Flash partition information. You can use the partition flash command to modify Flash partition. Refer to the command reference document for additional information. To work around this problem, run the Detailed Device Report. This report shows details about each Flash partition that was discovered when the router was added to inventory. |
None | Setting inventory collection for the year 2001 conflicts with Device Discovery. | Do not schedule inventory collection for the year 2001. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk01464 | Shutting off DNS resolution | The Y2K Compliance Assessment Tool import of IP addresses will sometimes hang if DNS resolution of the IP address does not work. To work around this problem, perform the following steps: Step 1 Add IP addresses in the local hosts file. Step 2 Fix the DNS so that reverse name lookups work. |
CSCdj60284 | IP-SNMP gets 94% CPU when polling ciscoFlashPartitionTable | A defect exists in certain versions of Cisco IOS that causes the SNMP agent on router devices to become unresponsive to SNMP queries when certain MIB variables are polled. This bug only exists on routers that support the CISCO-FLASH MIB, which includes the following routers: Cisco 7200 series, 7500 series, RSMs (the router card for 5xxx switches) and 7000 series with RSPs. 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. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Cannot add IP addresses to list box | Netscape Navigator and Internet Explorer will not allow you to add IP addresses to a list box unless the addresses are valid. |
None | After a reboot or power failure, discovery status may be reported incorrectly as running | The workaround is as follows: Step 1 Select Admin > Device Discovery > Start/Stop. Step 2 Click the radio button to stop device discovery. Step 3 Click the radio button to start device discovery or to schedule it to start at a predefined time. |
None | Cannot select a higher number than 48 in the Minutes selection box in the Start or Stop Discovery dialog box. | This only occurs on Netscape Navigator, and there is no workaround. It will be corrected in the next release. |
None | Able to select only the current month in the selection box in the Start or Stop Discovery dialog box. | This only occurs on Netscape Navigator. The workaround is to only schedule jobs for the current month. It will be corrected in the next release. |
None | Digits in the Year selection box in the Start or Stop Discovery dialog box are only partially visible. | This only occurs on Netscape Navigator. The workaround is to click Next, and then Back. |
None | May is the first month displayed in the selection box in the Start or Stop Discovery dialog box. | This occurs on both Netscape Navigator and Internet Explorer. The workaround is to move the cursor to the top of the list, and then complete list, beginning with January appears. |
CSCdi11581 | Routers running IOS version 8.2 might crash during device discovery. | An snmpget or snmpwalk to an unimplemented SNMP variable causes routers to crash. |
CSCdk30160 | Routers running IOS versions 11.2(08)SA3, 11.3, 11.3T, 11.3NA and 11.3WA4 might crash. | Routers might crash when trying to get a CDP-enabled device's address if no IP address is assigned to the device. |
CSCdi69892 | Device discovery can cause % SYS-3-CPUHOG messages. | On some routers, SNMP GetNext requests performed on the CISCO-CDP-MIB can cause a device to pause for an extended length of time. During that time, packets might not be forwarded by the router. This problem occurs with RSP4 images in IOS versions 11.1, 11.1CA, 11.2, and 11.2F |
CSCdj83870 | Device discovery can cause false access messages | Walking the CDP MIB can cause routers with many CDP-enabled neighbors to log false access messages. The messages do not indicate a serious problem. |
None | WAN switching devices are not discovered. | The workaround is to use the Y2K Compliance Assessment Tool Release 1.0.1. To verify what version you are running, select Home > About Y2K Compliance Assessment Tool > Copyright and Versions. If you are not running the correct version, download Release 1.0.1. |
Posted: Thu Sep 30 16:09:27 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.