|
|
These release notes describe the new features and caveats for the components of CiscoWorks for Switched Internetworks (CWSI) Release 2.1 (Windows NT), which include the following:
This document contains the following sections:
In addition to these release notes, the CWSI documentation set includes the following:
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 on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The online help supports Netscape 3.0 and 4.0 and Internet Explorer 4.0 (not Internet Explorer 4.0 with Active Desktop). It does not support Internet Explorer 3.0.
Some of the error messages do not have online help. The Help button on the error message window is unhighlighted (grayed-out).
CWSI 2.1 is a network management product that focuses on managing Cisco Catalyst and Light Stream switches. As part of the CWSI product, CiscoView also provides basic device management of routers. Refer to the CiscoView section of this release note for more information.
New devices are supported on all platforms unless otherwise noted. A README file describing device support is included on the Cisco Connection Online (CCO) service.
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 CCO.
Review the following information before installing CWSI 2.1 and its components.
Before installing CWSI 2.1 you must install OBDC and Service Pack 3. See the Installing CWSI with CRM document.
If you wish to use the Trend Reporting capability of TrafficDirector, you must purchase and install the Microsoft SQL Database.
If you receive the message "OpenView symbol registration error," uninstall the Cat216.pkg. This error is due to a bad Cat216.pkg that comes with CV4.1.
If you attempt to log in before CWSI 2.1 daemons have fully initialized and registered with CORBA, an error message is generated. To resolve this, wait until the daemons have initialized.
When integrating the Cat5500.pkg and Ls1010.pkg from the CWSI CD with OV Professional Suite, some MIB compilation errors relating to the PNNI MIB might appear. To avoid these errors, upgrade to the Cat5500/LS1010 1.8 or later packages from CCO.
In order for CWSI to discover your network, you need provide CWSI with a starting point. The starting point is called the seed device IP address, and you input it during installation. You can select any device in your network as the seed device.
For LANE discovery to work, the following software versions are needed on the switches:
| Device | Version |
|---|---|
| LightStream 1010 | Cisco 105 Release 11.2(8) |
| Routers | 11.2(10) |
| Catalyst 5000 | NMP (2.4.3)/ATM 3.2(5) |
| Catalyst 3000 | 2.2(2) |
The seed device that you supply during the CWSI installation is very important for the product to operate correctly. Verify that the seed device meets the following requirements before installing the CWSI product:
All CWSI 2.1 components are Year 2000 compliant.
During CiscoView installation, select the .pkg files you need based on the devices you plan to use in your network and whether you are going to run TrafficDirector.
In order to launch TrafficDirector Port Zoom from the CWSI Topology window, you must first install the CiscoView td_intg package. Select Help>About to check whether this package is installed. If it is not installed, you must install it from the CWSI CD. If you selected all packages when installing CWSI, then this package is installed.
There is no GUI interface available for entering the default community strings to be used for CWSI discovery and configuration. You must edit the communities file manually. This file is called communities.dat and is located in the install directory\etc\cwsi\ directory. If the read community strings in your network are different from the default "public," you must edit this file before starting your first discovery.
After installing CWSI 2.1, you must reboot your machine for the installation to take effect.
You can uninstall CWSI if necessary. Launch the uninstallation program from the Start Menu rather than Windows NT Explorer.
After uninstalling CWSI, some directories and files might remain. If this is the case, delete these directories and files manually. If you are unable to delete them and the message "the file is in use" appears, reboot your machine. You should then be able to delete the remaining files.
Before providing procedures for troubleshooting, this section includes a description of the CWSI daemons and their interactions with clients.
Asynchronous Network Interface (ANI or AniServer) is a multithreaded Java program. It is installed in Windows NT as a daemon process and runs in the background, beginning discovery as soon as the machine boots. ANI is responsible for the discovery of the network, both of devices and users. It is also responsible for all communication with the clients.
The database engine (dbEng50) is responsible for checkpointing all ANI information into the database. For ANI, this is a checkpoint only. ANI performs all of its operations from the data stored in memory. The database stores user-entered information and allows ANI to load its data model quickly into memory upon a subsequent restart. (The CRM database engine has the same name, so your system should be running two processes with this name.)
The CORBA agent (OsAgent) is responsible for being the traffic cop of interprocess communication messages. All servers must register with the OsAgent. All clients looking for service find it with the help of the OsAgent. The CWSI login window is used to register the CWSI client with OsAgent and to indicate that it is searching for an ANI named AniServer.
To see all servers registered with CORBA, and where they are located, run osfind.exe from a DOS window. This very useful troubleshooting tool is found in <CWSIROOT>\bin
RTPoller is used for periodic polling of the network for status of devices and links.
The event channel (EventChannel) is used to send events to all servers and clients who have registered with it.
The following command-line scripts control the CWSI daemons:
To use these scripts, open a DOS window Command Prompt. Type stopcwsiserver to stop the CWSI Server Processes. When the DOS prompt returns, all the daemons have been stopped. To restart the processes, type startcwsiserver and wait until the DOS prompt returns.
If, after running osfind, you see that the AniServer or one of the other servers is missing, or if in the Windows NT task manager you see that your database engine is missing, stop the CWSI servers and then start them again.
If you have just rebooted your machine and are unable to log in to AniServer, ANI may not yet be ready to receive messages. Wait five minutes, then try again.
If you are still unable to log in, run the osfind program to verify that AniServer has registered with the OSAgent. If so, verify that the name of AniServer in the login box is the same name as the name registered with OsAgent.
If you do not find AniServer, run the stopcwsiserver script (see "Stopping and Starting CWSI Daemons," earlier in this section), then run the startcwsiserver script. Run osfind again. If AniServer is there, log in to CWSI. If AniServer is still not registered, it may mean that you have a corrupt database.
To determine whether you have a corrupt database, first turn on trace to see if messages indicate this condition. If you are still unable to verify the status, contact your Cisco TAC for instructions.
ANI cannot perform effectively with a corrupt database. If you determine you have a corrupt database, you need to create a new one.
To create a new database, use the following steps:
Step 1 Run the stopcwsiserver script.
Step 2 Delete the current database <CWSIROOT>\db\data\cwsi.db.
Step 3 Copy the file cwsi_ini.db to the file cwsi.db. This is a fresh database file.
Step 4 Delete the file cwsi.log.
Step 5 Reboot your machine.
Asynchronous Network Interface (ANI) begins the discovery process immediately after rebooting, while the system is initializing. It runs as an NT service, as do the other daemons required for the correct operation of CWSI. It may take up to five minutes (longer for a very large network) for the initial discovery process to complete.
To start CWSI, select Start>Prog>CWSI 2.1>Start CWSI.
The login username parameter is ignored, but the server name must remain as it appears. This login is used to register CWSI as a client of ANI (named ANIServer). The interprocess communication is done through CORBA.
If you get an error message while attempting to log into CWSI, ANI is simply not yet ready to receive requests from its clients. Wait five minutes and try again.
To start the CWSI applications from the CWSI map window, select Tools>application name, or click the appropriate icon on the toolbar. You can also launch TrafficDirector and CiscoView in the following ways:
Use the following steps to start UserTracking:
Step 1 From the Windows NT Start menu, select Start>Programs>CWSI 2.1>Start UserTracking.
Or from the CWSI map window, select Tools>UserTracking or click the UserTracking icon on the tool bar.
Step 2 Select Action>Discover>End-User Nodes to start discovery.
Wait a few minutes until a message indicates that discovery has completed.
Step 3 To display the end-user nodes discovered in the network, select Action>Display>All Entries.
If your network is very large, you might want to create a query for UserTracking so that you do not have to display all the users at once. To limit the size of the table displayed, see the UserTracking for End-User Devices publication for more information about creating queries.
You can select and launch both CiscoView and TrafficDirector from HP OpenView Network Node manager. The additional CWSI functions, including the CWSI topology mapping services, VlanDirector, AtmDirector, and User Tracking, must be started from the main CWSI interface, which is launched from Windows NT as part of the normal start-up procedures for CWSI.
TrafficDirector and CiscoView are device-focused applications and are easily launched from HP OpenView based upon the device discovery process within HP OpenView. The additional CWSI functions require more detailed network-wide topology data that HP OpenView does not provide. The CWSI discovery and database services must be running for these additional applications to function, which makes it necessary to start these from the main CWSI window.
This section contains important information about CWSI network map.
This section provides device-specific caveats about the CWSI network map.
Moving ports between VLANs will fail on Catalyst 3000 switches running software versions prior to Release 2.2(2).
Not all modules are shown in the Node Attributes window. You can access the node attributes window by selecting the device and clicking the right mouse button. [CSCdj40028, CSCdj40030]
The following are LAN Emulation (LANE) issues:
This section describes new features and provides notes and caveats for the VlanDirector application.
VlanDirector provides the following new features:
This section provides important notes and caveats about the VlanDirector application.
The VlanDirector application permits you to display and configure the VLANs in your network. It requires at least one VTP server for each VTP domain. Other switches may be configured as VTP clients to participate in the VTP protocol, or may be configured in transparent mode, ignoring the VTP advertisements.
You must use the VlanDirector menu properties dialog to enable VLANs on switches in transparent mode.
If there is an LS1010 switch in your network which is unreachable, VlanDirector will not highlight trunk links in the network.To resolve this, ensure that CWSI can talk to all LS1010s in the network.
Upon successful creation of a new VLAN and its associated ATM VLAN through CWSI, the VLAN name is displayed in the VlanDirector Names window under a VTP Domain folder. However, its associated ATM VLAN is displayed under a Fabric folder.
CWSI cannot ensure the bridging of a VTP VLAN to an ATM VLAN until LANE LEC clients (created outside of CWSI) join the LANE services (created by CWSI). Once the LANE LEC clients are created (using the CLI or through enabling VTP), doing a Rediscover Map (on the CWSI Topology window) and a Refresh (on the VlanDirector) will bind the ATM VLAN to the VLAN and show it as one in the Names window.
Although CWSI supports SSRP, CWSI does not support LANE on a fabric containing multiple active LECS (that is, acting as master). When CWSI LANE discovery runs on such a fabric, CWSI picks and processes the first active LECS it encounters and ignores the other active LECS. All backup LECS will be processed by CWSI.
When multiple LES/BUS servers are specified to be configured as part of the CWSI ATM VLAN configuration, CWSI processes these configurations in parallel and thus cannot guarantee that the ORDER field which corresponds to each server matches the actual priority order of the created server.
The Discrepancy Report does not include any LANE discrepancies.
LECS addresses configured on LS1010s are not deleted when an LECS is deleted. This will be fixed in the next release.[CSCdj61498]
When an ATM fabric name is changed through ATMDirector, it is not automatically reflect in CWSI. The new ATM fabric name will be correctly displayed in the VlanDirector Names window after you do a Refresh in VlanDirector. [CSCdj68621]
UserTracking is a new application within CWSI that allows you to gather and locate information about end user stations attached to switches throughout your network.
This section describes the features and provides notes and caveats for the UserTracking application.
This section provides note and caveats about the UserTracking application.
UserTracking discovers and displays MAC addresses of devices (not including switches and routers) that are attached to switches. It associates the VLAN assigned to the switch port with the attached MAC address. It then finds the IP address(es) associated with that MAC address by reading the router ARP caches.
The changes you make in UserTracking are effective only when you connect a machine to a dynamic port. When you connect a machine to a static port, the machine is connected to the VLAN associated with that port; none of the UserTracking information about the MAC-to-VLAN mapping is used.
The MAC-to-VLAN mapping information in UserTracking is used only for connections to dynamic ports.
UserTracking cannot discover the MAC addresses of devices on VLANs that exist only on switches running VTP in transparent mode (sometimes called local VLANs).
There must be a router present in your network for UserTracking to display any entries.
Catalyst 5000 series switches must be running software release 2.3 or higher.
If you export a table in UserTracking and try to read it with Microsoft Excel version 7.0, by default Excel formats the data in the Port column as a date if the Port column uses a module/port format. For example, the field might contain the entry 2/3, to which Excel applies its general format; 2/3 will be interpreted as a date and it will be expanded to 2/3/1997.
One way to resolve this is in Excel. When you import the file in Excel, you go through the Text Import Wizard. In Step 3 (of 3), you can specify the format to use to format each column being imported. Scroll the window until the Port column is visible and select it. In the Column Data Format box, select Text. Excel will then treat the Port column as text rather than converting it to a date.
This section describes new features and provides notes and caveats for the TrafficDirector application.
TrafficDirector includes the following new major features and enhancements.
This section provides note and caveats about the TrafficDirector application.
TrafficDirector 5.1 does not support the creation of Alarms and Events for any device running IOS 11.1 or greater. TrafficDirector assumes that the RMON statistics group is always supported, which is not the case for IOS.
Deleting all TRAPs from an agent does not delete the ADMIN entry.
In Configuration Manager, when specifying the analyzer port number for a roving agent, you must specify a two-digit port number. For example, for Module 5 port 2, you would specify 5/02 as the module/port.
Only the first eight characters of any agent name, switch, or port are displayed in Configuration Manager.
The CWSI 2.1 TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the Windows NT or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete $NSHOME/usr/pingoff.
To integrate the TrafficDirector application with other NMS platforms, refer to "Integrating Traffic Director with Other Managers" in Appendix C of Using TrafficDirector.
Traffic Director does not support integration with SNMPc.
When you try to print a TrafficDirector screen that contains more than one graph per file, TrafficDirector drops the last letter of the name you specify and replaces it with a number. It creates a separate file per graph.
When setting thresholds on a device with a large number of ports (>100), you may encounter performance problems. The thresholds will be installed, but this may take up to five minutes. [CSCdj47127]
Table 1 indicates whether you need to use either a shared property file or a custom property file when configuring a specific property for agent or switch type.
| Agent Class | Properties | ||||||
|---|---|---|---|---|---|---|---|
| Monitor Domains | Domain Traps | Report Logging | RT Delays | RT Logging | Proxy SNMP | Resource Traps | |
| Agent | Shared | Shared | Shared | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. | Custom Mgt Intf. |
| Frm-Rly | Shared | Shared | Shared | Custom Mgt Intf. | Custom | Custom Mgt Intf. | Custom Mgt Intf. |
| DLCI (Frm-Rly) | Protocol domains from Shared | Custom | Custom | N/A | N/A | N/A | N/A |
| Switch | Shared | N/A | N/A | N/A | N/A | N/A | N/A |
| Switch Ports | Shared is copied | Custom | Custom | N/A | N/A | N/A | N/A |
Table 2 lists the devices supported by TrafficDirector.
| Device | RMON Support1 | Roving Support |
|---|---|---|
| Catalyst 1200: | Full RMON I | n |
| Catalyst 1600: | Mini-RMON | y |
| Catalyst 1800: | Mini-RMON | y |
| Catalyst 1900: | Mini-RMON | y |
| Catalyst 1912: | Mini-RMON | y |
| Catalyst 2100: | Proxy RMON | y |
| Catalyst 2800: | Proxy RMON | y |
| Catalyst 2820: | Mini-RMON | y |
| Catalyst 2900: | Mini-RMON | y |
| Catalyst 2926: | Mini-RMON | y |
| Catalyst 3000: | Mini-RMON | y |
| Catalyst 3100: | Mini-RMON | y |
| Catalyst 3200: | Mini-RMON | y |
| Catalyst 3900: | Mini-RMON | y |
| Catalyst 5000: | Mini-RMON | y |
| Catalyst 5002: | Mini-RMON | y |
| Catalyst 5500: | Mini-RMON | y |
| Catalyst 5505: | Mini-RMON | y |
| CPW2200: | Mini-RMON | y |
| 2500 Series | Full RMON I | n |
Proxy RMON is not supported for Catalyst 1700 in this release.
The following installation and startup issues exist for this release of TrafficDirector:
When a property file is installed on a probe it is applied to all ports on that probe. If you have a multi-port probe, be aware that when defining the properties, the last property files to be installed are applied to all ports on that probe. To avoid conflicts, either ensure that the property files for each port are identical or define properties for only one port on the probe.
TrafficDirector can be used to set TRAPs on non-RMON MIB objects. (For example, a non-RMON object would be ifOutoctets, which is the number of bytes within a packet transmitted out of a router or switch port.)
To set a TRAP on a non-RMON OID, do the following:
Step 1 Edit the $NSHOME/usr/usrtrap.oid to include the non-RMON OID MIB.
Step 2 Access Configuration Manager.
Step 3 Select the switch, then select Custom.
Step 4 Select Property.
Step 5 In the bottom half, select Add.
Step 6 In the Stats Type field, select User Defined, then select the non-RMON OID from the trap variable field.
Step 7 Select OK.
Step 8 Select Install.
An alternate way to do this is to add the MIB to the $NSHOME/usr directory in the same format as the other '*.mib' files. You can then use the Proxy SNMP feature with a probe to configure the TRAP.
If you wish to perform roving on your switch, use either the 6010E2 or 7100HD probes. Other probe models do not support roving.
TrafficDirector 5.1 roves to the specified port when you select data capture from the main TrafficDirector screen. For other applications, such as All Talkers, perform roving manually from Configuration Manager or launch the application from Traffic Monitor. [CSCdj62108]
If you wish TrafficDirector 4.1.3 and TrafficDirector 5.1/CWSI 2.1 to co-exist on the same machine, use the following methods for setting the NSHOME environment variable:
| System Variable | User Variable |
|---|---|
| C:\TRAFFDIR | Not Set |
| Not Set | C:\TRAFFDIR |
| C:\TRAFFDIR | C:\TRAFFDIR |
| System Variable | User Variable |
|---|---|
| C:\CWSI21 | Not Set |
| Not Set | C:\CWSI21 |
| C:\CWSI21 | C:\CWSI21 |
The Catalyst 3900 supports the following Token Ring RMON MIB groups only:
Trying to set thresholds on objects in any of the other Token Ring groups cause an "Install aborted unexpected SNMPAPI Error" error. [CSCdj52569]
This section describes new features and provides notes and caveats for the AtmDirector application.
This section describes the new features of the AtmDirector application.
AtmDirector now provides a main AtmDirector naming window which has a list of all Atm Fabrics and ATM-VLANs within that fabric in form of a tree structure. The PNNI peer group information also appears in the lower section of the window. You can use this window for summary information and for navigating to map windows.
The consolidated status of the ATM-VLANs is reflected in the main window on the ATM-VLAN cloud icon. If there are any ATM-VLAN components that are down, the icon turns red.
Fabric name can be changed by editing the name in the tree widget. This can be accomplished by clicking on the fabric name again after selecting it and then typing in a new name.
VC trace now displays the trace on the main fabric map showing the VPI/VCI values that are used between devices.
VC list between devices feature allows you to click links between two end devices and view the list of VCs between the two devices.
Enhanced traffic parameter setup is provided during configuration of SPVC/SPVP. You can also add new Traffic table rows in the agent for future use.
Link status is also polled periodically and link downs are displayed with a dashed line.
The AtmDirector application now displays a topology map for each ATM-VLAN showing all the ATM-VLANs components and the links between those components.
Status of each ATM-VLAN component is displayed as background colors on the corresponding iconnettes.
Context based popup menus are available by pressing the right mouse button while moving the mouse over the ATM-VLAN components.
The map contains menu options for Status, Diagnosis and Performance tools for debugging the LANE network.
The AtmDirector application now displays a logical PNNI map with the node topology with all the nodes in one Peer Group.
AtmDirector provides configuration and display of various PNNI properties in the PNNI network.
This section provides note and caveats about the AtmDirector application.
ATM-RMON features are not available in this release, but will be available in the following release. This is reflected by the grayed-out menu options listed below:
The polling feature is not supported for nodes displayed in the PNNI map. Nodes in the PNNI map show up as light blue, indicating that the PNNI node operational status is not polled.
The following caveats pertain to the ATM main window:
The following caveats pertain to the ATM fabric map:
In some cases the while displaying the Control Connection VCs, the Destination Host name field is blank. This is due to the host name not being correctly resolved from the Atm Address.
The following caveats pertain to PNNI:
This section describes new features and provides notes and caveats for the CiscoView application.
The number of MIB objects that can be queried has been increased from 512 to 2048.
| Caution Before installing CiscoView devices, read the caveats in "Troubleshooting" on page 32 |
This section provides notes and caveats for the CiscoView application.
CiscoView devices support Cisco IOS Software Release 10.2 through Release 11.2. Cisco 4000 series devices require Cisco IOS Release 10.3 or later.
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:
New devices are supported on all platforms unless otherwise noted. A README file describing device support is included on the Cisco Connection Online (CCO) service.
The following devices are supported by CiscoView:
www.cisco.com) periodically for download information on the latest device support and upgrades.
Table 3 describes the applications supported by CiscoView.
| Application | Description | Cisco IOS | Device Support |
|---|---|---|---|
| Threshold Manager | Threshold management application that monitors the availability and performance of Cisco devices | Release 11.1 or 11.2 with RMON events and alarms group support | All devices with appropriate Cisco IOS or RMON features |
| StackMaker | StackMaker manages the device membership in a Cisco stack. | 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 | The Flash File System provides file copying and editing features for the 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers. | Releases 10.0 through 11.2 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
Autodiscovery, after clearing the discovery log, either finds SNMP devices as ping nodes or finds nothing. 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]
If you cannot open a device in CiscoView, a message indicates that the device is unmanageable and specifies one of the following reasons:
When the SNMP Debug option is enabled, it displays a separate pop-up console window which shows the SNMP traffic to and from the device. Closing this will cause CiscoView to exit.
If you start CiscoView on the interface icon of an expanded node (for example, foo.cisco.com:1), you will not be able to telnet to that device because telnet thinks it should use port 1. Do not start CiscoView on device interfaces. [CSCdi56385]
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.
Do 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.
To delete an entry from the Set Managers configuration, enter an IP address of 0.0.0.0. The agent on the devices will not accept a blank entry for an IP address. [CSCdj03444]
When using the Switch Zoom menu (if Traffic Director 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 Configuration Manager to configure the Short-Term and Long-Term group manually or use Segment Zoom to view the port first.
If you launch Switch/Port Zoom from CiscoView and then delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again.
If you see an "IP address is not set in sysIpAddr MIB variable" message, it is because the Catalyst 1200 SNMP agent does not store the correct IP address in the sysIpAddr MIB variable. To correct this, use CiscoView to select Configure>Device, enter the correct IP address in the corresponding field, then click Modify.
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 will not be able to view the correct IP Address information of the device by selecting Device>Configure>IP Address Table.
You will not be able to create new static entries for IP Route Table and ARP Table through CiscoView.
In the interface configuration (Port>Config>Interface), modification of the IP parameters always results in an error message, but the modification completes successfully.
You will not be able to change the bridge type of the FDDI port to sr-only or srt.
You will not be able to 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 will change 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 there is a Monitor menu option available for both FDDI and repeater ports, this feature is not supported on these modules.
The Configure>Module option is supported for only one module type, even though it can be invoked for multiple module types.
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 above under different branches at the same time. However, 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.
If you launch Switch/Port Zoom (if Traffic Director is installed) from CiscoView and then you delete one of the RMON Agents using TrafficDirector, you must relaunch CiscoView before attempting to launch Switch/Port Zoom again.
When multiple ports are selected, the Port>Configure window will not display the Broadcast Suppression category. This is available for single port selection only.
When enabling port security administration on a port, timeouts may occur. If this happens, increase the SNMP timeout value to approximately 10 seconds.
The WS-X2901 module will show the speed LED lighted only when the speed is configured as 100Mbps and the port is connected.
When accessing a stack with six or more devices, there might be some significant performance problems. The performance can be improved 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. This problem can be fixed 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. This problem can be fixed 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. This problem can be fixed by upgrading to a later release of Catalyst 3000 software.
Due 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 Traffic Director 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 attempting 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 Bridge Configuration category allows you only to view a current configuration. 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.
In some cases, 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 re-open the device, or relaunch CiscoView. [CSCdj39860]
ATM, FDDI, and CDDI do not support Broadcast Suppression.
For machines that do not have a /tftpboot directory (such as a PC), an error will be displayed whenever the Upload/Download feature is invoked on a Catalyst 5000 module.
When using the Switch Zoom menu (available only if Traffic Director 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 Configuration Manager to configure the Short-Term and Long-Term group manually or use Segment Zoom to view the port first.
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.
TrafficDirector is not integrated with the Catalyst 5505 Ciscoview device package [CScdj68297].
The WS-X5213 and WS-X5213A modules show the 100 Mbps speed LED lighted only if the speed is configured at 100 Mbps and the port is connected.
If a general error (genErr) is displayed when changing vlanPortIslStatus, the selected port may not support ISL.
The values ifAdminStatus and ifLinkUpDownTrapEnable cannot be changed on an ATM port.
Port duplex settings cannot be changed on ATM and FDDI ports.
The value portSpanTreeFastStart cannot be changed on ATM and FDDI ports.
Table 4 details the availability of Broadcast Suppression in terms of pps (packets per second) or % (percentage) for modules on Catalyst 5000 series switches. The following conventions are used:
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 | + | - | |
| WS-X5010 | + | + | % available with newer hardware only |
| WS-X5113 | + | - | |
| WS-X5111 | + | - | |
| WS-X5213 | + | - | |
| WS-X5020 | + | - | |
| WS-X5114 | + | - | |
| WS-X5223 | + | + | |
| WS-X5224 | + | + | |
| WS-X5213A | + | - |
Configuring ports to unsupported speeds returns a general error (genErr). This is due to a problem in the device software.
For NetBeyond Fasthub 100+ and 300 Series 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 a NetBeyond Fasthub 100+ and 300 Series device, you must set the rptrReset MIB variable to noReset (default value) before the next reset can be performed. This is due to a problem on the device software and will be fixed in a later release. [CSCdi77452]
On a Catalyst 116 and CPW 316 fasthub, to delete an entry from the Set Managers configuration, enter a blank field. The IP address of 0.0.0.0 will not remove the entry from the Set Manager Table.
The CPW 1200/1400 and Catalyst 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these will display error messages.
When multiple ports of different types are selected, Port>Config might show duplicate categories.
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.
When you try to open a horizontal-chassis device such as the 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 bug, upgrade to the latest 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]
CiscoView displays an FEIP2-FX interface processor as an FEIP2-TX for all Cisco IOS versions before Release 11.1(11)CA. [CSCdj15831]
An invalid port level FSIP Config category will appear for devices with MIP cards running Cisco IOS software before Release 11.1. The dialog shows N/A for variables displayed in it, as these are not applicable to it. [CSCdj23970]
To configure an LECS address for a LightStream 1010 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, ATM Traffic Descriptor table does not show any rows. This is an agent bug. [CSCdj00685]
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, all 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.
|
|
