cc/td/doc/product/rtrmgmt/cw2000/cw2000_d
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Release Notes for CiscoWorks2000
CD One, 4th Edition on AIX and HP-UX

Cautions

New Features

Documentation Roadmap

Additional Information Online

Patch Requirements

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Documentation Errata

Known Problems

General Known Problems

CD One Installation Known Problems

CiscoView Known Problems

Device Support Utility Known Problems

Catalyst Devices Known Problems

Router and Hub Known Problems

General Device Package Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

ANI Server Known Problems

Device/Agent Known Problems Impacting ANI Server

Browser Known Problems

Obtaining Documentation

World Wide Web

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Release Notes for CiscoWorks2000
CD One, 4th Edition on AIX and HP-UX


These release notes are for use with the AIX and HP-UX server versions of CiscoWorks2000 CD One, 4th Edition. The supported versions are AIX 4.3.3
and HP-UX 11.0

These release notes provide the following information:

Cautions

New Features

Documentation Roadmap

Additional Information Online

Patch Requirements

Multi-Homed Machines

Security Enhancement

Operating System Upgrade

Support Information

Documentation Errata

Known Problems

Obtaining Documentation

Obtaining Technical Assistance

Cautions

CD One, 4th Edition and Resource Manager Essentials 3.1 cannot coexist on the same machine.

We have certified our product using HP-UX 11.0 with the September 2000 General Release patch bundle. Failure to install this patch bundle may lead to performance issues and other problems.

New Features

CD One contains these new features:

Scalability—The ANI Server is capable of managing 1500-2000 devices, and 40,000 user-tracking database entries.

Security enhancement—CiscoWorks2000 applications are now installed using the user casuser.

Support—CiscoWorks2000 contains support for the following:

AniClient support for Java Plug-in.

Workflow server and application support.

VTP server independence—CiscoWorks2000 supports VTP domains with and without a VTP server.

Cisco View, a component of CD One, contains these new features:

Device list import—Rapid loading and subsequent accessing of devices.

Device support enhancements—Both CiscoView and Campus Manager contain device support enhancements for several Cisco Products. The supported devices are:

CiscoView—http://www.cisco.com/kobayashi/sw-center/netmgmt/ciscoview/cvcww-download.shtml.

Campus Manager—http://www.cisco.com/univercd/cc/td/doc/product/
rtrmgmt/cw2000/camp_mgr/sup_dev/dev_spt.htm

New progress indicator—Provides status feedback on task execution.

Performance improvements—CiscoView contains performance improvements in the Monitor menu, Configuration menu, and Chassis view.

Remote upgrade of user preferences and device packages—CiscoView allows for remote upgrades of user preferences and device packages from previous versions of CiscoView.

Web-based Package Support Updater (PSU)—Scheduled and on-demand device support downloads from Cisco.com.

Documentation Roadmap

The documents provided in PDF on your product CD are:

Getting Started with the CiscoWorks2000 Server

Installing and Setting Up CD One

Installing and Setting Up Resource Manager Essentials

Using Campus Manager

Using CiscoView 5.3

Using Resource Manager Essentials

Using the TrafficDirector Application


Note Adobe Acrobat Reader 4.0 is required.


Use these publications to learn how to install and use CD One, 4th Edition:

Installing and Setting Up CD One—Provides installation instructions, including both server and client side system requirements, steps for installing and uninstalling, and installation troubleshooting information.

Getting Started with the CiscoWorks2000 Server—Provides information about setting up, administering, and assessing the CiscoWorks2000 Server, used by all CiscoWorks2000 applications.

Using CiscoView 5.3—Provides information about the use and operation of CiscoView, and also provides descriptions and scenarios for users or prospective users of this management tool.

Online Help for CiscoView and CiscoWorks2000 Server.

All product documentation is provided in PDF on your product CD.

You can order a complete set of hardcopy user guides for the products contained in the LAN Management Solutions Bundle using the part number CWDOC-RWAN-LMS.

You can place orders for documentation through an authorized Cisco reseller or a Cisco sales representative.

You can purchase individual installation and user guides using the Cisco MarketPlace ordering system. Cisco sales representatives, resellers, and users with direct ordering privileges can locate documentation part numbers and other ordering information by selecting the Documentation product family within MarketPlace and navigating to the CiscoWorks2000 section.

Additional Information Online

For information about CD One, 4th Edition supported devices, refer to:

Device Package Readme Files—Contain information about device, card, and platform support.

Device Package Installation Instructions—
http://www.cisco.com/kobayashi/sw-center/netmgmt/ciscoview/
cvcww-download.shtml

Patch Requirements

Patch Requirements for AIX Systems

The patch requirements for AIX 4.3.3 are:

X11.adt.lib(4.3.3.0)
bos.adt.include(4.3.3.1)
bos.net.tcp.client(4.3.3.3)
bos.sysmgt.serv_aid(4.3.3.2)
X11.base.lib(4.3.3.2)
X11.adt.motif(4.3.3.1)
X11.base.rte(4.3.3.2)
X11.Dt.rte(4.3.3.3)
X11.motif.mwm(4.3.3.1)
X11.motif.lib(4.3.3.2)
X11.compat.lib.X11R5(4.3.3.2)
bos.rte.libpthreads(4.3.3.3)
bos.adt.prof(4.3.3.3)
X11.Dt.lib(4.3.3.2)
bos.loc.com.utf(4.3.3.0)

For uniprocessor machines, add the following patch:
bos.up(4.3.3.3)

For multi-processor machines, add the following patches:
bos.up(4.3.3.50)
bos.mp(4.3.3.50)

Patch Requirements for HP-UX Systems

The patch requirements for HP-UX 11.0 are:

PHCO_20765 or PHCO_23770
PHKL_20202 or PHKL_23002
PHCO_19666
PHKL_20016
PHKL_18543
PHCO_20882 or PHCO_22453
PHKL_22380 or PHKL_23406
PHCO_21187or PHCO_22269
PHKL_21392 or PHKL_22432
PHKL_20674 or PHKL_22432
PHSS_21472 or PHSS_22614
PHSS_17535
PHSS_20864 or PHSS_22341
PHSS_23823
PHNE_22086
PHSS_20863
PHSS_21906 or PHSS_22543

Multi-Homed Machines

A multi-homed machine is a machine that has multiple NIC cards, each configured with different IP addresses. To run CD One on a multi-homed machine, there are two requirements:

All IP addresses must be configured in DNS.

Since there are restrictions with CORBA, only one IP address can be used by the client/browser to access the server. You must select one IP address as the external address, with which the client will login to the CiscoWorks2000 server.

