|
|
These release notes are for use with CiscoWorks2000 CD Two 1st Edition running on Solaris 2.6. They contain:
The following documents are provided in PDF on your product CD:
Use these publications to learn how to install and use CiscoWorks2000:
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 make sure that time zones are translated correctly -- especially when your devices, servers, and clients are in different time zones -- follow these guidelines:
 |
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, these steps illustrate 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 (such as syslog) containing the device time zone 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 either Pacific Standard Time (PST) or Pacific Daylight Time (PDT) and will likely be incorrectly translated. |
3. When a client requests a report, the GMT stored in the Essentials database is converted to the CiscoWorks2000 server's time zone and is displayed in Essentials reports. Because Perl and Java process Essentials reports differently, the server time zone is displayed as either an acronym or a GMT offset (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 | |||
+10:00, +11:00 | Australia | Brisbane, Melbourne | GMT + Offset | AEST, AET, or EAST |
+9:30 | Australia | Adelaide |
| ACT |
+9:00 | Japan/Tokyo | Tokyo |
| JST |
+8:00 | China | Beijing |
| CST |
+3:00, +4:00 (DST1) | Russia/Moscow | Moscow | GMT +3:00, |
|
+2:00, +3:00 (DST) | Cairo, Helsinki | Cairo, Helsinki |
| GMT +2:00, |
+2:00 | Israel | Israel |
| IDT |
+1:00, +2:00 (DST) | Germany, Italy | Berlin, Rome | GMT +1:00, |
|
+1:00, +2:00 (DST) | France, Spain | Paris, Madrid | GMT +1:00, | CEST |
0 | Africa, Great Britain/ London | Greenwich Mean Time | GMT | GMT |
-5:00, -4:00 (DST) | Eastern Canada | Atlantic |
| ADT |
-5:00, -4:00 (DST) | U.S./New York | Eastern Time |
| EST, |
-6:00, -5:00 (DST) | U.S./Chicago | Central Time |
| CST, |
-7:00, -6:00 (DST) | U.S./Denver | Mountain Time |
| MST, |
-8:00, -7:00 (DST) | U.S./Los Angeles | Pacific Time |
| PST, |
-10:00 | Hawaii/Honolulu | Hawaii |
| HST |
| 1DST = Daylight Savings Time |
This section contains known problems for CD Two 1st Edition.
Known problems are unexpected behaviors or defects in CD Two 1st Edition 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 | 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 | Printing from a browser does not work reliably | To print a 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 found under 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 does 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, wait 10 seconds then select task again. If this does not help, restart system by one of these methods:
|
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. |
| 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 cable interface IP address 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. Time interval exists between modem installation and modem configuration. During interval, 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 device to use a community string with same case (upper or lower) as successfully managed device. 2. Change device to use a unique value for community string. |
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 export will be invalid. Exported CSV file cannot be used for importing devices. |
CSCdp78299 | Device card names do not appear in Detailed Device Report | 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, operation times out after 5 minutes. To work around this problem, reduce number of devices and repeat. |
CSCdr32913 | Uninstalling CD Two | CD Two fails to uninstall if it coexists on a machine with Essentials. If installed with Essentials, CD Two becomes a subset of the Essentials application suite. CD Two incorrectly appears as a choice for uninstallation. |
CSCdr40106 | Inventory only package needs online help fix | User guide, device views, and job approval links should not appear in online help for CD Two. User guide that appears in CD Two online help is intended for use with Essentials 3.1. It includes applications not available in CD Two. |
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: Tue May 30 12:14:55 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.