|
|
These release notes describe the known problems for Resource Manager Essentials 3.1 (CiscoWorks2000) running on HP-UX 11.0 (Additional information can be found in the Release Notes for CD One on HP-UX). 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. |
The following documents are provided in PDF on your product CD:
For information about supported devices, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_3_x/index.htm
Table 1 lists the time zone acronyms that are supported in the 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 HP-UX servers, edit the TZ value in the /etc/timezone 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 steps illustrate how time zones are converted as they are passed 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 | |||
+09:00, +09:30 +10:00, +11:00 | Australia | Brisbane, Melbourne | GMT - 10:00 GMT + Offset | EAST |
+9:00 | Japan/Tokyo | Tokyo | GMT - 9:00 GMT + 9:00 | JST |
+8:00 | China | Beijing | GMT - 8:00 GMT + 8:00 | CCT |
+3:00 | Cairo, Helsinki | Israel | GMT - 3:00 | BT |
+1:00, +2:00 | Central Europe |
| GMT +2:00 | AT |
-1:00 | Africa/Algiers |
| GMT -1:00, | CET |
-1:00 | Cape Verde Islands |
| GMT 1:00 GMT -1:00 | WAT |
-5:00 | U.S./New York | Eastern Time | GMT 5:00 GMT -5:00 | EST |
-3:00 | U.S./Buenos Aires | Central Time | GMT 3:00 GMT -3:00 | ADT |
-5:00, -4:00 | U.S./Caracas |
| AST 4:00 GMT -4:00 | AST |
-6:00, -5:00 | U.S./Chicago |
| CST 6:00 CDT, GMT -6:00 | CST |
-7:00 | U.S/Phoenix |
| MST 7:00 GMY -7:00 | MST |
-7:00 | U.S/Denver |
| MST 7:00 MDT, GMT -7:00 | MST |
-8:00 | U.S/ Los Angeles |
| GMT +8.00 GMT -8:00 | PST |
-9:00 | U.S/ Anchorag |
| YST 9.00 YDT, GMT -9:00 | YST |
-10:00 | Hawaii |
| GMT +10.00 GMT -10:00 | CAT |
-12:00 | New Zealand |
| GMT -12:00 | NZT |
Table 2 shows time zone settings and their acronyms for your network devices that are not managed by Essentials. Using Table 2 ensures 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 the 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 |
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:
in your web browser.This section contains:
| Bug ID | Summary | Explanation | ||||
|---|---|---|---|---|---|---|
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 | 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. | ||||
None | Printing from a browser does not work reliably | To print a copy of an Essentials screen, use the Print Screen or Capture Screen function. | ||||
CSCdp07512 | JVM in Netscape 4.61 | The JVM in Navigator 4.61 leaks memory in proportion to the number of classes loaded by the applet being used. To work around the problem, close your browser to free all memory claimed by the VM. | ||||
CSCdp08278 | Tasks might fail if server is not 100% up |
| ||||
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 the 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 the 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 | When you upgrade your software, you might need to clear your browser cache file to display the 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. |
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 the problem, reinstall Essentials, then remove residual jobs by selecting unwanted job and clicking remove button. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Starting Essentials as root | If you start Essentials by logging in as root and entering /sbin/init.d/dmgtd start, make sure you do not suspend the root session with 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. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdm05454 | Protocol Distribution report shows 100% TCP/IP utilization for Catalyst 5000 switches | If you launch the Protocol Distribution report from the Reachability Dashboard, and the option for availability polling for Reload & Protocol Distribution is off, the Protocol Distribution report shows 100% TCP/IP utilization for Catalyst 5000 family devices. If you launch Protocol Distribution directly from the Availability menu, the application 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 to a job. If you have more than 25 devices it is advisable to create more jobs, each comprising less than 25 devices. This method is faster than creating one job with more than 25 devices. |
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 the problemTo work around the 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 the problem, restart Config Editor. Unless a new file is opened, you can edit private copies. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | TACACS with SecureID | The Essentials configuration archive does not support TACACS with SecureID. It supports static passwords, which are defined when you add or import devices into the Essentials inventory. |
None | Configuration Import Message | Cwconfig cannot validate the syntactic correctness of configuration files uploaded to the device via the import command. As a result, the import is reported successful even if the configuration file is invalid.The configuration update will not succeed on the device, but cwconfig cannot detect this failure. |
None | Access restrictions and file permissions | Cwconfig is a set-userid program owned by root; it belongs in bin. However, as soon as the program starts, cwconfig sets the userid to bin. Groupid of the process remains the same as the invoking user's groupid. Consequently, all files created by cwconfig, exported configurations and log files, are owned by bin and belong in the same group as the invoking user. The files have read-write permissions for both owner and group. |
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 | The Telnet transport mechanism cannot retrieve or update device configurations if any remote devices have nonstandard device prompts. The accepted, standard device prompts on Cisco IOS devices are the device prompt strings ending with the greater than symbol (>)or the pound symbol (#) at the Telnet login and enable mode. The accepted, standard device prompts on Catalyst devices end with the keyword "enable" at the Telnet enable mode. |
None | Devices with multiple IP addresses | The TFTP transport mechanism might not work for devices with multiple IP addresses when a given device is managed by using the hostname in the Inventory database. The SNMP library used by TFTP queries for only one IP address for a given hostname while performing hostname resolution with the corresponding domain name server. For a device with more than one IP address, hostname resolution might not return the IP address of the interface running the SNMP agent. In such cases, TFTP fails and displays SNMP Time Out Error. To work around the problem, import devices using the IP address in the inventory database. |
CSCdk12667 | Command-line syntax errors | When a cwconfig session has multiple syntax errors, only the first detected error is reported. The others remain unlisted. |
CSCdm83922 | Editing a job just before scheduled execution | If you edit a job just before it is scheduled to run and do not complete the edit in time, the job will run in its preedited state. The desired edit can still be scheduled, but you cannot reedit that job after the original edit is scheduled. To work around the problem, make sure your edit is complete before a job is scheduled to run or delete the job and create a new one. |
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 1 and number of devices supplied to the command is also greater than 1. To work around the problem, run command line interface application on problem device alone or reduce number of threads to 1, 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 su-directory. |
CSCdr09236 | cwConfig fails to download interactive config commands | When you use import or write2run commands, remove interactive config commands before scheduling a download. |
| Bug 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. Use a web browser to obtain information from the 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 the contract information. |
| Bug ID | Summary | Explanation |
|---|---|---|
None | Importing desktop machines | Do not import desktop machines unless they are running Cisco CallManager application. Otherwise, desktop machine appears incorrectly in the device selector under CallManagers. |
None | IP address may change between reboots | You must import cable modems ubr904 and ubr924 using the fully qualified pathname. These devices get the IP address of the cable interface using DHCP from the head-end cable router; the IP address might change between reboots. |
None | PIX Firewall device | Configure the PIX Firewall device on your SNMP server host so Essentials can manage it: Enter the server and IP address of your Essentials workstation. |
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 the 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 the database. If you add a device to the Essentials database with community strings similar to those already present in the ACCESS_DATA table (the only difference is the use of upper and lower case), the import fails. Because community strings are not removed from the database, this problem also applies to devices removed from the database. |
CSCdm75952 | Do not use special characters in the Change Device Attributes window | If you select Resource Manager Essentials > Administration > Inventory > Change Device Attributes, then select a device and click, you must select User Fields. Do not use special characters such as apostrophes (`), semicolons(;), or parentheses (())in these 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 the problem, reduce number of devices and repeat. |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdp21510 | NetConfig job scheduled by Approver throws exception | If you have only Approver status in the NetConfig application, you cannot create a NetConfig job using the command line interface or run a NetConfig job using the GUI. To work around the problem, you must also be designated a NetAdmin, NetOp, or SysAdmin. |
CSCdp25706 | 2 user defined templates for IOS. 1 enable mode, 1 config mode | For Cisco IOS and FastSwitch, you cannot create a NetConfig job containing both enable mode (user-defined templates) and config mode (system-defined templates.) Instead, create different jobs. |
CSCdr05087 | NetConfig window using CAM | When CAM is used, NetConfig appears in an atypically large window. To work around the 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 the 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 the 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. |
CSCdr16266 | HPUX Error (Exception) while invoking set exception policies. | In NetConfig window, clicking Admin>Set template policies throws negative array size exception, if the user logged in has not got an email address. To work around the problem, login as admin user and modify the concerned user's profile to include an email address. |
| 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 the MultiSwitch Feature Card for Catalyst 6000 devices and RouterSwitch Feature Card for Catalyst 5000 devices. Images running on these devices cannot be imported by the 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 > CCO Upgrade Analysis > Distribution, the upgrade might recommend a Flash upgrade for a device that already satisfies the Flash requirement. Some versions of Cisco IOS images report a Flash size that is less than the actual size, which causes the upgrade analysis to make incorrect conclusions about the Flash requirement. To work around the problem, if the upgrade analysis recommends a Flash upgrade, make sure that a Flash 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. |
CSCdm08758 | Error in reports with HKT as local time zone | To work around the problem, modify the following file: /opt/CSCOpx/objects/perl/lib/site_perl/Time/Timezone.pm In this file, in function tz_name, at line number 226, replace if ($CRM::CRM_OS_UF eq 'SOL') { with if (($CRM::CRM_OS_UF eq 'SOL') || ($CRM::CRM_OS_UF eq 'HPUX') || ($CRM::CRM_OS_UF eq 'AIX')) { |
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdk47488 | Changing the default logging facility | Syslog messages are logged to a file. The file is configured to store local7.info messages from routers, but for the PIX devices, the default is not local7. To work around the problem, set the 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. |
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
| Language | E-mail Address |
|---|---|
English | tac@cisco.com |
Hanzi (Chinese) | chinese-tac@cisco.com |
Kanji (Japanese) | japan-tac@cisco.com |
Hangul (Korean) | korea-tac@cisco.com |
Spanish | tac@cisco.com |
Thai | thai-tac@cisco.com |
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Wed May 17 04:52:10 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.