To select an IP address:


Step 1 Modify the gatekeeper file located in opt/CSCOpx/lib/vbroker/gatekeeper.cfg.

Step 2 Replace every instance of external-IP-address with the external IP address you choose

Step 3 Remove the # character, from:

#vbroker.gatekeeper.backcompat.callback.host=external-IP-address

#vbroker.se.exterior.host=external-IP-address

#vbroker.se.iiop_tp.host=external-IP-address

Step 4 After modifying the gatekeeper file, restart the Daemon Manager by entering /etc/init.d/dmgtd start.



Note To look up this topic on Bug Navigator II, use bug ID CSCds84075. For more information on using Bug Navigator II, see the "Known Problems" section.


Security Enhancement

To address a CiscoWorks2000 security issue, CD One and other related applications will no longer be installed under the user bin. Beginning with
CD One, 4th Edition, CiscoWorks2000 applications will be installed under the new user casuser, which belongs to the new group casusers. The role of casuser is to provide day-to-day product administration and maintenance without root privileges.

The casuser account has these attributes:

No password

No administrative privileges

No Login Shell

During an upgrade to CD One, 4th Edition all currently installed CiscoWorks2000 applications, with the exception of CD One, are disabled. File permissions are transferred to the user casuser, which is created along with the group casusers.

Key data from these applications, such as community strings and user and host information, are archived. As the latest versions of the applications are installed, they are re-enabled and the necessary archived data is imported.


Caution Do not give a login shell or create a password for the user casuser. To do so will affect accountability in CiscoWorks2000. If a user is not a member of the group casusers, and wants to run CiscoWorks2000 commands from a shell prompt, add that user to casusers.

Note To look up this topic on Bug Navigator II, use bug ID CSCdj26280. For more information on using Bug Navigator II, see the "Known Problems" section.


Operating System Upgrade

If you upgrade the operating system upgrade after CD One is installed, you must re-install CD One.

Re-installing CD One will allow the installation process to check for required patches. Install any patches that are found missing. For a list of required patches, see Chapter 1 of Installing and Setting Up CD One on AIX and Installing and Setting Up CD One on HP-UX.


Caution If CD One is run without the required patches, it will not function properly.

Support Information

CiscoWorks2000 supports the following:

Operating System—CiscoWorks2000 supports both AIX 4.3.3 and
HP-UX 11.0.

Browser—CiscoWorks2000 supports the following browsers:

Netscape 4.75.

Internet Explorer 5.5 with Service Pack 1.

Hardware—CiscoWorks2000 supports IBM PC-compatible computers with an Intel Pentium III or Pentium IV processor.

Java—CiscoWorks2000 uses two types of Java. Certain applications use the browser's native Java Virtual Machine (JVM), while others use Sun's Java Plug-in. In order for CiscoWorks2000 to function correctly, you must be using the correct version of Java.

The supported native JVM versions are:

Microsoft Internet Explorer 5.5—JVM 5.0.0.3186 or later.

Netscape 4.75—the correct version of JVM is installed.

The supported Java Plug-in versions are:

Windows 9x, NT, and 2000—Java Plug-in 1.3.0.

Solaris—Java Plug-in 1.3.0.

AIX—Java Plug-in 1.3.0.

HP-UX—Java Plug-in 1.2.2.


Note The Plug-in version is independent of the browser used.


To install the Java Plug-in:

Internet Explorer—When you attempt to launch any CiscoWorks2000 application that uses the Java Plug-in for the first time, Internet Explorer will automatically install the correct Java Plug-in version for you.

Netscape—When you attempt to launch any CiscoWorks2000 application that uses the Java Plug-in for the first time, CiscoWorks2000 will redirect you to a page from which you can download and install the correct Java Plug-in version.

Manual Installation—To manually install the Java Plug-in, refer to Chapter 3 of Getting Started with the CiscoWorks2000 Server.


Note CiscoWorks2000 only supports the Java Plug-in versions mentioned above. Installing a different version, including a newer version, can cause CiscoWorks2000 to malfunction.


To see Java related messages, see the Java console. To do this, enable and then open the Java console. There are two Java consoles involved:

Native JVM's Java console

Java Plug-in's Java console.

To enable the native JVM console when using Internet Explorer:

a. Select Tools > Internet Options > Advanced.

b. Click Java Console.

c. To open the console select View > Java Console.

To enable the native JVM console when using Netscape:

a. Select Preferences > Advanced > Enable Java.

b. To open the console select Communicator > Tools > Java Console.

To enable the Java Plug-in console when using Windows 98, NT, or 2000:

a. Select Start > Settings > Control Panel.

b. Double-click Java Plug-in.

c. Select Enable Java Console.

To enable the Java Plug-in console when using Solaris, AIX, or HP-UX:

a. Run the program Pathname to your Java 2 runtime environment installation directory/bin/ControlPanel.

b. Select Show Java Console.


Note The Java Plug-in console will automatically open when you launch an application that uses it.


Documentation Errata

The following are areas in which documentation may be inaccurate or have become outdated:

Disregard references to Event Query which appear in some copies of the Getting Started Guide with the CiscoWorks2000 Server. The option is no longer available.

Disregard substep b of the "Typical Installation" section, found in Chapter 2 of Installing and Setting Up CD One on Windows 2000 and Windows NT. This step should read,

"Select the adapter from the list of available adapters, or select other to choose an adapter that is not listed (you will be prompted to enter the path name of the adapter) and click Next. If you select none, go to Step 5."

Known Problems

Known problems are unexpected behaviors or defects in CiscoWorks2000
CD One, 4th Edition software releases. They are graded according to severity level. These release notes contain information for severity levels 1 through 3.

You can search for problems using the Cisco bug tracking tool, Bug Navigator II. To access Bug Navigator II, log into Cisco.com and select Service & Support >  Technical Support Help—Cisco TAC > Tools > Software Bug Toolkit > 
Bug Navigator II
, or enter the following URL in your web browser: http://www.cisco.com/support/bugtools.

Known problems are located in the following sections:

General Known Problems

CD One Installation Known Problems

CiscoView Known Problems

Device Support Utility Known Problems

Catalyst Devices Known Problems

Router and Hub Known Problems

General Device Package Known Problems

Package Support Updater (PSU) Known Problems

Integration Utility Known Problems

ANI Server Known Problems

Device/Agent Known Problems Impacting ANI Server

Browser Known Problems

General Known Problems

Table 1 General Known Problems 

Bug ID
Summary
Explanation

None

Two additional user roles (Developer and Export Data) are displayed in the security user account windows.

