CiscoWorks Windows 2.0(1) Release Note

Configuration Builder, Show Commands, and Health Monitor support the following devices:

• Configuration Builder
  

  • Routers: 2500, 2501, 2502, 2503, 2505, 2507, 2509, 2510, 2511, 2514, 2512, 2515, 4000, 4500
    

• HealthMonitor and Show Commands:
  

  • CiscoPro switch models CPW 10-100, CPW16, CPW500, CPW 1200, CPW1400, and CPW2115
    

  • Routers: AccessPro, 2501-15, 4000, 4500, 7000, 7010
    

  • Hub/Router: 2505 and 2507
    

  • Access Servers: 2509, 2510, 2511, and 2512
    

Incremental Installation Information

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 see the quick reference card for CiscoView and the CiscoWorks Windows registration/reference card for information on adding device support to CiscoView.

Troubleshooting

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:

• The Simple Network Management Protocol (SNMP) agent is not running in the device. You can still ping the device from the management station.
  

• You have entered an incorrect community string in the File>Open Device window.
  

• The management station cannot reach or successfully ping the device.
  

CiscoWorks Windows 2.0(1) Caveats

This section lists notes and restrictions that apply to the CiscoWorks Windows 2.0(1) release.

• Installation Caveats
  

• General Caveats
  

Installation Caveats

The installation notes and caveats are described below.

CiscoWorks Windows

• You should shut down all applications prior to CiscoWorks Windows installation. CiscoWorks Windows installation may replace old Windows dynamic link libraries (DLLs) with newer versions and may cause active applications to terminate.
  

• If the Kalpana SwitchVision application is installed on your system, please deinstall the product before proceeding with the CiscoWorks Windows install.
  

• If CiscoWorks Windows fails to run immediately after an initial installation, exit and restart Windows.
  

• For CiscoWorks Windows on HP OpenView, if you want to add the management information bases (MIBs) to the database, run the ovmibs.bat batch file created by the install process from the HP OpenView MIBs directory.
  

• When you run CiscoWorks Windows on SNMPc for the first time, you are prompted to compile MIB files. Select the Yes button. If you don't compile the MIB files, SNMPc may not properly discover and manage your Cisco devices, and CiscoWorks Windows applications may not execute properly.
  

• CiscoWorks Windows is a network management product for Cisco Enterprise routers. CiscoWorks Windows and CiscoVision should not be installed on the same workstation. This configuration is not currently supported, and results are unpredictable.
  

• Upon installing CiscoWorks Windows, you may receive the following error message:
  

Unable to open MIB database. (OV313-PX72).

Perform the following steps for a workaround:

• Select the win.ini file from your Windows directory.
  

• Search for the section called [Paradox Engine].
  

• In this section, add the following line: MaxTables=10.
  

Hardware Requirements

The hardware requirement for CiscoWorks Windows 2.0 is 35 to 100 MB, depending on the number of packages installed.

Changing the Device Community String

You can change the default device community string only once, 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:

Step 1 Select one node.

Step 2 Select Edit>Edit Object.

Step 3 Select Comm...

Step 4 Change to the appropriate community string.

Step 5 Select Change in the Edit Node Attributes window.

Step 6 Select Edit>Copy.

Step 7 Select Map>Select Nodes.

Step 8 Select All Agent Types and Entire Map.

Step 9 Select Edit>Paste.

Step 10 Make sure only Community and In Map are selected before clicking on OK.

This sets the community string for all selected objects.

For more information, refer to the Castlerock SNMPc release notes. This information is available by selecting the Notepad icon labeled SNMPc Release Notes in the SNMPc program group.

HP OpenView for Windows

• If you receive the following message when you double-click on an icon, exit and restart SNMPc.
  

Unknown Node name 

When SNMPc is started from HP OpenView, you are asked to compile MIBs. Select Yes. [CSCdi40732]

• If you receive the error message:
  

WinSNMP Could not runC:CV4NTtrapx.exe [No TRAPs or IPX!] 

when you restart CiscoVision or SNMP immediately after exiting a previous session, wait for at least 20 seconds before you attempt to restart CiscoVision and SNMPc. [CSCdi40713]

