|
|
![]() | Caution Make sure all applications are stopped before upgrading Resource Manager Essentials. The upgrade process depends on having reasonable interaction time with the database. If this is not possible, the upgrade will fail. |
These release notes describe the caveats for AIX releases of Resource Manager Essentials 2.1 and CWSI Campus 2.3. CiscoWorks2000 is supported only on AIX 4.2.1 and 4.3.2. This document contains the following sections:
For information about supported devices, go to the following URL:
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdm06596 | Changing time zones | Changes made to the system time zone from outside of CiscoWorks2000 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 CiscoWorks2000 applications. After changing the system time zone, restart all CiscoWorks2000 applications. |
CSCdm10820 | Netsys integration displays wrong year beyond 2000 | When the Device Configuration application is integrated with the UNIX version of Netsys 4.0 and 4.1, generated Netsys reports display the years 2000 and later as single digit numbers. For example, 2000 is displayed as 0, 2001 is displayed as 1, and so on. |
CSCdm21595 | Year displayed incorrectly during upgrade to Essentials 2.1 | During an upgrade to Essentials 2.1 from Cisco Resource Manager 1.1 or Essentials 2.0, the database upgrade log ($NMSROOT/dbupgrade/CSCOupgradedb.log) and the install log file (rme_in<three digit serial number>.log) display start and end timestamps for the upgrade. The year component of this timestamp is displayed incorrectly. For example, the date 2000/04/01 17:01:30 is displayed as 100/04/01 17:01:30 and the date 1999/04/01 17:01:30 is displayed as 99/04/01 17:01:30. The year component is offset by 1900. These messages are only informational, and there is no affect on the functionality of the product. |
CiscoWorks2000 utilizes the Java 1.1.6 Run-Time Environment and Perl 5.002 interpreter for report generation and syslog message analysis. Several limitations in these subsystems have been uncovered that affect time zone processing. These limitations include:
Because of these limitations, only a certain set of times will be supported.
Table 1 represents the time zones that are supported by CiscoWorks2000 on AIX.
This section contains notes and caveats for Resource Manager Essentials, as follows.
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Essentials web server not supported | The Essentials web server cannot support software not installed by Essentials. |
None | Browsers running on remote X servers | Browsers running on remote X servers are not supported. |
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. |
CSCdk17516 | Browser only accepts certain cookies | When using Navigator or Internet Explorer, you might encounter a situation in which Essentials 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 Navigator, select Edit > Preferences > Advanced > Cache. From the Cache window, select the option to clear your cache memory. If you are running Internet Explorer, select View > Internet Options > General > |
None | Internet Explorer times out after 5 minutes | Internet Explorer times out after 5 minutes while performing Essentials operations, especially those involving CCO transfers. Refer to article number Q181050 on the Microsoft support Web site for the resolution. |
CSCdk16546 | Internet Explorer 4.01: Unable to move back in Reachability Dashboard > Device Info > Browse | Due to the Internet Explorer history mechanism, there is no fix for this, as Internet Explorer does not have a way to clear an entire frame set. To work around this problem, click on a different item under Device Center. |
CSCdk31703 | Internet Explorer 4.01: Device Configuration task failures | Using Internet Explorer 4.x on a machine with Microsoft J++ installed might cause some |
CSCdk33035 | Internet Explorer 4.01: Cookie error if multiple Internet Explorer applications point to different Essentials servers | Essentials depends on cookies to transmit permission-related information. If multiple copies of Internet Explorer are launched from the Start menu or an icon on the desktop, Internet Explorer generates incorrect authorization failures when you are correctly logged in. To work around this problem, start new browser windows with the New option from within the browser. |
CSCdj50947 | Navigator 4.x: Open frame in new window is inoperative | The Navigator 4.05 right mouse button pop-up menu offers the Open Frame in New Window option. If you select this option while in Essentials, the right frame of the Essentials desktop appears but the navigation tree does not. To avoid this, complete all tasks in Essentials windows. |
CSCdj55007 | Navigator 4.x: Reachability Dashboard not updating | Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. |
CSCdj57449 | Navigator 4.x: Help > Glossary Back button links to contents | If you access the Glossary (Help > Glossary) with Navigator 4.05, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section. To return to the Glossary, click Glossary. |
CSCdk27845 | JavaScript error when clicking back from CCO web site | When using the online help file Help > Contents > CCO and Device Management > Case Management > Cisco Web Site link, if you select the Back button, an error message appears. |
CSCdk34547 | Navigator 4.x: Wrong date displayed for time zones with minute offset | Navigator 4.0x does not display the correct month and day for GMT time zones containing offset minutes. |
CSCdk44551 | Navigator 4.x: Self Test Collect server information report dated 25 days earlier | Navigator does not always display the date in the correct time zone or with the correct date on the Collect Server Info and Self Test pages. To work around this problem, use Internet Explorer 4.01. |
CSCdk44743 | Navigator 4.x: More records request shows internal error in Exception Report window | A server error message is displayed on the lower frame of the Exceptions Summary report in Change Audit > Exceptions Summary, but only under the following conditions:
The workarounds include:
If you are using Navigator and you select all days of the week to generate the report, after the server error message is displayed you can resize the report window or the lower frame of the report. This will remove the error message and display the report successfully. |
CSCdj64037 | Aborting Essentials installation procedure | If you abort the Essentials installation procedure before it completes, not all required components are installed. Restart the Essentials installation procedure from the beginning to complete the installation. |
CSCdj55007 | Reachability Dashboard Not Updating On Navigator 4.0 | Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. |
CSCdk27845 | JavaScript Error When Clicking Back from CCO Web Site | When using the online help file Help > Contents > CCO and Device Management > Case Management > Cisco Web Site link, if you select the Back button, an error message appears. |
CSCdm31404 | tftp transfer fails on AIX 4.3.2 | Software Manager and Device Configuration applications using TFTP as the transport system will not function properly on AIX 4.3.2. This problem is due to a bug in the TFTP daemon. To work around this problem:
Step 1 Change The tftp entry should look similar to this: Step 2 Save the file and exit. Step 3 Enter ps -ef | grep inetd to display the pid of inetd process. Step 4 Enter kill -1 <pid of inetd process> to allow the inetd process to re-read the /etc/inetd.conf file. Step 5 Enter ps -ef | grep tftpd to display two running tftpd daemons. The output should look similar to this. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Uninstalling Essentials | If you install Essentials and CWSI Campus on the same machine, you cannot uninstall Essentials without first uninstalling CWSI Campus. Refer to Installing Resource Manager Essentials and CWSI Campus on AIX for more information. |
None | Uninstall does not remove all Software Management images stored | Software Management stores images that are not removed by the Essentials uninstall procedure. If you want to permanently remove Essentials, you must manually remove these files from /usr/CSCOpx/files/sw_images. |
CSCdm19708 | CWSI Campus breaks Essentials if installed in same directory | The CWSI Campus installation needs to check the install directory to verify that it is not already occupied by Essentials. Otherwise, if Essentials is installed in the same directory as the Campus, Campus will overwrite files and break Essentials. To work around this problem, uninstall then reinstall both products using separate directories. |
CSCdj64037 | Aborting Essentials installation procedure | If you abort the Essentials installation procedure before it completes, not all required components are installed. Restart the Essentials installation procedure from the beginning to complete the installation. |
CSCdm20695 | Essentials installation and execution fails on AIX with assertion error | When you try to install Essentials 2.0 on AIX 4.2.1, the CSCOxrts package fails with the following error: Also, if Essentials is installed and running, the /var/adm/CSCOpx/log/daemons.log file starts filling up with the following error: The problem stems from a call to popen(). This call opens a named pipe to a command, and returns a pointer to a FILE structure. To work around this problem, add the following to the root .profile (located in /.profile): START=/.kshrc export ENV='${START-(_$-=0)+(_=1)-(_$-!=_${-%%*i*})-}' $ENV expands to .kshrc in interactive mode and to NULL in noninteractive mode. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Starting Essentials as Root | If you start Essentials by logging in as root and entering the following command in a C shell
make sure you do not suspend the root session using 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, and the processes restart normally. |
None | Essentials supporting firewalls | Essentials does not support authenticating firewalls or proxies in this release. |
None | Importing devices | If you encounter problems when importing devices, ensure your target system is configured correctly. Consult the following Essentials online help topics for instructions on what you need to do before importing devices:
|
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. |
CSCdm18788 | Database upgrade failure | Essentials 2.0 to 2.1 upgrade will fail if the database engine cannot come to a ready state within 5 seconds. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdm05454 | Protocol Distribution report shows 100% TCP/IP utilization for | If the Protocol Distribution report is launched 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 switches. If Protocol Distribution is launched directly from the Availability menu, the application recognizes that no views are configured for Protocol Distribution monitoring. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk10221 | Incorrect flash memory value in hardware report | When routers are configured to partition Flash memory into two Flash partitions, Essentials 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. To work around this problem, run the Detailed Device Report to check the router running configuration file. This report shows details about each Flash partition that was discovered when the router was added to inventory. You can also 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. |
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, Essentials 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. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Telnet passwords | In order for the configuration archive to successfully gather the ATM and RSM module configurations, these modules must have the same Telnet passwords as that of the supervisors for the Catalyst 5000 family of devices. |
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 syntactic correctness of configuration files uploaded to the device via import command. As a consequence, the import command reports success even if a configuration file with invalid contents is attempted to be written to the device. Notice that the configuration update will not succeed on the device, but cwconfig cannot detect this failure. |
None | Access restrictions and file permissions | On AIX, cwconfig is a set-userid program. It is owned by root, and belongs in bin group. However, as soon as the program is started, (internally) it 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 error detected by the tool is reported; the others remain unlisted. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk01464 | Shutting off DNS resolution | Essentials 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 exists only 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 |
|---|---|---|
CSCdk93048 | Downloading IOS image to the slot0 flash card on 8510CSR fails | When downloading an IOS image to the slot0 flashcard on the 8510CSR device using SNMP, the copy operation fails with To work around this problem, use slot1 instead of slot0 as the target location of the IOS image. |
CSCdk87046 | Problem upgrading software on Catalyst 5000 switches | Upgrading software on a Catalyst 5000 switch from a lower version code 2.x or 3.x to 4.x can sometimes cause problems. The MCP software does not get erased from the flash completely and will result in a mismatch between the NMP and the MCP software versions. To work around this problem, place an image on the flash card via the console of the Supervisor. |
CSCdk51236 | Supervisor image from device imported as ATM image during distribution | If you are not upgrading the Supervisor module in a Catalyst distribution job, but upgrading some other modules, do not select the "Backup current running image" job option. Selecting this option, which upgrades Catalyst modules other than Supervisor, can cause the Software Manager application to incorrectly import the current running Supervisor image as the module (ATM, FDDI, CDDI, Token Ring) image in the software library. |
CSCdk55124 | RCP not working on AIX | Software Manager fails if RCP is the transport mechanism for the default user; however, the job completes if TFTP is the fallback transport mechanism. Software Manager needs write permission in the .rhosts file for RCP. On AIX, RCP works only if .rhosts file has 0600 as its permission. This is a conflicting requirement for a non-bin user on AIX. To work around this problem, change the RCP user to bin. Select Admin > System Configure > RCP and set the user name to bin. Note Changing the RCP user to bin might involve security issues. |
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 Admin > Software Management > 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. |
| 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(2)WA4(4b) |
c5atm-wtall_113-3a_WA4_5.bin | 4(5) | 11.3(2)WA4(5) |
c5atm-wtall_113-4_WA4_7a.bin | 4(7a) | 11.3(2)WA4(7a) |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
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 | For Catalyst 5000 image 4.4(1), there is a new syslog message format. If service timestamp is enabled, Syslog Analyzer will not be able to parse it. To work around this problem, disable service timestamp in the device. |
This section contains notes and caveats for CWSI Campus, as follows:
This feature allows you to delete devices from the CWSI Campus database. To run the command line utility for deleting devices:
Step 1 Exit CWSI Campus.
Step 2 Enter stopcwsiserver.
Step 3 Enter the checkdb from command line with the IP address of the device to be deleted (checkdb -d IP). Specify multiple -d flags or colon-separated list of IP addresses to delete multiple devices.
Step 4 Enter startcwsiserver and then start CWSI Campus.
This script can be run without any parameters.
The AtmDirector fabric map has an option to show/hide the unknown UNI nodes. This feature allows for reduction of clutter on the map when many devices are displayed. To access this feature from the fabric map menu, select Map > Unknown UNI Devices > Show/Hide.
This feature gives you the option of turning off the domain names in the labels for nodes displayed on the map. Turning off the domain names makes the labels easier to read and reduces clutter on the map. To access this feature from the fabric map menu, select Map > Domain Names > Show/Hide.
This feature allows you to enter the name or IP address of a device into a text field. That device would then be highlighted on the map. To access this feature from the fabric, ATM-VLAN, or PNNI menus, select Map > Search.
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk49311 | Online help | To redirect CWSI Campus to another system (setting $DISPLAY to redirect the output to a different system) and have online help available, you must install the help files on each system where CWSI Campus will be used. |
CSCdm27812 | testdbconn gives false error message | After the system has successfully connected to the database, testdbconn gives the following message: This message can be ignored. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Upgrade Essentials 2.0 to Essentials 2.1 disables CWSI 2.2 | If Essentials 2.0 and CWSI 2.2 are installed, you cannot run CWSI 2.2.after upgrading to Essentials 2.1. You must upgrade from CWSI 2.2 to CWSI Campus 2.3 to run CWSI Campus successfully. |
CSCdm27636 | Installation script does not check for RAM or swap space | The installation will continue even if RAM or swap space does not meet the requirements documented in the installation guide. |
CSCdm28905 | Nondefault path for database causes CWSI Campus installation to fail | During CWSI Campus installation, selection of a nondefault path for the database will cause the installation to fail. To work around this problem, select the default path for the database location. |
CSCdm20370 | Port availability not verified | During CWSI Campus installation, you are asked to enter the TCP port for database use. The installation script does not verify that the port is available for connectivity. If another application has already reserved this port by adding an entry in /etc/services, that particular application will fail. To work around this problem: Step 1 Enter /usr/CSCOcwsi/bin/stopcwsiserver Step 2 Modify the entry for DB.url in /usr/CSCOcwsi/etc/cwsi/ani.properties. Enter a free port number: DB.url=jdbc:sybase:Tds:localhost:<free port number> Step 3 Enter /opt/CSCOpx/objects/db/conf/interfaces.pl localhost <free port number> cwsi Step 4 Enter /usr/CSCOcwsi/bin/startcwsiserver |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Catalyst 3000: Moving ports between VLANs | Moving ports between virtual local area networks (VLANs) will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2). |
CSCdm17900 | Some C2900XL series device types are inaccurate in the CWSI Network Map | In the CWSI topology map highlighting section, some C2900XL series device types are inaccurate. The correct naming follows:
|
CSCdj28689, CSCdj06709 | LAN Emulation on Catalyst 3000 switches | On Catalyst 3000 switches, LANE client (LEC) and LANE server/Broadcast and Unknown server (LES/BUS) components that do not bind with VLANs will not be discovered by CWSI Campus. As a result, ATM VLANs consisting of these LANE components will not be discovered. |
CSCdj24857 | CWSI Campus unable to discover some emulated LANs | Because of the agent inconsistency (lecsLesConfigTable MIB walk skips LES instances) that exists in Cisco IOS Release 11.1(X) and Catalyst 5000 ATM image 3.2(4) (and earlier), CWSI Campus is not able to discover some emulated LANs (ELANs). This inconsistency has been resolved in Cisco IOS Release 11.2 and Catalyst 5000 ATM image 3.2(5). |
None | Catalyst 5000 switch appears as ATM cloud | If a Catalyst 5000 switch appears as an ATM cloud on the CWSI Campus map, make sure that the switch has sufficient memory. The Catalyst 5000 switch comes with 16 MB of memory; however, this might be insufficient depending on the number of protocols the switch is running. Insufficient memory might prevent the supervisor agent and the LANE card from being connected. Without the connection, the ifEntries related to the LANE card will be missing from the ifTable and the device will show up as an ATM cloud on the topology. |
CSCdk23407 | Discovery process unable to discover LANE components on Catalyst 5000 | The discovery process is unable to discover LANE components and compute proper topology on Catalyst 5000 series devices with OC-3/OC-12 modules running 3.2(8)ATM/LANE software image. This problem is fixed in ATM/LANE image 11.3(4)WA4(7a), which is also known as 3.2(9). This fix is for all OC-3 and OC-12 modules. |
CSCdk91706 | Selected icons on the network map might appear as white on a white background | If you run Xterminal from an AIX box, selected icons on the network map might appear as white on a white background. To work around this problem, select Options > Properties > Map Dialog and change the network map background to a color other than white. |
CSCdm08404 | Network Map displays devices which have been removed | To run the command line utility for deleting devices: Step 1 Exit CWSI Campus. Step 2 Enter stopcwsiserver. Step 3 Enter checkdb from the command line, followed by the IP address of the device to be deleted (checkdb -d IP). Multiple devices can be deleted by specifying multiple -d flags or colon-separated list of IP addresses. Step 4 Enter startcwsiserver then start CWSI Campus. This script can be run without any parameters. |
CSCdm20592 | Upgrade to CWSI 2.3 does not discover newly supported devices | Device discovery will not work properly for newly supported device types when your network is upgraded to CWSI Campus 2.3 from an older version. If the network already consists of these new devices, they will be shown as unknown in the topology map. This happens only for those newly supported devices that are shown as unknown in the topology map of an older version of CWSI Campus. To work around this problem, remove these newly supported devices from the database by using the checkdb script. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdj63616 | Multiple configuration servers | Creating more than one configuration server at a time does not work properly. To work around this problem, create only one configuration server at a time. |
CSCdk27572 | VLAN creation and selection do not work on some Catalyst 5000 switches | VLAN configuration sometimes fails on Catalyst 5000 switches (with SMP Release 3.1.1, 3.2.1, 3.2.2, and 4.1). To work around this problem, enter the clear config all command on the device to return the device to its working state. |
CSCdm19468 | Port membership discovery per VLAN is not correct | On the Catalyst 2900XL series devices, when ports are configured in port groups, port membership discovery per VLAN will not be correct. To work around this problem, do not configure any port in port groups for these devices. The port group feature is not supported for this release. |
CSCdm19967 | LANE component configuration does not work after loading correct image | The LANE component configuration is supported only on some software images. The LANE component configuration does not work even if the device software images are updated after CWSI Campus discovers the network.This happens on Catalyst 5000 series switches with LANE/ATM modules, routers, and ATM switches. To work around this problem, stop the CWSI Campus server by entering stopcwsiserver, then restart it by entering startcwsiserver. You do not need to clean the database. |
CSCdk31419 | Configuration server error message | Configuring a configuration server or configuring the default ATM-VLAN might cause the following message to be displayed: Failed to assign auto ATM address of LE config server on port <port name> of device <ip Address>. <snmp error message: COM.cisco.nm.mojo.comm.snmp.SnmpValueException: SnmpResponseBadValue on <ipAddress> >
The following are possible causes:
To work around this problem remove the line from the configuration file and remove the database association from the particular interface (remove the line that says lane config database xxx) and try again. |
CSCdm20445 | LECS support does not work properly when LECS database name has more than 24 characters | In VlanDirector and AtmDirector, LECS related functionality will not be able to work properly when the LECS database contains more than 24 characters. To work around this problem, change the LECS database name to contain a maximum of 24 characters. |
CSCdm18742 | Configuring backup LANE Config Server may result in creation of an active configuration server | Configuring a backup LANE Config Server might result in creation of an active (master) configuration server. This can happen if CWSI Campus fails to create appropriate ILMI address registration entries (related to LANE Config Server) in ATM switches. To work around this problem, remove the newly created config server (through CLI), make sure that the community strings on ATM switches are correct and retry the operation. |
None | Some ATM-VLANS may not get discovered | Some ATM-VLANS might not be discovered by CWSI if LANE/ATM cards are running images that are not supported by CWSI. To work around this problem, download the image supported by CWSI on the LANE/ATM card, then rediscover the network. |
None | Atm cloud on topology map may appear because of incorrect image version on LANE/ATM card | Atm cloud on topology map may appear because of incorrect image version on LANE/ATM card. These topology problems occur for images 3.2(8), 3.2(10), and 3.2(11) on the following OC3 card models: WS-X5155, WS-X5154, WS-X5153, WS-X5156, WS-X5157, WS-X5158, WS-X5163, and WS-X5164. To work around this problem, download the image supported by CWSI on the LANE/ATM card, then clean the database and restart CWSI server. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk41893 | Deleting rows in the UserTracking table | Sometimes, when you delete rows in the UserTracking application, the application terminates with a thread dump. Currently there is no workaround. You must restart the UserTracking application. (When this occurs, the CWSI client is not affected, even if you started the UserTracking client from CWSI.) |
CSCdk42144, CSCdk55803 | The UserTracking application hangs when clicking in some columns | Sometimes, when you click on a cell in the VLAN, VTP Domain, or Port State columns in UserTracking, the UserTracking client might become inaccessible. You must terminate the UserTracking client and restart it. |
None | TFTP server and UserTracking | In the TFTP Configuration window, do not modify the entry that specifies the VTP domain serviced by this VMPS server (vmps domain <DomainName>). If you change this line, the VMPS server might no longer be recognized by UserTracking. |
None | UserTracking discovery could span more than desired subnet | When subnet discovery of user nodes is initiated, the devices in that subnet are marked for discovery. Because switches support multiple VLANs, the discovery could span more than the desired subnet. Therefore, UserTracking could discover additional end user nodes that are not in the selected subnet. |
CSCdm02267 | Sorting the port column | In CWSI 2.3, UserTracking by default sorts the Port column alphabetically. To sort the Port column numerically in CWSI 2.3: Step 1 Add the property: sortPortColumnNumerically=true to the CWSIROOT/etc/cwsi/userTracking.messages file. Adding this property affects all UserTracking clients run on that system. Step 2 After adding the property, you must restart the UserTracking client for it to take effect. You do not need to restart the ANI server. |
None | Information in UserTracking may not reflect most current state of network | The UserTracking discovery process takes information from the router and switch CAM tables and displays the results as the state of the end user nodes on the network or subnet in the Last Seen field. Because these devices work in various VLANs and subnets and collect their information at different times, the information they have might not always be the most current. Therefore, the information displayed in the Last Seen field does not always reflect the most current state of the network or subnet. |
None | Changes made to Minor Acquisitions interval do not take effect until the next scheduled acquisition | Changes made to the Minor Acquisitions interval (in the Acquisition Schedules dialog box) do not take effect until the already scheduled time for minor acquisitions is reached. For example, if the next scheduled minor acquisition will occur at 2:00 p.m., and at 1:00 p.m. the interval is changed to 10 minutes, the next minor acquisition will occur at 2:00 p.m., followed by one at 2:10 p.m., |
None | Resetting Minor Acquisitions | If you set the Minor Acquisitions interval to zero (to disable Minor Acquisitions), you can subsequently change the interval to a nonzero value, but the change will not take effect until the next time you start ANI (e.g., by invoking startcwsiserver). |
None | Changing column configuration | If you change the column configuration in the Customize Layout dialog, and select Action > Display > Entries without first clicking the Apply or New Layout button, the column headers displayed might not match the contents of the columns displayed. The modified column configuration will not have been saved, but no other column configurations will be lost, nor will any data be lost. If this occurs, exit the current UserTracking client and start a new one. To work around this problem, always click the Apply or New Layout button in the Customize Layout dialog before displaying new UserTracking entries. |
CSCdm19077, CSCdk20561 | Enduser incorrectly displayed as Token Ring on Catalyst 3000 switch. | The Catalyst 3000 switch returns incorrect CAM/Bridge table information for nonexistent VLANs. This causes UserTracking to show entries with duplicate MAC addresses and with incorrect port and vlan information. |
CSCdm34396 | Cannot enter MAC address in non-canonical format | Entering MAC addresses in a noncanonical format (for example, using a colon in the address) will cause an error. You are restricted to adding MAC addresses in canonical format. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Generic indexing scheme | To enable the TrafficDirector application to use a generic scheme to communicate with embedded RMON switches, you must enable the enable-generic-control-index flag in the default.dvp file, then restart the TrafficDirector application. |
None | Catalyst 1900 and 2800 switch support | If you get errors when installing a property file to the Catalyst 1900 and 2800 switch, run dvclean and perform the installation again. |
CSCdm10130 | No alerts for Catalyst 6000 switch | Alert Monitor does not receive any traps for Catalyst 6000 devices. To work around this problem, configure your station as a trap receiver from the command-line interface (CLI) on the Catalyst 6000. |
None | Network Analysis Module Release 4.3(1a) |
|
None | Mini-RMON support for VLANs and FECs on Catalyst 5000 | Mini-RMON is not supported for VLANs and FECs of the Catalyst 5000 family of switches. Trying to use a mini-RMON application (such as Traffic Monitor, Short- and Long-Term History, Segment Details, Segment Zoom, and so on) against a roved VLAN with the Network Analysis Module produces an error. |
None | Upgrading from TrafficDirector 5.3 |
|
CSCdj89834 | Running All Talkers | Running the All Talkers application for the ATALK domain may result in duplicate entries being displayed. |
CSCdk29981 | Learning VLANs and FEC | VLANs and FEC are only learned on Catalyst 6000, 5000, 4000, 2948G and 2926G series devices. |
CSCdk44815 | Support for switch roving | If you make any changes to a roved port, FEC, or VLAN without using the TrafficDirector application (for example, using the switch command-line interface), the TrafficDirector application will not reflect these changes. |
None | TrafficDirector as trap receiver | On all switches (except the Catalyst 4000 and 5000 series), the TrafficDirector application does not auto-configure itself as a trap receiver. You must manually set the trap destination from the switch command-line interface (CLI). |
CSCdk87967 | Network Analysis Module Release 4.3(1a) | Running Data Capture against a switch port, VLAN, or FEC that is roved to a Network Analysis Module may result in the Running For field showing an incorrect value. |
CSCdm03053 | Alert Monitor agent name | The Alert Monitor agent name is truncated at 16 characters. If you use long agent names, you might not be able to read the port on which the alert was reported. |
CSCdm10165 | No script file launched | When an alert is received in TrafficDirector, the script associated with that Threshold is not always launched. |
CSCdm26936 | TrafficDirector does not integrate automatically with NetView | During installation, the TrafficDirector application does not integrate automatically with NetView. For information on integration, refer to Using the Campus TrafficDirector Application. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdk87974 | Changing the community string | You can change the community string for a device using CWSI Campus. However, if you want to change the community string for a device on which you have already performed an SNMP operation using AtmDirector, you must change the community string, exit AtmDirector, and then restart AtmDirector. |
None | Main Window | While editing the fabric name on the tree structure in the main window the old name is not completely cleared from the display when the new name is being entered. The new name appears clearly after you press Return. |
None | ATM Fabric Map: Selecting an incorrectly configured ABR table | During SPVP/SPVC setup using Advanced Parameters, selecting an incorrectly configured ABR table displays the following message: To work around this problem, add a new row for the ABR traffic with the appropriate traffic parameters and apply it towards the SPVP/SPVC setup. |
None | ATM Fabric Map: AtmDirector displays unknown devices | If AtmDirector displays unknown devices that are no longer present in the network, follow these steps to remove them from the map. Step 1 Reset the interface on the LS1010 switch to which the unknown device is connected. This will clear the unknown device entry in CISCO-ATM-ADDR-REG table. Step 2 Delete the link between the LS1010 switch and the unknown device, after it is appears as broken line on the ATM fabric map. The unknown device will be deleted from the map after the link is deleted. |
None | ATM-VLAN map: Destination Host name field is blank | In some cases while displaying the Control Connection VCs, the Destination Host name field is blank. This situation is caused by the host name not being correctly resolved from the ATM Address. |
None | PNNI: Address not shown in Reachable Address dialog box | The addition of a new reachable address from the AtmDirector application will not be immediately reflected in the dialog box when invoked. After the next discovery cycle, the new address in Reachable Address dialog box is displayed. In the Reachable Address dialog box, if the Modify option does not work, delete the row and add a new row with the appropriate changes. |
None | PNNI: Modify button in the Reachable Addresses dialog is disabled | The Modify button in the Reachable Addresses dialog box is disabled for this release. The user can modify the existing reachable address by deleting the existing one using the Delete button and adding the desired one using the Add button. After deleting and adding the PNNI reachable address, exit from the AtmDirector application for those addresses to be updated on the database on the client. |
None | LANE Client Support | AtmDirector does not support multiple LANE clients for the same ELAN on the same device. |
None | TopN/Traffic Between/Call Failure Graphs |
|
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | CiscoView and internationalization | CiscoView does not support internationalization. |
None | CiscoView times out | In high traffic situations, you might experience timeouts. To increase the timeout period, select Options > Properties from the CiscoView menu and change the value for the Timeout field. You should not reduce the physical view polling interval below (retries*timeout), especially if you experience timeouts; this could exhaust system resources and result in a general error. |
None | Printing to LaserJet III | CiscoView might fail to print to a LaserJet III printer, especially in the "LaserJet" format, because of this printer's limited memory. |
None | StackMaker: Internal debugging | When the StackMaker Debug option is set to On, debug messages print to the StackMaker Debug Log file. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is /tmp/.smDebugLog. |
None | StackMaker: Log File from Apply Operations | The StackMaker log file stores the results of a saved stack configuration (Actions > Apply Stack Configuration). The log file is /tmp/stackmkr/sm.log. When the log file exceeds 1 MB, it automatically resets to 0 bytes. When StackMaker runs on Catalyst 1900 devices, some debug output is printed to the console. You can ignore this output. |
None | Threshold Manager | Some agents, most notably the Catalyst switches, impose a limit on the number of alarm and event entries that can be created. Applying a large number of thresholds to these devices will likely fail. In this case, some alarm entries might be successfully created but their associated event entries are not. These failed creations are marked as Failed in the Current Threshold Settings pane. If you attempt to delete those settings, Threshold Manager reports that the deletion failed (because it cannot delete nonexistent event entries.) In this case, you can ignore the error message and can verify that the deletion occurred by retrieving the threshold settings after the deletion. |
CSCdj00349 | StackMaker using community strings | StackMaker does not work with devices that have different community strings. (By default, stacked devices use the same community strings.) |
CSCdk12100 | Error messages invoking StackMaker for a device | You might get error messages when invoking StackView for a device, particularly if you just changed the "seed" device or if you previously opened and closed the stack. If you get error messages when invoking StackView, exit the current CiscoView session and launch a new CiscoView session. |
CSCdk24025 | MGX (formerly AXIS) errors | When CiscoView is using an AXIS device package, if the AXIS agent cannot process packets sent by CiscoView (generating tooBig errors), CiscoView core dumps. |
None | CiscoView: SNMP Community String Read/Write Changes | CiscoView SNMP Community String Read/Write changes defaults to SNMP Community String settings of the network management platform if installed to launch from a supported network management platform. To change CiscoView SNMP community strings, the change must be made to the network management platform SNMP community strings. A patch is available from CCO to enable modifications to community strings directly from CiscoView. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Error message: IP address is not set in sysIpAddr MIB variable | If you see "IP address is not set in sysIpAddr MIB variable," the Catalyst 1200 SNMP agent does not store the correct IP address in the sysIpAddr MIB variable. You must use CiscoView to correct this error. Select Configure > Device, enter the correct IP address in the corresponding field, and click Modify. |
| DDTS No. | Description | Explanation and Workaround |
None | Device agent does not update the IP address table | The device agent does not update the IP address table of MIB-II properly and does not reflect the correct IP address information of all the device interfaces. You cannot view the correct IP address information of the device by selecting |
None | Creating new static entries for IP Route Table and ARP Table | You cannot create new static entries for IP Route Table and ARP Table through CiscoView. |
None | Modifying IP parameters | In the interface configuration, |
None | Changing the bridge type |
|
None | System time configuration | The system time configuration is not included as part of device configuration. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | General Bridge window | CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The General Bridge window shows the bridge information for VLAN1 only. Bridge information for other VLANs is not available. |
None | Spanning Tree Protocol window | CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The Spanning Tree Protocol Window for switched ports is available for ports in VLAN1 only. This window does not show valid information for ports that are not in VLAN1. |
CSCdj03444 | Catalyst 1900, Catalyst 2820, CPW 1220, and CPW 1420: Blank entry for IP address | To delete an entry from the Set Managers configuration, enter an IP address of 0.0.0.0. The agent on the devices do not accept a blank entry for an IP address. |
CSCdj64496 | Dependency between the CPW1420 and Catalyst 2820 | CPW 1420 and Catalyst 2820. On the front panel display of the device, the Connect and Disabled LEDs on FDDI modules do not reflect the appropriate status. The Configure > Module option is supported only for one module type, even though it can be invoked for multiple module types. There is a dependency between the CPW1420 and Catalyst 2820. The CPW1420 device package will not run unless the Catalyst 2820 package is installed. |
| DDTS No. | Description | Explanation and Workaround |
None | Delete an entry from the Set Managers configuration | To delete an entry from the Set Managers configuration, enter a blank field. The IP address of 0.0.0.0 does not remove the entry from the Set Manager Table. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Catalyst 2600 device package contains two versions of the Enterprise MIBs for the Catalyst 2600 switch | C2600_cisco.my--This MIB file is installed to support devices with image versions prior to 2.2.1. C2600.my --This MIB file is installed to support devices with image version 2.2.1 or later. If you are using a MIB browser tool, you will see the MIB variables defined in each of these files, under different branches at the same time, although any particular Catalyst 2600 switch will respond to queries on only one of the MIBs, based on the release of software in the device. You should upgrade your Catalyst 2600 switches to version 2.2.1 or later. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Creating new embedded RMON agent group | If the number of the embedded RMON agent is over 50, you cannot create any new embedded RMON agent group for the new port. Use the Domain Manager to uninstall the agent group from the unused port to free the memory resource. |
None | Port > Configure window does not display the Broadcast Suppression category when multiple ports are selected | When multiple ports are selected, the |
None | Enabling port security administration | When you enable port security administration on a port, there may be timeouts. If this happens, increase the SNMP timeout value to approximately 10 seconds. |
None | WS-X2901 module | The WS-X2901 module shows the speed LED lit only when the speed is configured as 100 Mbps and the port is connected. |
None | Port Utilization tool | The Port Utilization tool has been removed from the Tools menu and is now available only on a per module basis from the Config > Module menu. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Accessing a stack with six or more devices | When you access a stack with six or more devices, there might be some significant performance problems. You can improve performance by increasing the SNMP timeout settings. |
None | RMON on either a stack or an ATM port | The Catalyst 3000 software does not support RMON on either a stack or an ATM port. |
None | Timeout messages | You might notice timeout messages and SNMP Set Failed messages when using the EtherChannel Configuration tool. If this happens, increase the SNMP timeout values for better performance. |
None | Running version 2.0(1) of the Catalyst 3000 software |
You can fix these problems by upgrading to a later release of Catalyst 3000 software. |
None | WS-X3006B is displayed in CiscoView as a WS-X3006A | Because of restrictions in the Catalyst 3000 software, the WS-X3006B is displayed in CiscoView as a WS-X3006A. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Viewing device | CiscoView does not show the rear view of the Catalyst 3900 box. |
None | Dragging ports in the VLAN table | When you attempt to drag port(s) to drop into one of the CRFs in the VLAN table, CiscoView might exit with an error. To work around this problem, first select the ports of interest, then bring the focus back to the VLAN Table window. Drag the selected port(s) and drop them into the desired CRF. |
None | The Configure... option under the Bridge Configuration category | The Configure... option under the Bridge Configuration category allows you to view a current configuration only. It reports an error when you attempt to configure new values for any parameter. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | Broadcast Suppression support | ATM, FDDI, and CDDI do not support Broadcast Suppression. |
None | Grapher in the CiscoView Monitor 10BaseT Group Switching Ethernet window | Do not use the Grapher in the CiscoView Monitor 10BaseT Group Switching Ethernet window. Use the Monitor or TrafficDirector tools (if TrafficDirector is installed) to see graphical views of the selected repeater ports. |
None | Repeater module port | When you select the repeater module port on a Catalyst 5000, it always uses the first port of the selected segment to create the RMON agent group. |
None | Experiencing timeouts | If all Catalyst 5500 slots are populated with modules and you experience timeouts, increase the SNMP timeout value to 15 seconds. |
None | WS-X5213 and WS-X5213A modules | The WS-X5213 and WS-X5213A modules show the 100-Mbps LED lit only if the speed is configured at 100 Mbps and the port is connected. |
None | FDDI/Ethernet Bridge category under Configure > Device displays an "unknown error." | Opening the FDDI/Ethernet Bridge category under Configure > Device can display an "unknown error." This is because of a problem with the device software. |
None | General error (genErr) displayed | If a general error (genErr) is displayed when you change vlanPortIslStatus, the selected port might not support ISL. |
None | ifAdminStatus and ifLinkUpDownEnable values | The values of ifAdminStatus and ifLinkUpDownEnable cannot be changed on an ATM port. |
None | Port duplex settings | Port duplex settings cannot be changed on ATM and FDDI ports. |
None | Value portSpanTreeFastStart | The value portSpanTreeFastStart cannot be changed on ATM and FDDI ports. |
None | Configuring ports to unsupported speeds | Configuring ports to unsupported speeds returns a general error (genErr). This is because of a problem in the device software. |
CSCdk14013 | Catalyst 5000: Changes to community strings do not take effect | When a Catalyst 5500 is open in CiscoView, any changes you make to the device's community strings do not take effect. To work around this problem, run xnmsmpconf and set the global default "set" value to "private." |
CSCdk14111 | Catalyst 5000: CiscoView uses changes in community strings as the default for unknown community strings | When a Catalyst 5000 is open in CiscoView, if you change the community strings, the changes will become the default community strings used by CiscoView for devices with unknown community strings. To work around this problem, close and reopen CiscoView, then change the default community strings by selecting Options > Properties from the menu. |
| Switch | Firmware Version |
|---|---|
Catalyst 2100 and 2800 | 3.63 or later |
EtherSwitch 1200 and 2800 | 3.63 or later |
EtherSwitch 10/100 | 1.38 or later |
Catalyst 1700 | 1.38 or later |
Grand Junction FastSwitch 10/100 | 1.37 or later |
Grand Junction FastSwitch 2100 and 2800 | 3.62 or later |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | CDP and CGMP Protocols Unsupported | The CPW 1200/1400 and Cat 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialog boxes for these devices will return errors. |
None | Community String Mismatching | When you enter values for read-only, write-only, and read-writeId with the command line interface (CLI) commands, these values must match. A mismatch results in noSuchName or timeout errors. To avoid these errors, use identical community strings in CiscoView and corresponding agents. |
None | Duplicate Categories | When multiple ports of different types are selected, |
CSCdk24862 | Catalyst 1924 with Firmware V8.00.04(03) | If you launch a Catalyst 1924 with Firmware V8.00.04(03), you cannot access the Port Zoom or Switch Zoom applications from Rmon Options. |
CSCdk40128 | VLAN colors not displayed in CiscoView | VLAN colors for a Catalyst 1900 are not displayed in CiscoView when a VLAN is highlighted in VlanDirector. |
CSCdk48245 | Catalyst 1700 version 4.0(1.4) not working properly | Version 4.0(1.4) of the Cat1700.pkg device package does not work properly if either of the following device packages are installed: Cat1900.pkg, Version 4.0(2.0); or Cat2820.pkg, Version 4.0(2.1). |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | CiscoView does not properly reflect the status of the T1/E1 channel_ports that have been configured for channel-group. | Status of T1/E1 Channel_ports for Channel-group. In the channel_modem view, CiscoView does not properly reflect the status of the T1/E1 channel_ports (timeslots) that have been configured for channel-group. This is a Cisco IOS software problem. |
None | Hot swap does not work for stacked Cisco 3600. | The hot swap feature is not available for stacked Cisco 3600 series routers. |
None | Changing async/sync port configuration | Whenever the async/sync port configuration is changed, you must reopen the stack for CiscoView to update the async/sync port status. However, the hot swap feature for the async/sync ports is supported for individual Cisco 3600 series routers. Also, whenever the async/sync port configuration is changed in a 16/32 port asynchronous network module, you must reopen the stack to obtain the latest state. However, the hot swap feature for the async/sync ports is supported for individual Cisco 3600 series routers. |
None | The Logical view and Channel Modem Mapping view are not available for stacked Cisco 3600 series routers | This support is scheduled for a future release. However, Logical View is available on individual or stacked Cisco 3600 routers if a digital modem carrier card and a |
None | Table misses interfaces with Cisco IOS versions below 11.1(7) | The fix for defect CSCdi69480 (PRI/E1 interfaces missing in cardIfIndex table) is integrated into Cisco IOS Release 011.001(007) and later. The Cisco 3600 4.0(6.1) device package incorporates the fix and might not work properly with Cisco 3600 series routers running Cisco IOS versions earlier than 011.001(007). |
CSCdk06905 | Cisco AS5800 Universal Access Servers: OID and Schema files for certain mibs are not included | The oid and schema files of the MIBs AAA, CISCO-PAGP-MIB, FASTMOD, FASTSWITCH, RFC1407-MIB, RFC1595-SONET-MIB, RFC1748-MIB, SNMPV2-CONF, ENTITY-MIB, CISCO-ENTITY-VENDORTYPE-OID-MIB, CISCO-5800-HEALTH-MON-MIB are not available in the package. The required oid and schema files are not published at the time of release. Therefore, these MIBs cannot be browsed in SNM and EM platforms. |
CSCdk11818 | Cisco AS5800 Universal Access Servers: Hotswap works inconsistently | After the hotswap, the dsphysical view alone gets redrawn. To work around this problem, exit CiscoView and reopen the device. |
CSCdk11819 | Cisco AS5800 Universal Access Servers: Cannot monitor PRI channels in CE1/CT1 card | Monitoring of individual channels of trunk ports in CE1/CT1 card is not available. Only the configuration information is displayed. |
CSCdk11820 | Cisco AS5800 Universal Access Servers: Help for compression card is incorrect | Incorrect help information displayed for sa-compression card. |
CSCdk11823 | Cisco AS5800 Universal Access Servers: HealthMon Status shows wrong values for ShelfId and ShelfAddress | In device configuration dialog of the SC3640, the values displayed for ShelfId and ShelfAddress are wrong. |
CSCdk11854 | Cisco AS5800 Universal Access Servers: Pixel and mask of size 38 is shown bigger | The pixel and mask of size 38 is shown bigger for AS5800 and SC3640. The relevant files contain size of 48 pixels for width and height. |
| DDTS No. | Description | Explanation and Workaround |
None | Configuring an LECS address for LS1010 | LightStream1010. To configure an LECS address for LS1010 from CiscoView, ServiceId needs to be the following: 10.1.3.6.1.4.1.353.1.5.1.<Index>, where Index is the row differentiator for configuring multiple LECS addresses. Index is an integer. |
None | Power Supply Display | By default, CiscoView 3.1(1) displays two power supplies for a Cisco 7000 router running Cisco IOS Release 10.2 and earlier. With Cisco IOS Release 10.3 and later, power supplies are displayed based on ciscoEnvMonSupplyState values. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
None | RFC1595-SONET-MIB support | The RFC1595-SONET-MIB is not supported in ubr7200 device package version 1.1. |
None | Downstream Channel MIB Variable Settings |
|
| Downstream Channel MIB Variable Settings (continued) |
|
None | Upstream Channel MIB Variable Setting |
|
None | Fast Serial MIB Variable Display Values | The Fast Serial port configuration dialog box for HSSI interface displays N/A for status of flow control signals (locIfFSIPrts,locIfFSIPcts, locIfFSIPdtr,locIfFSIPdcd,locIfFSIPdsr). The agent returns 0 instead of the acceptable values 1-3. (1 - Not Available, 2- Up, 3-Down). |
None | Oid and schema files for RF-IF-MIB in SNM and EM platforms | The oid and schema files for RF-IF-MIB are not included in ubr7200 device package version 1.1. The required oid and schema files are not published at the time of release. Therefore, RF-IF-MIB cannot be browsed on SNM and EM platforms. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdj23970 | IOS less than 11.1 cause FSIP dialogs in CV for mip ports | An invalid port level FSIP configuration category appears for devices with MIP cards running less than 11.1. The dialog just displays N/A for variables displayed in it as these are not applicable to it. |
CSCdj40816 | x25CircuitCalledDteAddress in ascii value | The variables x25CircuitCalledDteAddress and 25CircuitCallingDteAddress are displayed in ascii. It is better to show these in numeric form. |
CSCdj86030 | View menu is inconsistent | The view menus for the 7204 and 7206 have a front view, but all other 7000 series routers have only a rear view. |
CSCdj93913 | Delta values appear as absolute values | When CiscoView is used to monitor multiple ports, the delta value does not change relative to the 2 polling points but is simply a dump of the raw SNMP value. |
CSCdk03826 | CiscoView does not display pa-a8t | CiscoView fails to display a 7206 with pa-8b-st, pa-a8t-x21, c7200-io1fe and cpu-7200 cards correctly. |
CSCdk08747 | Mismatch of formula in help for buffer failure in 7000pkg | Device monitor shows the wrong help context. |
CSCdk13389 | CiscoView with the Cisco 7000 package 4.0(4.0) fails on token ring modules | Selecting category "TokenRing Errors" generates an error: "The MIBs are not supported by the device." However, launching CiscoView 4.0 with 7000 package 4.0(1.0) on the same router it does not generate any errors. |
| DDTS No. | Description | Explanation and Workaround |
|---|---|---|
CSCdj62089 | Find Tab: Customized find operation contains multiple items called CiscoView | Because of the way a master CiscoView contents file is used by the software when multiple CiscoView device package help files are present, the list of files to include when setting up a customized find operation contains multiple items called CiscoView. |
CSCdk49538 | Problem opening Help topics | While browsing Help pages, you might be unable to open a help topic and you might see an error message such as "cannot open file filename." If this occurs, it could be that there is a low limit on the number of files that can be opened by a specific process. To work around this problem, increase the kernel configuration parameter "number of open file descriptors per process" to approximately 90 or more. |
CSCdm08347 | Problem opening Help > Contents | When Help > Contents is selected from CiscoView, the help window might not open. If this occurs, it could be that there is a low limit on the number of files that can be opened by a specific process. To work around this problem, you can run the command "limit descriptors 1024", which will increase the file descriptors. |
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.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Aug 8 16:33:03 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.