Developer and Export Data roles are available only for Management Connection certification and third- party developers. In CiscoView, these roles only have read permission.

CSCdp87124

If the LDAPLoginModule is being used to authenticate users, the LDAP server must be configured to deny anonymous access to the directory where CiscoWorks2000 resides.

Unless LDAP server is set up to deny anonymous access, it authenticates any username entered without a password.

CSCdp94831

Cannot re-start CiscoWorks2000 server immediately after stopping it.

After you enter /etc/init.d/dmgtd stop, if any CiscoWorks2000 process does not release port promptly, entering /etc/init.d/dmgtd start will not restart Daemon Manager, and following message is returned:

The product could not start. The port is in use.

Workaround:

Enter /etc/init.d/dmgtd start until Daemon Manager starts.

Make sure that all CiscoWorks2000 processes are stopped before running
/etc/init.d/dmgtd start.

CSCdr94291

NEMI configuration dialog box for Metro 1500 device displays N/A as Subnet mask value.

NEMI configuration dialog box should display 255.255.255.0 as Subnet mask value.

Workaround:

No solution is available at this time.

CSCdr97090

CW2000 fails if Oracle is installed on the same system.

When Oracle is installed on a system it requires the tunable kernel parameters to be equal to what CW2000 needs. When you have Oracle Ingres or Informix installed on the same system it uses resources CW2000 expect to have available to it.

CSCds81730

After installation, error message occurs in log file.

If you upgrade to CD One 4th Edition, stop Daemon Manager, or Start Daemon Manager, this message appears in daemons.log:
sh: rvd: not found
TIB/Rendezvous Error.

Workaround:

Ignore this message.

CSCdt22462

Delay when downloading Java applets on Windows 2000 machines.

On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected (up to six minutes in some instances). After the applet has been loaded and cached locally, the problem no longer occurs.

The delay is caused by client side filtering mechanisms such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems.

This causes downloading to be significantly slower than expected. (The effect is less on systems with large amounts of RAM and virtual memory.)

Workaround:

Disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension).

Exact instructions vary depending on the virus scanner installed on your system.

For more information, see the following article:
http://support.microsoft.com/support/kb/articles/q240/3/09.asp.

CSCdt41354

Event Services administration port must be secured after installation.

Tibco HTTP port (7580) allows a local user, with a valid login to operating system, to access/modify the configuration information.

Workaround:

1. Secure port 7580 after installing CD One and changing desktop administrator password.

2. From a web browser on the machine where CMF is installed access http://localhost:7580

3. In the Configure section, click the link, Security.

4. Add the user name and password for use in configuring Event Services.

CSCdt50353

Unable to access help files for user-created management connections after reinstallation/upgrade of CiscoWorks2000.

After reinstallation/upgrade, CiscoWorks2000 fails to launch help files for user-created management connections that existed prior to reinstallation/upgrade.

Workaround:

Access help files directly. For example: to access help for a connection with folder name xyz, enter the following URL in the browser:
http:// CiscoWorks2000host:port /help/extern/xyz.html.

CSCdt74726

Error message appears when the ANIServer or JRM processes are stopped.

When you terminate the ANIServer or JRM processes using pdterm ANIServer or pdterm jrm, this error message appears:

ERROR: cmd failed. Server reason: No such process.

However, the process is terminated.

Workaround

There is no workaround available. You may ignore this message.


General Known Problems on AIX

Table 2 General Known Problems on AIX 

Bug ID
Summary
Explanation

CSCdp10560

Internet Explorer hangs when a Netscape Navigator session is also active.

When Explorer and Navigator are run together, the CW2000 desktop might hang.

Workaround:

Do not run Explorer when a Navigator session is active.

CSCdr97409

NetConfig fails if Japanese Characters are input in Job Description

CiscoWorks2000 applications are not always able to handle non-US (English) character set input. Entering viable non-English characters (Japanese and Swedish cases have been documented) may cause applications to fail.

Workaround:

Do not use non-US characters in input to CiscoWorks2000 applications.


General Known Problems on HP-UX

Table 3 General Known Problems on HP-UX

Bug ID
Summary
Explanation

CSCds44640

EDS GUI windows are not displayed on non-HP-UX workstation console.

Workaround:

Launch windows from HP-UX console.


CD One Installation Known Problems

The upgrade to CD One, 4th Edition sometimes hangs in the middle of the installation process (CSCds25842). The problem happens very infrequently and seems to be related to the length of time the existing CiscoWorks2000 software takes to fully shut down and relinquish resources to AIX and HP-UX.

To avoid the problem:

1. Log in as root.

2. Prior to starting the upgrade, enter the following commands to manually stop all CiscoWorks2000 processes:
%/etc/rc.dmgtd stop.(for AIX)
and
%/sbin/init.d/dmgtd stop (for HP-UX)

3. Wait 10 minutes, then start the upgrade process.

Table 4 CD One Installation Known Problems 

Bug ID
Summary
Explanation

CSCdm95087

DNS server required for Campus Manager.

Campus Manager requires a DNS server to function properly. Many functions will operate erratically or not at all if there is no DNS server on the network.

CSCdp94831

Cannot always launch CiscoWorks2000 after the installation of CD One Second Edition.

After you enter /etc/rc.dmgtd stop, if any child process does not release port promptly, entering /etc/rc.dmgtd start will not start Daemon Manager, and this message appears:
Daemon Manager could not start. The port is in use.

Workaround:
/etc/rc.dmgtd start until Daemon Manager starts.

Make sure that all CSCOpx processes are stopped before running /etc/init.d/dmgtd start.

CSCdr25407

Cleaning up a broken install.

Subsequent installs may fail if an installation is cancelled before completion, or the uninstall fails to perform a complete cleanup. In such a case, you need to clean up the CW2000 packages from the system and restart the install.

Workaround:

Use the script fpkgdel.sh which is available in the CD One CD under the install directory to perform cleanup.

Note This script is meant only for cleaning up broken installation. This script should not be used to perform a normal uninstall.

CSCdt15886

If upgrading from Solaris 2.6 to 2.7, after CiscoWorks2000 has been installed, logon screen does not appear.

For further information, including how to work around problem, see "Operating System Upgrade" section.

CSCdt31121

Cisco Voice Manager processes need to be stopped before upgrading to CD One,
4th Edition.

Workaround:

To stop Cisco Voice Manager processes:

(Windows NT/2000 clients)

At command line prompt, enter:
net stop CVM Server and Poller Service

(Solaris clients)

At command line prompt, enter:
/etc/init.d/cvm stop


