|
|
December 17, 1997
This document discusses the CiscoWorks Windows 3.1(1) release and includes the following information:
| Caution Before installing CiscoWorks Windows or CiscoView devices, read the caveats in "CiscoWorks Windows" on page 12. |
New devices are supported on all platforms unless otherwise noted. A README file describing device support is included on Cisco Connection Online (CCO).
To mount and install devices from the support CD, refer to the CD booklet included in the package. Be sure to read the README files on CCO.
This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing.
Configuration Builder devices support Cisco IOS software Releases 10.2 through 11.2. Access servers require a minimum of Cisco IOS software Release 10.3. Cisco 3600 devices require Cisco IOS software Release 11.1 or later. Cisco 4000 series devices require Cisco IOS software Release 10.3 or later.
CiscoView, Show Commands, and Health Monitor devices support Cisco IOS software Releases 10.2 through 11.2.
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:
The documentation for CiscoWorks Windows includes this document, a CD-ROM booklet, an overview manual, and online help. The primary documentation for CiscoWorks Windows is the online help. If you have documentation feedback, please forward comments to
bug-doc@cisco.com
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.
Table 1 shows supported CiscoView devices by product type.
| Small to Medium Business Products | Mid-Range Enterprise Products1 | High-End Enterprise Products |
|---|---|---|
Cisco and CiscoPro 761, 762, 765, 766, 771, 772, 775, 776 | Catalyst and CiscoPro switch models2 1200, 1400, 1600, 1601, 1700, 1800, 1900, 2100, 2600, 2800, 2820, 2900, 2926, 3000, 3100, 3200, 3900, 5002, and CPW2200 | Catalyst 5000, 5500, and 5505
|
Cisco or CiscoPro 1003, 1004, and 1005 | EtherSwitch Pro16,EPS2015, 1200, 1220, 1400, 1420 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
Cisco and CiscoPro 1601, 1602, 1603, 1604, 1605 | EtherSwitches: Pro16 and CPW16 | LS10103
|
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, CPW500, CPW1200, CPW1220, and CPW1400 |
|
CiscoPro 2051, 2052, 2503, 2504, 2505, 2507, 2509, 2511, 2513, 2514, 2516, 2520, 2521, 2522, 2523, and 2524 | Workgroup concentrators 1400 |
|
Cisco and CiscoPro 3600 series (includes 3620 and 3640) | Fasthub 216T |
|
Cisco and CiscoPro 4000 series4 (includes 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M) |
|
|
AS5200 Access Server | AS2509-RJ | AS5300 Access Server |
Cisco 1501, 1502, 1503, 1516 |
|
|
NetBeyond Fasthub 300 and Fasthub 100+ Series |
|
|
EPS-500, EPS-1500, EPS2115, CPW-500, CPW-2115, and CPW-16 |
|
|
Table 2 provides the CiscoWorks Windows applications and the devices each application supports.
| Configuration Builder1 | Show Commands | Health Monitor |
|---|---|---|
Routers: 2500, 2501, 2502, 2503, 2509, 2510, 2511, 2514, 2512, 2515, 2520, 2521, 2522, 2523, 2524, 2525, 4000, 4500, 7000, 7010, 7204, 7206, 7505, 7507, and 7513 | Routers: AccessPro, 2501-15, 4000, 4500, 7000, 7010, 7204, 7206, 7505, 7507, and 7513 | Routers: AccessPro, 2501-15, 4000, 4500, 7000, 7010, 7204, 7206, 7505, 7507, and 7513 |
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 |
Table 3 describes the applications supported by CiscoView.
| Application | Description | OS | Cisco IOS | Device Support |
|---|---|---|---|---|
Threshold Manager | Monitors the availability and performance of Cisco devices | Windows 95, | Release 11.1 or 11.2 with RMON events and alarms group support | All devices with appropriate Cisco IOS or RMON features |
StackMaker | Manages the device membership in a Cisco stack | Windows 95 | Releases 10.0 through 11.2 | Cisco and CiscoPro 1600, 3600, 3620, 3640, Catalyst 1900, Catalyst 2820, CPW1220, CPW1420, Fasthub 100+ and NetBeyond Fasthub 300 |
Flash File System | Provides file copying and editing features for Cisco 7000, 7010, 7204, 7206, 7505, 7507, and 7513 routers | Windows 95
| Releases 10.0 through 11.2 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
The CiscoView device packages included in this release are shown in Table 4.
| Device Package | Version |
|---|---|
1000.pkg | 4.0(1.2) |
1500.pkg | 4.0(1.2) |
1600.pkg | 4.0(4.2) |
2500.pkg | 4.0(3.1) |
3600.pkg | 4.0(6.1) |
4000.pkg | 4.0(2.4) |
700.pkg | 4.0(1.4) |
7000.pkg | 4.0(3.0) |
AS5200.pkg | 4.0(3.1) |
AS5300.pkg | 4.0(1.1) |
CPW10_100.pkg | 4.0(1.4) |
CPW1200.pkg | 4.0(1.4) |
CPW1220.pkg | 4.0(1.5) |
CPW1400.pkg | 4.0(1.4) |
CPW1420.pkg | 4.0(1.5) |
CPW16.pkg | 4.0(1.1) |
CPW2115.pkg | 4.0(1.1) |
CPW2200.pkg | 4.0(1.5) |
CPW316.pkg | 4.0(1.4) |
CPW500.pkg | 4.0(1.1) |
Cat116.pkg | 4.0(1.4) |
Cat1200.pkg | 4.0(1.4) |
Cat1600.pkg | 4.0(1.2) |
Cat1700.pkg | 4.0(1.4) |
Cat1800.pkg | 4.0(1.1) |
Cat1900.pkg | 4.0(1.6) |
Cat2100.pkg | 4.0(1.4) |
Cat216.pkg | 4.0(1.1) |
Cat2600.pkg | 4.0(1.2) |
Cat2800.pkg | 4.0(1.4) |
Cat2820.pkg | 4.0(1.5) |
Cat2900.pkg | 4.0(1.7) |
Cat3000.pkg | 4.0(1.6) |
Cat3900.pkg | 4.0(1.1) |
Cat5000.pkg | 4.0(1.8) |
Cat5500.pkg | 4.0(1.7) |
Cisco1516.pkg | 4.0(1.1) |
EPS2015.pkg | 4.0(1.1) |
LS1010.pkg1 | 4.0(1.4) |
| 1Please upgrade to LS1010 device package version 4.0(1.8). This package can be downloaded from CCO. |
You can add new devices to CiscoView from CCO. For more information, refer to the "Downloading Device Packages" chapter in Overview for CiscoWorks Windows. A quick reference version exists in the CiscoWorks Windows CD Installation Instructions booklet. For our partner-initiated customers, refer to the section "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 the "Downloading Device Packages" chapter in Overview for CiscoWorks Windows.
The following problems in CiscoWorks Windows 3.0(1) are fixed in CiscoWorks Windows 3.1(1). Only the most serious problems are shown in Table 5.
CSCdi70385 | Configuration Builder does not insert lines into access lists on router |
CSCdi82266 | CiscoView AS5200 package problem in SNMPc TrendWatch. |
CSCdi86422 | SNMPc Display MIB table not working for lifTable. |
CSCdi87065 | CiscoView 4.0 engine should not poll a device that is out of display in Stack |
CSCdj07135 | 10BaseT interface fails to select |
CSCdj07710 | Unable to configure Catalyst 5000 port |
CSCdj12860 | SanFran:Etna module reports error messages while getting displayed |
CSCdj14942 | CiscoView: 5111 and 5011 cards don't have link ports |
CSCdj15629 | CiscoView engine crashed due to continuously polling large table |
CSCdj15790 | 7000 symbol registered for 7010 router in oid_to_sym |
CSCdj17659 | Cannot set Token Ring segment on Catalyst 1600 |
CSCdj18660 | LS1010:LEDs on IBIS PAM not labeled |
CSCdj26323 | Fractional interfaces are displayed for one port only |
CSCdj28590 | ATM interface stats to be computed based on frames, not octets |
CSCdj30092 | Cannot modify VLAN number in port config for Catalyst 5000 |
CSCdj32207 | Config Builder cannot configure 8-port ISDN on 7XXX |
CSCdj56651 | CWW 3.0 locks OV MIB Database |
If you cannot open a device in CiscoView, you receive a message that the device is unmanageable for one of the following reasons:
This section contains notes and restrictions that apply to the CiscoWorks Windows 3.1(1) release.
Installation notes and caveats for CiscoWorks Windows follow.
(a) Remove VlanDirector by selecting Uninstall VlanDirector in the CiscoWorks Windows program group.
(b) Remove CiscoWorks Windows by selecting Uninstall CiscoWorks in the CiscoWorks Windows program group.
(c) Install CiscoWorks Windows. For details, refer to the CiscoWorks Windows CD Installation Instructions document.
If you select all the devices to be installed from the Device Install menu, it might take some time before there is an indication that the installation is progressing.
If the network management platform with which CiscoWorks Windows is integrated (for example, SNMPc 4.2.04) is uninstalled, CiscoWorks Windows behavior will be unstable. To work around this problem, uninstall CiscoWorks Windows before uninstalling the network management platform, then reinstall CiscoWorks Windows. [CSCdj40831]
NMS | Version | Approximate Disk Space Required (MB) |
HP OpenView Professional Suite | 7.3 D.01.02 | 28 |
HP OpenView Network Node Manager for Windows NT | 5.01 | 55 |
SNMPc | 4.2.04 | 8 |
General notes and caveats are divided into six sections:
General notes and caveats for CiscoWorks Windows operating systems and optional Network Management Systems follow.
You can change the default device community string only once in Castle Rock SNMPc, by using the Edit>Node Defaults command. You then need to save and reload the network map for the new default community string to take effect. Performing this procedure again has no effect. You can use the following workaround to change community strings in the future.
You can change the community strings for all devices at once, instead of one at a time.
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, then click OK.
This procedure sets the community string for all selected objects.
When the SNMP Debug option is enabled, it pops up a separate console window that shows SNMP traffic to and from the device. Do not close this window because CiscoView will exit also.
Use the following recommended actions for dealing with error messages:
Unknown Node name
WinSNMP Could not runC:CV4NTtrapx.exe [No TRAPs or IPX!]
Refer to the SNMPc Network Management Reference Guide for more information about running CiscoWorks Windows/SNMPc.
CiscoWorks Windows does not integrate traps with HP OpenView Professional Suite (HP OpenView Windows). [CSCdj12760]
Because of IPC (socket) problems in the TCL version used by CiscoView 4.1 on the Windows 95 operating system, the following features do not work properly and have been disabled:
On Windows 95, different colors appear in Grapher as port status is reset. You can refresh or redisplay the window as a workaround. [CSCdi53523]
CiscoWorks Windows 3.1(1) cannot be installed on Windows 95 if FPROTO 2.2.7 is also installed and active on the machine. Deactivate FPROTO 2.2.7 before you install CiscoWorks Windows 3.1(1) [CSCdj38627].
Under the Windows NT environment, running too many sessions of the CiscoWorks Windows applications (Health Monitor, Show Commands, and Configuration Builder) simultaneously can cause a General Protection Fault (GPF) in the module MFC250.dll. This is a known Microsoft bug that you can avoid by running fewer sessions of the applications. [CSCdi31282, CSCdi34536]
Windows 95 has a known Microsoft colormap problem. Some colors are mapped incorrectly when you switch between applications.
When you enter 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 errors, use identical community strings in CiscoView and corresponding agents.
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.
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 reach the secondary IP address for that device. [CSCdi31320]
Popup menu titles are raised; users can mistake them for menu items. [CSCdi53475]
If you start CiscoView on an expanded node's interface icon (for example, example.cisco.com:1), you will not be able to Telnet to that device---Telnet tries to use port 1. Do not start CiscoView on device interfaces. [CSCdi56385]
Stripchart and dials are not refreshed properly. This is especially true for Windows 95. [CSCdi51621]
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 standard TFTP. [CSCdi31004][CSCdi76685]
On some systems running Windows, launching CiscoView for the first time might take longer than a minute. [CSCdj52543]
The FEIP-FX card does not appear in CiscoView. When the Cisco 7000 series device comes up, you might see the error message "no such element in array." [CSCdj61077]
For some devices, config/monitor does not work for multiple ports. [CSCdj65066]
CiscoView does not support internationalization.
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.
When running CiscoView 4.1 on Windows 95, you might experience the following exception. If you experience this, exit all other running applications and run CiscoView as a standalone application. This crash has been observed while running Heat v 3.10 from Bendata Inc.
WISH caused an invalid page fault in
module KERNEL32.DLL at 014f:bff78040.
Registers:
EAX=00465504 CS=014f EIP=bff78040 EFLGS=00010206
EBX=005553f4 SS=0157 ESP=0068e994 EBP=00000466
ECX=00100000 DS=0157 ESI=00465504 FS=293f
EDX=0046000c ES=0157 EDI=000efef0 GS=20d6
Bytes at CS:EIP:
8b 03 a8 01 74 25 25 fc ff ff 0f 8b 53 08 03 f8
Stack dump:
00000466 000efef0 004653f4 00000110 bff782c7 00460000 00465504 000efef0
00000000 004653f4 00460000 00000041 0046000c 00000555 00000000 00000040
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 might 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]
For access server features, the Chat Script Manager dialog box might 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]
Selecting a menu item with the mouse and pressing F1 opens the Configuration Builder Help Contents main window instead of context-sensitive help. However, context-sensitive help is supported for all Configuration Builder dialog boxes. [CSCdi34304]
Dialog box margins might not align on some monitor resolutions. [3D-look]
On Windows NT, if an incorrect model is selected in the Model field of the New Configuration File dialog or the Cisco IOS field is empty or incorrectly filled in, you might encounter the following error message "Invalid OS Specified. OS version should be greater than 10.2."
The workaround is to enter the device's correct Cisco IOS version number into the Cisco IOS field. This Cisco IOS version should be greater than 10.2. [CSCdj12523]
Configuration Builder is designed for initial configuration and subsequent modifications of routers. A configuration sent by Configuration Builder might 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]
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.
When the StackMaker Debug option is set to On, debug messages print to the StackMaker Debug Log file. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is smDebugLog in c:\CWW or the install directory.
When the StackMaker Debug SNMP option is set to On, SNMP debug messages print to the console on the PC. The messages show the SNMP packets that have been sent and received. The default is Off.
The StackMaker log file stores the results of a saved stack configuration (Actions>Apply Stack Configuration). The log file is $NMSROOT\etc\cview\devices\stackmkr\sm.log. When the log file exceeds 1 MB, it automatically resets to 0 bytes.
Some agents, most notably the Catalyst switches, impose a limit on the number of alarm and event entries that can be created. Applying a large number of thresholds to these devices will likely fail. In this case, some alarm entries might be successfully created but their associated event entries are not. These failed creations are marked as Failed in the Current Threshold Settings pane. If you attempt to delete those settings, Threshold Manager reports that the deletion failed (because it cannot delete nonexistent event entries). In this case, you can ignore the error message, and can verify that the deletion occurred by retrieving the threshold settings after the deletion.
New policies are always added to the display list.To view the new policies, exit the Configure Thresholds window, then reopen it. [CSCdi62741]
Policy filenames do not match if the IP address is used. To correct this, use the host name instead of the IP address when saving host-specific policies. [CSCdi62739]
Duplicate global/device/host policies may be allowed, depending on which window is used. When creating a custom policy, you can save it only once, either as global, device, or host. But after saving the policy, you can use the Modify Threshold Policy window to modify the saved custom policy and save it as all three. [CSCdi68329]
To delete an entry from the Set Managers configuration, enter an IP address of 0.0.0.0. The agent on the devices do not accept a blank entry for an IP address. [CSCdj03444]
To delete an entry from the Set Managers configuration, enter a blank field. The IP address of 0.0.0.0 does not remove the entry from the Set Manager Table.
The Cat216 4.0(1.1) device package will not work in HP OpenView Professional Suite 7.2 (C.02.17) and 7.3 (D.01.00 and D.01.02) because of an invalid HP OpenView device ID.
When you use the Switch Zoom menu (if TrafficDirector is installed) from CiscoView to view multiple switch ports, the default configuration for the Catalyst 1200 is to configure Statistics, Short-Term history, Long-Term history, and Host group. To see the Short-Term or Long-Term history from Traffic Monitor, use the Domain Manager to configure the Short-Term and Long-Term groups manually or use Segment Zoom to view the port first.
When you use the Segment Zoom menu from CiscoView to view the port segment, the default configuration for the Catalyst 1200 is to configure the Statistics, Short-Term history, Long-Term history and Host group. For the Catalyst 5000 it is Statistics, Short-Term history, and Long-Term history.
If you see the message "Error: Entry or Group not present in Agent" when invoking Segment Zoom, Switch Zoom, or Data Capture, the write community string might not be matched with the device. If the community string is matched and the problem still occurs, use the CiscoView Configure Device menu to see whether the RMON capability is enabled.
If you launch Switch/Port Zoom from CiscoView and then delete one of the RMON agents using TrafficDirector, you must relaunch CiscoView before launching Switch/Port Zoom again.
If you see the message "IP address is not set in sysIpAddr Mib variable," it is because the Catalyst 1200 SNMP agent did not store the correct IP address in the sysIpAddr MIB variable. You must use CiscoView to correct it. Select Configure>Device, enter the correct IP address in the corresponding field, and click Modify.
TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
The device agent does not update the IP address table of MIB-II properly and does not reflect the correct IP address information of all the device interfaces. You cannot view the correct IP Address information of the device by selecting Device>Configure>IP Address Table.
You cannot create new static entries for IP Route Table and ARP Table through CiscoView.
In the interface configuration (Port>Config>Interface), modifying the IP parameters always displays ian error message, but the modification is successful.
You cannot change the bridge type of the FDDI port to sr-only or srt.
You cannot change the bridge type of the Token Ring port to srtb or tb-only.
The system time configuration is not included as part of device configuration.
CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820---The General Bridge window shows the bridge information for VLAN1 only. Bridge information for other VLANs is not available.
CPW1220, CPW1420, Catalyst 1900, and Catalyst 2820---In the CDP Configuration Dialog, changing the transmission time of one port changes the transmission time of all ports. This is a feature of the implementation of the corresponding MIB objects in the device firmware. [CSCdi83959]
CPW1200, CPW1220, CPW1400, CPW1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820---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.
On the front panel display of the device, the Connect and Disabled LEDs on FDDI modules do not reflect the appropriate status.
Although a Monitor menu option is available for both FDDI and repeater ports, this feature is not supported on these modules. [CSCdj57452]
The Configure>Module option is supported for only one module type, even though it can be invoked for multiple module types.
There is a dependency between the CPW1420 and Cat2820. The CPW1420 device package will not run unless the Cat2820 package is installed. [CSCdj64496].
The Catalyst 2600 device package contains two versions of the enterprise MIBs for the Catalyst 2600 switch:
If you are using a MIB browser tool, you will see the MIB variables defined in each of the files above, under different branches, at the same time, although any particular Catalyst 2600 switch will respond to queries on only one of the MIBs, based upon the release of software in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to version 2.2.1 or later.
Under a heavy load condition, SNMP responses are slow. You might see an "error, no response since...." message in the CiscoView status window. Select Options>Properties and increase the Polling Frequency and Timeout values. [CSCdi57962]
If the number of the embedded RMON agent is over 50, you cannot create any new embedded RMON agent groups for the new port. Use the Domain Manager to uninstall the agent group from the unused port to free the memory resource.
If you launch Switch/Port Zoom (if TrafficDirector is installed) from CiscoView and then delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before launching Switch/Port Zoom again.
TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
When multiple ports are selected, the Port>Configure window does not display the Broadcast Suppression category. This category is available only for single port selection.
When you enable port security administration on a port, there might be timeouts. If this happens, increase the SNMP timeout value to approximately 10 seconds.
The WS-X2901 module shows the speed LED lit only when the speed is configured as 100 Mbps and the port is connected.
The Port Utilization tool has been removed from the Tools menu and is now available only on a per module basis on the Config>Module menu.
When you install CiscoView 4.1 and integrate it with HP OpenView 4.1.1, you will see an error relating to the C3_2_0.my MIB file display. This error is because of duplicate definitions in the Catalyst 3000 MIB files. To correct this problem, download a new copy of the C3_2_0.my MIB and README files from CCO at the following location: ftp://www.cisco.com/cisco/netmgmt/ciscoview/temp-smu/
CSCdj03981.README and CSCdj03981.tar.Z [CSCdi03981]
When you access a stack with six or more devices, there might be some significant performance problems. You can improve the performance by increasing the SNMP timeout settings.
The Catalyst 3000 software does not support RMON on either a stack or an ATM port.
You might notice timeout messages and SNMP Set Failed messages when using the EtherChannel Configuration tool. If this happens, increase the SNMP timeout values for better performance.
If you are running version 2.0(1) of the Catalyst 3000 software, you will not be able to drag a port to a VLAN that does not already have ports assigned to it. You can fix this problem by upgrading to a later release of Catalyst 3000 software.
If you are running version 2.0(1) of the Catalyst 3000 software, changes to Full/Half Duplex settings will not always be reported correctly. You can fix this problem by upgrading to a later release of Catalyst 3000 software.
If you are running version 2.0(1) of the Catalyst 3000 software, the SAID value entered when creating a new VLAN will be redisplayed as a different value. However, the VLAN will have been created with the SAID value you specified. You can fix this problem by upgrading to a later release of Catalyst 3000 software.
The Domain Configuration and EtherChannel Configuration tools are not supported on Windows 95.
Because of to restrictions in the Catalyst 3000 software, the WS-X3006B is displayed in CiscoView as a WS-X3006A.
If you launch Switch/Port Zoom from CiscoView (if TrafficDirector is installed) and then delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again. TrafficDirector works only if CWSI is installed.
CiscoView does not show the rear view of the Catalyst 3900 box.
When you attempt to drag port(s) to drop into one of the CRFs in the VLAN table, CiscoView might exit with an error. To work around this problem, first select the ports of interest, then bring the focus back to the VLAN Table window, and then drag the selected port(s) and drop them into the desired CRF.
The Configure... option under the Bridge Configuration category allows you to view a current configuration only. It reports an error when you attempt to configure new values for any parameter.
The Threshold Manager and TrafficDirector applications have not been fully tested with the Catalyst 3900.
While integrating some device packages with HP OpenView Network Node Manager, some Catalyst 5000 device-specific traps are not integrated into HP OpenView. [CSCdj63184]
After an online insertion/removal (OIR) event (also called a "hot-swap"), CiscoView does not show the correct module or port status. The only way to display the correct status is to reopen the device or relaunch CiscoView. [CSCdj39860]
ATM, FDDI, and CDDI do not support Broadcast Suppression.
In machines that do not have a /tftpboot directory (such as a PC), an error is displayed whenever the Upload/Download feature is invoked on a Catalyst 5000 module.
Do not use the Grapher in the CiscoView Monitor 10BaseT Group Switching Ethernet window. Use the Monitor or TrafficDirector tools (if TrafficDirector is installed) to see graphical views of the selected repeater ports.
When you use the Switch Zoom menu (if TrafficDirector is installed) from CiscoView to view multiple switch ports, the default configuration for the Catalyst 5000 is to configure Statistics only. To see the Short-Term or Long-Term history from Traffic Monitor, use the Domain Manager to configure the Short-Term and Long-Term groups manually or use Segment Zoom to view the port first.
When you use the Segment Zoom menu from CiscoView to view the port segment, the default configuration for the Catalyst 5000 is Statistics, Short-Term history, and Long-Term history.
If you see the "Error: Entry or Group not present in Agent" message when invoking Segment Zoom, Switch Zoom, or Data Capture, the write community string might not be matched with the device. If the community string is matched and the problem still occurs, use the CiscoView Configure Device menu to see whether the RMON capability is enabled.
When you select the repeater module port on a Catalyst 5000, it always uses the first port of the selected segment to create the RMON agent group.
If all Catalyst 5500 slots are populated with modules and you experience timeouts, increase the SNMP timeout value to 15 seconds.
The WS-X5213 and WS-X5213A modules show the 100 Mbps speed LED lit only if the speed is configured at 100 Mbps and the port is connected.
Opening the FDDI/Ethernet Bridge category under Configure>Device can display "unknown error." This is because of a problem with the device software.
If a general error (genErr) is displayed when you change vlanPortIslStatus, the selected port might not support ISL.
The values of ifAdminStatus and ifLinkUpDownTrapEnable cannot be changed on an ATM port.
Port duplex settings cannot be changed on ATM and FDDI ports.
The value of portSpanTreeFastStart cannot be changed on ATM and FDDI ports.
Configuring ports to unsupported speeds returns a general error (genErr). This is because of a problem in the device software.
The following list details the availability of Broadcast Suppression in terms of pps (packets per second) or % (percentage) for modules on Catalyst 5000 series switches. A plus sign (+) means available, while a minus sign (-) means not. Modules not on this list do not have Broadcast Suppression. The Broadcast Suppression feature is not available on ATM and FDDI. [CSCdi90909]
| Module | Packets per Second (pps) | Percentage | Note |
|---|---|---|---|
|
|
|
|
WS-X5013 | + | + |
|
WS-X5011 | + | - |
|
| | | % available with newer hardware only |
WS-X5113 | + | - |
|
WS-X5111 | + | - |
|
WS-X5213 | + | - |
|
WS-X5020 | + | - |
|
WS-X5114 | + | - |
|
WS-X5223 | + | + |
|
WS-X5224 | + | + |
|
WS-X5213A | + | - |
|
For devices that have an expansion module, the port numbering is not consistent with the management console. Ports 17 through 32 are listed in CiscoView as Repeater 2: Port 1 through 16. [CSCdi77159]
After the first reset of the device, you must set the rptrReset MIB variable to noReset (default value) before the next reset can be performed. This is because of to a problem on the device software and will be fixed in a later release. [CSCdi77452]
The CPW 1200/1400 and Cat 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these return errors.
When you enter 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 errors, use identical community strings in CiscoView and corresponding agents.
For this release, use the middle mouse button to drag on a PC. Only Catalyst devices (such as the CAT1200, CAT1600, CAT5000, CPW16) have defined their ports for dragging across devices.
When multiple ports of different types are selected, Port>Config might show duplicate categories.
The following firmware versions must be used in the 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:
No response from the device
After restarting the system, deactivate STP before you reconfigure. This problem is fixed in version 9.1 of the device firmware. [CSCdi41317]
The following network processor modules are supported:
The following network processor modules are supported:
A Cisco IOS defect causes CiscoView to not display the DS1 Line Channelized info when a T1/E1 port is configured for cas-group. This is applicable when the option is selected from the global menu item Connection Info or if it is selected through the Line_ds1 config dialog box. [CSCdj44707]
In the channel_modem view, CiscoView does not properly reflect the status of the T1/E1 channel_ports (timeslots) that have been configured for channel-group. This is a Cisco IOS software problem.
The following WAN interface cards are supported:
The following WAN interface cards are supported:
The following network modules are supporrted:
For the BRI interface in 8-port BRI cards or 4-port BRI card, the configure and monitor information shown in CiscoView is not correct. The information does not correspond to the correct BRI interface. This problem is present only if you use Cisco IOS Release 11.2 and above. This is a Cisco IOS software defect, CSCdj50307.
The hot swap feature is not available for stacked Cisco 3600 series routers.
Whenever the async/sync port configuration is changed, you must reopen the stack for CiscoView to update the async/sync port status. However, the hot swap feature for the async/sync ports is supported for individual Cisco 3600 series routers.
Also, whenever the async/sync port configuration is changed in a 16/32 port asynchronous network module, you must reopen the stack to obtain the latest state. However, the hot swap feature for the async/sync ports is supported for individual Cisco 3600 series routers.
The Logical view and Channel Modem Mapping view are not available for stacked Cisco 3600 series routers. This support is scheduled for a future release. However, for individual Cisco 3600 routers, Logical View is available if a digital modem carrier card is present, and Channel Modem View is available if a CT1/CE1 card is present.
The fix for defect CSCdi69480 (PRI/E1 interfaces missing in cardIfIndex table) is integrated into Cisco IOS Release 011.001(007) and above. The Cisco 3600 4.0(6.1) device package incorporates the fix and may not work properly with Cisco 3600 series routers running Cisco IOS versions below 011.001(007).
The following network processor modules (npm) are supported:
For 4000 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 follow: [CSCdi28566]
| Status | Status Color |
|---|---|
disabled | brown |
standby | brown |
connecting | blue |
active | green |
The following interface processors and port adaptors are supported:
When you try to open a horizontal-chassis device such as the Cisco 7204, 7206, or 7505 with a Fast Ethernet port adapter installed, the error message "can't read `DD(port-23.port-26.pos)': no such element in array" is displayed. To fix this, upgrade to the latest Cisco 7000 CiscoView package at http://www.cisco.com/cgi-bin/tablebuild.pl/cview40. [CSCdj16247]
No MIB object is associated with the test port on a CT3IP card. [CSCdj18638]
CiscoView always displays the multimode fiber SC type of ATM connector on AIPs, even when the media interface is of another type. [CSCdi53420]
For pa-1e3 and pa-1t3 cards, DS3 Configuration does not appear in the config rport dialog box. Also, DS3 Current Statistics and DS3 Total Statistics do not appear in the monitor rport dialog box. [CSCdj60001]
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 follow. [CSCdi28566]
| Status | Status Color |
|---|---|
disabled | brown |
standby | brown |
connecting | blue |
active | green |
CiscoView displays an FEIP2-FX interface processor as an FEIP2-TX for all Cisco IOS versions before Release 11.1(11)CA. [CSCdj15831]
The feip-fx card does not appear in CiscoView. When the Cisco 7000 series device comes up, you might see the error message "no such element in array." [CSCdj61077]
For devices running Cisco IOS Release 10.2, a FIP card's PhyA and PhyB LEDs do not appear lit in CiscoView. [CSCdj23023]
When performing the Squeeze operation on a Flash card, the error message "Failed to Squeeze. Try increasing the timeout property under Options in the Main window" might be observed even though the operation succeeds. [CSCdj03172]
On the Cisco 7513 and Cisco 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 it is in use. [CSCdi49049]
An invalid port level FSIP Config category will appear for devices with MIP cards running Cisco IOS software earlier than Release 11.1. The dialog box shows N/A for variables displayed in it, as these do not apply. [CSCdj23970]
CiscoView might display a 4-port FastSerial port adapter (pa-4t) as a HSSI adapter (pa-ah1t). [CSCdj17487, CSCdj17516]
After an online insertion/removal (OIR) event (also called a "hot-swap"), CiscoView does not show the correct module or port status. The only way to display the correct status is to reopen the device or relaunch CiscoView. [CSCdj39860]
In the DS1 Configuration dialog, dsx1LoopbackConfig is reported with an unknown enumeration. [CSCdj17466]
Ensure you are using the latest LS1010 device package (version 1.8). You can download this package from CCO. [CSCdj59465]
To configure an LECS address for LS1010 from CiscoView, ServiceId needs to be the following: 10.1.3.6.1.4.1.353.1.5.1.<Index>, where Index is the row differentiator for configuring multiple LECS addresses. Index is an integer.
From CiscoView for LS1010, the ATM Traffic Descriptor table does not show any rows. This is an agent bug. [CSCdj00685]
By default, CiscoView displays two power supplies for a Cisco 7000 router running Cisco IOS Release 10.2 or earlier. With Cisco IOS Release10.3 or later, power supplies are displayed based on ciscoEnvMonSupplyState values.
The creation of the full-text search database (Find option) in online help might take several minutes, depending on the number of devices you have installed.
Because of the way a master CiscoView contents file is used by the software when multiple CiscoView device package help files are present, the list of files to include when setting up a customized find operation contains multiple items, called CiscoView. [CSCdj62089]
The Cisco 4000 Series help incorrectly states that they are stack devices. There is also a link to the StackMaker help that does not work. To reach StackMaker help, ensure the StackMaker help package is installed and select Help>Contents to locate the StackMaker help topics. [CSCdj01872]
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Mon Nov 15 14:17:56 PST 1999
Copyright 1989-1999©Cisco Systems Inc.
