|
|
This document discusses the CiscoView 3.2 release and includes the following information:
The CiscoView 3.2(1) release now includes several new Cisco devices on a separate CD called the Network Management Support CD. These devices are also available from the Cisco Connection Online (CCO) service. To mount and install devices from the support CD, refer to the special CD booklet included in your package. Be sure to read the README files on the Network Management Support CD or turn to the section "CiscoView Incremental Device Package Information."
The CiscoView 3.2 release now includes support for HP-UX 10.01 and 10.10 and Solaris 2.5 and 2.51.
CiscoView 3.2 consists of the CiscoView 3.1.1 product and device support, plus the additional device support now found on the Network Management Support CD. If you already have release 3.1 installed, you do not need to reinstall release 3.2 (1). Only install the devices you need off the Network Management Support CD.
Table 1 lists the new Cisco devices included on the Network Management Support CD. These devices are supported on all platforms unless otherwise noted.
Table 1 : New Device Support in CiscoView Release 3.2
This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing. New devices and further specifics on IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:
CiscoView supports Cisco IOS Software Releases 10.0 through 11.1 with the exceptions of access servers, which require a minimum of Cisco IOS Software Release 10.2.
The documentation for CiscoView includes this release note, a CD-ROM booklet, incremental installation instructions, and online help. The primary documentation for CiscoView is the online help. If you have documentation feedback, please email comments to: The documents shipped with this release include:
Customer documentation can also be found on the Cisco Enterprise Customer Documentation CD or on CCO.
CiscoView and Device Information
CiscoView is a GUI-based (graphical user interface) device management software application that provides dynamic status, statistics, and comprehensive configuration information for Cisco Systems' switched and internetworking products. CiscoView lets you display a graphical representation of each network device, view configuration and performance information, configure and control Cisco devices, and perform minor troubleshooting capabilities.
Table 2 contains the list of supported CiscoView devices by product type.
Table 2 : Supported CiscoView Devices
Other CiscoView applications supported include:
Incremental Installation Information
There are several ways to add (or incrementally install) new devices to CiscoView 3.2. For our direct customers, refer to the section "Accessing CCO for Additional Cisco Device Support." For our partner initiated customers, refer to the section "Partner Initiated Customer Accounts."
Accessing CCO for Additional Cisco Device Support
Customers can add new devices to CiscoView from CCO or from the Network Management For more information, refer to the Downloading New Cisco Devices and Applications quick reference card or to CCO. The CCO URL for the quick reference card is:
It includes information on logging into CCO and how to get devices added to CiscoView.
For access to the device package files from CCO the URL is:
Be sure to read the device README files before downloading any device.
Partner Initiated Customer Accounts
To get more information about the Partner Initiated Customer Accounts (PICA) program before accessing CCO for device package files, use the following URL:
http://www.cisco.com/acs/info/pica.html
You can also refer to "Downloading New Cisco Devices and Applications" for CiscoView for information on adding device support. It is orderable, or available on CCO or the Enterprise Customer Documentation CD.
If you cannot open a device in CiscoView 3.1(1), a message appears indicating that the device is unmanageable. This message indicates one of the following conditions:
This section lists notes and restrictions that apply to the CiscoView 3.1(1) release.
For caveats on the incremental Cisco devices in CiscoView Release 3.2, refer to a specific Cisco device in the "CiscoView Incremental Device Package Information," on page 16.
For caveats on the CiscoView Release 3.2 for HP-UX 10.x, refer to the section "Installation Notes and Caveats."
Installation Notes and Caveats
The installation caveats are described below.
Device Installation Patch/Software Module Update (SMU)
If you plan to install incremental device packages at this time or in the future, we recommend you install the CiscoView patch prior to performing the CiscoView incremental device installations.
If this patch is not installed, you might encounter the following error messages:
Install the CiscoView parse.unix patch before you perform CiscoView incremental installation using cvinstall. Otherwise, the above problem might be observed. To install the patch, refer to "Installing the CiscoView Patch" for instructions. To install the patch/SMU from CCO, refer to the CiscoView Upgrade Planner at the following URL:
[CSCdi68751]
Installing the CiscoView Patch If you have the Network Management Support CD, there is a /patch directory that contains the following files:
If you do not have the Network Management Support CD, you can access CCO for the CiscoView SMU.
To install the CiscoView patch from the Network Management Support CD, do the following:
Access Device Package Installation Issues
To install the following device packages off the Network Management Support CD (760, 2500, or 1000 series routers), you must have the 7000 or 4xxx device packages previously installed on your system. [CSCdi69040]
For SUNOS 4.1.x installs, you must define /usr/lib before /lib in LD_LIBRARY_PATH. If LD_LIBARY_PATH has /lib:/usr/lib then cvinstall fails when trying to run cvtest, and displays the following error message. [CSCdi58364]
The xnmloadmib program in HP OpenView might have problems reloading MIB files into the database. The definition of CiscoNetworkProtocol in CISCO-TC-V1SMI.my and OwnerString in IF-MIB-V1SMI.my displays an error message similar to the following when you run cvinstall -f:
The work around is to run xnmloadmib manually, select and unload all Cisco-specific MIB files from the list box in xnmloadmib GUI, then run the command cvinstall -f to load all Cisco-specific MIB files. [CSCdi56399]
The CiscoView 3.1(1) installation attempts to put the X resource file for HyperHelp in the /usr/lib/X11/app-defaults directory. Because different systems have different types of X Windows installations, the HyperHelp application does not always locate this resource file. When the resource file is not read, the HyperHelp viewer text might be unreadable on your screen. Do the following to make sure that this resource file is read:
Choose Options>Set Hyperhelp Defaults from the CiscoView menu to set resources.
If you get the following error message,
this might mean that the missing program (eg xrdb) is not in your path. Check your path environment variable. [CSCdi57661]
Solaris 2.5 and HP OpenView 4.1 Patch Requirement
The CiscoView installation on Solaris may fail if you do not install several Hewlett-Packard patches.
There is now a patch for Software Distributor and I4LS to allow customers to run HP OpenView Network Node Manager (NNM) 4.1 on Solaris 2.5.
The patch for Software Distributor is PSOV_1090. This patch is required to install NNM 4.1 on Solaris 2.5 and must be installed prior to installing NNM 4.1. Be sure to follow the modified installation instructions described in the PSOV_1090.text file.
The patch for the I4LS licensing software is PSOV_1138. This patch is required to run a license server on Solaris 2.5. If your license server is on a different machine, this patch is not necessary.
Both patches consist of a tar file and a text file describing the patch.
To obtain the patch files, do the following:
Make sure you have installed Patch level 4 for SNM 2.2.2 under SunOS so that snm_discover discovers your devices correctly. If the Grapher does not send more than one request, verify that your snm_cmd file is 36864 bytes in size.
Multiple selections show all categories, whether they apply to a specific group of selections or not. If the category doesn't apply, the config table will show "N/A" in the cells. [CSCdi48854]
Upgrading CiscoView 3.1(1) or 3.2
If you are upgrading from an existing CiscoView release to CiscoView 3.1(1) or 3.2 (or upgrading CiscoWorks), perform an upgrade or a reinstallation. Deinstallation of the CiscoView product is not recommended. Deinstallation of the existing CiscoView release requires manual changes to the Network Management platform (min) or CiscoWorks breaks. If you do deinstall, refer to the "Deinstallation Notes and Caveats" for a workaround.
Deinstallation Notes and Caveats
The deinstallation caveats are described below.
Upgrading CiscoView 3.1(1) or 3.2
If you are upgrading from an existing CiscoView release to CiscoView 3.1(1) or 3.2 (or upgrading CiscoWorks), perform an upgrade or a reinstallation. Deinstallation of the CiscoView product is not recommended. Deinstallation of the existing CiscoView release requires manual changes to the Network Management platform (min) or CiscoWorks breaks.
This problem has been fixed on Solaris 2.4 and 2.5 only.
If you remove CiscoView from a Sun/HP-UX platform where CiscoWorks exists, do the following:
Cleaning Up CiscoView Before Upgrading To do a proper clean up of CiscoView, create a script that works on your network management system.
The following procedure is for the HP-UX 10.x platform. For other platforms, replace the directory paths with your platform-specific paths.
The general notes and caveats follow. They are divided into six sections:
Notes and Caveats for Enterprise Network Management Products
General notes and caveats for Enterprise Network Management products are described below.
Dragging Ports
For this release, use the middle mouse button to drag on UNIX. Only certain devices (such as the CAT1200, CAT1600, CAT5000, CPW16) have defined their ports for dragging across devices.
HP OpenView Discovery Issue
When a switch is configured as two or more domains, HP OpenView discovery might not work properly and might discover only one of the domains. If this occurs, use CiscoView to manage the domain directly rather than launching the switch from the map.
HP OpenView IP Addresses and Wildcards
CiscoView 3.1 or 3.2 does not support HP OpenView community strings if there are any wildcards in the IP address (for example, 192.20.*.*). Only a direct match of an IP address will work. If you wish to set the CiscoView default community strings to something other than Loading Correct SNMP Daemon
You might be unable to view a Fiber Distributed Data Interface (FDDI) SBus adapter on a device in CiscoView 3.1(1). Make sure you have the correct SNMP daemon (snmpd) loaded. The default snmpd for SunOS does not allow you to view this adapter. To correct this problem, stop the existing snmpd process and reload the snmp.cfddi daemon, which is generally located in the /etc directory. If you cannot locate the snmp.cfddi daemon, check the rc.local file to determine where the it might be located.
Motif Window Manager (mwm1.x)
You cannot reduce any window size if you are using mwm 1.x. Choose the Property dialog option to make CiscoView 3.1(1) circumvent this problem.
Open Look
Open Look caveats include:
Popup Menu Titles
Popup menu titles are raised; users might mistake them for menu items. [CSCdi53475]
Running CiscoView 3.1(1) or 3.2 with Little Swap Space
If the server or display workstation is running out of swap space, you see a message such as "X error: Couldn't allocate color cell," and CiscoView core dumps. If you are running other applications, you might want to check your swap space occasionally.
To check swap space on a SunOS 4.1.x workstation, enter the following:
To check swap space on a Sun Solaris 2.x workstation, enter the following:
To check swap space on an HP-UX 9.0x and 10.x system, enter the following:
If your system is running out of swap space (for example, only 200 KB of swap space remains), quit some of the other applications you are running or increase your swap space, if possible. [CSCdi37063]
SunNet Manager Grapher
The SNM grapher can graph only three or four variables at a time. Selecting more variables generates a "too long" error message. This affects Graphing from Monitor dialog boxes. Do not ask the SNM grapher to graph more than four variables at a time. If you need to see more, start two SNM graphs, select the SNM graph control box, and combine both graphs into one.[CSCdi51362]
Switching Between Colormaps
Programs such as Netscape take up all the colors on workstations with 8-bit graphics cards (typical for SUN). CiscoView 3.1(1) dithers colors to the NetScape colormap. SunNet Manager creates a private colormap, and the screen swaps colormaps as you switch between applications.
Tables Show All Categories
Multiple selections show all categories, whether they apply to a specific group of selections or not. If the category doesn't apply, the config table will show "N/A" in the cells. CSCdi48854]
Notes and Caveats for Workgroup Products
Following are general notes and caveats for the Cisco Workgroup family of products.
Catalyst 2800, Catalyst 2100, EtherSwitch 1200, and EtherSwitch 1400
Following are general notes and caveats for the above Workgroup products:
Community String Mismatching
When the user enters values for the "read-only," "write-only," and "read-writeId" with the Command Line Interface (CLI) commands, these values must match. A mismatch results in "noSuchName" or "timeout" errors. To avoid these error conditions, use identical community strings in CiscoView and corresponding agents.
Exiting CiscoView 3.1(1) Causes Applications to Close
If you are using the CiscoPro 16/Catalyst 3000 and close the CiscoView window, any application window that was launched from it automatically closes. Close the EtherChannel and Domain Configuration application windows before you open another CiscoView application or exit from the CiscoView application. There is no limit on the number of CiscoView applications that you can run.
False Error Reported After Setting Parameters
On the CiscoPro 16 and Catalyst 3000, when you try to set parameters for the EtherChannel/Domain application under moderate to high traffic conditions, the application incorrectly displays an error window indicating that the operation was not successful. However, the command was successful, and you should dismiss the error dialog.
LightStream 100 The LightStream 100 VCTool supports virtual circuit management of the LS100 and can be run from the LS100 CiscoView 3.1(1) application.
The LightStream 100 VCTool is currently supported on SunOS 4.1.X and HPUX 9.X.
Next Button
On the port config dialog of a Catalyst 5000, you might see some category names repeated twice. This is caused by rapidly press the Next button. Close and reopen the window to remove the duplicate names. [CSCdi57910]
ProStack Power Supply Link Problem
The rear view of the Prostack matrix power supply does not indicate whether the connector link is up or down (for example, the connector does not display green if there is a link).
Switch Firmware The following firmware versions must be used in the switches:
Switches
If you configure EtherChannel or Virtual Domains in Kalpana switch models EPS2015RS, EPS2115RSM, and Pro16 while running version 9.0 firmware with STP active, the map icons become red, and you receive the following error message:
After restarting the system, deactivate STP before you attempt to reconfigure. This problem is fixed in version 9.1 of the device firmware. [CSCdi41317]
VlanDirector Compatibility
CiscoView 3.1 or 3.2 requires VlanDirector version 1.1. Both are available in CWSI.
Notes and Caveats for Access Products
Following are general notes and caveats for the Cisco Access family of products.
Card Support for Cisco 4000, 4500, and 4700 Series
The following network processor modules (npm) are supported:
CiscoView Release 3.1 supports cards nmp-400-fddi-sas through nmp-4000-4t above. The incremental devices for 4000, 4500, and 4700 support cards nmp-4000-4b through nmp-4000-6e above. For the latest information on supported CiscoView devices, check CCO.
FDDI Port Status Functionality
The Cisco 4000 series devices with DAS FDDI ports show status on only the lower one of the two connectors. The status color is determined from the port's administrative status (ifAdminStatus) and operational status (ifOperStatus) values. [CSCdi28566]
Read-Only MIB Variables
The administrative status (ifAdminStatus) value "testing" and the ring speed (dot5RingSpeed) variable are implemented as "read-only" in all Cisco IOS versions and cannot be set through popup menus on CiscoView Configure Port screens. However, Configure Port tables (of multiple ports) offer popup menus that permit attempts to set these variables. Such attempts result in "Permission Denied" messages. [CSCdi50635]
Tunnel Interface
A "can't read `port': no such variable" message appears at the bottom of the config port dialog when a tunnel interface is encountered while you click up through the ports. This message can be ignored. [CSCdi55765]
Notes and Caveats for High-End Business Products
Following are general notes and caveats for the Cisco High-end Business suite of products.
Displayed ATM Connector Type
CiscoView 3.1(1) always displays the multimode fiber SC type of ATM connector on AIPs, even when the media interface is of another type. [CSCdi53420]
FDDI Port Status Functionality
For 7000/7500 series routers running Cisco IOS Release10.2 or earlier, the displayed status color is determined from the port's administrative status (ifAdminStatus) and operational status (ifOperStatus) values. This status color will be the same on each connector. For devices running Cisco IOS 10.3 through 11.x, the displayed status color is determined from the Port Connect State (fddimibPORTConnectState) for each connector. The possible values for this status and the corresponding status colors are listed below. [CSCdi28566]
High System Availability (HSA)
On 7513 and 7507 chassis, when the master rsp (route switch processor) is in use, the console port changes color on the CiscoView 3.1(1) display. However, when a slave rsp is installed, its console port mirrors that of the master, regardless of whether or not it is in use. [CSCdi49049]
LightStream 2020 MIB Support
For the LightStream 2020 device there is currently no MIB support for the LNS OK, LN FLT, BITS OK, and TCS SEL LEDS on front linecards. These LEDS appear blank. In addition, the TX and RX LEDS on front linecards blink too rapidly for SNMP polling purposes, and also appear blank.
Lighstream 2020 Software Releases Supported
The LightStream 2020 supports Release 2.3(1) or later.
Power Supply Display
By default, CiscoView 3.1(1) displays two power supplies for a 7000 running Cisco IOS Release10.2 and earlier. With Cisco IOS Release 10.3 and later, power supplies are displayed based on ciscoEnvMonSupplyState values.
Read-Only MIB Variables
The administrative status (ifAdminStatus) value "testing" and the ring speed (dot5RingSpeed) variable are implemented as "read-only" in all Cisco IOS versions and cannot be set through popup menus on CiscoView Configure Port screens. However, Configure Port tables (of multiple ports) offer popup menus that permit attempts to set these variables. Such attempts result in "Permission Denied" messages. [CSCdi50635]
Notes and Caveats for Online Help
Following are notes and caveats for online help.
Glossary Links
Some device-specific help files do not have links to the glossary file. To view the glossary, select Help>Using CiscoView in the help window.
Options Menu
The following information was omitted from the online help information for the Options menu:
CiscoView Incremental Device Package Information
This section contains the release note updates (README files from CCO) for the CiscoView incremental device packages shipped in the CiscoView 3.2 release. For a list of devices, refer to Table 1.
Each update might contain the following sections:
If your Cisco device is not mentioned in this section, check on CCO for more up-to-date README information.
Every device in Release 3.2, with the exception of the AS5200, supports the following network management platforms (which are the same as the CiscoView 3.1.1 release):
The AS5200 supports the SNM, Release 2.2.2, and HP OpenView, Release 3.3.
Every device in Release 3.2, with the exception of the AS5200, supports the following operating systems (which are the same as the CiscoView 3.1.1 release):
The AS5200 supports the SunOS 4.1.x (Solaris 1.x) and HP OpenView, Release 3.3.1, running on HPUX operating system 9.0.4.
Cisco and CiscoPro 765 and 766 Series Device Package
This section describes the Cisco and CiscoPro 765 and 766 Series device package.
The Cisco and CiscoPro 765 and 766 routers connect Ethernet local-area networks (LANs) to corporate networks over Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) lines. They offer multiprotocol routing capabilities between WAN and LAN ports, as well as the ability to function as a transparent bridge.
Cisco IOS Software Releases 10.3, 11.0, and 11.1 support the Cisco and CiscoPro 765 and 766 series routers.
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco 765 and 766 Notes and Caveats
Cisco 765 and 766 notes and caveats include:
Cisco 1003, 1004, and 1005 Series Device Package
This section describes the Cisco 1003, 1004, and 1005 Series device package.
The Cisco 1003, 1004, and 1005 series routers are easy-to-install, inexpensive, multiprotocol routers designed for small offices and other remote sites.
Cisco IOS Software Releases 10.3, 11.0, and 11.1 support the Cisco 1003, 1004, and 1005 series routers.
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco 4000, 4500 and 2500 Series Device Package
This section describes the Cisco 4000, 4500, 4700, and 2500 Series device package.
The Cisco 4000 series routers provide a variety of feature sets that can accommodate all types of network computing environments.
The Cisco 2500 routers provide a variety of models designed for small office and remote site environments.
This incremental install includes support for these devices:
The basic CiscoView 3.1(1) and CiscoWorks Windows 2.0(1), without this incremental install, includes support for Cisco 4000 and 4500, and Cisco 2501 through 2516, except for 2506 and 2508, which do not exist.
All CiscoPro routers that have a corresponding Enterprise router are also supported.
Network Processor Modules Supported
This incremental install includes support for the following network processor modules (npm):
Cisco IOS Software Release 11.1 and earlier support the 4000, 4500 and 2500 series routers. Releases 10.2 and 10.3 do not support all cards for the 4000 Series routers. All 4000 series routers are supported from Software Release 11.0 or later.
SNMP MIB files are available for network management. The following Cisco Connection Online (CCO) WEB location contains many MIBs: http:// or ftp://ftp-eng.cisco.com/pub/mibs/
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
The following notes and caveats are for Cisco 2500 routers only.
Cisco AS5200 Universal Access Server Device Package
This section describes the Cisco AS5200 Universal Access Server device package.
The Cisco AS5200 is a versatile data communications platform that provides the functions of an access server, a router, and digital modems in a modular chassis.
The Cisco AS5200 package file (*.pkg) currently runs on the following UNIX systems:
Cisco IOS Software Release 11.1(5) supports the Cisco AS5200.
SNMP MIB files are available for network management. The following Cisco Connection Online (CCO) WEB location contains many MIBs: http:// or ftp://ftp-eng.cisco.com/pub/mibs/
The Cisco AS5200 package includes the AS5200 Manager application. The AS5200 Manager application includes modem management, and it enables you to remotely view, monitor, configure, and troubleshoot the AS5200 Universal Access Server from within CiscoView.
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco IOS Release 11.1 (474) Release Note and Update to Configuration Guides and Command References for the AS5200 Access Server (This is the hardcopy title for the above document.)
The installation of the AS5200 Manager application includes these steps:
Step 1. Make sure you are running CiscoView 3.1 or later.
Step 2. Create a cv_pkgs directory in the install_directory.
Step 3. Change the default directory to cv_pkgs.
Step 4. Access CCO.
Step 5. Download the tar file onto your workstation.
Step 6. Untar the tar file.
Step 7. Install the package file onto CiscoView.
Step 8. Check the cvinstall.log file.
The tar filename is AS5200.cv311.P1-1.tar.
Refer to the AS5200 Manager Guide on CCO for installation details. You can use the following URL to locate Chapter 2, which contains installation information:
AS5200 Manager Notes and Caveats
This section contains notes and caveats about problems you might encounter while using the AS5200 Manager application within the CiscoView environment.
Cisco 7000, 7200, and 7500 Series Device Package
This package contains new device support, new functionality, and several bug fixes.
This device package supports the following:
This device package supports the following new functionality:
The following caveats were fixed in this release.
Cisco 7000, 7200, and 7500 Series Notes and Caveats
Cisco 7xxx notes and caveats include:
This section describes the Cisco Catalyst 1200 device package.
Cisco Software Release 4.1 for the Catalyst 1200.
This device package extends the CiscoView device manager to include support for:
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco Catalyst 1200 Notes and Caveats
Catalyst 1200 notes and caveats follow:
Cisco Catalyst 2600 Device Package
This section describes the Cisco Catalyst 2600 device package.
Cisco Software Release SR-2.06.
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco Catalyst 2900 Device Package
This section describes the Cisco Catalyst 2900 device package.
Cisco Software Release 2.1 for the Catalyst 2900.
This device package extends the CiscoView device manager to include support for:
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco Catalyst 2900 Notes and Caveats
Catalyst 2900 notes and caveats include:
Cisco Catalyst 3000 Device Package
This section describes the Cisco Catalyst 3000 device package.
Cisco Software Releases 1.1, 1.2 and 1.3 for the Catalyst 3000.
This device package extends the CiscoView device manager to include:
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco Catalyst 3000 Notes and Caveats
Catalyst 3000 notes and caveats include:
Cisco Catalyst 5000 Device Package
This section describes the Cisco Catalyst 5000 device package.
Cisco Software Releases 1.4, 1.5 and 2.1 for the Catalyst 5000.
This device package extends the CiscoView device manager to include support for:
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
Cisco Catalyst 5000 Notes and Caveats
Catalyst 5000 notes and caveats include:
This section describes the Cisco CPW16 device package.
Cisco Software Release 1.1 for the CPW16.
This device package extends the CiscoView device manager to include support for CDP configuration.
Look for these documents on the Cisco Connection Documentation, Enterprise Series CD-ROM:
CPW 16 notes and caveats include:
This section describes the Cisco LS1010 device package.
Cisco Software Release 11.1, IISP release for LS1010.
Cisco LS1010 Notes and Caveats
OAM ping functionality is grayed out since it is not available yet in the LS1010 11.1, IISP release.
Copyright 1988-1996 © Cisco Systems Inc.
Supported Operating Systems and Network Management Software
Cisco Device
Software Releases
SunOS/Solaris and SNM1
SunOS/Solaris and HP OpenView2
HP-UX and HP OpenView3
765 and 766
Cisco IOS 10.3, 11.0, and 11.1
X
X
X
CiscoPro 765 and 766
Cisco IOS 10.3, 11.0, and 11.1
X
X
X
1003, 1004, and 1005
Cisco IOS 10.3, 11.0, and 11.1
X
X
X
2520, 2521, 2522, 2523, 2524, 2525, 4000, 4000-M, 4500, 4500-M, 4700, 4700-M
Cisco IOS Software Release 10.0 to 11.1 (Releases 10.2 and 10.3 do not support all cards for the 4000 Series routers.)
X
X
X
CiscoPro 4500
Cisco IOS 11.1 through 11.3
X
X
X
CiscoPro 2520, 2522, 2524
Cisco IOS 10.3, 11.0, and 11.1
X
X
X
AS5200 Universal Access Server
Cisco IOS 11.1(5)
SunOS 4.1.x (Solaris 1.x)
NA
HP-UX 9.0.4
HP OpenView 3.3
7206
Cisco IOS 11.1(5)
X
X
X
Catalyst 1200
Cisco Software Release 4.1
X
X
X
Catalyst 2600
Cisco Software Release SR-2.06
X
X
X
Catalyst 2900
Cisco Software Release 2.1
X
X
X
Catalyst 3000
Cisco Software Release 1.1, 1.2, and 1.3
X
X
X
Catalyst 5000
Cisco Software Release 1.4, 1.5, and 2.1
X
X
X
CPW16
Cisco Software Release 1.1
X
X
X
LS1010
Software Release 11.1, IISP
X
X
X
1 Includes SunOS 4.1.3, 4.1.4, Solaris 2.4 with SunNet Manager 2.2.2 and Solaris 2.5 and 2.51 with SNM 2.2.3 or 2.3
2 Includes SunOS 4.1.3, 4.1.4, Solaris 2.4 with HP OpenView 3.3 and Solaris 2.5 and 2.51 with HP OpenView 4.01 and 4.1. Solaris 2.5 and HP OpenView 4.1 require a patch. For more information, refer to "Installation Notes and Caveats" on page 6.
3 Includes HP-UX 9.04, 9.05 with HP OpenView 3.3 and HP-UX 10.0 and 10.10 with HP OpenView 4.01 and 4.1
bug-doc@cisco.com
Access Products
Workgroup Products
High-End Business Products
Cisco and CiscoPro 765 and 766
Catalyst switch models 1200, 1600, 1700, 2100, 2600, 2800, 2900, 3000, and 5000 series
LightStream 100 (formerly called the Cisco HyperSwitch A100) running RTOS version 3.1(1) and LightStream 2020 running 2.3(1) or later
Cisco 1003, 1004, and 1005
EtherSwitch Pro16, EPS-500, EPS-1500, EPS2115, and EPS2015
Cisco 7000 series (includes 7000 and 7010), 7200 series (includes 7206), and Cisco 7500 series (includes 7505, 7507, and 7513) routers
Cisco 4000 series (includes 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M and CiscoPro 4500)
EtherSwitches: EPS-500, EPS-2115, and Pro16 are managed by their CiscoPro equivalents: CPW500, CPW2115, and CPW16 respectively.
Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525
CiscoPro switch models CPW10-100, CPW16, CPW500, CPW1200, CPW1400, and CPW2115
CiscoPro 2520, 2522, and 2524
Workgroup concentrators 1000, 1100, and 1400, and Workgroup FDDI/CDDI adapters
Access 5200 Universal Access Server (UNIX release only) with Modem Management application
Cisco LS1010
No more textual conventions possible. (OCTETSTRING): ...
INFO: parse new mib.txt failed. Exiting.
# cd /cdrom/patch
# ./patch.unix
dlopen: stub interception failed
/usr/nms/bin/cvinstall: <pid> Abort - core dumped
Error detected while loading MIB file: /net/cv311/etc/cview/mibs/CISCO-TC-V1SMI.my
This MIB cannot be loaded until the following problem is corrected:
Line 44613: Error defining ASN.1 Type: duplicate type with conflicting definition
`CiscoNetworkProtocol'
couldn't execute "xrdb": no such file or directory
Note there is a number one (1) instead of an al in the word avalanche.
-rw-r----- 1 tr nmsd 7802880 Aug 15 10:04 PSOV_1138.tar
-rw-r----- 1 tr nmsd 217908 Aug 15 10:04 PSOV_1138.text
-rw-r----- 1 tr nmsd 11991940 Jul 2 15:48 PSOV_1090.tar
-rw-r----- 1 tr nmsd 1374787 Jul 2 15:48 PSOV_1090.text
For example, enter: get PSOV_1138.tar
cp
CW_DIR
/hpov/icons
$OV_BITMAPS/C
.
#cvclean script start
#!/bin/sh
. /opt/OV/bin/ov.envvars.sh
# Note ov.envvars.sh only exists in HP OpenView 4.0 or later. If you have
# HP OpenView 3.3, delete the line above and hard code OV_BITMAPS to the
# HP OpenView bitmaps directory. For example, /usr/OV/bitmaps.
ls -l $OV_BITMAPS/C | grep ^l|grep cview|awk '{print $9}'>/tmp/cvlink.lst
for ix in 'cat /tmp/cvlink.lst'
do
rm -f $OV_BITMAPS/C/$ix
done
#cvclean script end
# chmod +x cvclean.sh
# cvclean.sh
(including CiscoView and other products)
read=public
and
write=private
, then edit $NMSROOT/etc/cview/cview.ini.. This will be fixed in a future release of CiscoView. [CSCdi49735]
hostname% pstat -s
hostname% swap -l
hostname% swapinfo
No response from the device
Status
Status color
disabled
brown
standby
brown
connecting
blue
active
green
Options>Set HyperHelp Defaults sets the HyperHelp resources so that the HyperHelp viewer text
is readable on the screen.
Options>Debug records trace information into a file located in /tmp/ .cvlog.
supportlists/as5200/supportlist.html
supportlists/as5200/supportlist.html