CD One Installation Known Problems on HP-UX

Table 5 CD One Installation  Known Problems on HP-UX 

Bug ID
Summary
Explanation

CSCdr40548

JRE on HP-UX require OS patches

HP recommends a set of OS patches to be installed when using JRE. Since CW2000 uses JRE 1.1.8 and JRE 1.2, it is advisable to install these patches before you start the install of our product.

PHCO_20765 PHKL_20202 PHCO_19666 PHKL_20016 PHKL_18543 PHCO_20882 (PHKL_21532, PHCO_19047, PHKL_21392, and PHKL_20674 are dependencies of PHKL_18543.)

Note Go to the HP website for more information. Without PHKL_18543 and its dependencies, install of the product itself might fail.


CiscoView Known Problems

Table 6 CiscoView Known Problems 

Bug ID
Summary
Explanation

None

Log file location not supplied in other documentation.

CiscoView log file is found in cw2000-install-dir/www/classpath/cv.log. This file is also displayed in CiscoView administration page (select Device Manager > Administration > CiscoView Server Admin > Setting debug options and display log). You can open a window to display log file.

Since the log file is on the server, it contains trace and error messages for all CiscoView clients. Trace and Error entries will be appended to log file until the system administrator clears it explicitly from CiscoView Administration dialog box.

CSCdm53849

Launching a second CiscoView window from the desktop replaces the current CiscoView window.

When you click CiscoView to open multiple windows, a new window replaces the current window.

Workaround:

No solution is available at this time.

CSCdm57814

In Internet Explorer, the tab key does not work properly in User Preferences or TAC mailer option dialog box.

Pressing tab key in User Preferences dialog box or TAC mailer option changes focus but it does not move cursor to next text field.

Workaround:

Use the mouse to move the cursor to desired text field.

CSCdp84996

Attempt to start telnet session in CiscoView returns this error message:

Cannot launch telnet.Java.io.IO Exception:Too many open files.

Problem occurs on Solaris, HP-UX, and AIX clients when Telnet session opened more than 10 times.

Workaround:

Close and relaunch CiscoWorks2000.

CSCdp91288

Telnet window not launched from CiscoView on AIX clients.

Telnet does not work on an AIX client. This is because Navigator uses it own proprietary library, libc.a, which does not handle Telnet protocol.

Workaround:

Use netscape_aix4 executable in MOZILLA_HOME.

Or

Edit the following netscape script and change the LIBPATH to default system library path:

if test "${LIBPATH}xxx" = "xxx" then LIBPATH="${MOZILLA_HOME}/lib${OS_LIB}:${M OZILLA_HOME}:/usr/lib:/lib" else LIBPATH="${MOZILLA_HOME}/lib${OS_LIB}:${M OZILLA_HOME}:${LIBPATH}:/usr/lib:/lib" fi

to

if test "${LIBPATH}xxx" = "xxx" then LIBPATH="${LIBPATH}:/usr/lib:/lib:${MOZIL LA_HOME}/lib${OS_LIB}:$ {MOZILLA_HOME}" else LIBPATH="${LIBPATH}:/usr/lib:/lib:${MOZIL LA_HOME}/lib${OS_LIB}:$ {MOZILLA_HOME}" fi

CSCdr33955

Multiport monitor graphs for device running CiscoView display incorrect values.

Workaround:

Generate monitor graphs for individual ports.

CSCdr67552

Chassis window does not repaint properly after being resized.

This problem is observed in HP-UX clients running
CD One, 3rd Edition and later.

Workaround:

Close and relaunch CiscoView.

CSCdr80987

java.lang.OutOfMemory
Exception
sometimes occurs when multiple chassis views and configuration/dialog boxes are opened.

The problem occurs only on Solaris 2.6/2.7 client machines running CiscoView 5.2 in Netscape browser with Java Plug-in version 1.2.2 installed and two or three chassis views, as well as configuration and monitor dialog boxes, opened.

Java Virtual Machine (JVM) sometimes runs out of memory and returns error when two or three chassis views are opened along with configuration and monitor dialog boxes. As a result, chassis views, dialog boxes, and other GUI screens are not refreshed properly. The GUI will appear frozen.

Workaround:

Open Java Plug-in control panel and increase allocated memory of Java Virtual Machine to -mx128m.

CSCdr88151

Chassis view cannot be printed from Solaris clients running CiscoView 5.2.

With chassis view open, click Print icon and blank pages are printed.

Workaround:

Print screen captures of chassis view.

CSCdr93132

Second level configuration/ custom monitor dialog boxes sometimes display Warning: Applet Window.

The problem occurs only on Solaris 2.6/2.7 client machines running CiscoView 5.2 in Netscape browser with Java Plug-in version 1.2.2 installed and configuration or custom monitor dialog box opened.

Workaround:

No solution is available at this time.

CSCds36118

CiscoView engine does not collect device mappings from base device packages.

Workaround:

No solution is available at this time.

CSCds38925

Cannot change the category in a CiscoView monitor dialog box.

This problem occurs if you:

1. Open a monitor dialog box in CiscoView.

2. Go to Preferences and change value in Show Alias field from Alias to Descriptor.

3. Change category in monitor dialog box, and monitor dialog box does not respond.

Workaround:

Close and reopen monitor dialog box.

CSCds41560

Printing chassis view from CiscoView running in Internet Explorer 5 returns error.

This problem is observed on NT client running CiscoView in Internet Explorer 5. This problem occurs if you:

1. Open a device and bring up chassis view.

2. Select File > Print to print chassis view and error message is returned.

Workaround:

Click Print icon to print chassis view.

CSCds73008

Bean Control window is sometimes displayed after selecting "Import Device List" from CiscoWorks2000 desktop.

This problem is observed in CD One, 3rd Edition and later running in Internet Explorer.

Workaround:

Close and relaunch CiscoWorks2000.

CSCdt04355

CiscoView console buttons cannot be selected with Enter key.

This problem is observed in CD One, 3rd Edition and later.

Workaround:

Use the mouse or spacebar to select the console buttons instead of the Enter key.

CSCdt11838

When launching application, user not prompted to install Java Plug-in.

For further information, refer to CSCdt11838 in the "Browser Known Problems" section.

CSCdt22462

Delay when downloading Java applets on Win2K.

For a detailed explanation of this problem, refer to CSCdt22462 in the "General Known Problems" section.

CSCdt43794

Configure window displayed behind main chassis window in CiscoView 5.x, Japanese Edition.

