|
|
These release notes describe the new features and caveats for the components of the CW2000 family of products:
This document contains the following sections:
The systems requirements for Essentials and CWSI Campus are listed in Table 1.
| Requirement Type | Essentials | Essentials and CWSI Campus |
|---|---|---|
System hardware |
|
|
Memory (RAM) | 192 MB minimum; 256 MB recommended | 256 MB minimum; 256 MB recommended |
Available drive space1 |
|
|
System software2 | Windows NT Workstation 4.0 or Windows NT Server 4.0 US English or Japanese versions | Windows NT Workstation 4.0 or Windows NT Server 4.0 US English or Japanese versions |
Browser | Microsoft Internet Explorer 4.01 with Service Pack 13 | Netscape Navigator4 4.04 or 4.05 or Microsoft Internet Explorer5 4.01 or higher with Service Pack 1 (without Active Desktop)6 |
Additional software7 |
|
|
Note the following browser information:
| Browser | Version | Operating System |
|---|---|---|
Netscape Navigator1 | 4.04 or 4.05 | Solaris 2.6, Solaris 2.5.1, Windows NT 4.0, Windows 95, AIX 4.2.1 or 4.3, and HP-UX 10.10, 10.20, or 11.0 |
Microsoft Internet Explorer2 | 4.01 with Service Pack 13 | 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. |
No browser is required for the Essentials server system. Client systems must have a supported browser installed. Refer to Installing Resource Manager Essentials and CWSI Campus on Windows NT for more information.
This section provides further information to help you choose a system that will best meet your specific needs.
Three major considerations can help you to determine your minimum system configuration requirements.
1. Consider the number of managed devices to be polled by Availability.
2. Consider the number of Syslog messages expected daily.
3. Consider the number of managed devices expected in Inventory and
Device Configuration.
Availability is the primary consideration, after which you can then consider syslog messages and managed device expectations and determine your needs accordingly.
Table 3 lists system recommendations for Windows NT running Essentials only.
| Minimum System Configuration | Availability (# Managed Devices) | Syslog (# Messages/Day) | Configuration (# Managed Devices) | Inventory (# Managed Devices) |
|---|---|---|---|---|
Pentium II 300 | 0 - 250 | 0 - 60,000 | 0 - 750 | 0 - 750 |
Dual Pentium II 300 | 250 - 750 | 60,000 - 150,000 | 750 - 2,500 | 750 - 2,500 |
Quad Pentium Pro | 500 - 1,000 | 150,000 | 2,500 - 5,000 | 2,500 - 5,000 |
For CWSI Campus, use a system configuration that will support the number of devices you want to manage using CWSI Campus and the number of end hosts you plan to manage using UserTracking. Select a configuration that will support the application with the higher requirement. For example, if you have 82 devices and 2500 end hosts, choose the Pentium II or better. See Table 4 for the CWSI Campus system recommendations.
| Minimum System Configuration | Number of Network Devices | Number of End Hosts (managed by UserTracking) |
|---|---|---|
Pentium II 300 MHZ | <100 | <2000 |
Dual Pentium II 300 MHZ | 100 - 250 | 2000 - 5000 |
Quad Pentium II 300 MHZ | 250 - 500 | 5000 - 10,000 |
Review the information in this section carefully before installing the product.
Installing Essentials is a multistep process that must be performed in a specific order. Depending on your system requirements, installing the software prerequisites might require three or more separate Microsoft software application installations, in addition to your specified options. Refer to Installing Resource Manager Essentials and CWSI Campus on Windows NT for step-by-step installation instructions.
 | Caution The order in which you install the software is crucial to the successful installation of Essentials. You must install the software in the order specified in the Installing Resource Manager Essentials and CWSI Campus on Windows NT, or you could disable your system. |
Also, note the installation information in the following sections.
If you received Essentials as part of a bundled package with CWSI Campus, refer to Installing Resource Manager Essentials and CWSI Campus on Windows NT for installation instructions.
If you install Essentials and CWSI Campus as a bundled package, be aware that some components and processes are shared between the two applications. For more information, refer to Installing Resource Manager Essentials and CWSI Campus on Windows NT.
After the uninstall is completed, an empty CSCOpx directory might remain. Verify the directory is empty and does not contain any user files.
The workaround is to manually remove the directory. [CSCdk47236]
Uninstallation might leave the following registry entries:
CWMIBDIR
SYBASE
If you move the configuration archive directory to a new location, for example, newDir, the Essentials uninstallation script deletes all files with the following extensions:
newDir\config\any_subdirectory\*running.cfg
newDir\config\any_subdirectory\*startup.cfg
newDir\config\any_subdirectory\*running.dfr
newDir\config\any_subdirectory\*running.dfc
newDir\config\any_subdirectory\*running.cmt
If you created your own files with these extensions, make sure you move them to a different directory before uninstalling Essentials.
These error messages do not affect Essentials operation and can be ignored. [CSCdk44100]
When an error message is too long, the message "Error 401. String variable is not large enough for string. Please check string declarations" is displayed.
The workaround is to proceed with the Essentials installation. The full text of the error message is available in the installation log file. Please review the file after the installation has completed, then report the problem to the Cisco TAC. [CSCdk49397]
During the upgrade of Cisco Resource Manager 1.1 to Essentials from the CD-ROM, you might see the error message "Cannot find isqllog.log." This message can be ignored. The information in this file is available in the product install log c:\rme_inNNN.log, where NNN is a three-digit number starting with 001. [CSCdk36909]
After uninstalling Resource Manager, registry entries remain in the NT registry that will cause the CWMIBDIR environment variable to remain in a user's environment. [CSCdj75036]
NT uses both a computer name and a host name. The computer name is used for SMB, LanMan, and so forth; the host name is used for TCP/IP.
Verify your PX-HOST is set to the host name for proper operation. [CSCdk28171]
The Back button in the installation screen is inoperative. If you want to make changes during the installation process (select or deselect items), abort the installation procedure and then restart. [CSCdk25654]
Users cannot launch the login window from the client machine if the class path is set in the autoexec.bat file.
The workaround is to verify that the autoexec.bat file contains no class path that points to anywhere other than the running version of Netscape. [CSCdk14878]
If you abort the Essentials installation procedure before it completes, not all required components are installed, and Essentials will not operate successfully. To recover from an aborted installation, start the Essentials installation procedure from the beginning. [CSCdj64037]
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 Windows NT for more information.
Software Management stores images that are not removed by the Essentials uninstallation procedure. If you want to permanently remove Essentials, you need to remove these files manually from C:\Program Files\CSCOpx\files\sw_images.
If you uninstall Essentials and restart the Windows NT system, the installation directory, C:\Program File\CSCOpx, remains on the system. The following directories also remain:
You can remove these directories manually after the uninstall procedure, or keep them on your system for future reference. [CSCdj74400]
Review the following information before installing CWSI Campus 2.2:
This section provides a procedure for upgrading from CWSI Campus 2.1.1 to 2.2. Before upgrading, consider the following notes:
Step 1 Close all CWSI Campus windows before upgrading and reinstalling CWSI Campus.
Otherwise, the install process aborts while trying to overwrite files that are in use.
Step 2 Start the install process using the installation guide.
The install process looks for any previous CWSI Campus installation and its version.
Step 3 You are prompted to confirm that you want to save the database and the data files. If you click No, these files are overwritten. If you click Yes, a backup directory is created under the CWSI Campus installation directory.
The CWSI Campus database cwsi.db and the data files (ani.properties, atmd.properties, and communities.dat) are copied into this directory. These files are copied back to their original locations when the installation is complete.
The system displays information about the previous installation of CWSI: the installation folder, the database folder, the seed device and the components that are installed (Cisco View, Traffic director and ATM Director), if any.
The Cisco View devices directory is deleted to allow you to install the latest version of the device packages and avoid the possible incompatibility with the shared device files. You must select the previously installed packages in addition to the new packages.
Step 4 Reinstall and select all the optional CWSI Campus components (TrafficDirector, ATMDirector, and Cisco View) that were installed previously.
You can uninstall CWSI Campus if necessary. Start the uninstallation program from the Start Menu.
Note the following caveats:
This section contains information, notes, and caveats for Resource Manager Essentials.
Essentials lets you import device information from both local and remote network management databases, identified in Table 5 and Table 6, respectively.
Essentials can be installed on the same machine as HP OpenView, CiscoWorks Windows 3.x, and CWSI Campus without any compatibility problems. If you plan to install all products on the same machine, check the compatibility notes of each product.
For remote device imports, the remote server must be a Solaris, HP-UX, or AIX machine. Essentials does not support remote device imports from Windows NT machines.
Table 5 and Table 6 list the software that Essentials supports for importing device information from local and remote systems. You can import remote devices from a UNIX workstation running the supported versions of CiscoWorks, HP OpenView Network Node Manager, or CiscoWorks for Switched Internetworks (CWSI).
| Software | Version |
|---|---|
HP OpenView Network Node Manager | 5.01 and 5.02 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1 |
CW2000 Campus | 2.2 |
CastleRock SNMPc | 4.1r, 4.2.4 |
| Software1 | Version |
|---|---|
HP OpenView Network Node Manager | 4.11, 5.0, and 5.01 |
CiscoWorks | 3.2 and 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1.1 |
CW2000 Campus | 2.2 |
| 1You can import remote devices from the listed software running on a UNIX system only. |
Essentials supports the devices listed in Table 7 through Table 11. See the "Cisco IOS Versions Supported" section for information on the supported Cisco IOS versions. See Table 11 for the devices the Essentials Software Management module supports.
It is possible to insert an ATM Signal Processor (ASP) card into slot 13 of a Catalyst 5500 chassis. Other LS1010 cards might also be inserted in the chassis. Due to hardware limitations, the supervisor card in the Catalyst 5500 cannot accurately detect the presence or status of these cards. As a result, Essentials inventory will not display this hardware correctly in certain reports, and available slots might be inaccurate. Hardware enhancements have been proposed to address this problem.
.
| Product Family | Devices Supported |
|---|---|
Cisco CS500 | CS500 |
Cisco/CiscoPro 7xx | 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 |
Cisco/CiscoPro 10xx | 1000, 1003, 1004, 1005, 1020 |
Cisco/CiscoPro 16xx | 1601, 1602, 1603, 1604, 1605 |
Cisco 2xxx | 2000, 2102, 2202 |
Cisco/CiscoPro 25xx | 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF |
Cisco 26xx | 2601, 2610, 2611 |
Cisco/CiscoPro 3xxx | 3000, 3101, 3102, 3103, 3104, 3202, 3204, 3620, 3640, |
Cisco switching access concentrator | MC3810 |
Cisco/CiscoPro 4xxx | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M |
Cisco 25xx access servers | 2509RJ, 2511RJ |
Cisco AS5xxx access servers | AS5200, AS5300, AS5800 |
Cisco 7xxx | 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 |
Viper Switch | CPW16, ESP2015 |
Catalyst | 1220, 1600, 1700, 1800, 1900, 1912, 2200, 2600, 2800, 2820, 2828, 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 2926, 3000, 3001, 3011, 3011 router, 3100, 3200, 3500, 3600, 3900, 3920, 5000, 5002, 5500, 5505, 5509, 5CRSM, 8510 |
CiscoPro EtherSwitch | 10/100, 1100, 1200, 1220,1220&L, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1601, Pro 16, 1900, 1900L, 2200 |
ATM switch | Light Stream 1010, 1015, 2020 |
Multiservice switch | BPX 8620, BPX 8650, IGX 8410, IGX 8420, IGX 8430, MGX 8220, IPX 8xxx |
SwitchProbe | WS-PB7-4ETH-32, WS-PB7-8ETH-32, WS-PB7-12ETH-64, WS-PB6-1ETH-8, WS-PB6-1ETH-16, WS-PB6-2ETH-16, WS-PB6-1TR-8, WS-PB6-1TR-16, WS-PB6-2TR-16, WS-PB6-ETHTR-16, WS-PB6-1WANETH-8, WS-PB6-1WANETH-16, WS-PB6-1WANTR-8, WS-PB6-1WANTR-16, WS-PB7-2WANTR-32, WS-PB7-3WANTR-32, WS-PB7-4WANTR-32, WS-PB7-HSSIETH-32, WS-PB8-DFDDIETH-32, WS-PB8-ATM3ETH-32, WS-PB8-1FEHD-TX-32, WS-PB8-1FEFD-TX-32, WS-PB8-2FEHD-TX-32, WS-PB8-1FEHD-FX-32, WS-PB8-1FEFD-FX-32, WS-PB8-2FEHD-FX-32 |
Workgroup concentrator | 1000, 1100, 1400 |
FastHub | 300, 100+, 316T, 3116, 316C, 2116, 216T, 116T, 116C, 1116 |
MicroHub | 1502, 1503, 1516 |
General SNMP devices | Most MIB II compliant |
| Product Family | Devices Supported |
|---|---|
Cisco CS500 | CS500 |
Cisco/CiscoPro 7xx | 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 |
Cisco/CiscoPro 10xx | 1000, 1003, 1004, 1005, 1020 |
Cisco/CiscoPro 16xx | 1601, 1602, 1603, 1604, 1605 |
Cisco 2xxx | 2000, 2102, 2202 |
Cisco/CiscoPro 25xx | 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF |
Cisco 26xx | 2601, 2610, 2611 |
Cisco/CiscoPro 3xxx | 3000, 3101, 3102, 3103, 3104, 3202, 3204, 3620, 3640, |
Cisco switching access concentrator | MC3810 |
Cisco/CiscoPro 4xxx | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M |
Cisco 25xx access servers | 2509RJ, 2511RJ |
Cisco AS5xxx access servers | AS5200, AS5300, AS5800 |
Cisco 7xxx | 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 |
Catalyst | 1220, 1600, 1700, 1800, 1900, 1912, 2200, 2600, 2800, 2820, 2828, 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 2926, 3000, 3001, 3011, 3011 router, 3100, 3200, 3500, 3600, 3900, 3920, 5000, 5002, 5301, 5500, 5505, 5509, 5CRSM, 8510 |
| Product Family | Devices Supported |
|---|---|
Cisco CS500 | CS500 |
Cisco/CiscoPro 7xx | 751, 752, 753, 761, 762, 765, 766, 771, 772, 775, 776 |
Cisco/CiscoPro 10xx | 1000, 1003, 1004, 1005, 1020 |
Cisco/CiscoPro 16xx | 1601, 1602, 1603, 1604, 1605 |
Cisco 2xxx | 2000, 2102, 2202 |
Cisco/CiscoPro 25xx | 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF |
Cisco 26xx | 2601, 2610, 2611 |
Cisco/CiscoPro 3xxx | 3000, 3101, 3102, 3103, 3104, 3202, 3204, 3620, 3640, |
Cisco switching access concentrator | MC3810 |
Cisco/CiscoPro 4xxx | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M |
Cisco 25xx access servers | 2509RJ, 2511RJ |
Cisco AS5xxx access servers | AS5200, AS5300, AS5800 |
Cisco 7xxx | 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 |
Viper Switch | CPW16, ESP2015 |
Catalyst | 1220, 1600, 1700, 1800, 1900, 1912, 2200, 2600, 2800, 2820, 2828, 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 2926, 3000, 3001, 3011, 3011 router, 3100, 3200, 3500, 3600, 3900, 3920, 5000, 5002, 5301, 5500, 5505, 5509, 5CRSM, 8510 |
CiscoPro EtherSwitch | 10/100, 1100, 1200, 1220,1220&L, 1400, 1402, 1408, 1420, 1422, 1428, 1442, 1448, 1601, Pro 16, 1900, 1900L, 2200 |
ATM switch | Light Stream 1010, 1015, 2020 |
Multiservice switch | BPX 8620, BPX 8650, IGX 8410, IGX 8420, IGX 8430, MGX 8220, IPX 8xxx |
Workgroup concentrator | 1000, 1100, 1400 |
FastHub | 300, 100+, 316T, 3116, 316C, 2116, 216T, 116T, 116C, 1116 |
MicroHub | 1502, 1503, 1516 |
General SNMP devices | Most MIB II compliant |
| Product Family | Devices Supported |
|---|---|
Cisco/CiscoPro 10xx | 1000, 1003, 1004, 1005 |
Cisco/CiscoPro 16xx | 1601, 1602, 1603, 1604 |
Cisco/CiscoPro 25xx | 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF |
Cisco 26xx | 2601, 2610, 2611 |
Cisco/CiscoPro 3xxx | 3620, 3640 |
Cisco switching access concentrator | MC3810 |
Cisco/CiscoPro 4xxx | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M |
Cisco 25xx access servers | 2509RJ, 2511RJ |
Cisco AS5xxx access servers | AS5200, AS5300, AS5800 |
Cisco 7xxx | 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513 |
Catalyst | 2900, 2908XL, 2916M-XL, 2924XL, 2924CXL, 5000, 5002, 5500, 8510, C5RSM, Catalyst 5000 modules supported: NMP, TR, FDDI, ATM, CDDI |
ATM switch | Light Stream 1010, 1015 |
| Product Family | Devices Supported |
|---|---|
Cisco/CiscoPro 7xx | 760 series, 770 series. |
Cisco/CiscoPro 10xx | 1000, 1003, 1004, 1005. |
Cisco/CiscoPro 16xx1 | 1601, 1602, 1603, 1604, 1605. |
Cisco/CiscoPro 25xx2 | 2500, 2501, 2502, 2503, 2504, 2505, 2506, 2507, 2508, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 1516, 2517, 2518, 2519, 2520, 2521, 2522, 2523, 2524, 2525, 2501CF, 2502CF, 2501LF, 2502LF. |
Cisco 26xx | 2601, 2610, 2611 |
Cisco/CiscoPro 3xxx | 3620, 36403. |
Cisco switching access concentrator | MC3810. |
Cisco/CiscoPro 4xxx | 4000, 4000-M, 4500, 4500-M, 4700, 4700-M. |
Cisco 25xx access servers 4 | 2509RJ, 2511RJ |
Cisco AS5xxx access servers5 | AS5200, AS5300, AS5800 |
Cisco 7xxx, 7500 RSP series routers6 | 7000, 7010, 7204, 7206, 7505, 7506, 7507, 7513, including CIPs |
Catalyst7 | 29008, 2926, 5000, 5002, 5005, 5500, 5505, 5509, 8500, 8510, C5RSM, Catalyst 5000 modules supported: NMP, TR, FDDI, CDDI, ATM; software upgrades supported. |
ATM switch | Light Stream 1010, 1015. |
When using Essentials with Token Ring switching products, verify you have installed the firmware revisions as noted in Table 12:
| Product | Module | Revision Number |
|---|---|---|
Catalyst 3900 | Main | 3.0(2) |
Catalyst 3900 | ATM | 1.2(3) |
Catalyst 5000 | Supervisor module | 3.2(2) |
Catalyst 5000 | Token Ring module | 3.2(2) |
Catalyst 5000 | ATM line module | 70.1(1) |
Table 13 lists platform-specific software supported when using Essentials on Catalyst devices:
| Software | Revisions |
|---|---|
Supervisor I, Supervisor II | 2.1 - 4.2 |
Supervisor III | 3.1 - 4.2 |
ATM | 2.2 - 4.7 |
Token Ring | 3.1 - 4.2 |
FDDI, CDDI | 2.1 - 3.1 |
Support is provided for devices running Cisco IOS Versions 10.3 to 11.3 only. Unless your devices are running Cisco IOS Version 10.3 or later, not all MIB values may be supported. As a result, devices running versions of Cisco IOS earlier than 10.3 might not provide all device details in the inventory reports.
This section contains the notes and general caveats that apply to Essentials on Windows NT operating systems. It consists of the following sections:
On Windows NT Workstation 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.
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 Server 4.0.
If a graph looks awkward, or if text scrolls off a screen, reload or refresh the browser page. Usually, if you reload or refresh the page, the problem corrects itself.
Some e-mails sent to the user contain broken URL links. The workaround is to log in to Essentials, then use the Essentials tree control to perform the operation.
To print an exact copy of an Essentials screen, use the Print Screen or Capture Screen function on your machine.
When using Netscape 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 (Netscape: Edit > Preferences > Advanced > Accept all cookies; Internet Explorer: View > Internet Options > Advanced, select Cookies). [CSCdk17516]
If you are upgrading your software from Resource Manager 1.1 to Essentials 2.0, 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.
The login dialog is not shown after you upgrade your version of Internet Explorer. The workaround is to flush your browser cache. [CSCdk18245]
The following sections describe caveats for particular web browsers.
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. [CSCdk27845]
When the device selector is shown on some of the Essential screens, if the Finish button is clicked before the applet code has finished initializing, a java script popup error displays.
You can ignore this message, because the device selector works normally. [CSCdk07201]
The Event Channel Admin screen (Admin > System Admin > Event Channel Admin) might hang or incorrectly report that "Event Channel Services are not running" if one of the processes using the Event Channel is not responding to the Event Channel manager.
If the Event Channel Admin screen hangs or reports the system is down, verify the EDS process is running using the Process Status screen (Admin > System Admin > Process Status). If running, check the daemons log (Program Files\CSCOpx\log) for process failures or errors in EDS, SyslogAnalyzer, or ChangeAudit. EDS and the dependent processes might need to be restarted if failures are found. [CSCdk09614]
For Catalyst 5500 devices, you must adjust SNMP parameters. You must stop and restart the DIServer and ICServer after you modify the SNMP parameters under Admin > General Setup. [CSCdk34633]
Some proxy or firewall products require users to be authenticated before accepting or forwarding connections. The Essentials proxy function does not provide authentication information to these proxy servers and requires per-user authentication information itself. [CSCdk05720]
When you add or import a device or change device information, avoid using angle brackets (< or >) in the User or Serial Number fields. When some browsers encounter these characters, they might interpret the information incorrectly. [CSCdj24567]
If you encounter problems when importing devices, make sure your target system is configured correctly. Consult the following Essentials online help sections for instructions on what you need to do before importing devices:
All Essentials scripts are executed by the web server in the bin account. This anonymous user account is created by Essentials during the installation procedure.
This account is created for anonymous Web login and is restrictive so it can provide security. It is also created as local to the system on which Microsoft IIS is installed. As a result, Essentials does not usually see shared network directories on Windows NT servers.
If you determine that it is appropriate for Essentials to access a network drive, you can add the necessary permissions for accessing the network drive to the bin account. All persistent drive mappings will be available to Essentials.
We recommend that you not make network drives available for Essentials because this can potentially become a security flaw. [CSCdj53223]
The Essentials Admin > System Admin > Process Status command causes an unusually large number of error messages to be written to the file C:\Program Files\CSCOpx\log\syslog.log, which causes this file to grow by approximately 100K each time Process Status is used.
To workaround this problem:
Under certain conditions, the restore from backup function might exit with an error if it is run for the first time after a new installation of Essentials. You might receive the following error:
ERROR: tar command exited abnormally !!
If this error appears, rerun the restore backup function, and it will run successfully. [CSCdk32521]
When you select Admin > Inventory > Export to File and specify the filename to which the device information is to be exported, if the filename already exists, the system will overwrite the existing file and no warning or reconfirmation message appears. Caution should be used when specifying a filename, as it could potentially overwrite important files. [CSCdk48937]
For Y2K and Software Version Reports generated by Resource Manager 1.1, the EPROM revision is blank for software version 5.3(5) or greater; however, versions less than 5.3(5) are in the report. [CSCdj91789]
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.
The workaround is to go to the device and configure the modem for use, then reacquire the inventory data for the device. [CSCdk35153]
When devices such as the Cisco 2500 series 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.
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.
The workaround is to run the Detailed Device Report, which shows details about each Flash partition that was discovered when the router was added to inventory. [CSCdk10221]
If reports generated by export have data fields that contain commas, the Save As function saves the data as displayed in a CSV file. If this file is imported into another application as a CSV file, then the comma in the particular data field will be treated as a separator instead of part of the data for that field.
The workaround is to remove any unwanted commas that might cause data to be placed in separate fields when they should be placed in a single field. [CSCdk25851]
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.
If Tasks > Device Configuration > Update Archive is used frequently, or if running or startup configuration files are retrieved frequently from the configuration reports that provide access to these configuration files, after weeks or months of use, the Essentials product stops working correctly because it has run out of file descriptors.
The workaround is to go to Control Panel/Services and stop, then start the JRunProxyServer service, or enter the command net stop JRunProxyServer, followed by net start JRunProxyServer at the DOS prompt. [CSCdk54194]
If the log files created by Netsys under $ECSP_DATA/tmp/ do not have write permission to "All," other users cannot create the baseline. The log file permissions depend on the umask of the user. If the permissions are not set correctly, users will get the error message, "Unable to create baseline." To workaround this problem, change the permission of the log files. [CSCdk52137]
If you delete a device from the Essentials inventory, the corresponding Netsys report for that device is not removed. The old report remains, but it will not be updated. [CSCdk51481]
If the configuration archive is relocated, search by pattern (when no devices are selected) will not yield any results.
Click the Unload All Clients option. The page will be refreshed after the clients are unloaded. Then click the Load All Clients option. [CSCdk52938]
Partial failure for getting module configurations for Catalyst devices results in error strings being shown as part of the raw configuration, as well as raw diff. [CSCdk49749]
The following steps were omitted from the Essentials online help. To move the configuration archive by selecting Admin > Device Configuration > General Setup, you must perform the following steps:
Step 1 Stop the Change Audit process by selecting Admin > System Admin > Stop Process then selecting the ChangeAudit process.
Step 2 Move the configuration archive by selecting Admin > Device Configuration > General Setup.
Step 3 Start the Change Audit process by selecting Admin > System Admin > Start Process then selecting the ChangeAudit process.
When a cwconfig session has multiple syntax errors, only the first error detected by the tool is reported; the others remain unlisted. Currently, there is no workaround. [CSCdk12667]
Currently, cwconfig cannot validate the syntax of configuration files uploaded to the device via the import command. Consequently, the cwconfig import process reports success even if a configuration file with invalid contents is attempted to be written to the device. The configuration update does not succeed on the device, but cwconfig cannot detect this failure. [CSCdk18495]
If cwconfig is invoked by a user that does not belong to the administrator's group, the error message, "Error invoking cwconfig" is displayed, and the program exits. A more detailed error message indication will be included in a future release. [CSCdk52609]
If the cwconfig commands get, start2run, or import are performed on too many devices in a single command, you might get an exception "java.lang.NoClassDefFoundError: org/omg/CORBA/INITIALIZE". As a workaround, change the operating system's configuration to increase the number of open file descriptors allowed per process. [CSCdk53421]
After you add or import devices, one or more devices might end up in the "Not Responding" category when the Admin > Inventory > Import Status window is displayed. A number of possible causes exist for this situation. Follow the procedures in the online help section "Diagnosing Non-Responding Devices." If these procedures do not resolve the situation, increase the SNMP timeout and retry parameters to a value that allows the device to be imported. Do not change the "fast timeout" value, only the "slow timeout" value. The slow timeout value is used on devices that fail to respond after the fast timeout and retry attempts have failed.
A defect exists in certain versions of Cisco IOS that causes the SNMP agent on router devices to become unresponsive to SNMP queries when certain MIB variables are polled. This bug only exists on routers that support the CISCO-FLASH MIB, which includes the following routers: Cisco 7200 series, 7500 series, RSMs (the router card for 5xxx switches) and 7000 series with RSPs.
The workaround is to upgrade Cisco IOS to 11.2(14)P or higher. Note that 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. [CSCdj60284]
A problem has been observed importing Catalyst 5500 devices on the Windows NT platform. Increasing the slow timeout and retry parameters to large values might allow you to work around this problem. Another possible workaround is to manage your devices from a Solaris-based workstation. [CSCdk51830]
Importing device information from a file that was exported from Essentials inserts empty annotation fields in the database for devices that have no annotation information configured in the NMS from which the device details got exported. Some of these annotation fields are used during the device startup configuration process. If these values are empty, startup configuration fails.
The workaround is to verify that TACACS information is properly configured, or delete TACACS information completely for such devices. [CSCdk31318]
Essentials import of IP addresses will sometimes hang if DNS resolution of the IP address does not work.
The workaround is:
1. Add IP addresses in the local hosts file.
2. Fix the DNS so that reverse name lookups work.
When importing a large number of devices, if you see a Dr. Watson window or a debugger window appear on the screen, click OK. The system recovers itself. [CSCdk49811]
If Internet Explorer does not have MIME type text/plain set up properly, when displaying a dynamic html page with Content type text/plain, the browser might bring up a notepad instead of displaying the page on the browser.
The workaround is as follows:
Step 1 From the Start button at the lower left of the Windows NT screen, click the right button and select Explorer.
Step 2 Click File Types.
Step 3 Select Text Document from the list and click Edit.
Step 4 In Content_Type (MIME) item, either select text/plain or type in text/plain, then click Okay.
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 Management application to incorrectly import the current running Supervisor image as the module (ATM, FDDI, CDDI, Token ring) image in the software library. [CSCdk51236]
When you are importing images from L2 and L3 Catalyst switches to the Software Management library, you might get a warning message stating "Either there is no image present in the Flash or Flash MIB is not supported by this device," in addition to the list of images on that device.
You can ignore this message. [CSCdk52400]
The Backup Current Running Image option under Job Control Information screen for Catalyst switches apply to only Supervisor modules (I, II, III).
The Work Order Report that is displayed during the Distribute Images job creation process for Catalyst switches incorrectly displays that the image will be copied to the software library at the time of distribution for ATM, FDDI, and Token Ring modules. This message should be ignored, because it does not affect the software distribution on these modules. [CSCdk51176]
At the time of importing Catalyst module software images (ATM, FDDI, CDDI, and Token Ring) into the library, Software Management allows users to input the minimum Supervisor software version that is compatible with the module software image. Currently, this attribute is not checked at the time of creating Software Distribution Jobs using the Distribute Images user interface.
Users should manually verify that the Catalyst switch is running a compatible Supervisor software version before proceeding with module software upgrades. [CSCdk50317]
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.
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 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) |
In the Recommend Image Upgrade screen, verify from the software version numbers whether the new target image supports all the features you wish to deploy. Software Management does not check if all current configured features in the ATM module are present in the new image. [CSCdk40327]
This affects Supervisor III software images belonging to 4.2(x) version. While importing Supervisor III software images from CCO or a file system into the library, Software Management does not correctly read the image version number.
For example, Supervisor III software image belonging to 4.2(1) version (filename cat5000-sup3.4-2-1.bin) is incorrectly imported as 4.2 software image without the maintenance release number.
Users should edit the version number in the Edit Image Attributes screen while adding the image from the file system to the library. If the image is imported from CCO, (CCO images are shown with superscript 3 in the Recommended Image Upgrade window) users should use the Browse Library > Edit Image Attributes screen to edit the version number.
If the 4.2(x) image is selected as the target image during Image Distribution from CCO, then users should also use the Browse Library > Edit Image Attributes screen to edit the version number. [CSCdk50101]
The Microcom firmware for 56K modems is available in two formats:
The AS5300 supports only the combined image. The AS5200 running Cisco IOS 11.2(10)P also supports the combined file format only.
Software Management supports only the combined format files (for example, mcom-modem-code-xx.bin) but it does not support the separate firmware and dsp code files. These files cannot be imported to the software library. [CSCdk27380]
Software Management does not recognize Supervisor 8-MB correctly. It is recognized as a regular supervisor image. Do not use "Add Image to Library" from the "Device Option" to add a Supervisor 8-MB RAM software image from a Catalyst 5000, 5500, or 2900 device.
This restriction applies to Supervisor I, II software images only, and to 3.1 and 3.2 releases, for which all maintenance releases are affected. Supervisor III software images and regular Supervisor I and II images (which require 16-MB RAM) are not affected.
The workaround for this problem is to import the 8-MB RAM images from CCO, if CCO is available. Otherwise, upload the image from the device to the tftp server manually. (Use telnet to connect to the device, then enter the copy flash tftp command.)
Rename the image file to cat5000-sup8m.<ver-no> (for example, cat5000-sup8m.3-2-1b.bin for Supervisor 8MB 3.2(1b) image), then add the image to the library using the "Add Image to Library" option. [CSCdk22546]
When performing the CCO Upgrade Analysis, the number of devices that could be selected before having the browser timeout errors is a function of CCO server load, network bandwidth from CCO to Essentials and from Essentials server-to-client station, Essentials server load, and so forth.
As a workaround, users should select less than 50 devices if they have a slower link to the Internet. [CSCdk32490]
If you import images that require more than 20 minutes to complete, the browser might time out and display a message that says, "Document contains no data." Decrease the number of images you import at one time to ensure the import process requires less than 20 minutes. [CSCdj25733]
If you import an image from CCO when the temporary directory's file system is full, you might receive server errors when running other Essentials functions. To avoid these errors, keep the temporary directory clear of unneeded files. [CSCdj44161]
When upgrading the software images, single Flash bank devices require Telnet access. Therefore, when adding the device to Essentials, you must provide the appropriate passwords and access information, which should include both an enable password and an enable secret password. Refer to the online help for more information about passwords and access information.
All devices with microcode (MICA modems, Microcom firmware, or CIP cards) require telnet access to upgrade software images, and you must provide the appropriate passwords and access information. The devices requiring telnet access are:
Refer to the online help for more information about passwords and access information.
Router Switch Modules (RSMs) on Catalyst 5000 and 5500 devices run Cisco IOS software and have their own host names and IP addresses. To upgrade the RSM on a Catalyst device, select the Cisco IOS device type in the Select Device Type dialog box (Tasks > Software Management > Distribute Images).
For Supervisor III modules on Catalyst 5500 devices, the baseline and synchronization options are supported only when the modules are running software version 4.1 or later. [CSCdk06556]
If you are using Cisco 700 series routers, you must provide appropriate telnet passwords and access information to enable software upgrades. Software upgrades for 77x series (771, 772, 775, 776) routers are supported only if they are running a software version greater than 4.0(0) because the SNMP agent on the older versions does not provide adequate information. For the same reason, software management allows software downloads of versions greater than 4.0(0) to 77x series (771, 772, 775, 776) routers.
Cisco 160x devices run the same software image, although the 1605 is runs from RAM, and the other 160x devices run from Flash memory. The Cisco 1605 requires more DRAM than the other 160x devices, because it is an RFR device. When a user has a network that is using 160x devices, the user can import a software image into the library once, then use it for distributing to all 160x routers.
Users are advised to input the DRAM requirement for the 1605 device as the minimum RAM requirement for the software image at the time of importing the software image. this will ensure that Software Management will check the correct DRAM requirement for all 160x devices.
In the following reports, the severity field is defined incorrectly, which results in empty reports:
The workaround for each report is as follows:
Step 1 Login to Essentials.
Step 2 Go to Admin > Syslog Analysis > Define Custom Report.
Step 3 Change each message with the format PIX-*-6-106002 as follows:
Click Advance, then double-click on each 6 and replace it with *, then press the enter key. [CSCdk49695]
Syslog analysis does not show the primary facility of Channel Interface Processor (CIP) messages. For example, the CIP message
..%CIP4-6-MSG: %MSG802-6-LLC.START: Starting LLC-2...
is stored as
%MSG802 6 LLC_START Starting LLC-2...
where MSG802 is the facility, 6 is the severity, LLC_START is the mnemonic, and the remaining text is the description. The first part (CIP4-6-MSG) is not used. Only the second part of the CIP message is stored. [CSCdj16580]
Syslog reports do not have Cisco IOS explanations for some messages. Refer to the latest Cisco IOS reference manual for additional information on reported messages. [CSCdj61218]
For Windows 95 and Internet Explorer users who access the Resource Manager server over ISDN, the Syslog Analyzer reports might be blank the first time the reports are generated. To workaround this problem, retry the task to generate the syslog report. [CSCdk33214]
Case Management Query (Tools > Case Management > Case Query/Update) may not show all your open cases. This situation occurs when there is more than one contract associated with your CCO User ID because CCO uses the contract number as the validation key for the Case Query operation.
To work around this situation, request via e-mail to cco-team@cisco.com that all your contracts be added to the Additional Contracts field in your CCO user profile. [CSCdj50287]
If you open a case with CCO via e-mail after unsuccessfully trying to open a case using Essentials (Tools > Case Management > Case Open), processing of the e-mail might take a while. The Technical Assistance Center (TAC) is usually able to process these requests within an hour, but it may take longer. Until the case is processed, the case is not available via Case Query/Update (Tools > Case Management > Case Query/Update). [CSCdj50294]
Case Management cannot gather configuration information from a router running TACACS when the router is configured for TACACS login but is not configured for enable secret password. To correct this situation, enter the enable password in the Enable Secret Password field for the device (Admin > Inventory > Change Device Attributes). [CSCdj82514]
Internet Explorer does not open a second window with collection details when you click on the Pass or Fail link in the "Inventory and Telnet Collection Status" window. [CSCdk32038]
The Telnet option under Case Management fails if the showtech type of information takes more than 30 seconds to download from the device. To workaround this problem, edit the $CRMROOT/cgi-bin/smartcase/IosTelnet.pm file and change the line:
$IosTelnet::Timeout = 30;
to
$IosTelnet::Timeout = 90;
Keep incrementing this value until the process completes successfully. [CSCdk50702]
Catalyst 1900 devices are not supported by Device Navigator in this release. [CSCdk43726]
The Device Navigator help currently includes a help window that displays multiple button panels only. The workaround is to close the help window and view that help topic manually through the Help Contents window. [CSCdk11625]
The CWSI Campus components are as follows:
This section contains information that applies to all of these components. Notes and caveats for the individual components are described in these release notes in the sections about the specific component.
Table 15 shows the Cisco devices that CWSI Campus applications support and the minimum software version required on the device.
| Device Family | Cisco Devices | Network Topology | Device Mgmt | Traffic Mgmt (RMON) | VLAN Mgmt | LANE Mgmt | ATM Mgmt | User Tracking | Minimum Software |
|---|---|---|---|---|---|---|---|---|---|
| Catalyst Switches | |||||||||
Catalyst 1200 | 1201, 1202, 1211, 1212 | X | X | X | - | - | - | - | 4.29 |
Catalyst 1900 | 1912, 1924 | X | X | X | X | - | - | -1 | 8.0 (Enterprise) |
Catalyst 2820 | 2822, 2828 | X | X | X | X | X2 | X | -1 | 8.0 (Enterprise) |
Catalyst 2900XL | 2908XL, 2916XL/ | X | X | X3 | -4 | -5 | -5 | -4 | IOS 11.2(8) SA |
Catalyst 2900 | 2901, 2902, 2926 | X | X | X | X | - | - | X | 2.4.3 |
Catalyst 3000 | 3000, 3100, 3200 | X | X | X | X | X | X | X1 | 2.2.2 |
Catalyst 3900 | 3900, 3920 | X | X | X | X | -6 | X | X7 | 3.0(2) |
Catalyst 5000 | 5000, 5002 | X | X | X | X | X8 | X | X | 2.4.3
|
Catalyst 5500 | 5500, 5505, 5509 | X | X | X | X | X8 | X | X7 | 2.4.3 |
Catalyst 5509 | 5509 | X | X | X | X | - | - | X7 | IOS 11.3 |
Catalyst 8500 CSR | 8510 | X | X | X9 | - | - | - | X10 | IOS 11.3 |
| ATM Switches | |||||||||
LightStream | LightStream 1010 (with Frame Card 1) | X | X | X11 | - | X | X | - | IOS 11.2 (8.0.1) FWA4.1 |
Catalyst 8500 MSR | Catalyst 8510 (with PFQ feature card) | X | X | X11 | - | X | X | - | IOS 11.2 (8.0.1) FWA4.1 |
| Routers | |||||||||
Route Switch Module | Catalyst 5000 | X | X | -12 | - | - | - | X13 | IOS 11.2 |
C7200 | 7202, 7204, 7206 | X | X | -12 | - | - | - | X13 | IOS 11.1 |
C7500 | 7513, 7507, 7505 | X | X | -12 | - | - | X | X13 | IOS 11.1 |
C4000 | 4500, -M, 4700, -M | X | X | -12 | - | - | X | X13 | IOS 10.3 |
C3600 | 3620, 3640 | X | X | -12 | - | - | X | X13 | IOS 11.3 |
C2600 | 2610, 2611, 2612 | X | X | -12 | - | - | - | X13 | IOS 11.3 |
C2500 (LAN/ | C2501- | X | X | -12 | - | - | - | X13 | IOS 10.3 |
C2500 (hub/ | C2505, 2507, 2516, 2519, 2524, 2525 | X | X | -12 | - | - | - | X13 | IOS 10.3 |
C2500 (Frame Relay) | C2520-C2523 | X | X | -12 | - | - | - | X13 | IOS 11.0 |
C1600 | 1601-1605 | X | X | -12 | - | - | - | X13 | IOS 11.2 |
C1000 | 1000, 1003-1005, 1020 | X | X | -12 | - | - | - | X13 | IOS 10.3 |
| Probes and Analysis Modules | |||||||||
- | LAN SwitchProbes (Ethernet, Token Ring, FDDI, Fast Ethernet) | - | X14 | X | - | - | - | - | 4.21 |
- | WAN SwitchProbes (FR, ATM, HSSI) | - | X14 | - | - | - | -15 | - | 4.2.1 |
- | WAN SwitchProbes (Multiport T1/E1) | - | X14 | X | - | - | - | - | 4.2.2 |
- | Network Analysis Modules (NAM) (Catalyst 5X00 module) | - | X | X | - | - | - | - | 4.3 (Catalyst) |
Asynchronous Network Interface (ANI) begins the discovery process immediately after rebooting, while the system is initializing. ANI runs as an NT service, as do the other daemons required for the correct operation of CWSI Campus. It may take up to five minutes (longer for a very large network) for the initial discovery process to complete.
To start CWSI Campus, select Start>Prog>CWSI 2.2>Start CWSI.
The login username parameter is ignored, but the server name must remain as it appears. This login is used to register CWSI Campus as a client of ANI (named ANIServer). The interprocess communication is done through CORBA.
If you get an error message while attempting to log into CWSI Campus, ANI is not ready to receive requests from its clients. Wait five minutes and try again.
To start the CWSI Campus applications from the CWSI Campus map window, select Tools>application name, or click the appropriate icon on the toolbar. You can also start TrafficDirector and CiscoView in the following ways:
To start UserTracking, follow these steps:
Step 1 From the Windows NT Start menu, select Start>Programs>CWSI 2.2>Start UserTracking.
Or from the CWSI Campus map window, select Tools>UserTracking or click the UserTracking icon on the tool bar.
Step 2 Select Action>Discover>End-User Nodes to start discovery.
Wait a few minutes until a message indicates that discovery has completed.
Step 3 To display the end-user nodes discovered in the network, select Action>Display>All Entries.
If your network is very large, you might want to create a query for UserTracking so that you do not have to display all the users at once. To limit the size of the table displayed, see the Using the Campus UserTracking Application publication for more information about creating queries.
You can select and start both TrafficDirector and CiscoView from HP OpenView Network Node manager. The additional CWSI Campus functions, including the CWSI Campus topology mapping services, VlanDirector, AtmDirector, and UserTracking must be started from the CWSI Campus Network Map, which is launched from Windows NT as part of the normal start-up procedures for CWSI Campus.
TrafficDirector and CiscoView are device-focused applications and are easily started from HP OpenView based upon the device discovery process within HP OpenView. The additional CWSI Campus functions require more detailed network-wide topology data than HP OpenView provides. The CWSI Campus discovery and database services must be running for these additional applications to function, which makes it necessary to start these from the main CWSI Campus window.
Some of the error messages do not have online help. The Help button on the error message window is not highlighted (grayed-out).
All CWSI Campus 2.2 components are Year 2000 compliant.
This section describes new features and provides notes and caveats for the CWSI Campus network map.
CWSI Campus Network Map provides the following new features:
This section provides important notes and caveats about the CWSI Campus Network Map.
Moving ports between virtual local area networks (VLANs) will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2).
Not all modules are shown in the Node Attributes window. You can access the node attributes window by selecting the device and clicking the right mouse button. [CSCdj40028, CSCdj40030]
The following are LAN Emulation (LANE) issues:
The following are issues related to starting CWSI Campus applications:
Error accessing agent domain rmon while retrieving ETSTATS error: entry or group not present in agent
"invalid command name "Sess0" "bad window path name ".en"
The discovery process is unable to discover Catalyst 5505 switches with OC-12 dual port modules running release 4.12. This problem also occurs with the release that supports MPOA. [CSCdk23407]
This section describes new features and provides notes and caveats for the VlanDirector application.
The VlanDirector application provides the following new features:
This section provides important notes and caveats about the VlanDirector application:
"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> >
This section describes new features and provides note and caveats about the UserTracking application.
The UserTracking application provides the following new features:
This section provides important notes and caveats about the UserTracking application.
This section describes new features and provides notes and caveats for the TrafficDirector application.
The TrafficDirector application includes the following new major features and enhancements.
map-conversations:1
This section provides note and caveats about the TrafficDirector application.
The TrafficDirector 5.3 application does not support the creation of Alarms and Events for any device running IOS 11.1 or greater. The TrafficDirector application assumes that the RMON statistics group is always supported, which is not the case for IOS.
In Configuration Manager, when specifying the analyzer port number for a roving agent, use the exact port number (port name or module/port number including leading zeros) learned by the TrafficDirector application and displayed in the ports window or the switch.swp file.
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.
To integrate the TrafficDirector application with other NMS platforms, refer to "Integrating Traffic Director with Other Managers" in Appendix C of the Using the Campus TrafficDirector Application guide.
Traffic Director does not support integration with SNMPc.
Table 16 indicates whether you need to use either a shared property file or a custom property file when configuring a specific property for agent or switch type.
| Agent Class | Properties | ||||||
|---|---|---|---|---|---|---|---|
| Monitor Domains | Domain Traps | Report Logging | RT Delays | RT Logging | Proxy SNMP | Resource Traps | |
Agent | Shared | Shared | Shared | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. |
Frm-Rly | Shared | Shared | Shared | Custom Mgt Intf. | Custom | Custom Mgt Intf. | Custom Mgt Intf. |
DLCI (Frm-Rly) | Protocol domains from Shared | Custom | Custom | N/A | N/A | N/A | N/A |
Switch | Shared | N/A | N/A | N/A | N/A | N/A | N/A |
Switch Ports | Shared is copied | Custom | Custom | N/A | N/A | N/A | N/A |
Table 17 lists the devices supported by the TrafficDirector application.
| Switch | Full RMON1 | Mini- RMON2 | Proxy RMON | Roving RMON |
|---|---|---|---|---|
Catalyst 1200 | X |
|
|
|
Catalyst 1600 |
| X |
| X |
Catalyst 1800 |
| X |
| X |
Catalyst 1900 |
| X |
| X |
Catalyst 1912 |
| X |
| X |
Catalyst 1924 |
| X |
| X |
Catalyst 2100 |
|
| X | X |
Catalyst 2800 |
|
| X | X |
Catalyst 2820 |
| X |
| X |
Catalyst 2900 |
| X |
| X |
Catalyst 2908 |
| X |
| X |
Catalyst 2916 |
| X |
| X |
Catalyst 2924 |
| X |
| X |
Catalyst 2926 |
| X |
| X |
Catalyst 3000 |
| X |
| X |
Catalyst 3100 |
| X |
| X |
Catalyst 3200 |
| X |
| X |
Catalyst 3900 |
| X3 |
| X |
Catalyst 5000 |
| X |
| X |
Catalyst 5002 |
| X |
| X |
Catalyst 5500 |
| X |
| X |
Catalyst 5505 |
| X |
| X |
Catalyst 5509 |
| X |
| X |
Generic |
| X |
|
|
Proxy RMON is not supported for the Catalyst 1700 switch in this release.
When a property file is installed on a probe it is applied to all ports on that probe. If you have a multiport probe, be aware that when defining the properties, the last property files to be installed are applied to all ports on that probe. To avoid conflicts, either ensure that the property files for each port are identical or define properties for only one port on the probe.
The TrafficDirector 5.3 application roves to the specified port when you select data capture from the main TrafficDirector screen. For other applications, such as All Talkers, perform roving manually from Configuration Manager or start the application from Traffic Monitor. [CSCdj62108]
If you are using a switch probe for roving and monitoring a switch, the probe does not reinitialize itself or relearn its location when it is physically moved from one location to another (for example, SPAN destination has changed). If you disconnect your probe and reconnect it to another switch or a different port on the same switch, you must reinitialize your probe by resetting it. If you fail to reinitialize the probe, you will encounter errors when you try to use the probe for roving.
The Catalyst 3900 switch supports the following Token Ring RMON MIB groups only:
If you try to set thresholds on objects in any of the other Token Ring groups, the following error message appears:
"Install aborted unexpected SNMPAPI Error"The VLAN learn feature is only supported for the Catalyst 5000 series switches. All other switches will show an empty list when VLANs are learned.[CSCdk29981]
VLANs can only be roved when they pass the following criteria:
Disabling the host-conv-getbulk option in the default.dvp configuration file results in duplicate entries being seen in the ATALK All Talkers display.[CSCdj89834]
The following caveats pertain to TrafficDirector TRAPs:
(a) Shut down the TrafficDirector application.
(b) From the Windows NT menu bar, select Start>Control Panel>Services.
(c) Stop the SNMP Trap Service.
(d) Access the command prompt. From the Windows NT menu bar, select Start>Programs>Command Prompt.
(e) From the command prompt, enter dbshutdn -all.
(f) Verify that the dvtrapd daemon is not running. Using your right mouse button, click a blank area on the taskbar. Then Click Task Manager.
(g) Start TrafficDirector. TrafficDirector will automatically start the dvtrapd daemon.
Integration of the TrafficDirector application with Sun NetManager results in the switch probes being discovered and displayed on the Sun NetManager topology with the TrafficDirector application icons.[CSCdk24059]
To run TrafficDirector reports on Windows NT, you must first install and configure MicroSoft SQL database. See the Installing CWSI Campus on Windows NT publication.
To filter out MAC addresses when performing a data capture, set the MAC address format to FF-FF-FF-FF-FF-FF instead of FFFFFFFFFFFF. (F can be any hex number.)
This section describes new features and provides notes and caveats for the AtmDirector application.
The AtmDirector application provides the following new features:
This section provides note and caveats about the AtmDirector application.
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.
If you launch and close the Netscape browser many times, sometimes AtmDirector help cannot be launched. If this happens, close Netscape (and AtmDirector if necessary) and wait for few seconds. Then try again.
The following caveats apply to the ATM fabric map:
Traffic Type not understood
(a) 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.
(b) 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.
The following caveats apply to the PNNI function in the AtmDirector application:
ORB DB Error.
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.
AtmDirector does not support multiple LANE clients for the same ELAN on the same device.
This section describes new features and provides notes and caveats for the CiscoView application.
The CiscoView application provides the following new features:
| Small to Medium Business Products | Mid-Range Enterprise Products1 | High-End Enterprise Products |
|---|---|---|
Cisco 761, 762, 765, 766, 771, 772, 775, 776 | Catalyst switch models2 1200, 1400, 1600, 1601, 1700, 1800, 1900, 2100, 2600, 2800, 2820, 2900, 2900XL, 2926, 3000, 3100, 3200, 3900, 5002, and CPW2200 | Catalyst 5000, 5500, 5505, and 5509; and 8510 |
Cisco 1003, 1004, and 1005 | EtherSwitch Pro16, EPS2015, 1200, 1220, 1400, 1420 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
Cisco 1601, 1602, 1603, 1604, 1605 | EtherSwitches: Pro16 and CPW16 | LS1010
|
Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525 | Workgroup concentrators 1400 |
|
Cisco 3600 series (includes 3620 and 3640) and 3800 series | Fasthub 216T |
|
Cisco 4000 series3 (includes 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M) |
| Cisco uBR7246 and uBR904 |
AS5200 Access Server | AS2509-RJ | AS5300 Access Server AS5800 Access Server |
Cisco 1501, 1502, 1503, 1516 |
|
|
Fasthub 300 and Fasthub 100+ Series |
|
|
EPS-500, EPS-1500, EPS2115, CPW-500, CPW-2115, and CPW-16 |
|
|
MWEB200 |
|
|
| Application | Description | OS | Cisco IOS | Device Support |
|---|---|---|---|---|
Threshold Manager | Monitors the availability and performance of Cisco devices | AIX 4.2.1 and 4.3 | Cisco IOS 11.1 or 11.2 with RMON events and alarms group support | Cisco 7000, 7010, 7505, 7507, and 7513; Cisco 4000, 4500, and 4700; Cisco 2501-2505, 2507, 2509-2525; Catalyst 1200 and 5000 |
StackMaker | Manages the device membership in a Cisco stack | Solaris 2.4, 2.5.1, and 2.6 | Cisco IOS 10.0 through 11.2 | Cisco 1600, 3600, 3620, 3640, Catalyst 1900, Catalyst 2820, CPW1220, CPW1420, Fasthub 100+ and Fasthub 300 |
Flash File System | Provides file copying and editing features for the 7000 Series routers | Solaris 2.4, 2.5.1, and 2.6 | Cisco IOS 10.0 through 11.2 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
Cisco TN3270 Monitor | Monitors TN3270 capability embedded in Cisco devices with IBU feature set. | Solaris 2.5.1 and 2.6 | Cisco IOS 11.0(13)BT, 11.2, or 11.3 with cip22-14 | Cisco 7000 and 7500 (with a CIP card) and Cisco 7200 (with ECPA card) |
| Device Package | Version |
|---|---|
1000.pkg | 4.0(1.2) |
1500.pkg | 4.0(1.2) |
1600.pkg | 4.0(5.0) |
2500.pkg | 4.0(4.0) |
2600.pkg | 4.0(3.0) |
3600.pkg | 4.0(11.0) |
3800.pkg | 4.0(1.02) |
4000.pkg | 4.0(3.1) |
700.pkg | 4.0(1.4) |
7000.pkg | 4.0(5.0) |
AS5200.pkg | 4.0(5.0) |
AS5300.pkg | 4.0(3.1) |
AS5800.pkg | 4.1(2.0) |
CPW10_100.pkg | 4.0(1.4) |
CPW1200.pkg | 4.0(1.4) |
CPW1220.pkg | 4.0(1.5) |
CPW1400.pkg | 4.0(1.4) |
CPW1420.pkg | 4.0(1.5) |
CPW16.pkg | 4.0(1.1) |
CPW2115.pkg | 4.0(1.1) |
CPW2200.pkg | 4.0(2.1) |
CPW316.pkg | 4.0(1.4) |
CPW500.pkg | 4.0(1.1) |
Cat116.pkg | 4.0(1.4) |
Cat1200.pkg | 4.0(1.4) |
Cat1600.pkg | 4.0(1.3) |
Cat1700.pkg | 4.0(1.4) |
Cat1800.pkg | 4.0(1.1) |
Cat1900.pkg | 4.0(2.0) |
Cat2100.pkg | 4.0(1.4) |
Cat216.pkg | 4.0(1.4) |
Cat2600.pkg | 4.0(1.3) |
Cat2800.pkg | 4.0(1.4) |
Cat2820.pkg | 4.0(2.1) |
Cat2900.pkg | 4.0(2.1) |
Cat2900XL.pkg | 4.0(2.0) |
Cat3000.pkg | 4.0(1.6) |
Cat3900.pkg | 4.0(1.5) |
Cat5000.pkg | 4.1(2.6) |
Cat5500.pkg | 4.1(2.6) |
Cat8510.pkg | 4.1(1.1) |
Cisco1516.pkg | 4.0(1.2) |
EPS2015.pkg | 4.0(1.1) |
LS1010.pkg | 4.0(2.3) |
MWEB200.pkg | 4.0(1.1) |
ubr7200.pkg | 4.0(1.1) |
ubr900.pkg | 4.0(1.0) |
TD_INTG.pkg | 4.1(1.6) |
TN3270/TN3270_AIX.pkg | 4.1(1.2) |
TN3270/TN3270_HPUX.pkg | 4.1(1.2) |
TN3270/TN3270_SOL.pkg | 4.1(1.2) |
WG_Concentrator.pkg | 4.0(1.3) |
stackmkr.pkg | 4.0(1.1) |
Threshold_AIX.pkg | 4.0(1.1.3) |
Threshold_HP10.pkg | 4.0(1.1.3) |
Threshold_WIN.pkg | 4.0(1.1.3) |
Threshold_SOL.pkg | 4.0(1.1.3) |
This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing.
CiscoView supports Cisco IOS software Releases 10.0 through 11.3. Note the following restrictions:
New devices and further specifics on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:
There are several ways to add (or incrementally install) support for new devices to CiscoView 4.2(1). Direct customers should refer to the section "Troubleshooting" at the end of this release note for information about accessing CCO. Partner-initiated customers should refer to the section "Partner Initiated Customer Accounts" (following).
You can add new devices to CiscoView from the CiscoView Upgrade Planner page on CCO at http://www.cisco.com/kobayashi/library/netmanage/cview/. On this page, go to the section "Download CiscoView Software Updates" and click "CiscoView 4.x Packages." From the "CiscoView 4.x Packages" page, you can download packages for all supported devices. For more information, refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView. A quick reference version exists in the CiscoView CD Installation Instructions booklet.
In general, multiple devices within the same product family share a single device package. If you have a specific device in mind, look for the device package for the device's family.
To determine if your particular device is supported, look at the readme for the device package (available on the same webpage listed in the previous section).
To get more information about the Partner Initiated Customer Accounts (PICA) program before accessing CCO for device package files, use the following URL:
http://www.cisco.com/acs/info/pica.html
You can also refer to the "Downloading Device Packages" chapter in Getting Started with CiscoView.
Table 21 (following) lists problems in CiscoView 4.1(1) that are fixed in CiscoView 4.2(1). Only the most serious problems resolved in CiscoView 4.2(1) are listed.
Applet and device package problems that have been fixed since the previous release are described in the respective applet and device package readme files. (These readme files are available from the CiscoView Upgrade Planner:
http://www.cisco.com/kobayashi/library/netmanage/cview)
CSCdi51665 | Users preferences such as timeout are not persistent across CiscoView sessions. |
CSCdi62739 | When saving new policies for a host, they will not match if IP is in use. |
CSCdj13160 | Changing from CiscoView 3.1(1) to CiscoView 4.1(1) leaves symbolic links in $SNMHOME/snm/agent. |
CSCdj38584 | Sometimes CiscoView cannot be configured due to missing fonts. |
CSCdj39055 | CiscoView does not support workgroup concentrator WS-X1434. |
CSCdj43438 | CiscoView does not properly convert the Timeticks SYNTAX. |
CSCdj50382 | A wrong instance might be used for subclass discovery. |
CSCdj58682 | Running CiscoView dumps core when a device package is incrementally installed. |
CSCdj59472 | Newly created rows might not be added to table. |
CSCdj60605 | CiscoView might fail to open a device if both the Catalyst 5000 and Yosemite card are set to the same community strings. |
CSCdj61077 | CiscoView package for the Cisco 7000 has typo for feip-f |
CSCdj62691 | You might not be able to start the grapher on CiscoView integrated with EM 2. |
CSCdj64545 | TCL script interprets address as exponent ex. 1e550 |
CSCdj68522 | CiscoView port monitor default polling fails. |
CSCdj72051 | CiscoView is not able to work with AS5300. |
CSCdj75454 | Cisco 7000 package corrupts the Memory Used graph. |
CSCdj75485 | Need enhancement in engine for StackView support for AS5300. |
CSCdj90331 | CV4.1(1) integration with HPOV/SNM fails. |
CSCdj92755 | Ciscoview crashes when going to PVC Configuration menu. |
CSCdk03414 | Catalyst 5000 always uses default 6 sec snmp timeouts. |
CSCdk03853 | MIB files for the imported module SNMPV2-SMI are missing. |
CSCdk05042 | CiscoView installation may fail if $OV_BIN env. var. is defined on AI. |
CSCdk05800 | Change in the Wr.Com.Str When Opening a device doesn't change Op. |
CSCdk05801 | CV security patch is not invoked in AI. |
CSCdk08402 | Error message is displayed in em_service. |
CSCdk08741 | Error message displayed during installation. |
CSCdk08745 | Grapher is not working on CiscoView with EM 2.0 & SNM 2.2.3. |
CSCdk10191 | Wrong functionality during installation. |
CSCdk10541 | Default telephone text box accepting junk values. |
CSCdk11370 | Cancel option adds entries in phone book. |
If you cannot open a device in CiscoView 4.2(1), a message appears indicating that the device is unmanageable for one of the following reasons:
This section contains installation notes and caveats for CiscoView.
When a device package is installed, CiscoView updates HP OpenView with the device symbols and bitmaps.
If CiscoView does not appear in the Tools menu in Solstice Site Manager/Domain Manager, perform the following steps:
Step 1 Copy the file ciscoview.schema from the $NMSROOT/etc/cview/snm/struct directory to $SNMHOME/snm/struct, where NMSROOT is the CiscoView home directory (typically /opt/CSCOcv).
Step 2 Edit the $SNMHOME/snm/struct/ciscoview.schema file and replace the string "$NMSROOT" with your CiscoView home directory.
CiscoView 4.2(1) does not support an upgrade from CWSI 1.1. To upgrade CWSI to CiscoView 4.2(1), first upgrade CWSI 1.1 to CWSI 1.3 (or later) and then upgrade to CiscoView 4.2(1).
CiscoView 4.x is not compatible with CiscoWorks 2.x. To use CiscoView 4.x, remove CiscoWorks 2.x or upgrade to CiscoWorks 3.2.1 or later.
Some errors will be reported during the installation or incremental installation of device packages when MIBs are loaded into AIX NetView. For more information and workaround suggestions, refer to the following URLs:
http://www.cisco.com/public/mibs/app_notes/mib-compilers
or
ftp://ftp.cisco.com/pub/mibs/app_notes/mib-compilers
line 46: syntax error line 49: syntax error failed in loading /opt/SUNWconn/snm/struct/Cat3900.schema
This section contains general notes and caveats. They are divided into five sections:
line 27: Unknown record name 'component.cisco-c8510' line 27: Cannot initialize field value component.cisco-c8510 failed in loading /opt/SUNWconn/snm/struct/Cat5500.schema
line yyy: Duplicate attribute name <attrname> line xxx: Duplicate error code <errcod> failed in loading /opt/SUNWconn/snm/agents/CISCO-STACK-MIB.schema.
| 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 |
To work around this problem, increase the kernel configuration parameter "number of open file descriptors per process" to approximately 90 or more. [CSCdk49538]
Before providing procedures for troubleshooting, this section includes a description of the CWSI Campus daemons and their interactions with clients.
Asynchronous Network Interface (ANI or AniServer) is a multithreaded Java program. It is installed in Windows NT as a daemon process and runs in the background, beginning discovery as soon as the machine boots. ANI is responsible for the discovery of the network, for both devices and users. ANI is also responsible for all communication with the clients.
The database engine (dbeng50) is responsible for checkpointing all ANI information into the database. For ANI, this is a checkpoint only. ANI performs all of its operations from the data stored in memory. The database stores user-entered information and allows ANI to load its data model quickly into memory upon a subsequent restart. (The CRM database engine has the same name, so your system should be running two processes with this name.)
The CORBA agent (osagent) is responsible for monitoring interprocess communication messages. All servers must register with the osagent. All clients looking for service can find it with the help of the osagent. The CWSI Campus login window is used to indicate the name of the ANI server that the osagent should locate.
To see all servers registered with CORBA, and where they are located, run osfind.exe from a DOS window. This troubleshooting tool is found in CSCOpx\lib\visigenics\bin.
RTPoller is used for periodic polling of the network for status of devices and links.
The event channel (EventChannel) is used to send events to all servers and clients who have registered with it.
The following command-line scripts control the CWSI Campus daemons:
To use these scripts, open a DOS window Command Prompt. Enter stopcwsiserver to stop the CWSI Campus Server Processes. When the DOS prompt returns, all the daemons have been stopped. Wait a few moments for all processes to stop before restarting. To restart the processes, enter startcwsiserver and wait until the DOS prompt returns.
After running osfind, if you see that the AniServer or one of the other servers is missing, or if in the Windows NT task manager you see that your database engine is missing, stop the CWSI Campus servers and start them again.
If you have just rebooted your machine and are unable to log in to AniServer, ANI may not yet be ready to receive messages. Wait five minutes, and then try again.
If you are still unable to log in, run the osfind program to verify that AniServer has registered with the OSAgent. If so, verify that the name of AniServer in the login box is the same name as the name registered with osagent.
If you do not find AniServer, run the stopcwsiserver script (see "Stopping and Starting CWSI Campus Daemons," earlier in this section), and then run the startcwsiserver script. Run osfind again. If AniServer is there, log into CWSI Campus. If AniServer is still not registered, you might have a corrupt database.
To determine whether you have a corrupt database, turn on trace to see if messages indicate this condition. If you are still unable to verify the status, contact your Cisco TAC for instructions.
In addition to these release notes and online help, the CW2000 documentation set includes the following:
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 up to date 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 on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
A CCO web page for CW2000 contains links to marketing and technical documentation and includes the latest downloadable Essentials packages. To find this information, point your web browser to the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/cw2000
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the Information Packet that shipped with your product.
For service and support for a product purchased directly from Cisco, use CCO.
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: Thu Sep 30 12:25:43 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.