Refer to the SNMPc Network Management Reference Guide for more information about running CiscoVision/SNMPc with HP OpenView.

Path Environment Variables

If you get the following error message,

couldn't execute "xrdb": no such file or directory 

this may mean that the missing program (for example, xrdb) is not in your path. Check your path environment variable. [CSCdi57661]

SNMPc

• The SNMPc 4.1g CD contains the DSK directory. Under DSK you will see subdirectories named 1 and 2. Do not install SNMPc from DSK/1/setup.exe.
  

• Do not do a vendor installation of SNMPc after installing CiscoWorks Windows. If you do, you will need to reinstall CiscoWorks.
  

SNMPc Release Notes

Autodiscovery either finds 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

• CWW2.0 is not tested with Optivity 5.3/OV on the same system. [CSCdi57009]
  

• When double-clicking on Device Install to install a bad WG_Adapter package followed by a good WGConcentrator package, the following error message appears:
  

Log File for WGAdapter Install
Do you want to carry on with the rest of the setup?

Select yes and the setup continues, but the error window is not dismissed. [CSCdi57072]

General Caveats

The general caveats follow. They are divided into six sections:

• Enterprise Network Management Products and applications including CiscoView, Configuration Builder, Show Commands, and Health Monitor
  

• Workgroup Products
  

• Access Products
  

• High-end Business Products (including the 7000 series, 7500 series, and ATM switches)
  

• Online Help
  

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 may not work properly and may 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 may 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 are sometimes not drawn clearly. [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 to 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:

[startup]
nTasks=20

CiscoView

This section contains notes and caveats for the CiscoView application.

CiscoView Times Out

In high traffic situations, you may 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]

Configuration Builder

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

expect null/send null lines

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 the configuration process, 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 it. 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

• If you use the F1 key often while the input focus is within a dialog box, Configuration Builder spreadsheet controls can lose track of certain pointers. To release memory and refresh the pointers, log out of Windows and log in again. [CSCdi34671]
  

• When you use the keyboard to navigate spreadsheet style controls, you must press the spacebar twice to modify a checkbox. [CSCdi15204]
  

• The Esc key does not close the window when the input focus is in the spreadsheet style controls. Use the window menu or move the input focus out of the spreadsheet controls to close the window. [CSCdi15891]
  

Health Monitor

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

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:

This command is not supported by this IOS image .

[CSCdi30902]

Workgroup Products

Catalyst 2800, Catalyst 2100, EtherSwitch 1200, and EtherSwitch 1400

General notes and caveats for the above Workgroup Products are described below.

• In the front panel display of the Catalyst 2800 and EtherSwitch 1400, the Connect and Disabled LEDs on FDDI modules do not reflect the appropriate status.
  

• CPW 1200, CPW 1400, Cat 2100, Cat 2800---In the General Bridge Window, the Last Topology Change field does not apply when Spanning Tree is disabled.
  

• CPW1400, Cat2800---Do not attempt to invoke the Monitoring menu for an FDDI port or a repeater port. There is no monitoring function provided for these ports, although the pull-down menu is enabled when such ports are selected.
  

• CPW1400, Cat2800---The Configure Module Windows do not work when more than one module type is selected. Please select only one module type before opening these windows.
  

• CPW 1200, CPW 1400, Cat 2100, Cat 2800---The General Bridge window shows the bridge information for VLAN1 only. Bridge information for other VLANs is not available.
  

• CPW 1200, CPW 1400, Cat 2100, Cat 2800---The Spanning Tree Protocol Window for switched ports is available for ports in VLAN1 only. This window does not show valid information for ports not in VLAN1.
  

• The WG-Concentrator, CPW10-100, and WG_Adapter do not show version information in the About CiscoView dialog box. In these cases, the CiscoView About dialog box displays the package version only. However, the version information is displayed in the "Packages Installed" list.
  

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 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:

• Catalyst 2100 and 2800---v. 3.63 or higher
  

• EtherSwitch 1200 and 2800---v. 3.63 or higher
  

• Grand Junction FastSwitch 2100 and 2800---v. 3.62 or higher
  

Options>Debug records trace information into a file located in $NMSROOT/cvlog