This problem is observed in CiscoView 5.x, Japanese Edition, running in Navigator 4.75 on Windows 2000 Professional client. Select Configure from context (right-click) menu and Configure window is displayed behind main CiscoView chassis window.

Workaround:

Open configuration dialog by double-clicking component. The Configure window will launch automatically and be properly displayed.


Cisco View Known Problems on HP-UX

Table 7 CiscoView Known Problems on HP-UX

Bug ID
Summary
Explanation

CSCdr25387

With Netscape in HP-UX console, the button titles in CiscoView main window and labels in other dialogs are truncated and appear with ellipsis

With Navigator on a HP-UX console, the button titles in CiscoView main window and labels in other dialogs are truncated and appear with ellipsis.

Workaround:

Force Navigator to use certain small fixed fonts. This can be done by editing font.properties in $NETSCAPE_HOME/java/classes

Change Helvetica font size to 10 for all occurences of Helvetica font.

Change Helvetica font weight to 100 dpi for all the occurrences of Helvetica font

For example, replace:

helvetica.plain.0=-adobe-helvetica-medium-r-normal--*-%d-*-*-p-*-iso8859-1

with

helvetica.plain.0=-adobe-helvetica-medium-r-normal--10-100-*-*-p-*-iso8859-1

CSCdt79469

Button labels not completely displayed in CiscoView running in Navigator on HP-UX client.

With CiscoView running in Navigator on HP-UX client, button labels in the Main window and other dialog boxes are truncated and appear with ellipsis.

Workaround:

Change display resolution on your monitor to a higher value

Or

Select a different category and click OK to apply any changes made in the previous category.


Device Support Utility Known Problems

Table 8 Device Support Utility Known Problems 

Bug ID
Summary
Explanation

CSCdm52416

Can uninstall a package when the device is open.

When you open a device, Device Support Utility (DSU) is launched, and uninstall is selected, uninstallation continues without displaying necessary error message.

Workaround:

No solution is available at this time.

CSCds28899

Cannot uninstall device packages with DSU running in silent mode.

Device package installation aborts when run from command line with DSU running in silent mode.

Workaround:

No solution is available at this time.


Catalyst Devices Known Problems


Note If you have problems using the online help, download the latest device packages from Cisco.com.


Table 9 Catalyst Devices Known Problems (2900, 4000, 5000, 5500, 6000, 8000) 

Bug ID
Summary
Explanation

CSCdr34879

All ports on lennon (mod 7) are shown as green on a Catalyst 6000 device running CiscoView.

Only ports that are configured and connected should be shown as green.

This problem is caused by lack of mapping between MIB elements in agent and colors of ports on the board.

Workaround:

No solution is available at this time.

CSCdr36040

Cannot enable ports with Cosmos device package installed.

If you select Port > Enable, this error message appears:

CiscoView Error of Set failed!
Status=SnmpRequest Timeout
.

This problem is caused by incorrect value returned by portIfIndex, which causes SNMP Set Request for ifAdminStatus to timeout.

Workaround:

No solution is available at this time.

CSCds72290

Running CiscoView 5.x on device with Cisco IOS 12.1(2)E installed returns error.

Problem observed on Catalyst 2612 and Catalyst 6509 devices with Cisco IOS 12.1(2)E installed running CiscoView 5.x.

This error appears:
Failed to refresh chassis. Refer to error log for details.

Workaround:

No solution is available at this time.

CSCds78228

Contents of Catalyst 5000 device package readme file is different from what is listed in Package Details window.

This is seen, if you:

1. Select Device Manager > View Installed Packages from CiscoWorks2000 desktop,

2. Click Details icon for Catalyst 5000 device package to bring up Package Details window.

3. Although text in readme file link states Readme file for Cat5000 (1.2), click link and Catalyst 5000 (1.3) Installation instructions are displayed instead.

Workaround:

Ignore discrepancy.


Router and Hub Known Problems

Table 10 Router and Hub Known Problems 

Bug ID
Summary
Explanation

CSCdp35199

When you attempt to access help from a 700 series device, a URL not found error message appears.

When you reload help, and an empty page is displayed.

Workaround:

Open a new browser to recover normal state.

CSCdp49010

With CiscoView running on a 1516 device, the configuration dialog box disappears.

If you move the configuration dialog box to the left side of the screen far enough to conceal the majority of the box, and then select IP Information from the Category menu, the box disappears. Double-clicking on the chassis view does not relaunch it.

Workaround:

No solution is available at this time.

CSCdp94674

Starting StackMaker from CiscoView on a 1900 series device results in error message.

Problem observed in 1900 series device with Layer-2 topology. With CiscoView running, start StackMaker. The following error message appears:
Unable to display this category group. java.lang.NULLpointer.exception.

Workaround:

Click OK to clear error message, and StackMaster starts.

CSCdr39315

Cisco2524 device running Cisco IOS 12.05T and CiscoView 5.x does not display SM25-T1 card. A blank slot is shown instead.

Workaround:

No solution is available at this time.

CSCds55193

Incorrect formula used to calculate interface error percentage is listed in CiscoView online help.

CiscoView online help lists this as the formula used to calculate interface error percentage: [
ifInErrors /(ifInUcastPkts + IfInNUcastPkts)] *100.

The correct formula is:
[ifInError /(ifInUcastPkts + IfInNUcastPkts + ifInError+ifInUnknownProtos)] * 100.

CSCds86109

CiscoView 5.x, running on Cisco 1600 and 4000 series devices, displays a high number of collisions.

Workaround:

No solution is available at this time.

CSCdt02050

Flash (PCMCIA) card is not displayed on Cisco 7000 series device running CiscoView.

Workaround:

No solution is available at this time.

CSCdt07445

Unable to configure ports on Cisco7000 series device with Cisco 7200 device package installed.

This problem occurs if you:

1. Launch CiscoView and open device.

2. With a port selected, open Configure dialog box.

3. Make changes to port settings and internal error appears.

Workaround:

No solution is available at this time.

CSCdt26857

Cannot retrieve ATM statistics for ATM ports on devices with Cisco 7000 device package installed.

At present, only Interface statistics and several categories of SONET statistics can be retrieved.

Workaround:

No solution is available at this time.


General Device Package Known Problems

Table 11 General Device Package Known Problems

Bug ID
Summary
Explanation

CSCdr94291

In CiscoView, NEMI configuration dialog box for Metro 1500 device displays N/A as Subnet mask value.

NEMI configuration dialog box should display 255.255.255.0 as Subnet mask value.

Workaround:

No solution is available at this time.

CSCdr96333

HP OpenView topology map displays generic icon for Metro 1500 device.

