|
|
![]() | Caution If the Y2K Compliance Assessment Tool is installed on your machine, you must uninstall it before installing this version. Otherwise, the installation will fail. |
![]() | Caution Make sure all applications are stopped before you upgrade Essentials. The upgrade process depends on having reasonable interaction times with the database. If this is not possible, the upgrade will fail. |
These release notes describe the caveats for Resource Manager Essentials 2.2 and CWSI Campus 2.4. This document contains the following sections:
Use these publications to learn how to install and use CiscoWorks2000:
For information about supported devices go to the following URL:
In Installing CWSI Campus and Resource Manager Essentials on Windows NT, the software version numbers in Tables 2-2 and 2-3 are incorrect. The tables below show the correct version numbers.
| Browser | Version | Operating System |
|---|---|---|
Netscape Navigator1 | 4.5 | Solaris 2.5.1 or 2.6, Windows NT 4.0, Windows 95, AIX 4.2.1 or 4.3.2, and HP-UX 10.20 or 11.0 |
Microsoft Internet Explorer2 | 4.01 with Service Pack 4 or 53 | on Windows NT 4.0 and Windows 95 |
| 1With Java and JavaScript enabled; with accept all cookies enabled. 2with Enable Java Programs and Active-X Scripting enabled; with accept all cookies enabled. 3With Active Desktop disabled. |
| Local Import | |
|---|---|
| Software | Version |
HP OpenView Network Node Manager | 5.02, 6.0 |
CWSI Campus | 2.4 |
CastleRock SNMPc | 4.2.4 |
| Remote Import1 | |
| Software | Version |
HP OpenView Network Node Manager | 5.01, 6.0 |
CiscoWorks | 4.0 |
CWSI Campus | 2.4 |
| 1You can import remote devices from the listed software running on a UNIX system only. |
In Installing CWSI Campus and Resource Manager Essentials on Windows NT, the Product Upgrade Paths section is incorrect. The sections below show the correct product upgrade paths.
The following Essentials upgrade paths are supported in this release:
The following Campus upgrade paths are supported in this release:
| ID | Summary | Explanation |
|---|---|---|
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 /etc/TIMEZONE file) might not be reflected in already running CiscoWorks2000 applications. After changing the system Time Zone, users should 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 above as single digit numbers. For example, 2000 is displayed as 0, 2001 is displayed as 1, and so on. |
CiscoWorks2000 utilizes the Java 1.1.6 Run-Time Environment and Perl 5.002 interpreter for report generation and syslog message analysis. There are several limitations with these subsystems that have been uncovered, related to timezone processing. These limitations include:
Because of these limitations, only a certain set of timezones will be supported on
Windows NT.
| Offset | Timezone Settings | Java 1.1.6 | Perl | Device Timezone Acronyms |
|---|---|---|---|---|
-9 | Alaska | AST | YST | AST |
-8 | Pacific Time (US and Canada); Tijuana | PST | PST | PST |
-7 | Mountain Time | MST | MST | MST |
-6 | Central Time | CST | CST | CST |
-5 | Eastern Time | EST | EST | EST |
-3.5 | Newfoundland | CNT | -21000 | CNT |
-3 | Brasilia | BET | ADT | BET |
0 | Greenwich Mean Time; Dublin, Edinburgh, London, and Lisbon | GMT | GMT | GMT |
1 | Berlin, Stockholm, Rome, Bern, Brussels, and Vienna | ECT | CET | ECT |
1 | Paris, Madrid, and Amsterdam | ECT | CET | ECT |
1 | Prague, Warsaw, and Budapest | ECT | CET | ECT |
2 | Athens, Helsinki, and Istanbul | EET | EET | EET |
2 | Cairo | ART | EET | ART |
3.5 | Tehran | MET | +27000 | MET |
8 | Beijing, Chongqing, and Urumqi | CTT | CCT | CTT |
10 | Brisbane, Melbourne, and Sydney | AET | EAST | AET |
The section contains notes and caveats for Resource Manager Essentials, as follows:
| ID | Summary | Explanation |
|---|---|---|
None | Essentials must have dedicated web service | On Windows NT 4.0, Microsoft IIS 4.0 web service must be dedicated to Essentials. Do not use the web service used by Essentials to service other applications or internet clients requesting web pages other than those generated by Essentials. |
None | Microsoft IIS 4.0 supports multiple virtual web servers | On Windows NT 4.0 Server, Microsoft IIS 4.0 supports multiple virtual web servers so you can share the IIS 4.0 web service when running on Windows NT 4.0 Server. |
None | Cisco Voice Manager | Cisco Voice Manager cannot coexist on the same machine as Essentials. Install Cisco Voice Manager on a different machine. |
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 excepts only certain cookies | When using Netscape Navigator or Microsoft 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 Netscape Navigator on a PC, select Edit > Preferences > Advanced > Cache. From the Cache window, you will see the option to clear your cache memory. If you are running Microsoft Internet Explorer on a PC, select View > Internet Options > General > Temporary Internet File > Delete Files. |
None | Microsoft Internet Explorer 4.01: Times out after 5 minutes. | Microsoft 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 | Microsoft Internet Explorer 4.01: Unable to move back in Reachability Dashboard > Device Info > Browse | Due to the Microsoft Internet Explorer history mechanism, there is no fix for this, as Microsoft Internet Explorer does not have a way to clear an entire frameset. To work around this problem, click on a different item under Device Center. |
CSCdk26130 | Microsoft Internet Explorer 4.01: Printing from browser | When trying to print Device Configuration or Syslog (Java-based) reports from Microsoft Internet Explorer running on Windows 95, you get a system error. To work around this problem, save the HTML version of the report to your local disk, then print the report from your local machine. |
CSCdk31703 | Microsoft Internet Explorer 4.01: Device Configuration task failures | Using Microsoft Internet Explorer 4.x on a machine with an installation of Microsoft J++ might cause some |
CSCdk33035 | Microsoft 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 Microsoft Internet Explorer are opened for use with Essentials on the same desktop by launching them from the Start > Programs > Internet Explorer interface or from an icon on the desktop, Microsoft Internet Explorer generates incorrect authorization failures when you are correctly logged in. To work around this problem, start new browser windows using the New option from within the browser. |
CSCdj50947 | Netscape Navigator 4.x: Open frame in new window is inoperative | The Netscape 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 | Netscape Navigator 4.x: Reachability Dashboard not updating | On Solaris, HP-UX, and AIX, Netscape Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > |
CSCdj57449 | Netscape Navigator 4.x: Help > Glossary Back button links to contents | If you access the Glossary (Help > Glossary) with Netscape Navigator 4.05 on a Solaris, HP-UX, or AIX system, 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. |
CSCdk34547 | Netscape Navigator 4.x: Wrong date displayed for time zones with minute offset | Netscape Navigator 4.x does not display the correct month and day for GMT time zones containing offset minutes |
CSCdk44551 | Netscape Navigator 4.x: Self Test Collect server information report dated 25 days earlier | Netscape 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 Microsoft Internet Explorer 4.01. |
CSCdk44743 | Netscape 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
The workarounds include:
If you are using Netscape 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. |
| ID | Summary | Explanation |
|---|---|---|
CSCdj64037 | Aborting Essentials installation procedure | If you abort the Essentials installation, not all required components will be installed. To recover from an aborted installation, delete all files in the Essentials directory, then start the Essentials installation procedure from the beginning. |
CSCdm18788 | Database upgrade failure | Both Essentials 2.0 to 2.2 and 2.1 to 2.2 upgrades will fail if the database engine cannot come to a ready state within 5 seconds. To work around this problem, make sure all server applications are stopped before you upgrade. |
| ID | Summary | Explanation |
|---|---|---|
CSCdm55336 | Error Message during restore: | This problem is an error from the .tar file in the restore log. You can ignore this message only if the error is reported against the subdirectories that the .tar file creates during the restore operation. This error is valid if the .tar file reports an error for the files it is restoring. The working directory should be the _root_ directory on the drive where CiscoWorks2000 is installed, not the CiscoWorks2000 directory itself. The default directory for CiscoWorks2000 is To work around this problem, enter the following command at the DOS Prompt: perl c:\Program Files\CSCOpx\bin\ |
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. |
| ID | Summary | Explanation |
|---|---|---|
CSCdk43198 | Graphs display incorrectly for some color depths | When using either Netscape or Internet Explorer on a Windows based desktop, the labels on the X-axis of the Availability graphs are not displayed correctly. The NetCharts package incorrectly displays the labels if the Windows desktop is using 24 bit color. To work around this problem, double click the Display icon from the Windows Control Panel to launch the Display Properties dialog. Select the Settings tab and verify that the Color Palette is set to either 256 colors, or 65536 colors. |
CSCdm05454 | Protocol Distribution report shows 100% TCP/IP utilization for Catalyst 5000 switches | If launched from 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 500 switches. If Protocol Distribution is launched directly from under the Availability menus, the application does recognize that No views are configured for Protocol Distribution monitoring. |
| ID | Summary | Explanation |
|---|---|---|
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 ( |
CSCdk35153 | Chassis modem table is not polled correctly | Inventory reports only show modems that have been configured. 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. |
CSCdm01805 | Adding devices to Essentials fails | Adding devices to Essentials fails if case-insensitive community strings already exist in the database. If you add a device to the Essentials database with community strings similar to those already present in the ACCESS_DATA table (the only difference being the use of upper and lower case), the import will fail. Because community strings are not removed from the database, this problem also applies to devices removed from the database. Note All fields (RO_Comm_Str, RW_Comm_Str, Telnet_Password, Enable_Password) must contain the same case-insensitive values. |
| ID | Summary | Explanation |
|---|---|---|
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 those 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 the syntactic correctness of configuration files uploaded to the device via the import command. As a result, the import is reported successful even if the configuration file is invalid.The configuration update will not succeed on the device, but cwconfig cannot detect this failure. |
CSCdk12667 | Command-Line Syntax Errors | When a cwconfig session has multiple syntax errors, only the first detected error is reported; the others remain unlisted. |
| ID | Summary | Explanation |
|---|---|---|
None | Error invoking cwconfig | When CiscoWorks2000 is installed on Windows NT in an NTFS partition, only users in the administrator groups can use cwconfig. If cwconfig is invoked by a user not assigned to the administrator group, the error message "Error invoking cwconfig" is displayed and the program exits. To use cwconfig, users should either be assigned administrator privileges, or have Read-Write access to the |
| ID | Summary | Explanation |
|---|---|---|
None | MultiSwitch Feature Card for Catalyst 6000 and RouterSwitch Feature Card for Catalyst 5000 | Backup of current image during image distribution fails for MultiSwitch Feature Card for Catalyst 6000 and RouterSwitch Feature Card for Catalyst 5000. Images running on these devices cannot be imported using the image baseline or image synchronize task. |
CSCdk87046 | Problem upgrading software on Catalyst 5000 switches | Upgrading software on a Catalyst 5000 switch from an earlier version code 2.x or 3.x to 4.x can sometimes cause problems. The MCP software does not get erased from the Flash memory 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 from the console Supervisor. |
CSCdk93048 | Downloading IOS image to the slot0 flash card on 8510CSR device fails | When an IOS image is downloaded to the slot0 flashcard on the 8510CSR device using SNMP, the copy operation fails with copyUnknownFailure and the formatting information on the Flash card is erased. To work around this problem, use slot1 instead of slot0 as the target location of the IOS image. |
CSCdm56639 | Software Manager fails with Cisco IOS devices running the following software versions: 12.0(1), 12.0(2), 12.0(1)T, 12.0(1)T1, 12.0(1)XA3, 12.0(1)XB, 12.0(1)DB, 12.0(1)XD, and 12.0(1)XE (For all Cisco hardware platforms). Software Manager fails with low-end IOS hardware platforms when running the following software versions: 12.0(4), 12.0(5), 12.0(4)P, 12.0(5)P, 12.0(4)T, 12.0(5)T. | Do not upgrade devices to these software releases. Upgrading software devices to these releases will make further Software Manager Management upgrades impossible. If you have already upgraded devices to these software releases, you will need to manually upgrade the devices software to a supported IOS software release. |
CSCdm58566 | Catalyst 6000 image import produces incorrect version format | The "Edit 6000-Supervisor Image attributes" dialog box shows an incorrect image version number during import from either Catalyst 6000 devices, the filesystem, or CCO. To work around this problem, enter the correct version number in the "Edit 6000-Supervisor Image attributes" dialog box. |
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 > Add Image to Library from CCO. 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. |
| ATM Module upgrades on Catalyst switches (continued) | Token Ring LANE software image version umbers start from 70.1(1) onwards and the image file names follow c5atm-trlane.* format. To upgrade software images on WS-X5161, WS-X5162, WS-X5167, WS-X5168 modules, the Supervisor module must be running at least 4.1(1) software. These modules run software images whose file names follow the c5atm-wtall.* format. (For example c5atm-wtall.113-2a_WA4_4b.bin is the file name for LANE ATM software.) |
|
| LANE ATM software on these modules include Ethernet LANE, Token Ring LANE and PVC Traffic Shaping features. While importing these software images into the library from the File System/Device, input the part of the file name after WA as the software as the software version number. In the example above 4(4b) is the software version number. When this software is downloaded to an ATM module, the ATM module version number from show module command will display as 11.3(2a)WA4(4b). No problem results if the version numbers displayed using the show module command do not match Software Management version numbers |
| 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) |
| ID | Summary | Explanation |
|---|---|---|
CSCdk47488 | Changing the default logging facility | Syslog messages are logged to a file. The file is configured to store local7.info messages from routers, but for the PIX devices, the default is not local7. To work around this problem, the PIX device needs to be set 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 users to delete devices from the CWSI database. To run the command line utility for deleting devices:
Step 1 Exit CWSI Campus.
Step 2 Enter stopcwsiserver.bat.
Step 3 Enter checkdb.bat(in%CWSIROOT%\bin) from the 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.bat, 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 users 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 the user to type in 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.
| ID | Summary | Explanation |
|---|---|---|
CSCdm50212 | JRE related problems might cause CWSI Campus to fail | If you restart the application, the data from your previous session will be retained. |
CSCdm60136 | Failed report | CWSI Campus will fail to report multilayer switch router processors that are configured on a Cupernico router switch feature card on the Galilei NMP. |
| ID | Summary | Explanation |
|---|---|---|
None | Upgrade Essentials 2.0 to Essentials 2.2 disables CWSI 2.2 | If Essentials 2.0 and CWSI 2.2 are installed, you cannot run CWSI 2.2 after upgrading Essentials 2.0 to Essentials 2.2. You must upgrade from CWSI 2.2 to CWSI 2.4 to run CWSI Campus successfully. |
None | Upgrade Essentials 2.1 to Essentials 2.2 disables CWSI 2.3 | If Essentials 2.1 and CWSI 2.3 are installed, you cannot run CWSI 2.3 after upgrading Essentials 2.1 to Essentials 2.2. You must upgrade from CWSI 2.3 to CWSI 2.4 to run CWSI Campus successfully. |
CSCdm62032 | Uninstalling CWSI deletes TrafficDirector files | If you want to keep directory files created while using TrafficDirector, you must save them prior to uninstalling CWSI. |
CSCdm63990 | After uninstall of CWSI 2.4, stand-alone Traffic Director 5.7 installation fails | If you upgrade to CWSI 2.4 from CWSI 2.3 or 2.2 and then uninstall CWSI 2.4, the uninstallation will not remove the CWSI 2.4 registry key. To work around this problem: Step 1 Select Start > Run and enter regedit in the Open field to bring up the Registry Editor.
Step 2 Delete the CWSI registry key: HKEY_LOCAL_MACHINE\SOFTWARE\ Step 3 Run TrafficDirector setup again. |
CSCdk88673 CSCdm62351 | MIB compilation errors in SNMPc and | These errors appear during CWSI installation They will not affect the function of the device packages. Because some of the MIBs might not be properly loaded into HP OpenView, you will not be able to do use the HP OpenView MIB Browser to view those MIBs. |
| ID | Summary | Explanation |
|---|---|---|
None | Catalyst 3000: Moving ports between virtual local area networks | Moving ports between virtual local area networks (VLANs) will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2). |
None | ATM cloud on network map | The ATM cloud might appear on the network map because of an incorrect image version on the 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: wsx5155, wsx5154, wsx5153, wsx5156, wsx5157, wsx5158, wsx5163, wsx5164. To work around this problem, download the image supported by CWSI on the LANE/ATM card, then clean the database and restart CWSI server. |
CSCdj06709 CSCdj28689 | LAN Emulation (LANE): Catalyst 3000 switches | On Catalyst 3000 switches, LEC and 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. |
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 is:
|
CSCdm20592 | Upgrade to CWSI 2.3 does not discover newly supported devices properly | Device discovery will not work properly for newly supported device types when upgraded to CWSI 2.3 from an older version. This happens only for those newly supported devices that are shown as unknown in the topology map of an older version. To work around this problem, remove the newly supported devices that are shown as unknown from the database by using checkdb -d IP. |
| ID | Summary | Explanation |
|---|---|---|
None | Some ATM-VLANS may not get discovered | Some ATM-VLANS may not get discovered by CWSI if LANE/ATM cards are running images 3.2(8), 3.2(10), and 3.2(11) on the following OC3 card models: wsx5155, wsx5154, wsx5153, wsx5156, wsx5157, wsx5158, wsx5163, wsx5164. To work around this problem, download the image supported by CWSI on the LANE/ATM card, then rediscover the network. |
CSCdj63616 | Backup LECS on LS1015 created but not displayed | 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 images | VLAN configuration sometimes fails on Catalyst 5000 switches (with SMP Release 3.1.1, 3.2.1, 3.2.2, To work around this problem, enter the clear config all command on the device to get the device back to its working state. |
CSCdk31419 | Configuring a configuration server or default ATM-VLAN might cause error message | Configuring a configuration server or configuring the default ATM-VLAN might cause the following message to appear: 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.SnmpValueExceptionSnmpResponseBadValueon <ipAddress> > The following are possible causes: Wrong community strings Wrong device image Command already exists in the running configuration file of the LANE module (lane config auto-config-atm-address or lane config config-atm-address) 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. |
CSCdm18742 | Configuring backup Lane Config Server may result in creation of an active configuration server | If CWSI fails to create appropriate ILMI address registration entries (related to Lane Config Server) in ATM switches, this can happen. 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. |
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. |
| ID | Summary | Explanation |
|---|---|---|
None | UserTracking Discovery: UserTracking 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. UserTracking could discover additional end user nodes that are not in the selected subnet. |
None | UserTracking Discovery: UserTracking might not reflect most current state of the 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 | 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 | 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) 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:00pm, and at 1:00pm the interval is changed to 10 minutes, the next minor acquisition will occur at 2pm, followed by one at 2:10pm, 2:20pm, and so forth. |
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 (for example, 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 button or New Layout button in the Customize Layout dialog before displaying new UserTracking entries. |
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 |
CSCdk20561,CSCdm19077 | Enduser incorrectly displayed as Token Ring on Catalyst 3000 switch | The Catalyst 3000 switch returns incorrect CAM/Bridge table information for non-existent VLANs. This causes UserTracking to show entries with duplicate MAC addresses and with incorrect port and VLAN information. |
| ID | Summary | Explanation |
|---|---|---|
None | Ping | The TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the Windows NT or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete the $NSHOME/usr/pingoff file. |
None | Generic indexing scheme | To enable the TrafficDirector application, 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 properties file to the Catalyst 1900 and 2800 switch, run dvclean and perform the installation again. |
None | Network Analysis Module Release 4.3(1a) only |
|
CSCdk79994 | Upgrading from TrafficDirector |
|
CSCdk29981 | Learning VLANs and FECs | VLANs and FECs are only learned on Catalyst 5000, 6000, 2948G, and 2926G series devices. |
CSCdk40368 | Viewing managed interfaces | In the Add Agent window, if you select View, the managed interface of the SwitchProbe device is displayed. You must deselect this agent before saving any of the entries as agents. |
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, 5000, and 6000 series and the Catalyst 2926G and 29489 switches), the TrafficDirector application does not autoconfigure itself as a trap receiver. You must manually set the trap destination from the switch command-line interface (CLI). |
CSCdm10165 | No script file launched | When an alert is received in the TrafficDirector application, the script associated with that threshold is not always launched. |
CSCdm51836 | Alert Monitor does not show description correctly | The trap message contains only the object identifier (OID) instead of the description. |
CSCdm52292 | Cannot start All IP Talker for Traffic Monitor using the Network Analysis Module | When selecting a non-roved port and starting an application such as TopN Talker, you must use Configuration Manager to rove to the selected port and enable the correct domain required for TopN Talker. You must then return to Traffic Monitor and start the application. This problem has been observed on switches using the Network Analysis Module because when a port is roved, a default properties file is installed on the roving agent. Because there are fewer domains enabled in the default properties file for the Network Analysis Module than there are on SwitchProbe devices, the Network Analysis module is more likely to exhibit these symptoms. |
CSCdm60856 | Cannot launch TrafficDirector with a Catalyst 8510 link | For a Catalyst 8510 link, the Catalyst 8510 package should be installed to start TrafficDirector from the CWSI Topology map |
| ID | Summary | Explanation |
|---|---|---|
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 is currently 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 client database. |
None | 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 | 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 |
|
| ID | Summary | Explanation |
|---|---|---|
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 can exhaust resources on Windows 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 When StackMaker runs on Catalyst 1900 devices, some debug output is printed to the console. You can ignore this output. |
None | 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. |
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. |
CSCdk23763 | Dr. Watson for Windows NT error | If you have an AS5200, AS5300, Catalyst 216, and Cisco 3640 in a stack, and you are using CiscoView in CiscoWorks Windows, LS3 Setup might crash with a Dr. Watson for Windows NT error with the error message "wish.exe exception access violation." This crash occurs only if you click any item under Connection Info twice and if the Catalyst 216 is the seed device. |
| ID | Summary | Explanation |
|---|---|---|
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. |
| ID | Summary | Explanation |
|---|---|---|
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 Device > Configure |
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. |
| ID | Summary | Explanation |
|---|---|---|
None | History control bucket | The maximum history ControlBucketGranted is 20 for the current release of the Catalyst 1900 series. |
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. |
| ID | Summary | Explanation |
|---|---|---|
None | Catalyst 2600 device package contains two versions of the Enterprise MIBs for the Catalyst 2600 switch |
If you are using a MIB browser tool, you will see the MIB variables defined in each of the above 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 upon the release of software in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to version 2.2.1 or later. |
| ID | Summary | Explanation |
|---|---|---|
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. |
None | Catalyst 2600 device package contains two versions of the Enterprise MIBs for the Catalyst 2600 switch |
If you are using a MIB browser tool, you will see the MIB variables defined in each of the above 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 upon the release of software in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to version 2.2.1 or later. |
| ID | Summary | Explanation |
|---|---|---|
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 might 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 on the Config > Module menu. |
| ID | Summary | Explanation |
|---|---|---|
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 | Domain Configuration and EtherChannel Configuration tools | The Domain Configuration and EtherChannel Configuration tools are not supported on Windows 95. |
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. |
| ID | Summary | Explanation |
|---|---|---|
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. |
| ID | Summary | Explanation |
|---|---|---|
None | Broadcast Suppression support | ATM, FDDI, and CDDI do not support Broadcast Suppression. |
None | Machines that do not have a /tftpboot directory | In machines that do not have a /tftpboot directory (such as a PC), an error is displayed whenever the Upload/Download feature is invoked on a Catalyst 5000 module. |
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 speed 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 |
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. |
| 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 |
| ID | Summary | Explanation |
|---|---|---|
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 dialogs for these will return errors. |
None | Community String Mismatching | When the user enters values for the 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 error conditions, 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 are not displayed in CiscoView for a Catalyst 1900 with a VLAN is highlighted in VLAN Director. |
| ID | Summary | Explanation |
|---|---|---|
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 T1/ E1 card is present. |
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 below 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 can't be browsed in SNM and EM platforms. |
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. |
| ID | Summary | Explanation |
|---|---|---|
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. |
| ID | Summary | Explanation |
|---|---|---|
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 |
|
None | Upstream Channel MIB Variable Setting |
|
None | Fast Serial MIB Variable Display Values | The Fast Serial rport 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 can't be browsed in SNM and EM platforms. |
| ID | Summary | Explanation |
|---|---|---|
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 menu for the 7204, 7206 has front view too but all the other 7000 series routers have just the rear view. |
CSCdj93913 | Delta values appear as absolute values | When using CV 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. |
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 does not generate any errors. |
| ID | Summary | Explanation |
|---|---|---|
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. |
CSCdm08347 | Problem opening Help > Contents | When Help > Contents is selected from CiscoView the help window may 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.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Aug 8 16:37:35 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.