CiscoWorks for Switched Internetworks (CWSI) 1.3.1 contains CiscoView 4.0, VlanDirector 1.4, and TrafficDirector 4.1.3a software releases. These release notes describe the features, caveats, and modifications in these software releases.
This section contains the following information for CWSI:
CWSI provides the following new features:
CWSI 1.3.1 requires Solaris 2.5 or higher. For Solaris 2.5.1, a minimum of the development environment must be installed.
In addition to the devices already supported by CWSI, CWSI 1.3.1 supports the Catalyst 3000, Catalyst 3100, Catalyst 3200, Catalyst 5500, and Catalyst 5002 devices.
The "cgthree" video graphics controller card is no longer supported. To find out whether the system has this card installed, type the following at the UNIX prompt:
# sysdef -d | grep cgthree
- If the following message appears, the system has the unsupported card:
Node 'cgthree', unit #-1 (no driver)
- Use the "cgsix" video graphics controller card instead.
This section contains the following information for CiscoView:
Additional documentation for CiscoView includes the CiscoView Release Note for software release 4.0, the CiscoView Getting Started Guide, and online help. The primary documentation for CiscoView is the online help. If you have documentation feedback, please email comments to bug-doc@cisco.com.
Documentation can also be found on the Cisco Enterprise Customer Documentation CD or on Cisco Connection Online (CCO). Refer to the "Cisco Connection Online" section for the CCO web address.
CiscoView has these new features:
- Scrolling to support the Catalyst 5500 display
- Composite view to support the display of a LightStream 1010 inside a Catalyst 5500
- Stacked view to support StackMaker and the display of the FastHub 100+, FastHub 300 series, 3600, 3620, 3640, 1600, Catalyst 1900, Catalyst 2820, CPW 1220, and CPW 1420 devices.
- Support for the Catalyst 5002
- Support for Catalyst 5000 series software Release 2.2 software and its supporting line cards
- Support for the WS-X5223, WS-X5224, WS-X5213A, and WS-X5013 modules
If you cannot open a device in CiscoView 4.0, you see 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.
- Check your device package and compare the date to the CCO device package version. Upgrade your device package to the latest version, if required.
General notes and caveats for Enterprise Network Management products are described below.
CiscoView and Internationalization
CiscoView does not support internationalization.
CiscoView Times Out
In high traffic situations, you might experience timeouts. To increase the timeout period, select Options>Properties from the CiscoView menu and change the value for the Timeout field.
You should not reduce the physical view polling interval (retries*timeout), especially if you experience timeouts; this can exhaust resources on Windows and result in a general error.
Dragging Ports
For this release, use the middle mouse button to drag on UNIX. Only certain devices (such as the Catalyst 1200, Catalyst 1600, Catalyst 5000, CPW 16) have defined ports for dragging across devices.
SunNet Manager (SNM)
SNM needs patch 104018-02 from Sun Microsystems to prevent SNM from hanging during discovery under certain circumstances.
Open Look
The caveats for Open Look are as follows:
- Popup menus might be out of focus. To correct focus, move your mouse pointer out of the window and back into the menu.
- Popup menus occasionally lose events. The menus always appear, but might not always let you select anything. When this occurs, move your mouse pointer out and back into the menu to start tracking the events. [CSCdi50535]
Popup Menu Titles
Popup menu titles are raised; users might mistake them for menu items. [CSCdi53475]
Running CiscoView 4.0 with Little Swap Space
If the server or display workstation is running out of swap space, you see a message such as "X error: Couldn't allocate color cell," and CiscoView core dumps. If you are running other applications, you might want to check your swap space occasionally.
To check swap space on a Sun Solaris 2.x workstation, enter the following:
hostname% swap -l
If your system is running out of swap space (for example, only 200 KB of swap space remains), quit some of the other applications you are running or increase your swap space, if possible. [CSCdi37063]
Threshold Manager
The caveats for Threshold Manager are as follows:
- 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 verify that the deletion occurred by retrieving the threshold settings after the deletion.
- Cisco 7000 devices do not display Threshold Manager in the CiscoView pulldown menu. To correct this, refer to the CiscoView documentation for information on how to modify the c7com.dd file or update the 7000 package. [CSCdi61080]
- New policies are always added to the display list. To view these policies, exit from the Configure Thresholds window, and then reopen it. [CSCdi62741]
- Policy filenames do not match if the IP address is used. Use the hostname 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 only save it 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]
Following are general notes and caveats for the Cisco Workgroup family of products.
Catalyst 1200
The caveats for the Catalyst 1200 are as follows:
- When you see the Switch Zoom menu 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 group manually or use Segment Zoom to view the port first.
- When you see 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 series switches it is Statistics, Short-Term history, and Long-Term history.
- If you get the "Error: Entry or Group not present in Agent" message when invoking Segment Zoom, Switch Zoom, or Data Capture, the write community string may not match with the device. If the community string is matched and the problem still happens, use the CiscoView Configure Device menu to see if the remote monitoring (RMON) capability is enabled or not.
- 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 "IP address is not set in sysIpAddr Mib variable," it means that the Catalyst 1200 SNMP agent does not store the correct IP address in the sysIpAddr Management Information Base (MIB) variable, so you have to use CiscoView to correct it. Go to Configure>Device, enter the correct IP address in the corresponding field, and click Modify.
- You cannot launch TrafficDirector 3.3 for interfaces with ifIndex values greater than 1000.
Catalyst 1800
The caveats for the Catalyst 1800 are as follows:
- 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 through Device>Configure>IP Address Table.
- New static entries for the IP Route Table and Address Resolution Protocol ARP Table cannot be created through CiscoView.
- In the interface configuration (Port>Config>Interface), modification of the IP parameters always results in an error message being displayed, but the modification is done successfully.
- The bridge type of the Fiber Distributed Data Interface (FDDI) port cannot be changed to sr-only or srt.
- The bridge type of the Token Ring port cannot be changed to srtb or tb-only.
- The system time configuration is not included as part of device configuration.
Catalyst 1900, Catalyst 2100, Catalyst 2800, EtherSwitch 1200, and EtherSwitch 1400 Series Devices
The caveats for the Catalyst 1900, Catalyst 2100, Catalyst 2800, EtherSwitch 1200, and EtherSwitch 1400 series devices are as follows:
- CPW 1200, CPW 1220, CPW 1400, CPW 1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The General Bridge window shows the bridge information for VLAN 1 only. Bridge information for other VLANs is not available.
- CPW 1220, CPW 1420, Catalyst 1900, and Catalyst 2820--In the Cisco Discovery Protocol (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]
- CPW 1200, CPW 1220, CPW 1400, CPW 1420, Catalyst 1900, Catalyst 2100, Catalyst 2800, and Catalyst 2820--The Spanning-Tree Protocol window for switched ports is available for ports in VLAN 1 only. This window does not show valid information for ports not in VLAN 1.
CPW 1420 and Catalyst 2820
The caveats for CPW 1420 and Catalyst 2820 are as follows:
- On the front panel display of the device, the Connect and Disabled LEDs on the 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 only supported for one module type, even though it can be invoked for multiple module types.
Catalyst 2600
The Catalyst 2600 device package contains two versions of the enterprise MIBs for the Catalyst 2600 switch:
- C2600_cisco.my--This MIB file is installed to support devices with image versions prior to Software Release 2.2.1.
- C26000.my --This MIB file is installed to support devices with image Software Release 2.2.1 or later.
If you are using a MIB browser tool, you will see the MIB variables defined in each of the above MIB files, under different branches, at the same time, though any particular Catalyst 2600 switch will respond to queries on only one of the MIBs based upon the software release in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to Software Release 2.2.1 or later.
CPW 2200, Catalyst 2900, and Catalyst 5000 Series
The caveats for CPW 2200, Catalyst 2900, and the Catalyst 5000 series switches are as follows:
- Under a heavy load condition, SNMP responses are slow. You may 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 deinstall the agent group from the unused port to free the memory resource.
- 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. TrafficDirector only works if CWSI is installed.
- CWSI TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
- When multiple ports are selected, the Port>Configure window displays the Broadcast Suppression category. This is only available for single port selection.
- When enabling port security administration on a port, you might experience timeouts. If this happens, increase the SNMP timeout value to approximately 10 seconds.
- ATM, FDDI, and CDDI do not support Broadcast Suppression.
- The WS-X2901 module only shows the speed LED lighted 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.
- CiscoView 4.0 has limited SNMP support for the LightStream 1010 (LS1010) module in the Catalyst 5500 switch. The workaround for this situation is to assign the same community string to both the LS1010 module (ASP) and the supervisor module (NMP).
- CiscoView has limited SNMP support for the Catalyst 5500 switch in that it does not automatically update the display with the LS1010 modules installed in the chassis. To manually update the display with the LS1010 modules, perform the following steps:
- Launch CiscoView with the IP Address of the Catalyst 5500. The Catalyst 5500 chassis is displayed without the LS1010 modules.
- Click LS1010, located on the toolbar at the top of the CiscoView display. A prompt appears, requesting the IP address of the LS1010 module.
- Enter the IP address and click OK.
- The LS1010 modules appear in the Catalyst 5500, allowing you to manage these modules and the Catalyst 5500 modules.
Catalyst 3000 Series
Caveats for the Catalyst 3000 series switches are as follows:
- When you view the Catalyst 3200 using CiscoView, you will notice that it does not follow the traditional real-life display model for CiscoView device support. The display shows all Catalyst 3200 modules compacted into a two slot chassis, with module numbers increasing from left to right and top to bottom.
- When accessing a stack with six or more devices, you might notice some significant performance problems. You can improve the performance by increasing the SNMP timeout settings.
- The Catalyst 3000 series software does not support RMON on either a stack or an ATM port.
- The coloring of ports on the router module according to port status is not supported in this release. If you wish to manage the router module, use the right mouse button and select the CiscoView Router menu. Then use the left mouse button to launch another CiscoView session to manage the router. The Catalyst 3000 series software does not allow the modification of the parent VLAN number. [CSCdi76775]
- Timeout messages and SNMP Set Failed messages might appear when using the EtherChannel Configuration tool. If this happens, increase the SNMP timeout values for better performance.
- If you are running Release 2.0(1) of the Catalyst 3000 series software, you cannot 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 Release 2.0(1) of the Catalyst 3000 series software, you will notice that 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 series software.
- If you are running Release 2.0(1) of the Catalyst 3000 series software, you will notice that the SAID value entered when creating a new VLAN is 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 series software.
- The Domain Configuration and EtherChannel Configuration tools are not supported on Windows 95.
- The VLAN & Bridge application does not highlight ISL ports.
- Due to restrictions in the Catalyst 3000 series software, the WS-X3006B is displayed in CiscoView as a WS-X3006A.
- 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. TrafficDirector only works if CWSI is installed.
Catalyst 5000 Series
The caveats for the Catalyst 5000 series switches are as follows:
- For machines that do not have a /tftpboot directory (such as a PC), an error is displayed whenever you invoke the Upload/Download feature on a Catalyst 5000 series module.
- Do not use the Grapher in the CiscoView Monitor 10BaseT Group SwitchingEthernet window. Use the Monitor or Traffic Director tools to see graphical views of the selected repeater ports.
- When you use the Switch Zoom menu from CiscoView to view multiple switch ports, the default configuration for the Catalyst 5000 series switch is to configure Statistics only. To see the Short-Term or Long-Term history from the traffic monitor, use the Domain Manager to configure the Short-Term and Long-Term group 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 series switch is Statistics, Short-Term history, and Long-Term history.
- If you get the "Error: Entry or Group not present in Agent" message when invoking Segment Zoom, Switch Zoom, or Data Capture, the write community string may not match the device. If the community string is matched and the problem still happens, use the CiscoView Configure Device menu to see if the RMON capability is enabled or not.
- When you select the repeater module port on a Catalyst 5000 series switch, 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 only show the 100-Mbps speed LED lighted if the speed is configured at 100 Mbps and the port is connected.
- If you open the FDDI/Ethernet Bridge category under Configure>Device, you might receive an unknown error due to a problem with the device software.
- If you see a general error (genErr) displayed when changing vlanPortIslStatus, the selected port may not support ISL.
- You cannot change the values of ifAdminStatus and ifLinkUpDownTrapEnable on an ATM port.
- You cannot change the port duplex settings on ATM and FDDI ports.
- You cannot change the value of portSpanTreeFastStart on ATM and FDDI ports.
- If you configure ports to unsupported speeds, you will get a general error (genErr) due to a problem in the device software.
- The security category is not supported for ATM, FDDI, and CDDI port configuration on the Catalyst 5000 series switches.
- The following list shows the availability of broadcast suppression in terms of pps (packets per second) or % (percentage) for modules on Catalyst 5000 series switches. A plus sign (+) indicates availability, while a minus sign (-) indicates nonavailability. 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
| +
| -
|
|
Fasthub 100+ and 300 Series
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: Ports 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 due to a problem on the device software and will be fixed in a later software release. [CSCdi77452]
CDP and CGMP Protocols Unsupported
The CPW 1200/1400 and Catalyst 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these will return errors.
Community String Mismatching
When you enter values for the "read-only," "write-only," and "read-writeId" with the Command Line Interface (CLI) commands, these values must match those set for the device. A mismatch results in "noSuchName" or "timeout" errors. To avoid these error conditions, use identical community strings in CiscoView and corresponding agents.
Duplicate Categories
When you select multiple ports of different types, Port>Config may show duplicate categories.
Next Button
On the port config dialog of a Catalyst 5000 series switch, you might see some category names repeated twice. This is caused by rapidly pressing the Next button. Close and reopen the window to remove the duplicate names. [CSCdi57910]
Switch Firmware
The following firmware versions must be used in the switches:
- Catalyst 2100 and 2800--Release 3.63 or higher
- EtherSwitch 1200 and 2800--Release 3.63 or higher
- EtherSwitch 10/100--Release 1.38 or higher
- Catalyst 1700--Release 1.38 or higher
- Grand Junction FastSwitch 10/100--v. 1.37 or higher
- Grand Junction FastSwitch 2100 and 2800--v. 3.62 or higher
Note The Grand Junction FastSwitch 2100 and 2800 are managed the same as the Catalyst 2100 and 2800, respectively.
CWSI TrafficDirector
When launching TrafficDirector from CiscoView make sure that /usr/lib is included at the start of the LD_LIBRARY_PATH environment variable. A segmentation fault may occur if it is not included.
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. TrafficDirector only works if CWSI is installed.
CWSI with TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
This section contains the following information for TrafficDirector:
For additional documentation for TrafficDirector, refer to the Release Notes for TrafficDirector UNIX Release 4.1.3a, the TrafficDirector UNIX Software Configuration Guide, and online help. The primary documentation for TrafficDirector is the configuration guide. If you have documentation feedback, please email comments to bug-doc@cisco.com.
Documentation can also be found on the Cisco Enterprise Customer Documentation CD or on CCO. Refer to the "Cisco Connection Online" section for the CCO web address.
The following enhancements have been added to Release 4.1.3:
- Integrated support for switches with full RMON, mini-RMON, proxy RMON, and roving RMON. Release 4.1.3 supports the following switches:
- Catalyst 1200 series
- Catalyst 2000 series
- Catalyst 3000 series (mini-RMON only)
- Catalyst 5000 series (mini-RMON only)
- Enhanced SQL-based database for reporting
- Autodiscovery of embedded RMON agents on switches
- ISL filters for VLAN packet capture
- Enhanced Protocol Monitor to show layer-by-layer protocol distributions
- Frame relay support with data-link connection identifier (DLCI) statistics.
- Inter-Switch Link (ISL) virtual LAN (VLAN) traffic monitoring with switches and high-end routers.
- NetFlow support for Cisco routers that redirect IP packet streams from all interfaces to a preconfigured User Datagram Protocol (UDP) port and IP address.
- Domain Editor to support either generic or protocol domains. (You can define generic domains for SwitchProbe devices only.)
- Domain Manager to support multiple selections while installing domains for supported switches.
- Protocol Monitor to display relationships between multiple parent and children protocols.
- Data capture to support dynamic roving.
- Support for the 10-byte IPX address format.
- SQL-based database to support the Trend Reporter reporting system.
The following command line utilities provide enhanced functions:
- nstosnif--Converts FDDI data capture files to Network General Corporation's Sniffer Network Analyzer format. FDDI, Ethernet, and Token-Ring formats are supported.
- nspdec--Provides support for reading Network General Corporation's Sniffer Network Analyzer-formatted FDDI capture files (*.fdc files).
This section provides compatibility, filter editing, installation, and Trend Reporter information for Release 4.1.3a. The following topics are included:
Note the following information before installing TrafficDirector:
- Use the instructions for installing TrafficDirector in the CWSI 1.3.1 Installation Guide for Solaris; do not use the instructions in the TrafficDirector manual.
- By default, the superuser (root) is the only user who can use TrafficDirector. If you want a different user to be able to access TrafficDirector, you can specify that user during the VlanDirector installation. You must first install VlanDirector and specify the user and group member; then, install TrafficDirector. TrafficDirector will recognize the same user and group member as VlanDirector.
- Only the user and group member specified during the VlanDirector installation is permitted to run TrafficDirector. During installation, if you chose the default (user: bin group: bin) as the permitted group, only the superuser is permitted to run CWSI.
The Trend Reporter poller requires the exclusive use of the default UDP port 4732. If UDP port 4732 is in use, you must specify an alternative port.
To specify an alternative UDP port, you must edit the MSQL_TCP_PORT variable in the .traffdir file, changing the default UDP port value to the value of an available port. See the "Setting Up Environment Variables" section in the TrafficDirector UNIX Software Configuration Guide for more information.
Note If more than one version of TrafficDirector is installed on your system, you must edit the MSQL_TCP_PORT variable that occurs in each instance of the
.traffdir.sh file for sh or ksh users or the .traffdir.cshrc file for csh users.
Taking full advantage of TrafficDirector Release 4.1.3a requires SwitchProbe Release 3.1.0 or later. Refer to the SwitchProbe Installation and Configuration Guide for more information.
TrafficDirector Release 4.1.3 includes 11 predefined ISL filters for monitoring VLAN traffic:
- ISL_VALL--Used for all VLAN traffic
- ISL_V1--Used for VLAN ID 1
- ISL_V2--Used for VLAN ID 2
- ISL_V3--Used for VLAN ID 3
- ISL_V4--Used for VLAN ID 4
- ISL_V5--Used for VLAN ID 5
- ISL_V6--Used for VLAN ID 6
- ISL_V7--Used for VLAN ID 7
- ISL_V8--Used for VLAN ID 8
- ISL_V9--Used for VLAN ID 9
- ISL_V10--Used for VLAN ID 10
You can edit these filters to monitor additional VLANs by changing the VLAN ID binary values in the VLAN (L-7Bit)+BPDU and VLAN [H-8Bit] fields in the Filter Editor window.
To edit one of the predefined ISL filters, follow this procedure:
Step 1 Determine the binary value of the VLAN ID you want to monitor:
If the VLAN ID is less than 128, determine the 7-bit value. For instance, the 7-bit value of VLAN ID 12 is 0001100.
If the VLAN ID is greater than 128, determine the high-bit (8-bit) and low-bit (7-bit) values. For instance, the high-bit and low-bit values of VLAN ID 1000 are 00000111 and 1101000, respectively.
Step 2 Launch the Filter Editor from the TrafficDirector main window.
Step 3 Select one of the ISL filters.
Step 4 Click Edit. The Edit Filter window appears and displays the filter information for the ISL filter you selected.
Step 5 Enter a new name for the ISL filter in the Filter Name field.
Step 6 Change the values in the VLAN (L-7Bit)+BPDU and VLAN (H-8Bit) fields using the values you determined in Step 1 to reflect the new VLAN ID you want to monitor. The following conditions apply:
If the VLAN ID is less than 128, enter the 7-bit value in the VLAN (L-7Bit)+BPDU field. (Ensure that the VLAN (H-8Bit) field is empty.) For instance, if the 7-bit value is 0001100, you would enter it in the VLAN (L-7Bit)+BPDU field as follows:
If the VLAN ID is greater than 128, enter the high-bit (8-bit) value in the VLAN (H-8Bit) field and the low-bit (7-bit) value in the VLAN (L-7Bit)+BPDU field.
For instance, if the high-bit value is 00000111, you would enter it in the VLAN (H-8Bit) field as follows:
If the low-bit value is 1101000, you would enter it in the VLAN (L-7Bit)+BPDU field as follows:
Step 7 Click OK to enter the changes.
If you receive the "Cannot connect to the database server" error message when viewing a report, wait 30 minutes, and try again. The Trend Reporter reporting daemon generates reports every 15 minutes.
When you use the Trap Manager application with a selected switch, Trap Manager only shows the status of one switch port. To view the status of other switch ports on the switch, select the Agent option from the Scope menu, and select a switch port from the Scope Agent list.
The following caveats describe possibly unexpected behavior by Release 4.1.3a:
- In some UNIX environments, TrafficDirector encounters problems finding the colors for displays. This results in some graphs and charts being displayed in black and white.
- To work around this, either close other applications that use many colors, such as a web browser, and then relaunch TrafficDirector, or launch the other applications using private color maps.
- The TrafficDirector agent test function fails on Solaris 2.5.1 platforms due to platform limitations. To resolve this problem, you can obtain a patch, 103866-02, from the Sun Microsystems FTP site at ftp://sunsolve.sun.com/pub/patches/patches.html.
- You can work around this by creating an empty file, called pingoff, in the $NSHOME/usr. TrafficDirector looks for this file in the $NHOME/usr directory, but does not run the ping portion of the agent test function. Do not include any configuration information in the file or give it a filename extension.
- Font sizing on the Solaris 2.5 platform sometimes produces an unreadable MAC address in the Agent Information window.
- A Motif error message is displayed in the system console window when you click Refresh or select a menu item in the Host List window. This error message can be ignored.
- If broadcast and multicast rates cannot be seen when monitoring a VLAN from Top N hosts or All Hosts, you must upgrade your Fast Ethernet SwitchProbe device to the most recent firmware version. You can find the most recent version on (CCO).
- Confirmation dialog boxes do not always minimize correctly. To work around this, respond to the confirmation dialog boxes when they are displayed, and do not minimize them.
- Trap Manager does not launch correctly from the Resource Manager window. To work around this, launch Trap Manager from the TrafficDirector main window.
- Trap Manager-generated traps do not identify the source interface or port where the trap was generated. To work around this, include the interface or port number in the trap description.
- The Trap Manager View Alarm option does not map the alarm object ID to a variable name, such as "Packets."
- SNMP traps received from SunNet Manager 2.3.3 or later and OpenView 4.x are not forwarded to TrafficDirector.
- The TrafficDirector trap daemon does not receive traps on SunOS, Solaris, HP-UX 9.9 or 10.x platforms running OpenView 4.x. TrafficDirector does not receive traps for OpenView 3.x, SunNet Manager 2.3.3, SunOS, or Solaris.
- When using Traffic Monitor or Domain Manager with a selected agent, do not select a trunk or server probe and then launch an application from the Traffic Monitor or Domain Manager Launch window. This might cause a TrafficDirector application error.
- To work around this, select an agent from the Agents list in the TrafficDirector main window, and then launch the application.
- Utilization rates for full-duplex Ethernet and Fast Ethernet switch ports are incorrectly reported at twice their actual rates.
- The pkgchk command, which checks the integrity of the installation, is not supported.
This section describes the TrafficDirector 3.3 problems that were resolved in TrafficDirector 4.1.3a.
- CWSI 1.3.1 allows separate installation locations for VlanDirector, CiscoView, and TrafficDirector. CWSI 1.2 forced all three applications to be in the same home directory.
- CWSI 1.3.1 checks for disk space availability for each application during installation of CiscoView, VlanDirector, and TrafficDirector.
- CWSI 1.3.1 installation allows you to install the application over previous versions of CWSI.
- CWSI 1.3.1 allows integration of VlanDirector and CiscoView with HP OpenView 4.1.
This section contains the following information for VlanDirector:
For additional documentation for VlanDirector, refer to the VlanDirector User Guide and online help. The primary documentation for VlanDirector is the online help. If you have documentation feedback, please email comments to bug-doc@cisco.com.
Documentation can also be found on the Cisco Enterprise Customer Documentation CD or on CCO. Refer to the "Cisco Connection Online" section for the CCO web address.
- Support for the Catalyst 3000, 3100, 3200 (Release 2.02 and greater)
- Support for the Catalyst 5002 and 5500
- Support for Catalyst 5000 series Software Release 2.1.5 and greater
- "Show Trunking" display on the Network Topology map in order to help troubleshoot VTP problems.
- Windows, especially the topology windows have new features for customizing device labels to make the windows more readable. In the Names window, select Options>Properties>Views.
In VlanDirector 1.0, the Read and Write community strings are defaulted to public and private. In VlanDirector 1.4, when you start VlanDirector without specifying a Community String File (-csf option from the command line) or -wr, VlanDirector uses public for both the read and write community strings. This is different from the defaults on the boxes and was implemented to help prevent problems with inadvertent sets on the boxes.
If you have a LightStream1010 (or an ASP) connected to an Ethernet network through the Ethernet port, disable CDP on that port. VlanDirector discovery should proceed through the ATM cloud.
VlanDirector works as documented, with the following exceptions and caveats:
- The "No more colors left in colormap..." message means your display has run out of colors for all the programs you are simultaneously running.
- Workaround: Stop running some programs and restart VlanDirector.
- In a network where an ATM cloud connected to a Catalyst 5000 series switch is discovered, certain VLAN creation and deletion operations fail with the detailed reason "genErr."
- Workaround: Use the CLI to create or delete a VLAN on an ATM port.
- ATM LANE links to routers are not displayed in the Network Topology or VLAN Topology windows. This will be a major feature of VlanDirector 2.0.
To find the version of VlanDirector from the command line, use the -V option instead of -v. The -v option is no longer available, as it is used internally by the Tcl subsystem.
- Black icon link.
- The pkgchk command, which checks the integrity of the installation, is not supported.
This section describes the VlanDirector 1.3 problems that were resolved in VlanDirector 1.4.
- On the Catalyst 5000 series switch and the Catalyst 7000 router, having more than 19 characters in the Fast Ethernet subinterface name caused ANI to crash. This problem is fixed in this release.
- Discrepancy calculations performed after the discovery process was completed caused ANI to crash. The workaround was to disable the optional discrepancy calculation. This problem is now fixed in this software release.
- If there were more than eight devices on the Vlan Topology map, the names for the associated ports in the Vlan Ports window were incorrect. This problem has been fixed in this software release.
CCO, formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content 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, 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 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:
- WWW: http://www.cisco.com.
- WWW: http://www-europe.cisco.com.
- WWW: http://www-china.cisco.com.
- Telnet: cco.cisco.com.
- Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