This problem occurs if you:

1. Install HP OpenView and then CiscoView 5.1.

2. Run NMIM integration.

3. Using Device Support Utility, install Metro 1500 device package version 1.2.

4. Launch HP OpenView.

5. Select Edit > Add Object > Cisco FastHub > Metro 1500.

6. Click on Metro 1500 icon and drag it into topology map.

Workaround:

No solution is available at this time.


Package Support Updater (PSU) Known Problems

Table 12 Package Support Updater (PSU) Known Problems 

Bug ID
Summary
Explanation

CSCdt04070

No error message appears when network connection is lost during the download of device packages from Cisco.com.

Workaround:

No solution is available at this time.

CSCdt24701

No error message appears after an unsuccessful attempt to uninstall nmidb packages.

After an unsuccessful attempt to uninstall nmidb packages, an error message does not appear stating that process failed. Also, in View History window, completed successfully appears under status tab when failed should appear instead.

Workaround:

No solution is available at this time.

CSCdt35177

PSU appears without a banner and left frame in browser.

Workaround:

Make sure your browser's caching policy is not set to Never. Set caching policy to Every visit to the page in Internet Explorer browsers and Every time in Netscape browsers.

CSCdt36869

Installing same device package from Cisco.com using multiple PSU sessions results in errors.

Errors are returned when device packages are downloaded and installed from Cisco.com using PSU web interface and standalone PSU (psu, xpsu) at the same time.

Workaround:

Do not use PSU web interface and standalone PSU simultaneously to download device packages from CCO.

CSCdt73771

Error message appears when multiple PSU web clients install/uninstall device packages at the same time.

When multiple PSU web clients install/uninstall device packages at the same time, following error message appears:

Could not connect to JRun Connector Proxy. Please contact the system administrator for this web site.

Workaround:

Click on the Click here to view list of all CiscoWorks2000 client sessions link to send broadcast message which informs all active clients of a server restart. This link is accessible from Confirmation package selection page for installation/uninstallation.


Integration Utility Known Problems


Note The file NMIDBOptions.properties contains Cisco.com passwords, in an encoded form, and is accessible only to root users. Root access to the host needs to be restricted if Cisco.com password security is a concern.


Table 13 Integration Utility Known Problems 

Bug ID
Summary
Explanation

None

The integration currently done with Netview 5.1 to integrate MIBs, icons, and application registration will not be visible to web clients of Netview, and is not supported in this version of Integration Utility.

If you access Netview through a web browser, you might not see integrated information.

Workaround:

No solution is available at this time.

None

Changing the browser used by one application changes the browser used by all applications registered through the Integration Utility.

In Application Registration screen, when you change browser used by an application, for example, CiscoView, and you click tab for another application, like Essentials, you will notice that its browser has also changed.

Workaround:

No solution is available at this time.

CSCdm61980

Cannot launch CiscoView by double-clicking device icons in NMS after integration.

Some NMS adapters do not support double-clicking device icons from topology map, even if CiscoView is set as default application (using Change Integration Options).

Workaround:

No solution is available at this time.

CSCdm91445

If you run the utility to change only application registration information (such as browser, server, and port number), a full integration occurs.

If you change only application registration information, only application integration should occur. Instead, full integration occurs.

Workaround:

No solution is available at this time.

CSCdp89456

Null pointer exceptions occur when you click the Browse button.

If you select Change Integration Options and click Browse in any window, error messages might appear. You can ignore them, since they do not affect user operations.

CSCdp90186

After integration, if CiscoView 5.x is launched twice from the HP OpenView Network Node Manager, one of the following error messages appear:

1. Issuer certificate is invalid.

2. java.lang.security exception: system classes were not signed.

This problem happens occasionally when a Navigator browser is opened by anyone other than the installer.

Workaround:

Log in as root and reinstall. Also verify that $HOME system variable is set properly.

CSCdp90728

On Unix platforms, when the Update Cisco Device Support task is run from the Netview, generated messages are not displayed.

Workaround:

Go to window from which Netview was started to view generated messages.

CSCdr38931

Error messages may be displayed when running Change Integration Options on a system with insufficient disk space.

After integration, when you run Change Integration Options, your system extracts NMIDB. If there is not enough disk space to extract NMIDB, extraction fails.

Workaround:

Clear up some disk space and relaunch Change Integration Options. For Windows NT, if FAT file system is in place, make sure you have at least
190 MB of free disk space. For other file and operating systems, make sure you have at least
25 MB of free disk space.

CSCdr80401

Uninstallation of
CiscoView 4.2 removes all Cisco icons from HP OpenView.

Cisco icons added by CD One 3rd Edition installation removed from HP OpenView after you:

1. Install HP OpenView 6.0.

2. Install CiscoView 4.2 and integrate with HP OpenView.

3. Install CD One 3rd Edition and integrate with HP OpenView.

4. Uninstall CiscoView 4.2.

Workaround:

Run nmic.sh and run integration with HP OpenView, again.

CSCds19672

Only one subset of Cisco traps is loaded into the NMS by the Integration Utility.

Integration Utility version 1.3 only loads one subset of Cisco traps into NMS using the trapd.41x file. This file does not include many Cisco traps that exist in newer Cisco MIBs. HP OpenView and Tivoli NetView integrations are impacted.

Workaround:

Manually add/define traps using Event configuration GUI provided by NMSs.

CSCds22851

Changes in CiscoWorks2000 web server port number after upgrade to CD One 3rd Edition requires reintegration with NMSs.

After an upgrade to CD One 3rd Edition, the default web server port is sometimes changed to 1741. This requires you to change application registration information using Integration utility (in Application Registration screen).

Workaround:

To reintegrate NMSs with new port number:

1. Start Change Integration Options GUI as root/Administrator.

2. Go to Application Registration screen.

3. Change port numbers for all applications that point to upgraded CiscoWorks2000 server.

4. Proceed with integration by clicking Integrate in Choose Adapter screen.

CSCdt52492

Applications do not always launch from NMS menu if a browser is not already running.

If browser path defined in Change Integration Options GUI is a shell or binary wrapper to actual Netscape executable and wrapper script does not return proper error codes, you will not be able to start browser from NMS menu.

Workaround:

Do not use Netscape wrapper scripts. Instead, configure original Netscape binaries within the Integration Utility. Another option is to modify wrapper scripts so that error codes are properly returned by browser back to the shell.


Integration Utility Known Problems on AIX

Table 14 Integration Utility Known  Problems on AIX 

Bug ID
Summary
Explanation

None

Application does not load V2 traps.

Netview 5.1 does not support loading V2 traps.

