|
|
These release notes are for use with CiscoWorks2000 Resource Manager Essentials 3.1 running on Solaris 2.6. This document contains the following sections:
 |
Caution If the Y2K Compliance Assessment Tool is installed on your machine, you must uninstall it before installing this version. Otherwise, the installation fails. |
|
Caution Make sure all applications are stopped before you upgrade Essentials. The upgrade depends on having reasonable interaction time with the database. If this is not possible, the upgrade fails. |
|
Caution CWSI Campus 2.x and Essentials 3.1 cannot coexist on the same machine. |
Use these publications to learn how to install and use CiscoWorks2000:
All Essentials documents are provided in PDF on your product CD.
For information about Essentials supported devices, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/
dev_sup/e3_1.htm
Table 1 shows the time zone acronyms supported in CiscoWorks2000 applications that use the time zone feature. These time zones can be configured on Essentials managed devices. Details in Table 1 are:
When configuring time zones on CiscoWorks2000 servers, use the supported value in Column 3. To set time zones on CiscoWorks2000 Solaris servers, edit the TZ value in the /etc/default/init file.
 |
Note Changes made to the system time zone from outside CiscoWorks2000 applications might not be reflected in already-running CiscoWorks2000 applications. After changing the time zone, restart all CiscoWorks2000 applications. |
To help you understand the importance of setting time zones correctly, the following illustrates how time zones are converted as they pass from devices to servers to clients in different time zones:
1. An event occurs on a managed device, and the application message containing the device's time zone information is sent to the server.
2. An application daemon on the server reads the incoming message, converts the time zone to GMT, and stores it in the Essentials database.
|
Note If the device acronym in the incoming message does not appear in Column 1, the stored time zone defaults to Pacific Standard Time (PST) or Pacific Daylight Time (PDT) and will likely be translated incorrectly. |
3. When a client requests a report, the GMT time stored in the Essentials database is converted to the server time zone, and displayed in Essentials reports. Because Perl and Java process Essentials reports differently, the report will display the server time zone as an acronym or an offset from GMT (as shown in Column 4.)
1 Offset from GMT | 2 Area Covered (Country/City) | 3 Time Zone Setting on Server | 4 Output in Report | |
|---|---|---|---|---|
| GMT | Acronym | |||
+9:00, +9:30, +10:00, +11:00 | Australia | Australia/(Region) | GMT + Offset | ACT, AEST, AET, EAST |
+9:00 | Japan/Tokyo | Japan |
| JST |
+8:00 | China | PRC |
| CST |
+4:00 | Russia/Moscow | W-SU | GMT + 4:00 |
|
+2:00, +3:00 (DST1) | Cairo, Helsinki, Israel | EET | GMT +2:00, | EET |
+1:00, +2:00 (DST) | Central Europe | MET |
| CEST, MET |
0, +1:00 (DST) | Great Britain/London | GB | GMT +0, |
|
0 | Africa | GMT | GMT |
|
-4:00 | Brazil | Brazil/West | GMT -4:00 |
|
-5:00, -4:00 (DST) | Canada | Canada/Eastern |
| EST, |
-5:00, -4:00 (DST) | U.S./New York | EST5EDT |
| EST, |
-6:00, -5:00 (DST) | U.S./Chicago | CST6CDT |
| CST, |
-7:00, -6:00 (DST) | U.S./Denver | MST7MDT |
| MST, |
-8:00, -7:00 (DST) | U.S./Los Angeles | PST8PDT |
| PST, |
-10:00 | Hawaii | US/Hawaii |
| HST |
| 1DST = Daylight Savings Time |
Table 2 shows time zone settings and their acronyms for your network devices that are not managed by Essentials. Use Table 2 to ensure that Syslog Analysis and the CiscoWorks2000 server function correctly. Make sure that the time zone information is correct on your devices. To set time zones on your devices, use your command-line interface (refer to your device-specific command reference manual.)
Syslog Analysis depends on receiving correct time zone information from your network devices. As a message is parsed by Syslog Analysis, the time zone acronym in the message is read and compared with a standard table within Essentials. If the time zones on your network devices are not configured properly, the comparison fails. Syslog Analysis defaults to PDT/PST, resulting in the wrong time conversion.
When Syslog Analysis parses and writes data to the database, the application converts all time zones to GMT and stores a message time zone in the database as GMT. If the acronym on your device is set properly, correct conversion occurs, and the GMT is calculated correctly. (See page 3 for a step-by-step description of time zone conversion between devices, servers, and clients in different time zones.)
1 Offset from GMT | 2 Time Zone Acronym Setting on Device | 3 Area Covered (Country/City) |
|---|---|---|
+12:00 | IDLE | International Date Line East |
+12:00 | NST, NZST, NZT | New Zealand/Wellington |
+11:00 | EADT | Australia/Queensland |
+11:00 | SST | Pacific/Guadalcanal, Solomon Islands |
+10:00, +11:00 | AEST, AET, EAST | Australia/Melbourne, Sydney |
+10:00 | GST | Mariana Islands/Guam |
+9:30 | ACT | Australia/Darwin |
+9:00 | JST | Asia/Tokyo |
+8:00 | CCT, CTT | Asia/Beijing, Shanghai, Taiwan |
+7:00 | VST | Asia/Bangkok |
+7:00, +8:00 (DST1) | WAST, WADT (DST) | Australia/Perth |
+6:00 | BST | Asia/Dacca |
+5:30 | IST | Asia/Calcutta |
+5:00 | PLT | Asia/Karachi |
+4:00 | NET | Asia/Yerevan |
+4:00 | ZP4 | Russia/Moscow |
+3:00 | ADT, EAT | Asia/Riyadh |
+3:00 | BT | Asia/Baghdad |
+2:00 | ART | Africa/Cairo |
+2:00, +3:00 (DST) | EET | Europe/Istanbul |
+1:00 | CAT | Atlantic/Cape Verde |
+1:00 | CET, ECT, FWT, MET, MEWT, | Paris/Madrid |
+1:00, +2:00 (DST) | SWT | Sweden/Stockholm |
0 | GMT, UTC2 | Africa, Great Britain/London |
-1:00 | WAT | Cape Verde Islands |
-2:00 | AT | Azores Islands |
-2:00 | FST | Finland |
-2:00 | MEST, MESZ | Mid-Europe |
-3:00 | AGT | South America/Buenos Aires |
-3:00 | BET | South America/Sao Paulo |
-3:30 | CNT | Canada/St. Johns |
-4:00 | PRT | South America/Caracas |
-5:00, -4:00 (DST) | EST, EDT (DST) | U.S./New York |
-5:00 | IET | U.S./Indianapolis |
-5:00 | ZP5 | U.S./Chesapeake Bay |
-6:00, -5:00 (DST) | CST, CDT (DST) | U.S./Chicago |
-6:00 | ZP6 | U.S./Chesapeake Bay |
-7:00, -6:00 (DST) | MST, MDT (DST) | U.S./Denver |
-7:00 | PNT | Pacific/Pitcairn |
-8:00, -7:00 (DST) | PST, PDT (DST) | U.S./Los Angeles |
-9:00, -8:00 (DST) | AST | U.S./Anchorage |
-9:00, -8:00 (DST) | YST, YDT (DST) | Canada/Yukon |
-10:00 | AHST, HDT, HST | Hawaii/Honolulu |
-11:00 | MIT | Pacific/Asia |
-11:00 | NT | Alaska/Nome |
-12:00 | IDLW | International Date Line West |
-13:00 | NZDT | New Zealand/Wellington |
| 1DST = Daylight Savings Time 2UCT = Coordinated Universal Time |
This section contains known problems for Resource Manager Essentials.
Known problems are unexpected behaviors or defects in Resource Manager Essentials software releases. They are graded according to severity levels. These release notes contain information for severity levels 1 and 2 only.
You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II. To access Bug Navigator II, do one of the following:
|
Note Essentials supports U.S. English and Japanese. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Installation guide lists incorrect JVM version for Internet Explorer | Installing and Setting Up Resource Manager Essentials 3.1 lists the incorrect Java Virtual Machine version for Internet Explorer. The correct version is 5.0.0.3186 or later. To verify correct version: 1) Select Tools > Internet Options > Advanced and click Java console enabled. 2) Restart browser. 3) Select View > Java Console. |
None | Browsers running on remote X servers | Browsers running on remote X servers are not supported. |
None | Cisco Voice Manager | Cisco Voice Manager must be installed on a different machine than Essentials. |
None | ACLM 1.1 and Essentials 3.1 | ACL Manager 1.1 requires the ACL Manager 1.1.1 patch to work with Essentials 3.1. |
None | Printing from a browser does not work reliably | To print an Essentials window, use Print Screen or Capture Screen function on your machine. |
None | Navigator 4.x: Table of contents or index does not appear in online help | If table of contents or index does not appear in online help, hold down Shift key and click Reload. |
CSCdk44743 | Navigator 4.x: Under certain conditions, requesting more records causes an internal error message | Server error message is displayed in lower frame of Exceptions Summary Report, Change Audit > Exceptions Summary, but only:
To work around this problem:
|
CSCdp07512 | Virtual memory in Navigator 4.6.1 | Virtual memory (VM) in Navigator 4.6.1 leaks memory in proportion to number of classes loaded by applet being used. To work around this problem, close browser to free all memory claimed by VM. |
CSCdp08278 | Tasks might fail if server is not 100% up | If you try to access CiscoWorks2000 before server is running fully, Login Manager will not appear. To work around this problem:
At beginning of CiscoWorks2000 session, if you select a task from navigation tree before server is running fully, task might fail. To work around this problem, select task again. If this does not help, restart system by one of these methods:
|
CSCdp13935 | NetConfig exit in conjuction with device-search applets can crash browser | If you use NetConfig application extensively and use device-selection applets on desktop at same time, browser crash might occur when you exit NetConfig. |
CSCdp22312 | Multiple sessions of Essentials on a single client is not supported | Only one instance of Essentials can be run from any given client. |
CSCdp74251 | Application performance very slow with HTTP proxy | Accessing Essentials via HTTP proxy might cause significant performance degradation. To work around this problem, access CiscoWorks2000 Server directly from client. |
CSCdp82755 | Navigator 4.x: Cannot access CiscoWorks2000 | After Config Editor Job browser is launched, you cannot access CiscoWorks2000 Desktop or Java console. To work around this problem, close Config Editor Job browser before trying to access other applications. |
CSCdr15447 | Netconfig jobs fail when the user logged in as ADMIN | Passwords are case-sensitive, usernames are not. NetConfig jobs fail if you log in as ADMIN instead of default admin. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | ATM image version and image family might be incorrect after upgrade | After an upgrade to Essentials 3.1, delete, then reimport ATM images from software image library. |
CSCdk18245 | Clearing cache after software upgrade | When you upgrade software, you must clear browser cache file to display login frame. If you are running Navigator, select Edit > Preferences > Advanced > Cache, then select Clear Memory Cache. If you are running Internet Explorer, select View > Internet Options > General > Temporary Internet File > Delete Files. |
CSCdk89921 | Essentials screen appears without the login applet | Do not change default file ownership and permissions for /var/sadm directory. If you do, bin will not be able to read files in directory. |
CSCdp11661 | Server error when attempting to open Inventory report | If you install TrafficDirector after Essentials and select /opt/CSCOpx for TrafficDirector installation directory (or the subdirectory where Essentials is installed), TrafficDirector could corrupt Essentials. If problem occurs, uninstall both Essentials and TrafficDirector and reinstall both products. Uninstalling only TrafficDirector does not clear problem in Essentials. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdp05515 | After an Essentials uninstall, Job Resource Manager does not remove NetConfig jobs | If you uninstall Essentials 3.x, you might notice NetConfig jobs are still displayed under CiscoWorks2000 Server > Administration > Job Management. To work around this problem, reinstall Essentials, then remove residual jobs by selecting unwanted job and clicking remove button. |
CSCdp24862 | After uninstalling RME only, re-install of RME fails | If you uninstall Essentials 3.x, then install it again on a CD One installation, second installation fails during database update. Failure is due to problem in Essentials 3.x uninstallation code, which removes files belonging to CD One. If you have this problem, log in as root, then: 1. Stop the Daemon Manager, if it is running, by entering /etc/init.d/dmgtd stop. 2. If Essentials 3.x was already installed and failed, uninstall it. 3. You must be perform this step before installing Essentials 3.x again: 4. Install Essentials 3.x. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Starting Essentials as root | If you start Essentials by logging in as root and entering /etc/init.d/dmgtd start, make sure you do not suspend session with suspend command. If you suspend the root session after manually starting Essentials, other processes, such as Daemon Manager, DIServer, and IcServer, are also suspended. To resolve this issue, unsuspend the root session. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdm05454 | Protocol Distribution report shows 100% TCP/IP utilization for Catalyst 5000 switches | If you launch Protocol Distribution report from Reachability Dashboard, and availability polling option for Reload & Protocol Distribution is off, report shows 100% TCP/IP utilization for Catalyst 5000 family devices. If you launch Protocol Distribution directly from Availability application, option recognizes that no views are configured for Protocol Distribution monitoring. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Managing configuration jobs | Selecting CiscoWorks2000 Server > Administration > Job Management is not preferred method for managing configuration jobs. Use Config Editor job browser. |
CSCdp74464 | Config Editor purge job can be removed from Job Manager | Do not remove a ConfigJobPurg job from CiscoWorks2000 Server > Administration > Job Management. If job was removed accidentally, you can create it again in Config Editor by selecting Edit > Set Job Policies. |
CSCdp84463 | Running Config Editor from Config Viewer or Job Manager leaves empty browser | If you run Config Editor from Config Viewer or Job Manager, an empty browser is launched. Do not close browser or some features might not function properly. |
CSCdp95147 | Downloading configuration files to devices | When using Config Editor, do not add more than 25 devices when downloading configuration files to devices in a single job. Adding more than 25 devices in a single job will take more time to create that job. |
CSCdp98004 | Stopping a running job | Stopping a job while it is running could cause unpredictable results. |
CSCdr09236 | Config Editor fails to download interactive config commands | If you try to download a configuration in "merge" mode and it has interactive config commands, such as set interface commands in Catalyst switches, download fails. To work around this problem, remove interactive config commands before scheduling a download. |
CSCdr11687 | System admin is able to delete and stop Config Edit jobs | Although unable to view Job Details or run Config Editor, you can delete and stop Config Editor jobs through Job Manager if you have system admin permissions. |
CSCdr14391 | Unable to edit config file from Solaris Netscape browser | You cannot edit a file after opening it by Device and Version or Pattern search. Private copies previously opened are also affected. To work around this problem, restart Config Editor. Unless a new file is opened, you can edit private copies. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | TACACS with SecureID | Essentials configuration archive does not support TACACS with SecureID. It supports static passwords, defined when you add or import devices into Essentials inventory. |
None | Configuration Import message | Cwconfig cannot validate syntactic correctness of configuration files uploaded to device via import command. As a result, import is reported successful even if configuration file is invalid. Configuration update does not succeed, but cwconfig cannot detect failure. |
None | Access restrictions and file permissions | Cwconfig is a set-userid program owned by root; it belongs in bin. However, as soon as program starts, cwconfig sets userid to bin. Process groupid remains the same as your groupid. Consequently, all files created by cwconfig, exported configurations and log files, are owned by bin and belong in same group as your groupid. Files are read-write for both owner and group. |
None | Banner commands on devices | Banner values are contained between quotation marks (") in config archive and between Ctrl-C (^C) characters in a device. When using NetConfig or Config Editor, or Telneting to a device, do not add quotation marks or Ctrl-C characters to banner commands on devices. Banner commands containing these characters cause configuration applications to function incorrectly. |
None | Updating modules in Catalyst 5000 Switches | cwConfig does not update or change configurations of individual modules in Catalyst 5000 switches even when import or write2run commands report a successful download. cwConfig updates only supervisor engine module configuration. |
None | Standard device prompts required for Configuration Archive Telnet mechanism | Telnet transport mechanism cannot retrieve or update device configurations if any remote devices have nonstandard device prompts. Accepted, standard device prompts on Cisco IOS devices have strings ending with greater than symbol (>) or the pound symbol (#) at Telnet login and enable mode. Accepted, standard device prompts on Catalyst devices end with keyword "enable" at Telnet enable mode. |
None | Devices with multiple IP addresses | TFTP transport mechanism might not work for devices with multiple IP addresses when device is managed by using hostname in the inventory database. SNMP library used by TFTP queries for only one IP address for a given hostname while resolving hostname with corresponding domain name server. For device with more than one IP address, hostname resolution might not return IP address of the interface running the SNMP agent. In such cases, TFTP fails and displays SNMP Time Out Error. To work around this problem, import devices using IP address in inventory database. |
CSCdk12667 | Command-line syntax errors | When a cwconfig session has multiple syntax errors, only first detected error is reported. Others remain unlisted. |
CSCdp30606 | TFTP functions fail on multihome machines | On multihome machines, you should have two mutually unknown networks: one for browser clients, one for network devices. If Essentials chooses IP address of browser-side interface for server, it also uses that address as TFTP server address, which causes TFTP operations to fail. Use of Essentials on multihome machines is not supported. |
CSCdp91314 | Netshow error: "java.lang.outOfMemory" | Netshow might flag a "java.lang.outOfMemory" error on a device. This problem occurs only with specific types of devices and only if number of threads (set in properties file) is greater than one and number of devices supplied to the command is also greater than one. To work around this problem, run command line interface application on problem device alone or reduce number of threads to one, and run serially. |
CSCdp98087 | Selecting Config Editor from Device Config report throws Java exception | Select Resource Manager Essentials > Configuration Management > NetConfig and create a new job. Select device from the Select Devices dialog box then select View Configuration to display Device Configuration Quick View Report. If you select Config Editor from this report, it gives a Java exception. If you try to use both NetConfig and Config Editor from same browser, one might fail. |
CSCdr00103 | Netsys: Message incorrectly confirms the creation of a baseline | When creating a baseline using an invalid Netsys installation directory, a message appears stating that a Netsys baseline was created successfully although creation failed. |
CSCdr03091 | Netsys: Setting the baseline name value | Netsys setup creates a directory called sConfig under the Netsys installation directory which contains config files Essentials passes to Netsys. Directory is deleted after setup. You should not set baseline name value in Netsys setup to sConfig or any sub-directory. |
CSCdr09236 | cwConfig fails to download interactive config commands | When you use import or write2run commands, remove interactive config commands before scheduling a download. |
| ID | Summary | Explanation |
|---|---|---|
CSCdm87814 | Essentials' Check Contract Status tool generates information for routers only. | If you select Resource Manager Essentials > Contract Connection > Check Contract Status, information is generated for routers only. Obtain information from CCO URL: http://www.cisco.com/cgi-bin/front.x/ From View Contracts, select By Contract > Serial > Purchase Order > Service Order Number (Contract Lookup) and find contract information. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Importing desktop machines | Do not import desktop machines unless they are running Cisco Call Manager application. Otherwise, desktop machine appears incorrectly in the device selector under Call Managers. |
None | IP address may change between reboots | You must import cable modems ubr904 and ubr924 using fully qualified pathname. These devices get IP address of the cable interface using DHCP from head-end cable router; IP address might change between reboots. |
None | PIX Firewall device | Configure PIX Firewall device so Essentials can manage it: Enter IP address of Essentials server. |
CSCdk35153 | Chassis modem table is not polled correctly | Inventory reports show only configured modems. An interval exists between modem installation and modem configuration. During interval, the Inventory application might detect only one modem. Additionally, log messages might display database integrity violations. These messages can be ignored. To work around this problem, go to device and configure modem, then reacquire inventory data. |
CSCdm01805 | Adding devices to Essentials fails | Adding devices to Essentials fails if case-insensitive community strings already exist in database. If you add a device to database with community strings similar to devices already present (difference is use of upper and lower case), import fails. To work around this problem: 1. Change the device to use a credential that has same case (upper or lower) as successfully managed device. 2. Change device to use a unique value for credential. |
CSCdm75952 | Do not use special characters in user fields | Do not enter special characters such as apostrophes ('), semicolons (;), or parentheses in user fields. |
CSCdp61331 | Comma included in password will cause device import to fail | In comma separated value (CSV) format, the "," character is used as a delimiter. Therefore, fields in the CSV file should not contain the "," character. If you use a "," character in password or other fields while adding a device, CSV file generated after exporting will be invalid. Exported CSV file cannot be used for importing devices. |
CSCdp62990 | Change Audit Reports might time out | If inventory contains 3000 devices or more, selecting Change Audit > All Changes or 24-Hour Reports > Change Audit Report might cause timeout. |
CSCdp78299 | Device card names do not appear in Detailed Device Report | The Detailed Device Report for BPX 8600, IGX 8400, and IPX devices running switch software releases earlier than 9.1 does not show interface information. |
CSCdr02713 | Chassis Summary and Software Version Graphs fail | If you click Chassis Summary Graph or Software Version Graph and select 2000 or more devices, the operation will time out after 5 minutes. To work around this problem, reduce number of devices and repeat. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdr05087 | NetConfig window using CAM | When CAM is used, NetConfig appears in an atypically large window. To work around this problem:
|
CSCdr05712 | Password template fails to get module configurations | If you run NetConfig job to change password on a device and ATM and RMS modules on that device are configured with same telnet and enable passwords, passwords on those modules and NetConfig job will fail to retrieve module configurations from device. To work around this problem, select Update Archive for device after NetConfig job is done. |
CSCdr08236 | Out Of Memory Error on java console | On Navigator or Internet Explorer, creating more than 10 jobs in the same NetConfig session might cause Out Of Memory errors. To work around this problem:
|
CSCdr09236 | NetConfig fails to download interactive config commands | In NetConfig, do not use interactive config commands such as set interface commands in Catalyst switches, with adhoc templates. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | MultiSwitch Feature Card for Catalyst 6000 and RouterSwitch Feature Card for Catalyst 5000 | Backup of current images during image distribution fails for MultiSwitch Feature Card for Catalyst 6000 devices and RouterSwitch Feature Card for Catalyst 5000 devices. Images running on these devices cannot be imported by image baseline or image synchronize task. |
CSCdm78469 | CCO Upgrade Analysis task may recommend incorrect flash upgrade requirements | If you select Resource Manager Essentials > Software Management > Distribution > CCO Upgrade Analysis, upgrade might recommend a Flash memory upgrade for a device that already satisfies Flash requirement. Some versions of Cisco IOS images report Flash size less than actual size, which causes upgrade analysis to make incorrect conclusions. To work around this problem, if upgrade analysis recommends Flash upgrade, make sure that upgrade is necessary. |
CSCdp92065 | Adding image to library from device fails | If you select Resource Manager Essentials > Administration > Edit Preferences and you have a Catalyst device running Supervisor 5.4(1), do not select rcp option. Otherwise, distribution and image import jobs fail. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdk47488 | Changing the default logging facility | Syslog messages are logged to a file configured to store local7.info messages from routers, but for PIX devices, the default is not local7. To work around this problem, set PIX device to facility 23. |
CSCdr10072 | Syslog automated action $M parameter works, $D does not | Errors exist in sampleEmailScript.pl. When $D value has more than one dash (-), for example enm-4000-4, parse routine fails. This is part of a sample script for using automated action and does not affect Essentials functionality. |
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.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@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: Mon Apr 3 13:22:26 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.