|
|
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 system requirements for Essentials and Essentials and CWSI Campus combined products are listed in Table 1.
| Requirement Type | Essentials1 | Essentials and Campus1 |
|---|---|---|
System hardware |
|
|
Memory (RAM) | 256 MB minimum | 256 MB minimum |
Available disk space |
|
|
System software | AIX 4.2.1 or 4.33 | AIX 4.2.1 or 4.33 |
Browser | None4 | Netscape 4.04 or 4.055 |
Additional software | None | Essentials |
| 1SV+ coexistence with CW2000 is not supported. 2For each Software Management job running, 8 MB of space is required in the /tmp directory. 3AIX 4.2.1 and 4.3 require patches to run Essentials. Refer to the "Essentials Installation Notes" section in these release notes and the Installing Resource Manager Essentials and CWSI Campus on AIX "Server Requirements" section for more information. 4No browser is required for the Essentials server system. Client systems must have a supported browser installed. Refer to Table 2, "Browser Requirements and Versions," and to Installing Resource Manager Essentials and CWSI Campus on AIX "Client Requirements" section for more information. 5The browser is used only to display the Campus online help. |
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.013 with Service Pack 1 | 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. |
This section provides more information to help you select a system that best meets 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 AIX running Essentials only.
| Minimum System Configuration | Availability (# Managed Devices) | Syslog (# Messages/Day) | Configuration (# Managed Devices) | Inventory (# Managed Devices) |
|---|---|---|---|---|
AIX Single Processor | 0 - 500 | 0 - 80,000 | 0 - 1000 | 0 - 1000 |
AIX Multiple Processor | 500 - 1000 | 80,000 - 150,000 | 1000 - 5000 | 1000 - 5000 |
For CWSI Campus, use a system configuration that supports 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 150 devices and 3000 end hosts, select the AIX Multiple Processor. See Table 4 for the CWSI Campus recommended system configurations.
| Minimum System Configuration | Number of Network Devices | Number of End Hosts (Managed by UserTracking) |
|---|---|---|
AIX Single Processor | <200 | <2500 |
AIX Multiple Processor | 200 - 400 | 2500 - 6000 |
Review the information in this section carefully before installing the product.
Review the following installation information before installing Essentials.
If you abort the Essentials installation procedure before it completes, not all required components are installed and Essentials will not operate successfully.
The workaround is to uninstall Essentials using the uninstall.sh command, then again perform the Essentials installation procedure.
If you run /usr/CSCOpx/bin/unintall.sh, the script exits quickly and a message is displayed that indicates dmgtd is terminated with SIGKILL.
The workaround is to run uninstall.sh again. [CSCdk48753]
Uninstalling Essentials does not remove all Device Configuration related directories in /var/adm/CSCOpx/files. To remove all Device Configuration related files, remove the /var/adm/CSCOpx/files/archive directory. [CSCdk50635]
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, you must move them to a different directory before uninstalling Essentials.
If you install Essentials and CWSI Campus on the same machine, you cannot uninstall Essentials without first uninstalling CWSI Campus. Refer to Installing Resource Manager Essentials and CWSI Campus on AIX for more information.
Software Management stores images that are not removed by the Essentials uninstall procedure. If you want to permanently remove Essentials, you must manually remove these files from /usr/CSCOpx/files/sw_images.
The process RmeOrbLocationService fails to run after installing Essentials. The /var/adm/CSCOpx/log/daemons.log displays the following error message:
Could not load program /usr/CSCOpx/lib/visigenics/bin/locserv Symbol __CurrentException in dmgtd.aix is undefined Error was: Exec format error
The workaround is to install a C++ runtime environment patch xlC.rte.3.1.4.8. You can install the patch using SMIT. To restart the Daemon Manager after installing the patch, use the following commands:
/etc/rc.dmgtd stop /etc/rc.dmgtd start
Make sure you have the correct patches installed for the version of AIX on your system:
Installation fails for a user-defined Open Server Gateway port with the following error message:
ERROR: Could not create the interfaces file !! ERROR: Base package: CSCOxrts did not install. Exiting.
To correct this situation, perform the following steps:
Step 1 Login to the system as SuperUser.
Step 2 Edit the file /etc/services and edit the following line:
cscoosg 0/tcp # Resource Manager Essentials open server gateway
to read as
cscoosg XXXXX/tcp # Resource Manager Essentials open server gateway
where XXXXX is the value of a free port which had been entered previously during the installation. This port can also be identified from the ciscoinstall.log as follows:
fgrep 'Which tcp port should Open Server Gateway use' /var/tmp/ciscoinstall.log| tail -1
The output will look similar to the following:
Which tcp port should Open Server Gateway use ? INFO: Checking port 23434 for Open Server Gateway... Available.
In this case, the free port is 23434. Therefore, you must update /etc/services with this value.
If there is no output from fgrep, chose a port and validate that it is free by doing the following:
sh -c 'PORT=XXXXX ; netstat -an | egrep "\*\.${PORT}[ \t]+" | fgrep LISTEN ; grep ${PORT} /etc/services'
In this case, XXXXX is the value of a port and should be between 1024 and 65000. If the port is free there should be no output.
Step 3 Run setup.sh again to repair the configuration.
You will be prompted to reinstall the software. Enter Yes, otherwise the product will not fully install.
Step 4 Enter the following commands to reconfigure the Open Server Gateway:
/etc/init.d/dmgtd stop cd /opt/CSCOpx/objects/db/conf sh ./interfaces.pl localhost \QGetPkgParam CSCOmd PX_OSG_PORT\Q EssentialsOSG ./javaprops.pl /opt/CSCOpx/www/classpath/com/cisco/nm/cmf/dbservice/DBServer.properties com.sybase.jdbc.SybDriver jdbc:sybase:Tds:localhost:\QGetPkgParamCSCOmd PX_OSG_PORT\Q \QGetPkgParam CSCOmd PX_DATASTORE\Q /etc/init.d/dmgtd start
Step 5 Verify that all processes are running by entering the following command:
/opt/CSCOpx/bin/pdshow
Review the following information before installing CWSI Campus 2.2.
If the installation directory (/usr or whatever alternate directory you may have chosen) has insufficient space to install the Campus product, an error message is reported and you are given the option to select an alternate directory with more space. The installation process then begins again in the new directory.
In addition, the AIX install procedure "installp" requires a certain amount of space in the installation directory for it to operate. If there is insufficient space for "installp" it will report an error but will not give you the option of choosing an alternate directory. This occurs, for example, when you attempt to install in a directory with near zero available space. [CSCdk66452]
After installing CWSI Campus 2.2, wait approximately 5 minutes before starting the product. If you attempt to start the product too soon, the following error message is displayed:
osagent could not find the object object_name. ANI server
Click OK, wait a few minutes, and then start the product again. This error does not affect product operation.
In performing a reinstallation of CWSI Campus, any previously installed optional components that are not selected during the reinstallation will be uninstalled. From an installation perspective, CWSI Campus is comprised of CWSI Campus, CiscoView, TrafficDirector, and AtmDirector. TrafficDirector and AtmDirector are optionally installable components Following are some sample reinstallation scenarios:
[CSCdk76536]
To reinstall CWSI Campus 2.2, perform these steps:
Step 1 If you have CWSI Campus 2.2 (beta version) installed on your system, you must uninstall it before installing the released CWSI Campus 2.2 version.
Step 2 Close all CWSI Campus windows and applications. Enter stopcwsiserver. Then manually stop all remaining running processes by entering the following commands:
ps -ef | grep CSCOcwsi kill-9process_id
Otherwise, the install process aborts while trying to overwrite files that are in use. [CSCdk32436]
Step 3 Start the install process using the installation guide.
The install process looks for any previous CWSI install and its version.
Step 4 You are prompted to confirm that you want to save the database and the data files. If you click No, these data 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: namely, the installation folder, the database folder, the seed device, and the components that are installed (CiscoView, TrafficDirector and AtmDirector), if any.
The CiscoView 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 5 Terminate the previously running dvtrapd process (a process used by TrafficDirector) by entering the following commands:
# ps -ef | grep dvtrapd # kill process_id
Note the following caveats:
To uninstall CWSI Campus, enter the following commands:
cd /usr/CSCOcwsi/bin ./uninstall.sh
This section contains information, notes, and caveats for Resource Manager Essentials.
Essentials lets you import device information from remote network management databases identified in Table 5 and from local network management databases identified in Table 6.
Essentials can be installed on the same machine as HP OpenView, OpenView Professional Suite, CiscoWorks 4.0, and CWSI Campus without any compatibility problems.
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.
| Software | Version |
|---|---|
HP OpenView | 4.11 and 5.01 |
CiscoWorks | 3.2 and 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1.1 |
CWSI Campus | 2.2 |
| Software | Version |
|---|---|
CiscoWorks | 3.2 and 4.0 |
CWSI Campus | 2.2 |
Essentials supports the devices listed in Table 7 through Table 11. For information on supported Cisco IOS versions, see the "Cisco IOS Versions Supported" section. For information on supported Catalyst software versions, see the "Catalyst Software Versions Supported" section. For information on supported token ring firmware, see the "Using Essentials with Token Ring Switching Products" section.
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 | LightStream 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 | LightStream 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 | 29001, 5000, 5002, 5500, 8510, C5RSM, Catalyst 5000 modules supported: NMP, TR, FDDI, ATM, CDDI |
ATM switch | LightStream 1010, 1015 |
| 1Catalyst 2900XL devices are not supported. |
| 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 |
ATM switch | LightStream 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 |
Full 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 the AIX operating systems. It consists of the following sections:
Using the Apache http server to support software not installed by Essentials is not supported.
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]
The following sections contain caveats that pertain to Internet Explorer 4.X.
The following administrator options have been found to sometimes cause the Internet Explorer browser to hang.
Installing the Internet Explorer 4.0 Service Pack 1 eases the problem, but the browser still might hang occasionally. [CSCdk32462]
When trying to print Device Configuration or Syslog (Java-based) reports from Internet Explorer running on Windows 95, you get a system error. The workaround is to save the HTML version of the report to your local disk, then print the report from your local machine. [CSCdk26130]
Essentials depends on cookies to transmit permission-related information. If multiple copies of 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, Internet Explorer gets confused and generates authorization failures when you are correctly logged in.
The workaround is to start new browser windows using the New option from within the browser. [CSCdk33035]
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.
The following sections contain caveats that pertain to Netscape Navigator 4.04 and/or 4.05.
A server error message is displayed on the lower frame of the Exceptions Summary Report in Change Audit > Exceptions Summary, but only under the following conditions:
The workarounds include:
If you are using Netscape 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. [CSCdk44743]
Netscape 4.0x does not display the correct month and day for GMT time zones containing offset minutes [CSCdk34547]
Netscape 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. The workaround is to use Microsoft Internet Explorer 4.01. [CSCdk44551]
The Navigator 4.05 right mouse button pop-up menu offers the Open Frame in New Window option. If you select this option while in Essentials, the right frame of the Essentials desktop appears, but the navigation tree does not. To avoid this, complete all tasks in Essentials windows. [CSCdj50947]
Navigator 4.05 does not dynamically update the Reachability Dashboard (Tasks > Availability > Reachability Dashboard) when devices change state. To update the information in the Reachability Dashboard, click the Navigator Reload button. [CSCdj55007]
If you access the Glossary (Help > Glossary) with Navigator 4.05, clicking the Back button in the help window might take you to the help contents page instead of the beginning of the glossary section. To return to the Glossary, click Glossary. [CSCdj57449]
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]
When the database is down, if you click Admin > Inventory > Schedule Collection, a blank page is displayed. [CSCdj60419]
If you start Essentials by logging in as root and entering the following command in a C shell
# /etc/rc.dmgtd start
Ensure you do not suspend the root session using the suspend command. If you suspend the root session after manually starting Essentials, other processes such as the Daemon Manager, DIServer, and IcServer are also suspended. To resolve this issue, unsuspend the root session, and the processes restart normally.
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 (/var/adm/CSCOpx/log/daemons.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]
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, ensure your target system is configured correctly. Consult the following Essentials online help topics for instructions on what you need to do before importing devices:
When troubleshooting a device import from HP OpenView or CiscoWorks, you can run the DataPrep.pl script from the command line to help determine the cause of the failure. If you enter the command-line options incorrectly or omit them, DataPrep.pl will not report any errors. Refer to the Essentials online help for the correct use of the DataPrep.pl script and troubleshooting. [CSCdj54272]
When processing an import file, the checkaddr.pl uses a case-sensitive search when looking for the NM header. Any change in the case causes the header line to be filtered out, thus breaking the validity of the filtered import file. The workaround is to edit the filtered file and remove the incorrect prefix to the NM header line after the filtering is complete. [CSCdk51413]
When the user selects Admin > Inventory > Export to File and specifies 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]
In the Chassis Slot Details reports for Access devices (AS5200s and AS5300s) and RSMs, the number of available slots displays a negative number; however the same information is displayed correctly in the Detailed Device Report. [CSCdk52231]
When selecting Admin > Inventory > Schedule Collection, the pages have text that refers to SNMP settings, but SNMP setting controls have been moved to Admin > System Admin > System Configuration. [CSCdk39863]
For Year 2000 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 places 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 displays 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.
Performing ChangeAudit while performing ConfigUpload for approximately 1000 or more devices might dump core in the /opt/CSCOpx/objects/dmgt directory. The Daemon Manager will automatically retstart the ChangeAudit process.
The ChangeAudit process behaves this way due to a problem in JRE 1.1.4. This problem does not affect the functionality of Essentials and does not result in any data loss. No action is required by the user. [CSCdk76525]
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 receive the error message, "Unable to create the 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 is not updated. [CSCdk51481]
If the configuration archive is relocated, a search by pattern (when no devices are selected) will not yield any results.
To view the workaround, refer to URL:
http://<RME_server_hostname>/CSCOnm/servlet/JSServlet
Click the Unload All Clients option. The page will be refreshed after the clients are unloaded. Then click the Load All Clients option. [CSCdk52938]
The error message "Connection with remote device lost. Try again." appears in the Partially Failed Running Configuration Device Summary for the Catalyst 5000 family of devices. This failure reason is shown even when Configuration Archive is successful in receiving the device configuration. The workaround is to check the archived configuration file. [CSCdk50736]
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]
When you select Admin > Device configuration > General Setup >
Archive Setup Symptom, then select Archive Purge Policy, you might see an exception error if you leave the Older than field empty and click applY. For example, if the default is "Older than 30 days" and the user deletes 30 from the text box leaving the day count blank, the database is updated with the archive policy "Older than blank days."
The workaround is to ensure that you never leave the text field blank. [CSCdk49024]
The following steps were omitted from the Essentials online help. To move the configuration archive by selecting Admin > Device Configuration > General Setup, you must follow these 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.
On UNIX, cwconfig is a set-userid program owned by root and belongs in the bin group. However, as soon as the program is launched, (internally) cwconfig sets userid to bin. The groupid of the process remains the same as the invoking user's groupid. Consequently, all files created by cwconfig - exported configurations and log files - are owned by bin and belong in the same group as the invoking user. The files have Read-Write permissions for both owner and group. [CSCdk44589]
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 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]
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.
A defect exists in certain versions of Cisco IOS that causes the SNMP agent on router devices to become unresponsive to SNMP queries when certain MIB variables are polled. This bug only exists on routers that support the CISCO-FLASH MIB, which includes the following routers: Cisco 7200 series, 7500 series, RSMs (the router card for 5xxx switches) and 7000 series with RSPs.
The workaround is to upgrade Cisco IOS to 11.2(14)P or higher. Cisco IOS versions 11.3(2) and 11.2(9) also exhibit bug symptoms; Cisco IOS versions 11.3(3) and 11.2(13) contain fixes. ([CSCdj60284]
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]
Software Management fails with RCP as the transport mechanism for the default user (cwuser); however, the job completes with TFTP as a fallback transport mechanism.
The Software Management module needs write permission on .rhosts file for RCP. On AIX, RCP works only if .rhosts file has 0600 as its permission. This is a conflicting requirement for a non-bin user on AIX.
If you are aware of the security issues involved, you can use RCP by changing the RCP User Name to bin (Admin > System Configure > RCP). [CSCdk55124]
In the Browse History Report page for Catalyst devices, the Image Entity column displays extra text after the image name as in Supervisor.1/system SW. This extra text after the "/" character is incorrect and should be ignored. [CSCdk50175]
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.
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 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. Ignore this message 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 you to enter 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.
Before proceeding with module software upgrades, manually verify that the Catalyst switch is running a compatible Supervisor software version. [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 softwares into the library from the File System/Device, input the part of the file name after WA as the software version number.
In the previous example, 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 isl displayed 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.
Table 14 lists examples of software version information.
| Filename | Software Management | Show Module Command Version |
|---|---|---|
c5atm-wtall_113-2_WA4_3.bin | 4(3) | 11.3(2)WA4(3) |
c5atm-wtall_113-2a_WA4_4b.bin | 4(4b) | 11.3(2)WA4(4b) |
c5atm-wtall_113-3a_WA4_5.bin | 4(5) | 11.3(2)WA4(5) |
c5atm-wtall_113-4_WA4_7a.bin | 4(7a) | 11.3(2)WA4(7a) |
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.
You 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) you 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 you 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.
The workaround is to select less than 50 devices if they have a slower link to the Internet. [CSCdk32490]
If you import images that take more than 20 minutes to complete, the browser might time out and display a message that says, "Document contains no data."
The workaround is to decrease the number of images you import at one time to ensure the import takes 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 executing other Essentials functions.
The workaround is to 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.
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 from the Select Device Type dialog box (Tasks > Software Management > Distribute Images).
All devices with microcode (MICA modems, Microcom firmware, or CIP cards) require telnet access to upgrade their 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.
If you are using 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 you have a network that is using 160x devices, you can import a software image into the library once, then use it for distributing to all 160x routers.
You 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 ensures that Software Management checks the correct DRAM requirement for all 160x devices.
For Supervisor III modules on Catalyst 5000 and 2900 devices, the baseline and synchronization options are supported only when the modules are running software version 4.1 or later. [CSCdk06556]
For all Netscape browsers, the "All Syslog Messages" report from Device Center does not work. You will get a null pointer exception message. The internal cause of this is due to the "title" not being set for this report.
There is no workaround at this time. [CSCdk52585]
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 messages 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.
The workaround is to again generate the syslog report. [CSCdk33214]
Case Management Query (Tools > Case Management > Case Query/Update) might not show all your open cases. This 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 may take a while. The Technical Assistance Center is usually able to process these requests within an hour, but it could 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.
The workaround is to edit the $CRMROOT/cgi-bin/smartcase/IosTelnet.pm file and change the line:
$IosTelnet::Timeout = 30;to$IosTelnet::Timeout = 90;
Continue incrementing this value until the process completes. [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]
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 | NetworkTopology | 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 |
Catalyst 2820 | 2822, 2828 | X | X | X | X | X2 | X | -1 | 8.0 |
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 8500 CSR | 8510 | X | X | X9 | - | - | - | X10 | IOS 11.3 |
| ATM Switches | |||||||||
LightStream | LightStream 1010 (with Frame | 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 | 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 Switch | - | X14 | X | - | - | - | - | 4.21 |
- | WAN Switch | - | X14 | - | - | - | -15 | - | 4.2.1 |
- | WAN Switch | - | X14 | X | - | - | - | - | 4.2.2 |
- | Network Analysis Modules (NAM) (Catalyst 5X00 module) | - | X | X | - | - | - | - | 4.3 (Catalyst) |
You can select and start up both CiscoView and TrafficDirector applications from NetView. The additional CWSI Campus functions, including the CWSI Campus topology mapping services, VlanDirector, AtmDirector, and UserTracking applications, must be started from the CWSI Campus Network Map window. The map is started from AIX as part of the normal start-up procedures for CWSI Campus.
TrafficDirector and CiscoView are device-focused applications and are easily started from NetView based on the device-discovery process within NetView. The additional CWSI Campus functions require more detailed network-wide topology data than NetView can provide. The CWSI Campus discovery and database services must be running for these additional applications to function, which means you need to start these services from the main CWSI Campus window.
Using an X terminal to access and control CWSI Campus 2.2 applications is not officially supported.
Many X terminal systems might appear to run some of the CWSI Campus functions satisfactorily. However, there is a known problem when running a CWSI Campus client to an X display on a non-AIX workstation. JavaSoft's Java Runtime Engine (JRE) does not function properly because fonts are specified that are not available on many X11 servers. The result is that the X server on the remote system refuses to establish the session and exits.
If you decide to use Netscape as your browser, and it has not already been installed, you can install it at any time. Starting CWSI Campus Help does not provide the interaction for you to view and accept the Netscape licensing information. You must start Netscape at least once before starting CWSI Campus Help so that you can accept the Netscape licensing information. If you do not start Netscape before starting CWSI Campus help, CWSI Campus help will not start.
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.
The CWSI Campus network map does not show the device icons when running CWSI Campus on a remote display.
This situation cccurs only when a Solaris system is used for the remote display. This situation does not occur when using an HP system that is set for remote display or when the HP desktop console is the CWSI client. This situation does not occur on PCs using X-Term or Reflection-X
The workaround is to display the device icons as vector graphics instead of bitmap graphics. To do this, from the CWSI Network map, select Options > Properties > Map and change the Device Icons to Vector instead of Bitmap. [CSCdk56686]
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.
The following issues apply to the UserTracking discovery process:
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 Cisco IOS 11.1 or greater. The TrafficDirector application assumes that the RMON statistics group is always supported, which is not the case for Cisco 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 AIX or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete the $CWSIROOT/usr/pingoff file.
To integrate the TrafficDirector application with other network management system (NMS) platforms, see "Integrating Traffic Director with Other Managers" in Appendix C of the Using the Campus TrafficDirector Application publication.
Table 16 indicates when a shared property file or a custom property file is used when you configure 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, the file 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 launch 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. To reinitialize the probe, reset the probe and run the rm_rove script in the /usr/CSCOcwsi directory. 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 only the following Token Ring RMON MIB groups:
If you try to set thresholds on objects in any of the other Token Ring groups, the following error appears:
Install aborted unexpected SNMPAPI ErrorThe 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 config file results in duplicate entries being seen in he ATALK All Talkers display. [CSCdj89834]
Integration of the TrafficDirector application with Sun NetManager results in the switch probes being discovered and displayed on the Sun NetManager topology with TrafficDirector application icons. [CSCdk24059]
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 notes 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 is displayed 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 is 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.
AtmDirector Display Goes Blank
Under certain circumstances that have not been fully characterized, AtmDirector displays might go blank. To regain the display, you must close and reopen AtmDirector. No data will be lost. This problem has been experienced in only a few systems.
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 |
|
|
Support for other applications are listed in Table 19.
| Application | Description | OS | Cisco IOS | Device Support |
|---|---|---|---|---|
Threshold Manager | Monitors the availability and performance of Cisco devices | AIX 4.2.1 or 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 | AIX 4.2.1 or 4.3 | 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 | AIX 4.2.1 or 4.3 | 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 | AIX 4.2.1 or 4.3 | 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) |
WG_Concentrator.pkg | 4.0(1.3) |
stackmkr.pkg | 4.0(1.1) |
Threshold_AIX.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 "Cisco Connection Online" at the end of this release note for information about accessing CCO. Partner-initiated customers should refer to the section "Partner Initiated Customer Accounts."
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 caveats in CiscoView 4.1(1) that are fixed in CiscoView 4.2(1). Only the most serious caveats resolved in CiscoView 4.2(1) are listed.
Applet and device package caveats 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 unable 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 does not 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 NetView with the device symbols and bitmaps.
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:
line 46: syntax error line 49: syntax error failed in loading /usr/SUNWconn/snm/struct/Cat3900.schema
This section contains general notes and caveats. They are divided into five sections:
| 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 |
Before providing troubleshooting procedures, 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. 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 and for storing historical data for the UserTracking application. 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 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.
You can enter a command to view all servers registered with CORBA. However, before executing this command, you must make sure that the environment variable for the OSAGENT_PORT is set to 42342. To do this, enter the following command:
setenv OSAGENT_PORT 42342
Then to see all servers registered with CORBA, and where they are located, enter:
/usr/CSCOpx/lib/visigenics/bin/osfind
RTPoller is used to obtain real-time data for graphing in the AtmDirector application.
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, log in as Super User and enter the /usr/CSCOcwsi/bin directory.
Open a shell window Command Prompt window. Enter stopcwsiserver to stop the CWSI Campus server processes. When the shell 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 shell prompt returns. Wait a few minutes to allow the processes to start and get into a steady state before starting CWSI Campus.
After running osfind, if you see that the AniServer or one of the other servers is missing, or you see in the processes lookup 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, 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 Daemons," earlier in this section), and then run the startcwsiserver script. Run osfind again. If AniServer is there, log into CWSI. If AniServer is still not registered, you might have a corrupt database.
You will need to reinitialize the corrupt database, which will delete all current data in the database. To do this, follow these steps:
1. Log in as Super User.
2. Go to the /usr/CSCOcwsi/bin directory.
3. Run reinitdb.
In addition to these release notes and online help, the CWSI Campus documentation set includes the following documents:
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 Essentials contains links to marketing and technical documentation and includes the latest downloadable Essentials packages. To find the latest Essentials 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:24:22 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.