None

If you install the Integration utility 1.1 on a machine running CiscoView 4.x with your NMS, the utility does not integrate MIBs into the NMS.

Workaround:

If you uninstall CiscoView 4.x, however, the Integration utility will integrate MIBs into the NMS. To avoid compilation errors as MIBs are integrated, unload the old MIBs before running the utility.

CSCdp37614

Application does not load MIBs that have TEXTUAL-CONVENTIONS

Netview 5.1 has limitations in loading TEXTUAL-CONVENTIONS.


ANI Server Known Problems

Table 15 ANI Server Known Problems 

Bug ID
Summary
Explanation

CSCdj60832

All configuration changes are lost when device accidently shut down, if device running Cisco IOS software image.

Configuration changes are only applied to device's running configuration. If the device is accidently shut down, all changes are lost. Tnis is because the changes are not stored in the start-up configuration.

Workaround:

Open Telnet session to device, and save configuration changes by entering write mem from command line interface.

CSCdm48015

An ATM trunk port is shown as belonging to a VLAN, even if there is no corresponding LANE client associated with that VLAN.

In VLAN-to-port association, all ATM ports on switches (except ATM switches) belonging to VLAN appears.

Workaround:

Ignore ATM ports in VLAN-to-port association.

CSCdm58624

LANE trunks are not considered when determining a VTP disconnected domain discrepancy.

If VTP domain spans across ATM cloud and default ATM-VLAN is configured to carry VTP advertisements across cloud, domain is still displayed as disconnected domain discrepancy due to lack of support.

Workaround:

Ignore discrepancy.

CSCdp40303

Configuration changes are not saved to the NVRAM of a device.

Configuration changes are made only while the device is running. If the device is accidentally shut down, all changes are lost.

Workaround:

Open Telnet session to device and save configuration changes by entering write mem at the command line.

CSCdp41757

An empty virtual circuit list is returned by two LS1010 devices, even when a virtual circuit exists between those devices.

Running SNMP query on ciscoAtmSvcAddrTable returns empty table for devices. This problem is observed in LS1010 devices running Cisco IOS Release 12.0.

Workaround:

No solution is available at this time.

CSCdp76410

Campus client cannot connect to server using proxies.

CD One does not support proxies.

CSCdr68393

Device Synchronization from or to Essentials overwrites newer entries in database

Configure Device Synchronization to send the correct credentials to replace the existing ones. Device Synchronization is designed to overwrite the existing credentials with the correct ones no matter which is newer. The system should use the correct credentials even if they are older.

Workaround:

Ensure the credentials provided to the system are correct. You can use the Essentials Check Device Attributes to validate device credentials.

CSCdr74161

ANI discovery fails to write DBObject (non-ASCII characters in string)

SQL Anywhere supports only ASCII characters. Hence, special UNICODE characters above the ASCII range cannot be used. This error message appears in the ANI log file:

"Database update failed due to invalid character(s). Please review the previous error message for details. If the invalid character is part of information retrieved from a device, please correct that device to contain valid characters. For further information please contact technical support and provide bug-id CSCdr74161 as reference."

Workaround:

1. Scan the error message for any non-ASCII characters.

2. Identify the device and attribute which has the non-ASCII characters.

3. Modify the device information to contain valid characters.

4. Restart ANI.

CSCdr84799

Applications do not function across Network Address Translator (NAT).

Workaround:

No solution is available at this time.

CSCdt20329

ATM switches, for which Remote Monitoring (RMON) is enabled, is not highlighted when Show Enabled Devices selected.

This problem occurs if you:

1. Select Topography Services

2. Highlight an ATM fabric under Managed Domains/ATM Domains

3. Select Display View

4. Select devices, and click Tools->RMON Data Collection->Show Enabled Devices

Workaround:

No solution is available at this time.

CSCdt56346

Discovery filter does not permit discovery of single device.

Specifying single device for example, in ANI Discovery Filter section does not work. The filter string will be accepted, but ANI will not discover device.

Workaround:

Specify a wildcard: To specify a wildcard, replace last part of IP address with the character *. For example, if IP address is 209.165.200.224, the wildcard is 209.165.200.*.


ANI Server Known Problems on HP-UX

Table 16 ANI Server Known Problems on HP-UX 

Bug ID
Summary
Explanation

CSCdt92222

Internal Server Error occurs when CiscoWorks2000 is run from a browser.

This problem occurs when you run CiscoWorks2000 from a browser. The swap usage increases steadily, eventually becomes full, and this error message appears:

Internal Server Error

If the swap increase is not monitored, the swap usage reaches 100 per cent, and you may have to reboot the machine.

This problem may occur after running CW2000 Server continuously for a period of more than two weeks.

Workaround:

1. Monitor swapinfo using swapinfo -tm.

2. If the swap usage is nearing 90 percent, stop the ANIServer process by entering:

#cd /opt/CSCOpx/bin
#./pdterm ANIServer

3. Restart the ANIServer process by entering:

#./pdexec ANIServer


Device/Agent Known Problems Impacting ANI Server

Table 17 Device/Agent Known Problems Impacting ANI Server 

Bug ID
Summary
Explanation

None.

OamPing hardware requirements for a LS1010 device.

In LS1010 device, support for OAM on VP tunnel exists for:

FeatureCard1—ASP h/w version 3.3 or later.

FC3/FC-PFQ—ASP h/w version 4.0 or later.

Workaround:

To determine controller type, enter sh hardware at the command line and refer to cntrl_type field.

CSCdm90878

RSM link is shown as ISL trunk, but is not included in trunk report.

Caused by absence of VLAN-related MIB on router.

Workaround:

No solution is available at this time.

CSCdm91634

In Campus Manager device report, number of ports in a device's ATM module is incorrectly displayed as zero.

This problem is observed in Catalyst 5000 device running Catalyst OS version 4.3(1a), is caused by missing ifEntry for device ATM module. ANI Server depends on ifEntry to determine number of ports in a particular module.

Workaround:

No solution is available at this time.

CSCdp00593

SNMP report displays
wrong HwVersion and HwVersionMinor for LS1010 device.

Workaround:

Enter show hardware at the command line of the LS1010 device.

CSCdp51864

Trunk attributes are not shown for an RSM-switch trunk.

Trunk attributes are not reported for router links due to lack of MIB support.

Workaround:

Use the command line to access trunk attributes for router ports.

CSCdp56060/CSCdp56066

Virtual circuit trace does not work on a LS1010 device running Cisco IOS 12.0.

