|
|
These release notes describe the known problems for the HP-UX server version of CiscoWorks2000 CD One 2nd Edition.
These release notes provide the following information:
For information about CD One 2nd Edition supported devices, refer to:
Table 1 lists the time zone acronyms which are supported in the CiscoWorks2000 applications that use the time zone feature. The first column alphabetically lists the CiscoWorks2000 time zone acronyms supported. These time zones might not be supported by all CiscoWorks2000 applications. The following columns lists their definitions and area covered, their offsets from the Greenwich Mean Time (GMT), whether or not they are supported on the HP-UX server, as well as the resulting output in reports if the time zone is supported. Should you be generating reports, outputs will vary depending on if the data has been processed through Perl or Java. Table 1 also provides the possible outputs for either case scenario.
To make sure that time zones are translated correctly---especially when your devices, servers, and clients are in different time zones---follow these guidelines:
 |
Note Changes made to the system time zone from outside CiscoWorks2000 applications might not be reflected in already-running CiscoWorks2000 applications. After changing the time zone, restart all CiscoWorks2000 applications. |
1 Offset from GMT | 2 Area Covered (Country/City) | 3 Time Zone Setting on Server | 4 Output in Report | |
|---|---|---|---|---|
| GMT | Acronym | |||
+09:00, +09:30 +10:00, +11:00 | Australia | Brisbane, Melbourne | GMT - 10:00 GMT + Offset | EAST |
+9:00 | Japan/Tokyo | Tokyo | GMT - 9:00 GMT + 9:00 | JST |
+8:00 | China | Beijing | GMT - 8:00 GMT + 8:00 | CCT |
+3:00 | Cairo, Helsinki |
| GMT - 3:00 | BT |
+1:00, +2:00 | Central Europe |
| GMT +2:00 | AT |
-1:00 | Africa/Algiers |
| GMT -1:00, | CET |
-1:00 | Cape Verde Islands |
| GMT 1:00 GMT -1:00 | WAT |
-5:00 | U.S./New York | Eastern Time | GMT 5:00 GMT -5:00 | EST |
-3:00 | U.S./Buenos Aires | Central Time | GMT 3:00 GMT -3:00 | ADT |
-5:00, -4:00 | U.S./Caracas |
| AST 4:00 GMT -4:00 | AST |
-6:00, -5:00 | U.S./Chicago |
| CST 6:00 CDT, GMT -6:00 | CST |
-7:00 | U.S/Phoenix |
| MST 7:00 GMY -7:00 | MST |
-7:00 | U.S/Denver |
| MST 7:00 MDT, GMT -7:00 | MST |
-8:00 | U.S/ Los Angeles |
| GMT +8.00 GMT -8:00 | PST |
-9:00 | U.S/ Anchorag |
| YST 9.00 YDT, GMT -9:00 | YST |
-10:00 | Hawaii |
| GMT +10.00 GMT -10:00 | CAT |
-12:00 | New Zealand |
| GMT -12:00 | NZT |
Known problems are unexpected behaviors or defects in CD One 2nd Edition. They are graded according to severity level. These release notes contain information for severity levels 1 and 2 only.
You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II. To access Bug Navigator II, do one of the following:
Known problems are categorized in the following sections:
| Bug ID | Summary | Explanation | ||
|---|---|---|---|---|
CSCdr25407 | Cleaning up a broken install. | When an installation is cancelled before completion, or the uninstall fails to perform a complete cleanup subsequent installs may fail. In such a case, you need to clean up the CW2000 packages from the system and restart the install. Use the script 'fpkgdel.sh' which is available in the CD One CD under the install directory to perform cleanup.
| ||
CSCdm95087 | DNS server required for Campus Manager. | Campus Manager requires a DNS server to function properly. Many functions will operate erratically or not at all if there is no DNS server on the network. | ||
CSCdp94831 | Cannot always launch CiscoWorks2000 after the installation of CD One Second Edition. | After you enter /sbin/init.d/dmgtd stop, if any child process does not release port promptly, entering /sbin/init.d/dmgtd start will not start Daemon Manager, and following message is returned: To work around the problem, enter /sbin/init.d/dmgtd start until Daemon Manager starts. Make sure that all CSCOpx processes are stopped before running /sbin/init.d/dmgtd start. | ||
CSCdp96200 | CWSI database backup fails during upgrade to CD One. | If CWSI database is not in default location, move it before you upgrade to CD One. Otherwise, database will not be backed up during installation. To work around the problem: Stop CWSI and Essentials by entering: Copy database files from custom directory into the default directory, /opt/CSCOcwsi/db/data. | ||
CSCdr40548 | JRE on HP-UX require OS patches | HP recommends a set of OS patches to be installed when using JRE. Since CW2000 uses JRE 1.1.8 and JRE 1.2, it is advisable to install these patchesbefore you start the install of our product. PHCO_20765 PHKL_20202 PHCO_19666 PHKL_20016 PHKL_18543 PHCO_20882 (PHKL_21532, PHCO_19047, PHKL_21392, and PHKL_20674 are dependencies of PHKL_18543.) Go to the HP website for more information. Note Without PHKL_18543 and its dependencies, install of the product itself might fail. | ||
CSCdr14214 | Following error might be encountered during Integration Utility upgrade: java.lang.NullPointer Exception at com.cisco.nm.nmim.nmic. | Occurs during Integration Utility upgrade when option to integrate with CCO for integration data updates is not selected. New device information will not be added to your third party NMS. To correct problem, reintegrate using Change Integration Options utility after upgrade to CD One 2nd Edition is complete. At the command line, enter: cw2000-install-dir/bin/nmic.sh. Click Integrate in Choose Adapter dialog box. |
| Bug ID | Summary | Explanation |
|---|---|---|
None. | Log file location not supplied in other documentation. | The CiscoView log file can be found in the CiscoWorks2000 install directory located in /www/classpath/cv.log. The location of this log file is displayed in the CiscoView Administration Page located under Device Manager > Administration > CiscoView Server Admin > Setting debug options and display log. The client can also bring up a window to display the entries in the log file at real time through the administration page. Since this log file is on the server, it will contain trace and error messages for all the CiscoView clients. Trace and Error entries will be appended to the CiscoView log file on the server until the system administrator clears the log file explicitly through the CiscoView Administration page. |
CSCdk79655 | CiscoView displays incorrect values for variables grouped from two different tables having a common index. | None |
CSCdm11909 | CiscoView crashes when user attempts to modify a VISM card. | User entered a string of 192 or more characters in the SubNet Mask field. The same result is achieved when the sysNetMask field is set to a large string of characters in a Catalyst 5000 device. |
CSCdm13842 | CiscoView user has to play with close/open window to perform tasks. | None |
CSCdm51274 | When polling uses a large PDU, CiscoView doesn't seem to wait the expected "timeout" period before attempting the split-PDU retry. | When the first split-PDU attempt times out, the PDU is split again into one-fourths while the original response is still being processed. This problem is similar to CSCdk24025, but the problem here is with polled objects instead of dialog windows. |
CSCdm53849 | Launching a second CiscoView window from the desktop replaces the current CiscoView window. | When launching multiple CiscoView windows by clicking CiscoView, the new CiscoView window replaces the current CiscoView window, as opposed to opening a new window. This problem occurs only while using Internet Explorer |
CSCdm57814 | In Internet Explorer, the tab key does not work properly in User Preferences or TAC mailer option dialog box. | Pressing tab key in User Preferences dialog box or TAC mailer option changes focus but does not move cursor to next text field. |
CSCdp14240 | CiscoView mishandles ifTable entries for BRI from rfc2127. | When CiscoView attempts to open routers with BRI interfaces running 12.0(4)T (failure mode is identical with 1700s, 4000s, 7200s), it fails to open the device due to a failure to read information from cardTable. This is caused by the new behavior in 12.0T for ISDN. For rfc2127, the ifTable now has more entries for the BRI interface to represent the lower layers, and hence the strings used for ifDescr are not unique for the different layers. This is not prohibited by the RFC---the values for ifType are different, and Cisco View is apparently getting confused by seeing ifDescr "BRI0" multiple times, even though ifType is different for each layer. |
CSCdp14743 | It may take a long time to bring up a device view in certain cases. | Bringing up the chassis view of a selected device may take a long time. This may occur due to name service lookup failures when the device and/or the subdevices do not have name service entries. |
CSCdp41093 | Port config applet not opened when URL is typed. | Enter: http://server/CSConm/servlet/com.cisco.nm.cvw.servlet. This should open the specified device in CiscoView along with the specified port config applet. Instead the following error message appears: Unable to launch component dialog. Java.awt.illegalComponentStateException:component must be showing on the screen to determine its location. |
CSCdp51616 | ADP needs proper product name in about box. | None. |
CSCdp73744 | CiscoView returns can't read "DD(card-438.port.pos)": no such element in array error message when user attempts to open an MC3810 with a mc3810-mfm-e1 -unbalanced module installed (cardType 438). | None. |
CSCdp83822 | Device's About CiscoView dialog box continues to be displayed even after launching a new device. | With CiscoView running, click About to open About CiscoView dialog box for a device. Keeping dialog box open, enter new device name and IP address in Select Device field. About dialog box for previous device continues to be displayed, instead of closing when new device is launched. To access the About dialog box for new device, close previous device About dialog box. |
CSCdp84996 | Attempt to start telnet session in CiscoView returns the following error message: Cannot launch telnet. Java.io.IOException: | Problem occurs when Telnet session opened more than 10 times. To work around the problem, close and relaunch CiscoWorks2000. |
CSCdp91288 | Telnet window not launched from CiscoView on AIX clients. | Telnet does not work on an AIX client. This is because, Navigator uses it own proprietary library, libc.a, which does not handle Telnet protocol. To workaround problem:
Or
if test "${LIBPATH}xxx" = "xxx"
then
LIBPATH="${MOZILLA_HOME}/lib${OS_LIB}:${MOZILLA_HOME}:/usr/lib:/lib"
else
LIBPATH="${MOZILLA_HOME}/lib${OS_LIB}:${MOZILLA_HOME}:${LIBPATH}:/usr/lib:/lib"
fi
if test "${LIBPATH}xxx" = "xxx"
then
LIBPATH="${LIBPATH}:/usr/lib:/lib:${MOZILLA_HOME}/lib${OS_LIB}:$ {MOZILLA_HOME}"
else
LIBPATH="${LIBPATH}:/usr/lib:/lib:${MOZILLA_HOME}/lib${OS_LIB}:$ {MOZILLA_HOME}"
fi
|
CSCdr08822 | If a device dynamic view changes during rediscovery, the rediscoverDevice() | Problem occurs if hotswap changes device dynamic view. Reopen device to display correct view. |
CSCdr25387 | With Netscape in HPUX console, the button titles in CiscoView main window and labels in other dialogs are truncated and displayed with ellipsis | With Navigator on a HP-UX console, the button titles in CiscoView main window and labels in other dialogs are truncated and displayed with ellipsis. Workaround is to force Navigator to use certain small fixed fonts. This can be done by editing font.properties in $NETSCAPE_HOME/java/classes
helvetica.plain.0=-adobe-helvetica-medium-r-normal--*-%d-*-*-p-*-iso8859-1
helvetica.plain.0=-adobe-helvetica-medium-r-normal--10-100-*-*-p-*-iso8859-1 |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdm52416 | Can uninstall a package when the device is open. | When device is opened, Device Support Utility (DSU) is launched, and uninstall is selected, uninstallation continues without displaying necessary error message. |
CSCdp63879 | After device packages are upgraded through DSU, WebServer sometimes does not start. | If the web server does not start: As root, enter: cw2000-install-dir/CSCOpx/bin/ |
CSCdp94171 | Cannot open a device, nor find the applicable device package. | The web server was not restarted by DSU during device package installation. To work around the problem: As root, enter: cw2000-install-dir/CSCOpx/bin/ Enter cw2000-install-dir/CSCOpx/bin/ |
|
Note If you have problems using the online help, download the latest device packages from CCO. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdr11226 and CSCdr11320 | IP Permit and VMPS device configuration dialog boxes cannot be opened in Catalyst 2900 devices. | Problem fixed in latest Catalyst 2900 device package. If you have a problem with Catalyst 2900 device, download latest package from CCO. |
CSCdp75883 | Reset Action function from Scheduled Reset menu does not always work. | Reset Action function is available only for switches with redundant supervisor module. |
CSCdp96855 | MLS Included Routers table for a Catalyst 5500 device displays incorrect data. | When MLS Included Routers table is opened on a Catalyst 5500 device running CiscoView, table displays correct data and also 52 rows with N/A as the value. Click Create and following error message is returned: No more Router is allowed to be added. |
CSCdk24862 | With CiscoView running on a Catalyst 1924 device, the Port Zoom and Switch Zoom applications can't be launched from the RMON menu, and there is no corresponding error message. | The user should invoke CiscoView from CWSI in order to view the RMON menu and RMON icon. Also, the user can set the following environment variable (with the TrafficDirector base directory) to view the RMON menu, without invoking CiscoView from CWSI. |
CSCdp59117 | With all the components highlighted, selecting Show Channel from the FastEther dialog box returns the same name for different components. | This problem is caused by the lack of developer-specified component names distinguishing ports A, B, 1, and 2. Give ports A and B a name (via the KIND property), and the Application Programming Interface (API) should return different names for different components. |
| Bug ID | Summary | Explanation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
CSCdm71801 | Cable Modem Details dialog box lacks the functionality of its counterpart in CiscoView 4.2. | The following functionality is not available in the CiscoView uBR7200 device package:
| ||||||||
CSCdp08478 | Help is showing the "How to use help" page instead of the actual help page. | After launching CiscoView, open the Catalyst device. The help page does not appear for the following selections:
| ||||||||
CSCdp43480 | Format option is missing from PCMCIA pull down menu. | CiscoView 5.0 included both Configure and Format menu items. | ||||||||
CSCdk83147 | With CiscoView 4.2 running on a Catalyst 4000 device, the port utilization displays an incorrect value. | None | ||||||||
CSCdm04172 | With CiscoView running on a Catalyst 8540CSR device, running cat8540-c-in-mz.120-1a.W5.6 b.bin produces Mib errors. | The following errors are encountered:
| ||||||||
CSCdp62555 | Creating a VLAN on a Catalyst 4000 device returns an internal server error. | Modifying and deleting a VLAN produce the same error. | ||||||||
CSCdp61337 | Multiple port monitor charts display negative packet numbers. | While the property type is defined as integer, it appears that the value of these properties is the sum. | ||||||||
CSCdp74673 | CiscoView freezes on a Catalyst 4000 device when user attempts to run monitor process utilities on two components simultaneously. | With the monitor process utilities already running on one component, launching the monitor dialog with a second component selected returns a blank error dialog box. At this point CiscoView freezes, so both the CiscoView and CiscoWorks2000 browsers need to be closed. | ||||||||
CSCdp62231 | With CiscoView running on a Catalyst 5000 device, the fast ethernet port interface monitor report displays N/A in all fields. | None. | ||||||||
CSCdp86817 | With CiscoView running on a Catalyst 5000 and 5500 device, selecting Device > Configure > Boot Flash Memory returns following error message: | This problem might be caused by outdated classes that exist in your browser cache or classes that may have been corrupted. To work around this problem, try clearing your browser cache. The problem occurs only in Navigator browsers.
| ||||||||
CSCdp86512 | On accessing the Interface Type dialog box, the Capabilities column displays incorrect values. | With CiscoView running on a Catalyst 6000 device, the following steps produce the error:
| ||||||||
CSCdp78281 | User encounters error when attempting to create a new gateway on a Catalyst 6000 device running CiscoView. | The following actions result in the error:
| ||||||||
CSCdp66802 | Opening the Catalyst 8500 device package with the latest ADD compiler returns Error: non-existing image IMAGE "item.gif" message. | The C8515_Composite.add file detects whether or not the item.gif file is included in a particular device package. The item.gif file is not included in the Catalyst 8500 package, resulting in the error. | ||||||||
CSCdp33295 | CiscoView can't recognize Ethernet PAMs in Catalyst8540 devices. | The SNMP trace clearly shows that the Ethernet PAMs in slots 11 and 12 are unknown. It appears that there is a problem with the image. | ||||||||
CSCdm80003 | CiscoView is unable to monitor ports on Catalyst 6000 devices running SW 5.2(2). The Monitor Ports panel returns the following error message: The Mibs are not supported by the device. | CiscoView 4.2(1.0) is unable to monitor Ethernet ports on Catalyst 6000 devices running SW 5.2(2) because the SNMP ifXTable variables are only accessible by SNMP v2c queries, and the Monitor Ports panel sends SNMP v1 requests. | ||||||||
CSCdp32979 | User runs into difficulty uninstalling the 800 device package. | On a system where all the device packages are present, the uninstallpkg script will not uninstall the 800 device package as expected. The script first removes the 3800 device package. On consequent runs, it uninstalls the AS5800, Catalyst 1800, Catalyst 2800, and finally the 800 device package. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdr12561 | GSR12008 device displays power supply in the wrong slot. | When GSR12008 device has power supply in upper slot (slot 24), power supply incorrectly displayed in slot 25. |
CSCdp94674 | Starting StackMaker from CiscoView on a 1900 series device results in error message. | Problem observed in 1900 series device with Layer-2 topology. With CiscoView running, start StackMaker. Following error message is displayed: Unable to display this category group. java.lang.NULLpointer.exception. Click OK to clear error message, and StackMaster starts. |
CSCdp51779 | Set Managers Address does not appear. | In the Set Managers Table category in the device configuration dialog box of the FastHub400 device package in CiscoView 5.0, when a Set Manager needs to be added an entry should be made in the set Managers Table with the Set Manager's address as the index of the entry along with the row status. The entry should be made in a single request. Similarly, in the Trap Managers Table category, when a Trap Manager needs to be added an entry should be made in the Trap Managers Table with the Trap Manager's address as the index of the entry along with the community string of the manager and the row status. The entry should be made in a single request. |
CSCdp49010 | With CiscoView running on a 1516 device, the configuration dialog box disappears. | If the user moves the configuration dialog box to the left side of the screen far enough to conceal the majority of the box, and then selects IP Information from the Category menu, the box disappears. Double click on the chassis view and notice that the configuration dialog box is not relaunched. |
CSCdp81621 | With CiscoView running on a 2600 series device, the BRI port displays negative values in the monitor dialog box, and displays N/A as the values in the configuration dialog box. | None. |
CSCdp35199 | When user attempts to access help from a 700 series device, a URL not found error message is returned. | Reload help, and an empty page is displayed. Normal state is recoverable only by opening a new browser. |
CSCdp79841 | The Type 240 card (pa-a4t) is not supported in the 7000 series 5.0 device package. | None. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdm91793 | The 12000 series device package displays a wrong view of the GSR router. | The slot numbering is incorrec, and it does not display some boards. There are no "unsupported" messages shown, and the CSC boards are not displayed, either. |
|
Note The file NMIDBOptions.properties contains CCO passwords, in an encoded form, and is accessible only to root users. Root access to the host needs to be restricted if CCO password security is a concern. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | If you install the Integration utility 1.1 on a machine running CiscoView 4.x with your NMS, the utility does not integrate MIBs into the NMS. | If you uninstall CiscoView 4.x, however, the Integration utility will integrate MIBs into the NMS. To avoid compilation errors as MIBs are integrated, unload the old MIBs before running the utility. |
CSCdp90186 | After integration, if CiscoView 5.x is launched twice from the HP OpenView Network Node Manager, one of the following error messages are displayed: Issuer certificate is invalid. java.lang.security exception: system classes were not signed. | This problem happens occasionally when a Navigator browser is opened by anyone other than installer. To correct problem, log in as root and reinstall. Also verify that $HOME system variable is set properly. |
CSCdp89456 | Null pointer exceptions occur when browse button is clicked. | If you select Change Integration Options and click Browse in any window, error messages might be displayed. You can ignore them; they do not affect user operations. |
CSCdp90728 | In Unix platforms, when the Update Cisco Device Support task is run from the Network Node Manager (e.g. HP OpenView), generated messages are not displayed. | Go to window from which OpenView was started to view generated messages. |
CSCdm61980 | Cannot launch CiscoView by double-clicking device icons in NMS after integration. | Some NMS adapters do not support double-clicking of device icons from the topology map. Even if CiscoView is set as the default application (using Change Integration Options), it might not be invoked by double-clicking a device icon. |
None. | The integration currently done with Network Node Manager (NNM) 6.0 to integrate MIBs, icons, and application registration will not be visible to web clients of NNM, and is not supported in this version of Integration Utility. | Users accessing NNM through a web browser may not see the integrated information. |
CSCdm91445 | Application registration change causes full integration if you run Change Integration options and change the application parameters only (such as browser, server and port number) and integrate. | This causes MIB, icon and application integration instead of application registration. To perform application integration, you should: Step 1 Run the Change Integration option. Step 2 Change the application registration. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdp40303 | Configuration changes are not saved to a device's NVRAM. | Configuration changes are made only while device is running. If device is accidentally shut down, all changes are lost. To avoid problem, open Telnet session to device and save configuration changes by entering write mem from command line interface. |
CSCdp73016 | Topology Services might not pick up router names correctly. | To avoid problem, open nsswitch.conf file and make sure that hosts: is followed by files dns. |
CSCdp42333 | If a device's IP address is changed, the ANI server may not detect the change. | Device continues to show old IP address after one or more discovery cycles. It is marked as unreachable or unmanaged. To work around the problem, delete device and rediscover. |
None. | OamPing hardware requirements for a LS1010 device. | In LS1010 device, support for OAM on VP tunnel exists for:
To determine controller type, enter sh hardware in command line interface and refer to cntrl_type field. |
None. | 8540MSR device does not allow you to ping an NSAP address. | You can ping an NSAP address from LS1010 device. |
None. | Multilayer Switch Module (MSM) does not have MIB to support half/full duplex on Gigabit ports. | MSM is displayed as unknown-duplex for those ports in Campus Manager. |
CSCdp40584/CSCdp87405 and CSCdp77632/CSCdp68368 | When SNMP is used for Ethernet VLAN creation in a network, the VTP mode on Catalyst 5000 and 2948G devices change from transparent to server. | Fixed in Catalyst OS versions 3.2(9), 4.5(6), 5.2(4), 5.4(1), and later. Before creating VLANs in a network, make sure devices are running one of these releases. |
CSCdp29954 | Any value set for oamLoopbackPingDelay does not create any effect on a Catalyst 8540 device. | Delay parameter does not work for OamPing. |
CSCdp69373/CSCdp52126 | ANI server does not cover spanning tree states of Gigabit EtherChannel groups if device is running a Catalyst OS that precedes version 5.4(1). | Problem fixed in Catalyst OS version 5.4(1) and later releases. |
CSCdp51564/CSCdp41757 | An empty virtual circuit list is returned by two LS1010 devices, even when a virtual circuit exists between those devices. | Running SNMP query on ciscoAtmSvcAddrTable returns empty table for devices. Problem observed in LS1010 devices running Cisco IOS Release 12.0. |
CSCdm91634 | In Campus Manager device report, number of ports in a device's ATM module is incorrectly displayed as zero. | Problem, observed in Catalyst 5000 device running Catalyst OS version 4.3(1a), is caused by missing ifEntry for device ATM module. ANI Server depends on ifEntry to determine number of ports in a particular module. |
CSCdm58624 | LANE trunks are not considered when determining a VTP disconnected domain discrepancy. | Ignore discrepancy. If VTP domain spans across ATM cloud and default ATM-VLAN is configured to carry VTP advertisements across cloud, domain is still displayed as disconnected domain discrepancy due to lack of support. |
CSCdm48015 | An ATM trunk port is shown as belonging to a VLAN, even if there is no corresponding LANE client associated with that VLAN. | In VLAN-to-port association, all ATM ports on switches (except ATM switches) belonging to VLAN will be displayed. Ignore ATM ports in VLAN-to-port association. |
CSCdp51864 | Trunk attributes are not shown for an RSM-switch trunk. | Trunk attributes not reported for router links due to lack of MIB support. To avoid problem, use command line interface to access trunk attributes for router ports. |
CSCdp78944 | When an Ethernet VLAN is converted into a Token Ring Crf VLAN via the command line interface without deletion, it is no longer recognized by the ANI server. | To avoid problem, delete Token Ring Crf VLAN from command line interface, create a new one with same definition, and rediscover network. |
CSCdp90632 | When the Control Connections report is run from the LE Config Server menu in Topology Services, all the Peer hosts and ATM-VLAN fields are empty. | To work around the problem, assign appropriate non-zero value for ATM-VLAN entry in LECS database through command line interface. |
CSCdp36357 | FastEtherChannel link between a Cisco Catalyst 6000 and 8540CSR device is not discovered. | Catalyst 8540CSR device does not support PAGp MIB. |
CSCdp00593 | SNMP report displays | To avoid problem, enter show hardware in command line interface. |
CSCdp00534 | Catalyst 6000 device displays NULL port for module 3, port 11. | ifDescriptors of some modules not accessible by SNMP management. In User Tracking, active users connected to ports with missing ifEntry are not discovered. Occurs in Catalyst OS version 5.2(2) only and is fixed in version 5.2(3). |
CSCdp78464 | Sometimes ifSpeed is shown as zero for an ATM link connecting a Catalyst 5000 and LS1010 device. | None. |
CSCdm90878 | RSM link is shown as ISL trunk, but is not included in trunk report. | Caused by absence of VLAN-related MIB on router. |
CSCdp56060/CSCdp56066 | Virtual circuit trace does not work on a LS1010 device running Cisco IOS 12.0. | Cross-connect identifier returns -1 for virtual circuits 0/5 and 0/16, which prevents display of virtual circuit trace via SNMP. LS1010 devices running Cisco IOS 11.2 return correct values. Also, cross-connect information is properly displayed when accessed via command line interface. |
CSCdr15703 | In Device Synchronization, real-time device credential import to ANI from Essentials 3.0 does not work. | Real time device credential import uses event not compatible with Essentials 3.0. To enable, upgrade to Essentials 3.1. |
CSCdr15715 | In Device Synchronization, real-time device credential import to ANI from Essentials does not work unless it is enabled before ANI is started. | If real time device credential import enabled after ANI has already started, restart ANI. |
CSCdp36357 | FastEtherChannel link not discovered between certain devices, in this case the Cisco Catalyst 6000 and the 8540CSR devices. | The ANI server log indicates that the ports are all processed as part of the same topology group. |
CSCdp83733 | User is unable to access any of the ANI server administration options. | Selecting CiscoWorks2000 Server > Setup > ANI Server Administration > SNMP Settings returns the following error message: Verify you have read/write access to the anisnmp.conf file on the CiscoWorks2000 Server. A similar message is displayed when you try to access any of the options under the ANI server administration menu. |
None. | If ANI is restarted for any reason, a complete Discovery cycle will run. | ANI Discovery now runs on a fixed, user-configured, schedule (just like User Tracking Major Acquisition). However, a full complete Discovery (including User Tracking Major Acquisition) will run at every restart, regardless of whether or not the Fixed schedule shows it is time. |
CSCdp86051 | Mibinfo.dat file requires QPM specific MIB variables. | None. |
CSCdp75766 | Database update process is really slow. | Code has been written that utilizes prepared statements for writing to the database. Tests are being conducted to see if this improves performance and if it works correctly. |
| Bug ID | Summary | Explanation | ||||||
|---|---|---|---|---|---|---|---|---|
None. | Two additional user roles (Developer and Export Data) are displayed in the security user account windows. | They are not available for general use, only for Management Connection certification and third-party developers. | ||||||
None. | Parameter must be set using Netscape 4.61. | MOZILLA_HOME must be set to the Navigator installation directory. | ||||||
None. | Non-CiscoWorks2000 software is not supported. | The CiscoWorks2000 Server does not support software that is not included in the CiscoWorks2000 family of products. | ||||||
None. | Without CAM installed, you might encounter slow response times from Campus Manager applications while a virus checker is running. | Disabling virus checker might improve Campus Manager application response times. | ||||||
None. | Netscape 4.61 sometimes leaves a process running after browser is closed. | Sometimes one Navigator 4.61 process continues running after the browser is closed. Any attempt to restart the browser while the process is running causes problems with the new browser window. To avoid this problem: Step 1 Open Task Manager. Step 2 Search process list for all instances of netscape.exe. Step 3 Select them with mouse and click End Task Step 4 Restart Navigator. | ||||||
None. | Table of contents or index does not appear in online help. | If table of contents or index does not appear in online help, hold down Shift key and click Reload. | ||||||
CSCdp87124 | If the LDAPLoginModule is being used to authenticate users, the LDAP server must be configured to deny anonymous access to the directory where CiscoWorks2000 resides. | Unless LDAP server is set up to deny anonymous access, it authenticates any username entered without a password. | ||||||
CSCdr29960 | Cannot launch applets if graphics display is set incorrectly | On an HP-UX console, if the graphics display is not configured with appropriate values the following problems are observed
To work around the problem, set the graphics display to the values mentioned below:
| ||||||
CSCdp42241 | Upgrade from BG 2.X not retrieving user information. | When CiscoWorks2000 (Essentials 2.0 and CWSI Campus 2.2) is upgraded to CD One and Campus Manager, user information (username, password, and other profile information) is not transferred to the upgraded system unless Essentials is already installed. If problem occurs, manually reenter existing user information in Add Users dialog box. Select CiscoWorks2000 Server > Setup > Security > Add Users. | ||||||
CSCdm93875 | Print on Configuration dialog box in CiscoView prints blank pages instead of configuration details. | To work around the problem, print screen captures of configuration details. | ||||||
CSCdp53054 | Unable to paste text into CiscoView device selection combo box. | Following message displayed in Java console: Security exception - Clipboard access denied. | ||||||
CSCdp74251 | Application performance very slow with HTTP proxy. | Accessing Campus Manager via HTTP proxy might cause significant performance degradation. To work around the problem, access CiscoWorks2000 Server directly from client. | ||||||
CSCdp95045 | Internet Explorer and Navigator do not always operate correctly when CAM is installed on Windows 95 and 98 clients. | Some applications do not launch as expected To avoid problem, do not install CAM. | ||||||
CSCdr06886 | Configuration Editor cannot be launched from system running Internet Explorer with Java Virtual Machine (JVM) version 3186 or later and CAM installed. | From Internet Explorer: Log into CiscoWorks2000 as admin. Select Resource Manager Essentials > Configuration Management > Configuration Editor, and configuration editor is not launched. Configuration editor starts as expected with JVM 3182 and CAM installed. | ||||||
CSCdr11360 | CiscoWorks2000 sometimes takes awhile to start. | It might take up to 15 minutes for CiscoWorks2000 to start if system is extremely busy or any component fails to start and Daemon Manager exhausts all retry limits. | ||||||
CSCdr25387 | Netscape on HPUX console does not display applet completely | The problem occurs when netscape browser running on HP-UX desktop uses "lucida-medium" as its dialog fonts. To work around problem: Use fonts other than "lucida-medium" for dialog items (java gui components). This can be done by replacing lines having font definitions "lucida-medium"with any of following lines in the NETSCAPE_HOME/java/classes/font.properties file: -sony-fixed-medium-r-normal--*-*-*-*-c-*-iso8859-1 OR -dt-application-medium-i-normal-serif-*-*-*-*-p-*-iso8859-1 OR -hp-hp user-medium-r-normal-serif-*-*-*-*-m-*-iso8859-1 The user may try out the other fonts, which works well. | ||||||
CSCdp83694 | ANI Server fails to connect to the Daemon Manager if a non-default Daemon Manager port is used. | Default Daemon Manager port is set to 42340. If any other port is specified, ANI Server will not run. | ||||||
CSCdm83204 | Applets not working when accessed as local host. | Navigator does not operate well when the local host is used in place of the system name or IP address. To work around this, always refer to the local system by its name or IP address. Do not use local host. | ||||||
CSCdr06564 | Resizing Navigator browser window results in CCO login errors for the SWIM application. | When browser window is resized, tree control applet is reloaded. Because a valid session is already established, Login Manager is not shown, and cached copy of SWIM username is not set. To avoid problem, do not resize browser window while logged into CiscoWorks2000 Server. If problem has already occurred, log out, then log in again. | ||||||
CSCdp67063 | Bus error occurs when two CiscoView sessions have different MIB labels. | Open a device from CiscoView, select Preferences dialog box, and change MIB label from Alias to Descriptor, for example. To verify change, select Configuration dialog box for that device. Keeping dialog boxes open, start another CiscoView session from same server and client, and open another device. Select Preferences dialog box and change MIB label from Descriptor to Alias. To verify change, select Configuration dialog box for second device. With dialog boxes for both devices open, close first CiscoView session and a bus error occurs, which closes all browser windows. | ||||||
CSCdp06564 | Upgrade to Essentials 3.1 causes administrator's password to be reset. | When you are upgrading an Essentials 2.x installation to 3.0, the system administrator's password is reset to admin. To work around this, after installing CD One, but before installing Essentials 3.1, log in and change the admin password to that of Essentials 2.x. Then proceed with the installation of Essentials 3.1. | ||||||
CSCdp08278 | Tasks might fail if server is not 100% up |
| ||||||
CSCdp15013 | Help index does not appear | This applies to Internet Explorer 5.0 users only. The online help system index does not work in Internet Explorer 5.0 when you log in to a CiscoWorks2000 Server, log out, then log in again using the same browser instance. To avoid this, exit Internet Explorer and restart it after logging out of a CiscoWorks2000 Server and before logging in to a CiscoWorks2000 Server again. | ||||||
CSCdr04996 | After installing CAM and restarting Navigator, attempt to launch any of the Campus Manager applications returns the following message in the java console: Could not | Caused by problem that prevents CAM from downloading jar files for application. It turns a folder into a file so application runs normally. However, this prevents enabling CAM for this and other applications. To work around the problem:
| ||||||
CSCdp17038 | Help page is broken on double clicking the help node. | In Navigator, some help pages display a Transfer Interrupted message after double-clicking the help table of contents. To work around the problem, clear the cache by selecting Edit > Preferences > Advanced > Cache and selecting the Clear Memory Cache and Clear Disk Cache options. | ||||||
CSCdp51341 | Monitor Dialog Print button does not work. | Open any monitor dialog and click Print. Print does not print anything, not even blank pages, and the cursor never comes back from busy (clock) state. | ||||||
CSCdp85841 | Inability to print in Netscape browser. | When the user attempts to print the chassis view by clicking on the print icon, nothing happens. This also applies to configuration dialogs. | ||||||
CSCdp35193 | Clicking on Help button for 1700 series device returns URL not found error message, and disables browser. | Normal state is recoverable only by opening a new browser. | ||||||
CSCdp69807 | ATM Lane Module Interface Utilization % graph does not scale. | When monitoring an ATM WS-X5158 MM OC-3 Dual-Phy interface, the Utilization % graph displays a straight line at 0%, and in some instances a straight line at 100%. | ||||||
CSCdp50350 | Port Monitor buffer overflow doesn't display correct data. | None. | ||||||
CSCdp83446 | A Cisco Alarms directory is no longer created in Openview, making it more difficult for customers to monitor Cisco devices. | When device packages were installed in previous versions of CiscoView (4.x), the trapd.conf file in Openview was updated. A Cisco Alarms directory was created, and all Cisco traps were placed into this directory. This feature allowed customers to effectively monitor Cisco devices. Starting with Cisco View 5.0, a Cisco Alarms directory was no longer created in Openview. | ||||||
CSCdp81555 | NMCS: PutMsg call causes segmentation fault. | Since moving to the new LogSvr interface in Essentials 3.1's Config application, this problem occurs. In NMCS's com.cisco.nm.cmf.util.Util.class, there is a call as follows: int ret = logger.PutMsg(logId,6005,message,"", ""). This call results in a segmentation fault and causes JRun to die. | ||||||
CSCdp58879 | PersistentObjectException seen during DeleteDevice test. | None. | ||||||
CSCdp74685 | Path analysis window is too small when CAM is running. | With CAM turned on, the path analysis window, when it comes up, is not big enough to contain the start/stop buttons. Also, it doesn't have a horizontal slider. While the window can be resized, the horizontal slider never appears. | ||||||
CSCdp63879 | The Webserver does not always start when user runs pdterm WebServer, and then pdexec JRunProxyServer. | It takes some time for the Apache port to get freed up on Solaris after the process has stopped. Sometimes the ports are in the time_wait state. This may happen when 2 or 3 requests are pending when a few configuration reports are opened. It is recommended that after running pdterm WebServer, the user should wait and make sure that all of the ports are freed up, then close all browser connections to the server. At this point the user should run pdexec JRunProxyServer. |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
| Language | E-mail Address |
|---|---|
English | tac@cisco.com |
Hanzi (Chinese) | chinese-tac@cisco.com |
Kanji (Japanese) | japan-tac@cisco.com |
Hangul (Korean) | korea-tac@cisco.com |
Spanish | tac@cisco.com |
Thai | thai-tac@cisco.com |
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Fri Jul 7 15:13:07 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.