|
|
CiscoWorks Windows Release Note
This document discusses the CiscoWorks Windows 2.1(1) release and includes the following information:
CiscoWorks Windows 2.1(1) includes the original release of the CiscoWorks Windows applications and device support and the new release of CiscoView, version 3.2. CiscoView 3.2 consists of the CiscoView 3.1.1 application and device support, plus the additional device support now found on a separate CD called the Network Management Support CD. These devices are also available from the Cisco Connection Online (CCO) service.
If you already have CiscoWorks Windows installed, you do not need to reinstall release 2.1(1). Only install the devices you need off the Network Management Support CD.
To mount and install devices from the support CD, refer to the special CD booklet included in the package. Be sure to read the README files on the Network Management Support CD or turn to the section "CiscoView Incremental Device Package Information."
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
CiscoWorks Windows has the following features:
CiscoWorks Windows IOS Information
This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing. New devices and further specifics on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:
Configuration Builder devices support Cisco IOS Software Releases 10.0 through 11.0 (3), with the exception of access servers, which require a minimum of Cisco IOS Software Release 10.2.
CiscoView, Show Commands, and Health Monitor devices support Cisco IOS Software Releases 10.0 through 11.1.
The documentation for CiscoWorks Windows includes this document, a CD-ROM booklet, incremental installation instructions, and online help. The primary documentation for CiscoWorks Windows is the online help. If you have documentation feedback, please forward comments to You can also refer to the CiscoWorks Windows registration/reference card for information on adding device support to CiscoView.
The documents shipped with this release include:
Customer documentation can also be found on the Cisco Enterprise Customer Documentation CD or on CCO.
CiscoWorks Windows Device Information
Table 2 contains the list of supported CiscoView devices by product type.
Table 2 : Supported CiscoView Devices
Table 3 describes the CiscoWorks Windows application support for Cisco devices.
Table 3 : Supported CiscoWorks Windows Applications
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 Support CD. For more information, refer to the Downloading New Cisco Devices and Applications quick reference card (shipped attached to the registration card) or to CCO. The quick reference card can be located at the following CCO URL:
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, you receive a message indicating that the device is unmanageable. This message indicates one of the following conditions:
CiscoWorks Windows Notes and Caveats
This section lists notes and restrictions that apply to the CiscoWorks Windows 2.1 release.
Installation Notes and Caveats
The installation notes and 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.exe patch before you perform CiscoView increment installation using Device Install. Otherwise, the above problem might be observed. To install the patch from the Network Management Support CD, 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 on the Network Management Support CD that contains the following files:
If you do not have the Network Management Support CD, you can access CCO for the SMU.
To install the CiscoView patch, 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]
Access Devices and HP OpenView for Windows
HP OpenView for Windows caveats include:
A problem existed with HP OpenView for Windows, 7.2b (C.02.14) where CiscoView did not recognize several Access devices that were assigned invalid symbol IDs by Hewlett-Packard. HP has fixed this problem. The fix for this problem requires you to upgrade HP OpenView for Windows and run a conversion utility for any of the affected devices packages you might have installed.
If you are using the new Access devices that require this upgraded HP OpenView for Windows version referenced in Table 2 (Cisco 1003, 1004, 1005, Cisco 765 and 766, CiscoPro 765 and 766, CiscoPro 2520, 2522, and 2524, or CiscoPro 4500), do the following:
OR
Retrieving the Software Update from HP To retrieve an update of the HP OpenView for Windows software from the Hewlett-Packard FTP server, do the following:
Continue to "Running the Upgrade from HP" to complete the upgrade to version C.02.17.
Running the Upgrade from HP To run the upgrade to C.02.17, do the following:
Updating Access Device Packages The following notes and caveats should be followed:
Hardware Disk Space Requirements
The hardware disk space requirement for CiscoWorks Windows is 35 to 100 MB, depending on the number of packages installed.
Changing the Device Community String for SNMPc
You can change the default device community string only once in Castle Rock SNMPc, by using the Edit>Node Defaults command, and you need to save and reload the network map before the new default community string takes effect. Performing this procedure again has no effect. You can use the following workaround to change community strings in the future.
Change the community strings for all devices at once, instead of one at a time, with the following procedure:
This procedure sets the community string for all selected objects.
For more information, refer to the Castle Rock SNMPc release notes by selecting the Notepad icon labeled SNMPc Release Notes in the SNMPc program group.
Delay When Installing All Devices
If you select all the devices to be installed from the Device Install menu, it may take some time before there is an indication that the installation is progressing. Please standby, the installation will proceed.
Use the following recommended actions for dealing with error messages:
Refer to the SNMPc Network Management Reference Guide for more information about running CiscoWorks Windows/SNMPc with HP OpenView.
SNMPc caveats include:
Autodiscovery finds either SNMP devices as ping nodes or finds nothing after clearing the discovery log. Verify that the read community string is correct. Start autodiscovery again to see if the problem persists. If it does, terminate autodiscovery and restart from the SNMPc Map menu. [CSCdi40648]
Windows NT caveats include:
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.
Colormap Problems
Windows 95 has a known Microsoft colormap problem where some colors are mapped incorrectly when switching between applications.
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.
Dragging Ports
For this release, use the left mouse button to drag a port on Windows. 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 it from the map.
IP Address
The Health Monitor, CiscoView, Show Commands, and Configuration Builder applications communicate with a device using its primary IP address. If the primary interface is down, these applications can not locate or attempt to reach the secondary IP address for that device. [CSCdi31320]
Popup Menu Titles
Popup menu titles are raised; users can mistake them for menu items. [CSCdi53475]
Starting CiscoView on Device Interfaces
If you start CiscoView on an expanded node's interface icon (for example, foo.cisco.com:1), you won't be able to telnet to that device---telnet thinks it should use port 1. Do not start CiscoView on device interfaces. [CSCdi56385]
Stripchart and Dials
Stripchart and dials do not get refreshed properly. This is especially true for Windows 95. [CSCdi51621]
TACACS
If you have TACACS or login security enabled on your router, the Show Commands application and the Configuration Builder Learn and Send features will not function. However, you can send configuration files generated by Configuration Builder using the standard TFTP transfer methods. [CSCdi31004]
Windows 95
On Windows 95 there appears to be different coloring shades in Grapher as port stats is reset. You can refresh or redisplay the window as a work around. [CSCdi53523]
Windows NT
Under the Windows NT environment, running too many sessions of the CiscoWorks Windows applications (Health Monitor, Show Commands, and Configuration Builder) can cause a General Protection Fault (GPF) in the module MFC250.dll. This is a known Microsoft bug that can be avoided by running fewer sessions of the applications. [CSCdi31282, CSCdi34536]
WinSNMP Limits The NetPlus WinSNMP.dll allows only nine instances of CiscoView. The tenth one displays an initialization error message. This limit can be increased by setting nTasks = <desired #> under the section labeled [Startup]. For example:
This section contains notes and caveats for the CiscoView application.
CiscoView Times Out
In high traffic situations, you might experience timeouts. To increase the timeout period, select Options>Properties from the CiscoView menu and change the value for the Timeout field.
You should not reduce the physical view polling interval below (retries*timeout), especially if you experience timeouts; this can exhaust resources on Windows and result in a general error.
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]
This section contains notes and caveats for the Configuration Builder application.
Access Server Dialog Boxes
For access server dialog boxes, the cursor will not provide feedback for incorrect data entry in fields, nor is the field with incorrect data highlighted. Font resizing at various screen resolutions may cause the incorrect sizing of text or limit the visible selections in pull-down combo-boxes. You can select invisible combo-box selections by holding down the right mouse button while in the combo-box, then scrolling up or down. [CSCdi34066]
Access Server Features
For access server features, the Chat Script Manager dialog box may create
in a chat script. If you inadvertently create empty lines under the Expect and Send fields, you receive error messages about your chat script. Delete and recreate the chat script. [CSCdi34038]
Context-Sensitive Help
Selecting a menu item with the mouse and pressing the F1 key opens the Configuration Builder Help Contents main window instead of starting context-sensitive help. However, context-sensitive help is supported for all Configuration Builder dialog boxes. [CSCdi34304]
Dialog Box Margins
Dialog box margins may not align on some monitor resolutions. [3D-look]
Sending Configuration Files
Configuration Builder is designed for initial configuration and subsequent modifications of routers. A configuration sent by Configuration Builder may not completely overwrite a manually created or modified existing configuration. To simplify configuration, Configuration Builder supports the most common configuration options and uses defaults when possible. You are encouraged to view configurations before sending them to a router to ensure that the generated configuration commands and defaults meet your expectations.
If you receive a banner command timeout error message when sending a configuration file, remove the banner command from the configuration file and resend the file. If you receive other command timeout error messages when sending files, select File>Communication Timeouts. In the Communication Timeouts dialog box, increase the long and short timeout values, and try sending the file again. [CSCdi20708]
Spreadsheet Control
Spreadsheet control has the following caveats:
The F1 key context-sensitive help feature is not supported for Health Monitor menu items. Context-sensitive help is supported for all Health Monitor dialog boxes. [CSCdi32448]
Show Commands features are not supported by all device types. However, Show Commands' unsupported features can still be selected.
If you select an unsupported feature, you see an error message. For example, if you select the show controllers CxBus feature for a Cisco CPA2509, you see the following error message. [CSCdi30902]
Notes and Caveats for Workgroup Products
General notes and caveats for Workgroup products are described below.
Catalyst 2800, Catalyst 2100, EtherSwitch 1200, and EtherSwitch 1400
General notes and caveats for the above Workgroup Products are described below.
Community String Mismatching
When the user enters values for 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 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 will automatically close. Remember to close the EtherChannel and Domain Configuration application windows before you open another CiscoView application or exit from the CiscoView application. There is no limitation on the number of CiscoView applications that you can run.
False Error Reported after Setting Parameters
On the CiscoPro (CPW) 16 and Catalyst 3000, when you try to set parameters for the EtherChannel/Domain application under moderate to high traffic situations, the application incorrectly displays an error window indicating that the operation was not successful. In reality, the command was successful, and you should dismiss the error dialog. The application should continue to function properly.
LightStream 100 The LightStream 100 VCTool has support for virtual circuit management of the LS100 and can be invoked from the LS100 CiscoView application.
The LightStream 100 VCTool is currently supported for SunOS 4.1.X and HPUX 9.X.
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 come up 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]
Notes and Caveats for Access Products
Following are general notes and caveats for the Cisco Access family of products.
Access 3.2 Devices Require HP OpenView for Windows Upgrade
A problem existed with HP OpenView for Windows, 7.2b (C.02.14) where CiscoView did not recognize several Access devices that were assigned invalid symbol IDs by Hewlett-Packard. HP has fixed this problem. The fix for this problem requires you to upgrade HP OpenView for Windows and run a conversion utility for any of the affected devices packages you might have installed.
If you are using the new Access devices that require this upgraded HP OpenView for Windows version referenced in Table 2 (Cisco 1003, 1004, 1005, Cisco 765 and 766, CiscoPro 765 and 766, CiscoPro 2520, 2522, and 2524, or CiscoPro 4500), refer to the "Access Devices and HP OpenView for Windows" on page 8 for detailed instructions on how to perform the fix.
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 will permit attempts to set these variables. Such attempts will 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 clicking up through the ports. This message can be ignored. [CSCdi55765]
Notes and Caveats for High-End Business Products
General notes and caveats for High-End Business products are described below.
Core Routers View Options
For Cisco 7000, 7505, and 7513 routers, the legend area at the bottom of the CiscoView window may not be viewable. Displaying the entire device at 100% does not fit on a 1024x760 PC display. The workaround is to use the 50% view or to deselect the Options>Show Toolbar and select Options>Show System Info.[CSCdi50212]
Displayed ATM Connector Type
CiscoView 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 Release 10.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 Release 10.3 or later, 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 the 7513 and 7507 chassis, when the master rsp (route switch processor) is in use, the console port changes color on the CiscoView 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.
Lightstream 2020 Truncated
When using CiscoView on the PC platform (either standalone, under OVWIN, or under SNMPc CastleRock) for a LightStream 2020 ATM switch, a 1280x1024 resolution display is required. Any lower resolution results in truncated output. [CSCdi49654]
Lighstream 2020 Software Releases Supported
LightStream 2020 supports Release 2.3(1) or later.
Power Supply Display
By default, CiscoView displays two power supplies for a 7000 running Cisco IOS Release 10.2 orearlier. With Cisco IOS Release10.3 or 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 general notes and caveats for CiscoWorks Windows online help.
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 device information, refer to Table 1.
This section includes the following device README text files:
Each update may 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 Cisco device in Release 3.2, with the exception of the Access devices listed below, is supported on the following network management platforms:
The listed Access devices below are supported on the following network management platforms:
The Cisco AS5200 is supported on all UNIX platforms only. Refer to CCO for AS5200 support in the future.
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):
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 and CiscoPro 765 and 766 Notes and Caveats
Cisco and CiscoPro 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 1003, 1004, and 1005 Notes and Caveats
Due to a problem with how HP OpenView for Windows handles symbol IDs, the Cisco 1003, 1004, and 1005 devices require HP OpenView for Windows version 7.2 (C.02.17) to work with CiscoView properly. For information on upgrading and running the conversion utility, refer to "Access Devices and HP OpenView for Windows" on page 8.
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 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:
Cisco Catalyst 1200 Device Package
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
Windows1
HP OpenView for Windows2 and Castle Rock SNMPc
Cisco 765 and 766
Cisco IOS 10.3, 11.0, and 11.1
X
X 3
CiscoPro 765 and 766
Cisco IOS 10.3, 11.0, and 11.1
X
X3
Cisco 1003, 1004, and 1005
Cisco IOS 10.3, 11.0, and 11.1
X
X3
Cisco 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
CiscoPro 4500
Cisco IOS 11.1 through 11.3
X
X3
CiscoPro 2520, 2522, 2524,
Cisco IOS 10.3, 11.0, and 11.1
X
X3
Cisco AS5200 Universal Access Server
Cisco IOS 11.1(5)
UNIX only
UNIX only4
Cisco 7206
Cisco IOS 11.1(5)
X
X
Cisco Catalyst 1200
Cisco Software Release 4.1
X
X
Cisco Catalyst 2600
Cisco Software Release SR-2.06
X
X
Cisco Catalyst 2900
Cisco Software Release 2.1
X
X
Cisco Catalyst 3000
Cisco Software Release 1.1, 1.2, 1.3
X
X
Cisco Catalyst 5000
Cisco Software Release 1.4, 1.5, 2.1
X
X
Cisco CPW16
Cisco Software Release 1.1
X
X
LS1010
Software Release 11.1, IISP
X
X
1 Windows includes NT version 3.51 and Windows 95 version 4.0
2 HP OpenView for Windows includes version 7.2 (C.02.14 and C.02.17)
3 Requires HP OpenView for Windows version 7.2 (C.02.17). For information on upgrading, refer to "Access Devices and HP OpenView for Windows" on page 8.
4 Check CCO for AS5200 updates. Support for the PC will be added in the future.
bug-doc.cisco.com
Access Products1
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)
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
CiscoPro 4500
Cisco LS1010
1 The Access devices added in CiscoView 3.2 require HP OpenView for Windows version 7.2 (C.02.17). You must upgrade to this new HP version or your devices will not work with CiscoView. For more information, refer to the section on "Access Devices and HP OpenView for Windows" on page 8
www.cisco.com
) periodically for download information on the latest device support and upgrades.
Configuration Builder
Show Commands
Health Monitor
Routers: 2500, 2501, 2502, 2503, 2509, 2510, 2511, 2514, 2512, 2515, 4000, 4500, 7000, 7010
Routers: AccessPro, 2501-15, 4000, 4500, 7000, 7010
Routers: AccessPro, 2501-15, 4000, 4500, 7000, 7010
Hub/Router: 2505 and 2507
Hub/Router: 2505 and 2507
Hub/Router: 2505 and 2507
Access Servers: 2509, 2510, 2511, and 2512
Access Servers: 2509, 2510, 2511, and 2512
CiscoPro switch models CPW 10-100, CPW500, CPW 1200, CPW1400, and CPW2115
CiscoPro switch models CPW 10-100, CPW500, CPW 1200, CPW1400, and CPW2115
No more textual conventions possible. (OCTETSTRING): ...
INFO: parse new mib.txt failed. Exiting.
ERROR: CiscoView was not properly installed on this machine.
September 1, 1996, download the updated Access device packages onto your PC and run the HP conversion utility which is available on CCO. Details follow in the "Updating Access Device Packages" section on page 9.
Netscape or other graphical user interface (GUI) FTP clients will not work. This is a limitation HP recognizes and is working to correct in the near future. Command-line versions of FTP are included with Windows 95 and Windows NT.
For example, enter c:\opt\CSCOcv\c0217up.exe. This results in several other files displaying in your directory, including a setup.exe file.
For example, enter c:\opt\CSCOcv\setup.exe.
Go to CCO to access the conversion utility only if you have downloaded Access device packages from CCO prior to September 1, 1996.
If you have downloaded Access devices from the CCO server before September 1, 1996, to use those devices on CiscoView you must do the following steps. Otherwise, skip this procedure.
The convert.exe file does not support file path information, so you must copy this file to the same directory that contains the map files to be converted.
For the most up-to-date information, always refer to CCO. For your convenience, a brief description of the steps follows:
drive
and
directory_name
with the directory that contains the map files to be converted. Replace the
map_name
with the map to be converted.This starts the conversion process and redirects the convert.exe file output to a file for later reference (since it displays very quickly).
Unable to open MIB database. (OV313-PX72).
Unknown Node name
WinSNMP Could not runC:CV4NTtrapx.exe [No TRAPs or IPX!]
Log File for WGAdapter Install
Do you want to carry on with the rest of the setup?
[startup]
nTasks=20
expect null/send null lines
This command is not supported by this IOS image.
No response from the device
Status
Status color
disabled
brown
standby
brown
connecting
blue
active
green
Options>Debug records trace information into a file located in $NMSROOT/cvlog
supportlists/as5200/supportlist.html