Cross-connect identifier returns-1 for virtual circuits 0/5 and 0/16, which prevents display of virtual circuit trace via SNMP.

LS1010 devices running Cisco IOS 11.2 return correct values. Also, cross-connect information is properly displayed when accessed via the command line.

Workaround:

No solution is available at this time.

CSCds04828

Port attributes for Secondary SPE failed.

Launch port attributes dialog box by selecting a node on Layer 2 topology map and selecting Reports > Port Attributes. Port attributes dialog box for secondary SBC does not display any ports as expected. The ANI log file displays error, stating it failed to fetch ifTable from secondary SBC.

Workaround:

No solution is available at this time.

CSCds04846

Secondary SPE is not returning ccmStatus information.

Secondary SPE is not returning ccmStatus information because no ccm service is running. This error appears in the ANI log file and can be ignored:

2000/08/11 11:13:34 EvalTask-background-28 ani ERROR ICS7750CoreSMFGetDeviceId:
Could not get ccmStatus com.cisco.nm.lib.snmp.lib.SnmpException: SnmpResponseGenErr on <secondary SBC IP Address> while performing SnmpGet at
index = 0.

Workaround:

No solution is available at this time.

Note This error should be logged only for secondary SBC, not for primary.

CSCds27676

With missing entries in the anisnmp.conf file, performing a bulk synchronization from Campus Manager to Essentials results in an error.

java.lang.NullPointerException is returned when performing a bulk synchronization from Campus Manager to Essentials and devices in Campus Manager topology map do not have corresponding entries in anisnmp.conf (Campus Manager's SNMP communities file).

Workaround:

Add this line to the end of anisnmp.conf: *.*.*.*:public::::::private.

If you are using default community strings other than public and private, replace them in the line above. The strings do not have to be correct; they simply need to be non-null.

CSCds37157

FastHub devices may appear incorrectly in Layer-2 topology maps.

In a network with FastHub devices, some of these devices are not being discovered and are consequently missing from the network's topology map. Also, FastHub devices belonging to different switch clouds are displayed as if they are connected by Layer-2 connections.

Workaround:

No solution is available at this time.

CSCdt30017

Command Line Interface (CLI) does not update Remote Monitoring (RMON).

If RMON is disabled using GUI, CLI will show it as enabled. In all other ways, the CLI behaves the way it should, if RMON is disabled.

Workaround:

No solution is available at this time.


Browser Known Problems

Table 18 Browser Known Problems 

Bug ID
Summary
Explanation

None

Table of contents or index does not appear in online help.

Workaround:

If table of contents or index does not appear in online help, hold down the Shift key and click Reload.

CSCdr80627

Cannot launch CiscoView on a Windows 2000 client in a Navigator 4.73 browser with the Proxy Server setting enabled.

CiscoView cannot be launched from server running in same subnet as Windows 2000 client in Navigator 4.73 browser with Proxy Server setting enabled.

Workaround:

1. Disable Proxy Server setting while attempting to access a CiscoView server.

2. Close browser and open a new browser.

Another option is to use Internet Explorer 5.

CSCds89236

With "No" selected in Swing-based confirmation dialog boxes, hit Enter key and "Yes" is applied instead.

This problem is observed in Solaris clients running CD One 3rd Edition and later in Netscape.

Workaround:

Use mouse or spacebar to activate selection instead of Enter key.

CSCdt05102

Netscape crashes if you resize browser window while applet is loading.

This problem exists within Netscape.

Workaround:

No solution is available at this time.

CSCdt06518

Unable to launch a second instance of CiscoView in Internet Explorer while the first instance is waiting for user input.

This problem is observed in CD One 3rd Edition and later versions, running on Internet Explorer.

This problem occurs when you:

1. Launch CiscoView.

2. Open a device.

3. CiscoView will prompt for community strings.

4. Without entering community strings, launch a second instance of CiscoView, and it freezes.

Workaround:

Enter community strings before launching second instance of CiscoView.

CSCdt06530

Netscape does not recognize JRE Plug-in as installed.

This problem occurs when you:

1. Use Netscape to launch application that requires Java 1.3 Plug-in on machine that does not have plug-in installed.

2. Window appears instructing you to install plug-in.

3. Install plug-in.

4. Relaunch application.

5. Same window appears, instructing you to install plug-in.

Workaround:

Restart browser. For more information on Java 1.3 Plug-in, see the "Support Information" section.

CSCdt11838

User is not prompted to install the Java plug-in when launching an application that utilizes the plug-in for the first time.

If RealJukebox Plug-in for Navigator is already installed on a Windows client prior to first launch of application utilizing Java Plug-in, you are not prompted to install Java Plug-in. A blank screen is displayed.

Workaround:

Uninstall RealJukebox Plug-in.

Or

Rename nprjplug.dll file in Navigator Plug-ins directory with new extension—for example, nprjplug.dll.bak.

Note After Java Plug-in is installed, you can reactivate RealJukebox Plug-in by changing renamed file back to nprjplug.dll.


Browser Known Problems on HP-UX

Table 19 Browser Known Problems on HP-UX 

Bug ID
Summary
Explanation

None

Parameter must be set using Netscape 4.61.

Workaround:

MOZILLA_HOME must be set to the Navigator installation directory.

CSCdr25387

Netscape on HPUX console does not display applets completely

The problem occurs when Netscape browser running on HP-UX desktop uses "lucida-medium" as its dialog fonts.

Workaround:

Use fonts other than "lucida-medium" for dialog items (java gui components).

Do this by replacing lines with font definitions "lucida-medium"with any of these lines in the NETSCAPE_HOME/java/classes/font.properties file:

-sony-fixed-medium-r-normal--*-*-*-*-c-*-iso 8859-1

Or

-dt-application-medium-i-normal-serif-*-*-*- *-p-*-iso8859-1

Or

-hp-hp user-medium-r-normal-serif-*-*-*-*-m-*-iso88 59-1

CSCdr29960

Cannot launch applets if graphics display is set incorrectly

On an HP-UX console, if the graphics display is not configured with appropriate values, these problems occur:

The initial CW2000 screen appears with panels in Purple.

Certain applications like NetConfig, User Tracking cannot be launched.

Workaround:

Set the graphics display to these values:

Screen dimensions: 1600x1200 pixels (350x262 millimeters)

Screen resolution: 116x116 dpi


Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

http://www.cisco.com

http://www-china.cisco.com

http://www-europe.cisco.com

Ordering Documentation

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered CCO users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

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 your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com 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.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, 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 Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.


hometocprevnextglossaryfeedbacksearchhelp

Posted: Mon Oct 11 03:49:33 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.