cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi_1
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for CWSI UNIX
Version 1.1

Release Notes for CWSI UNIX
Version 1.1

This document contains notes for the CiscoWorks for Switched Internetworks (CWSI) product, including CiscoView 3.1, VlanDirector 1.2, and TrafficDirector 3.3.

Release Notes for CWSI Product

The following notes apply to the CWSI product in general.

CiscoWorks Integration

When installing CWSI on a machine where CiscoWorks has already been installed, all CiscoView packages are installed by default. There is no prompt asking you to select specific devices to install.

HPOV Install MIB Errors

When integrating CWSI with HP OV, MIB integration errors are generated. These errors have no effect on the subsequent execution of CWSI and can be ignored.

Solaris 2.5 Support

For CWSI 1.1 to support Solaris 2.5, a minimum of the Solaris 2.5 developement environment must be installed.

When installing CWSI on Solaris 2.5, several warnings are given that Solaris 2.5 is not supported. Ignore the warnings and continue with the installation. VlanDirector will run on Solaris 2.5. CiscoView and TrafficDirector will also run on Solaris 2.5, but there may be problems. Please see Appendix A for more details on Solaris 2.5 support for CiscoView.

SunOS 4.1.4

CWSI 1.1 is not supported on SunOS 4.1.4 due to problems in the operation of the version of TCL/TK used by both VlanDirector and CiscoView with SunOS 4.1.4 system calls. The main symptoms are loss of communication between VlanDirector and CiscoView, VLAN membership not highlighted on CiscoView, and loss of drag-and-drop functionality between CiscoView and VlanDirector. In some severe cases, VlanDirector may fail to launch.

Workaround: Some versions of SunOS 4.1.4 may work, but generally an upgrade to Solaris is required.

CWSI CiscoView Support

With CWSI, CiscoView support has been extended for the CPW16, Catalyst 1200, Catalyst 3000, and Catalyst 5000. Support has also been added for the Catalyst 2900. The following are caveats for these devices in CiscoView:

Release Notes for CiscoView UNIX
Version 3.1

This section discusses the CiscoView 3.1(1) release and includes the following information:

CiscoView 3.1(1) IOS Information

This section contains the latest Cisco IOS' (Internetwork Operating System) software version information at the time of printing. New devices and further specifics on IOS support will be announced following this release. Refer to the online release notes on the Cisco Customer Connection Online (CCO), formerly called Cisco Information Online (CIO), or on the Cisco Connection Documentation, Enterprise Series CD, or Cisco Connection Documentation, CiscoPro Solutions CD, which are both accessible via CCO and are continually updated.


Note The Cisco Connection Documentation, Enterprise Series CD was formerly called UniverCD and the Cisco Connection Documentation, CiscoPro Solutions CD was formerly called UniverCD for CiscoPro.

CiscoView supports Cisco IOS Software Releases 10.0 through 11.1 with the exception of Access Servers, which require a minimum of Cisco IOS Software Release 10.2.


Note CiscoView supports the Qualified Logical Link Control (QLLC) feature in Cisco IOS Software Release 10.3(7) or later and in Cisco IOS Software Release 11.0(2) or later. CiscoView supports the Synchronous Data Link Control (SDLC) feature in Cisco IOS Software Release 10.2 or later. CiscoView supports the CIP card in Cisco IOS Software Release 10.2 or later.

Additional Documentation Information

The documentation for CiscoView 3.1(1) includes this release note, a CD-ROM booklet, incremental installation instructions, and online help. The primary documentation for CiscoView is the online help. If you have documentation feedback, please forward comments to: cs-ciscoworks@cisco.com.

You can also refer to the quick reference card for CiscoView for information on adding device support.

CiscoView and Device Information

CiscoView is a GUI (graphical user interface-based) device management software application that provides dynamic status, statistics, and comprehensive configuration information for Cisco Systems' switched and internetworking products. CiscoView allows you to display a graphical representation of each network device, display configuration and performance information, and perform minor troubleshooting tasks.

CiscoView allows you to manage the following Cisco devices:


Note Refer to the "Switch Firmware" section in "Caveats for Workgroup Products" for firmware versions.

Note The Cisco 4700 is not supported by CiscoView 3.1(1) at this time, but support will be provided in the near future. Please check the Cisco World Wide Web site (www.cisco.com) periodically for download information on the latest device support and upgrades.
These enhancements apply to all high-end business unit devices (Cisco 7000 and Cisco 7500 Series). With this application, CiscoView 3.1(1) is enhanced to extend its capability to provide device management functionalities such as the following:

  • Software and Config files Upload/Download

  • Configuration File Editing

  • Flash Filesystem directory display

Incremental Installation Information

To get more information about the Partner Initiated Customer Accounts (PICA) program before accessing CCO for device package files, use the following URL:

http://www.cisco.com/acs/info/pica.html

You can also refer to the quick reference card for CiscoView for information on adding device support.

Troubleshooting

If you cannot open a device in CiscoView 3.1(1), a message appears indicating that the device is unmanageable. This message indicates one of the following conditions:

Installation Caveats

This section lists installation notes and restrictions that apply to the CiscoView 3.1(1) release.

Cvinstall Path Specification

For SUNOS 4.1.x installs, you must define /usr/lib before /lib in LD_LIBRARY_PATH. If LD_LIBARY_PATH has /lib:/usr/lib then cvinstall will fail when trying to run cvtest, and display the following error message:

dlopen: stub interception failed
/usr/nms/bin/cvinstall: <pid> Abort - core dumped

[CSCdi58364]

HyperHelp Resource File

The CiscoView 3.1(1) installation attempts to put the X resource file for HyperHelp in the /usr/lib/X11/app-defaults directory. Since different systems have different types of X Windows installations, the HyperHelp application does not always locate this resource file. When the resource file is not read, the HyperHelp viewer text may be unreadable on your screen. Do the following to make sure that this resource file is read:

Choose Options>Set Hyperhelp Defaults from the CiscoView menu to set resources.

Path Environment Variables

If you get the following error message,

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

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

SNM 2.2.2 Patch Requirement

Make sure you have installed Patch level 4 for SNM 2.2.2 under SunOS in order that snm_discover discovers your devices correctly. If the Grapher does not send more than one request, verify that your snm_cmd has the size 36864 bytes.

Tables Show All Categories

Multiple selections show all categories, whether they apply to a specific group of selections or not. If the category doesn't apply, the config table will show "N/A" in the cells. [CSCdi48854]

Deinstallation Caveats

This section lists deinstallation notes and restrictions that apply to the CiscoView 3.1(1) release.

Upgrading to CiscoView 3.1(1)

If you are upgrading from an existing Ciscoview release to CiscoView 3.1(1), perform an upgrade or a reinstallation. Deinstallation of the product is not recommended. Deinstallation of the existing CiscoView release requires manual changes to the Network Management platform (min), or CiscoView will break.

General Caveats

This section lists general notes and restrictions that apply to the CiscoView 3.1(1) release. They are divided into six sections:

Caveats for Enterprise Network Management Products

General notes and caveats for Enterprise Network Management products are described below.

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, and CPW16) have defined their ports for dragging across devices.

HP OpenView Discovery Issue

When a switch is configured as two or more domains, HP OpenView discovery may not work properly and may discover only one of the domains. If this occurs, use CiscoView to manage the domain directly rather than launching it from the map.

HP OpenView Error Message

The xnmloadmib program in HP OpenView may have problems reloading MIB files into their database. The definition of CiscoNetworkProtocol in CISCO-TC-V1SMI.my and OwnerString in IF-MIB-V1SMI.my will display an error message similar to the following when you run cvinstall -f:

Error detected while loading MIB file: /net/cv311/etc/cview/mibs/CISCO-TC-V1SMI.my
This MIB cannot be loaded until the following problem is corrected:
Line 44613: Error defining ASN.1 Type: duplicate type with conflicting definition 'CiscoNetworkProtocol'

The workaround is to invoke xnmloadmib manually, select and unload all Cisco-specific MIB files from the list box in xnmloadmib GUI, then run the command cvinstall -f to load all Cisco specific MIB files. [CSCdi56399]

Loading Correct SNMP Daemon

You may be unable to view a Fiber Distributed Data Interface (FDDI) SBus adapter on a device in CiscoView 3.1(1). Make sure you have the correct SNMP daemon (snmpd) loaded. The default snmpd for SunOS does not allow you to view this adapter. To correct this problem, stop the existing snmpd process and reload the snmp.cfddi daemon, which is generally located in the /etc directory. Check the rc.local file to determine where the snmp.cffdi daemon might be located.

Motif Window Manager (mwm1.x)

Windows cannot correctly resize smaller when running mwm 1.x. Choose the Property dialog option to make CiscoView 3.1(1) circumvent this problem.

Open Look

Popup Menu Titles

Popup menu titles are raised; users may mistake them for menu items. [CSCdi53475]

Running CiscoView 3.1(1) 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 will core dump. If you are running other applications, you might want to check your swap space occasionally.

To check swap space on a SunOS 4.1.x workstation, enter the following:

hostname% pstat -s

To check swap space on a Sun Solaris 2.x workstation, enter the following:

hostname% swap -l

To check swap space on an HP-UX 9.0x system, enter the following:

hostname% swapinfo

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]

Stripchart and Dials

Stripchart and dials are sometimes not drawn clearly. [CSCdi51621]

SunNet Manager Grapher

The SNM grapher can only graph three or four variables at a time. Selecting more variables will generate a "too long" error message. This will affect Graphing from Monitor dialog boxes. Do not ask SNM's grapher to graph more than four variables at a time. If you need to see more, start two SNM graphs, select SNM graph control box, and combine both graphs into one.[CSCdi51362]

Switching Between Colormaps

Programs such as Netscape take up all the colors on workstations with 8-bit graphics cards (typical for SUN). CiscoView 3.1(1) will dither colors to NetScape's colormap. SunNet Manager will create a private colormap, and the screen will swap colormaps as you switch between applications.

Tables Show All Categories

Multiple selections show all categories, whether they apply to a specific group of selections or not. If the category doesn't apply, the config table will show "N/A" in the cells. [CSCdi48854]

Caveats for Workgroup Products

Following are general notes and caveats for the Cisco Workgroup family of products.

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

Following are general notes and caveats for the above Workgroup products:

Community String Mismatching

When the user enters values for the "read-only," "write-only," and "read-writeId" with the Command Line Interface (CLI) commands, these values must match. A mismatch results in "noSuchName" or "timeout" errors. To avoid these error conditions, use identical community strings in CiscoView and corresponding agents.

Exiting CiscoView 3.1(1) Causes Applications to Close

If you are using the CiscoPro 16/Catalyst 3000 and close the CiscoView window, any application window that was launched from it will automatically close. Remember to close the EtherChannel and Domain Configuration application windows before you open another CiscoView application or exit from the CiscoView application. There is no limitation on the number of CiscoView applications that you can run.

False Error Reported After Setting Parameters

On the CiscoPro (CPW) 16 and Catalyst 3000, when you try to set parameters for the EtherChannel/Domain application under moderate to high traffic situations, the application incorrectly displays an error window indicating that the operation was not successful. In reality, the command was successful, and you should dismiss the error dialog. The application should continue to function properly.

LightStream 100

The LightStream 100 VCTool has support for virtual circuit management of the LS100 and can be invoked from the LS100 CiscoView 3.1(1) application.

The LightStream 100 VCTool is currently supported for SunOS 4.1.X and HPUX 9.X.

Next Button

If you rapidly press the Next button on a Catalyst 5000's port configuration dialog, you may see some category names repeated twice. Redisplay the window to remove the duplicate names. [CSCdi57910]

ProStack Power Supply Link Problem

The rear view of the Prostack matrix power supply does not indicate whether the connector link is up or down (for example, the connector does not come up green if there is a link).

Switch Firmware

The following firmware versions must be used in the switches:


Note The Grand Junction FastSwitch 2100 and 2800 are managed the same as the Catalyst 2100 and 2800 respectively.

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 attempt to reconfigure. This problem is fixed in version 9.1 of the device firmware. [CSCdi41317]

Caveats for Access Products

Following are general notes and caveats for the Cisco Access family of products.

Card Support for Cisco 4000 and 4500 Series

FDDI Port Status Functionality

The Cisco 4000 series devices with DAS FDDI ports show status on only the lower one of the two connectors. The status color is determined from the port's administrative status (ifAdminStatus) and operational status (ifOperStatus) values. [CSCdi28566]

Read-Only MIB Variables

The administrative status (ifAdminStatus) value "testing" and the ring speed (dot5RingSpeed) variable are implemented as "read-only" in all Cisco IOS versions and are not settable through popup menus on CiscoView Configure Port screens. However, Configure Port tables (of multiple ports) offer popup menus that permit attempts to set these variables. Such attempts result in "Permission Denied" messages. [CSCdi50635]

Tunnel Interface

A "can't read 'port' : no such variable" message appears at the bottom of the config port dialog when a tunnel interface is encountered while you click up through the ports. This message can be ignored. [CSCdi55765]

Caveats for High-end Business Products

Following are general notes and caveats for the Cisco High-end Business suite of products (including 7000 and 7500 series and ATM switches).

Displayed ATM Connector Type

CiscoView 3.1(1) always displays the multimode fiber SC type of ATM connector on AIPs, even when the media interface is of another type. [CSCdi53420]

FDDI Port Status Functionality

For 7000/7500 series routers running Cisco IOS Release10.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 IOS 10.3 or later, the displayed status color is determined from the Port Connect State (fddimibPORTConnectState) for each connector. The possible values for this status and the corresponding status colors are listed below:

Status Status color
disabled brown
standby brown
connecting blue
active green

[CSCdi28566]

High System Availability (HSA)

LightStream 2020 MIB Support

For the LightStream 2020 there is currently no MIB support for the "LNS OK," "LN FLT," "BITS OK," and "TCS SEL" LEDS on front linecards. These LEDS appear blank. In addition, the "TX" and "RX" LEDS on front linecards blink too rapidly for SNMP polling purposes, and also appear blank.

LightStream 2020 Software Releases Supported

The LightStream 2020 supports Release 2.1(2) or later.

OIR Support

Hotswap is only supported on devices running Cisco IOS Release 11.0 or later. [CSCdi53447]

Power Supply Display

By default, CiscoView 3.1(1) displays two power supplies for a 7000 running Cisco IOS Release10.2 and earlier. With IOS Release 10.3 and later, power supplies are displayed based on ciscoEnvMonSupplyState values (ENVIRONMENTAL MIB).

Read-Only MIB Variables

The administrative status (ifAdminStatus) value "testing" and the ring speed (dot5RingSpeed) variable are implemented as "read-only" in all Cisco IOS versions and are not settable through popup menus on CiscoView Configure Port screens. However, Configure Port tables (of multiple ports) offer popup menus that permit attempts to set these variables. Such attempts result in "Permission Denied" messages. [CSCdi50635]

Caveats for Online Help

Following are caveats for online help.

Glossary Links

Some device-specific help files may not have links to the glossary file. To view the glossary, select Help>Using CiscoView in the help window.

Options Menu

The following information was omitted from the online help information for the Options menu:

Options>Set HyperHelp Defaults sets the HyperHelp resources so that the HyperHelp viewer text is readable on the screen.
Options>Debug records trace information into a file located in /tmp/.cvlog.

Release Notes for VlanDirector UNIX
Version 1.2

VlanDirector works as documented, with the following exceptions and caveats:

Known Defects

HP-UX 9.X Release

On this release, the Help menu incorrectly indicates that the version of VlanDirector is 1.1.

ATM fabric support

Certain VLAN creation and deletion operations performed in a network where an ATM cloud connected to a Catalyst 5000 is discovered fail with the detailed reason "genErr". This problem will be resolved with release 2.1.4 of the Catalyst 5000 software. [CSCdi67171]

Workaround: Use the CLI to create or delete a VLAN on an ATM port.

ATM LANE links to routers are not displayed on the Network and VLAN Topology displays.

Dragging and dropping devices to wastebasket fails

Dragging and dropping a device from the VLAN Topology to the wastebasket fails to remove the ports from the VLAN. [CSCdi68068]

Workaround: Drag ports and links individually to the wastebasket to remove them from a VLAN.

Opening Networks

If one or more blanks are specified as the seed device name when reopening a network that is currently open, such as using "Open Network" for the current network, a non-existent device is added to the topology. [CSCdi67472]

Workaround:

1. Drop the device using the mouse menu button for the device in Network Topology.

2. Rediscover the network leaving the Discovery Device field empty, or specify the correct seed device.

Catalyst 1200 802.10

Enabling 802.10 on an FDDI link connected to a Catalyst 1200 fails. [CSCdi67785]

Workaround: Use the CLI on the Catalyst 1200 to enable trunking.

Catalyst 3000 EtherChannel

Moving or deleting individual ports belonging to an EtherChannel group appears from VlanDirector to only move or delete those ports and not the whole group. However, the operation is successful. [CSCdi68957]

Workaround: Rediscover the network after altering the VLAN assignment of a port in an EtherChannel.

Translational Bridging

Using the VLAN Modification dialog to unbridge a VLAN unbridges the VLANs on the network but does not update VlanDirector. [CSCdi68959]

Workaround: Rediscover the network after performing the unbridge operation.

When creating a bridged VLAN, if the name of the FDDI VLAN is typed into the advanced dialog box, the following error may appear: "VLAN or folder name may not be zero length" and an unbridged Ethernet VLAN is created. [CSCdi68905]

Workaround: Use the fully extended name for the FDDI VLAN. For example, prepend the folder extension before the VLAN Name, such as ".:FDDIVlan".

STP Discovery

Spanning Tree configuration is not always properly determined during the initial discovery of a new network. [CSCdi68919]

Workaround: Rediscover the network.

Display of 100baseF links

The link icon on a 100baseF link appears as a black square. This does not affect operations on that link. [CSCdi68921]

SAID Assignments

When an SAID is assigned to a VLAN in the VLAN Creation dialog box and subsequently read in the VLAN Modify dialog box, the numbers do not match. This is due to an inconsistency between the device and VlanDirector SAID assignment, but does not affect the VLAN operation in any way. [CSCdi68491]

Discovery Error

VlanDirector discovery may generate a "mrtqcon" error and terminate. This occurs when calculating discrepancies on a link where one end of the link is unmanaged. [CSCdi68961]

Workaround: Disable Multi-Colored Discrepancy detection in the Options->Properties-> Discrepancy Management dialog box.

VlanDirector Version

To find the version of VlanDirector, use the -V option instead of -v. The -v option is no longer available, as it is used internally by the TCL subsystem.

Using Help (SunOS only)

The initial size of the Help window is not wide enough to display the Find button.

Workaround: Resize the help window at least 0.75 inches wider to display the Find button.

The Find window is displayed directly on top of the Help window and completely obscures it. This makes it appear that the Go To button in the Find window does not work.

Workaround: Move the Find window away from the Help window.

VLAN Names

VlanDirector allows VLAN names up to 32 characters long, except when there are Catalyst 3000s in the network. (Catalyst 3000s only accept VLAN names up to 16 characters long.) VlanDirector does not take this into consideration when validating the length of a VLAN name.

Workaround: Make sure VLAN names do not exceed 16 characters in length if you have Catalyst 3000s in your network.

Features that might not exhibit expected behavior

Community Strings

In VlanDirector 1.0, the Read and Write community strings defaulted to 'public' and 'private' respectively. In VlanDirector 1.2, only the Read community string has a default value ('public'). Therefore, when you start VlanDirector without specifying a CSF or -wr, VlanDirector uses 'public' for both the Read and Write community strings.

Release Notes for TrafficDirector UNIX
Version 3.3

This section describes the features and modifications of TrafficDirector Version 3.3. Refer to the TrafficDirector UNIX User Guide for detailed information about the TrafficDirector product.

Product Overview

TrafficDirector is an RMON console software application that lets you monitor, troubleshoot, and record information about your network's operation. TrafficDirector helps you analyze network traffic patterns and identify and isolate a wide variety of fault conditions in data communications networks.

TrafficDirector works as a distributed system. It uses a central management console running TrafficDirector software in conjunction with data-gathering agents located at various points on a network. It can simultaneously collect wide-ranging statistical data, display selectively captured and fully decoded network traffic, set user-defined alarm conditions, and obtain real-time updates from all segments of a widely dispersed internetwork. TrafficDirector accomplishes this from a centralized, SNMP-compatible network management console.

TrafficDirector is based on two standards that enable it to operate in a multi-topology, multi-vendor environment:

TrafficDirector has four main functions:

TrafficDirector gathers and analyzes network information using SwitchProbes and Cisco IOS RMON agents attached to network segments.

SunOS 4.1.X Patch

If you experience x-server crashes when running TrafficDirector in a SunOS 4.1.X and OpenWindows 3.0 environment, you need to apply patch 100444-xx to your system. Download the patch from the following FTP server or network web site:

After you download the image, perform the following steps:

Step 1 Decompress the file, as follows:

A response similar to the following appears:


Step 2 Obtain the patch files by performing the following:

Step 3 Follow the instructions in the README file to apply the patch.

Licensing

TrafficDirector requires a serial number and password to unlock the software for use. A temporary evaluation serial number and password are attached to the shipping box. This serial number allows you to begin using TrafficDirector as soon as you receive it. However, you will need to request a permanent password before the evaluation expiration date. If you change the IP address of the host, or if you move the software to another machine, you must contact Cisco for a new password.


Note The license agreement requires a separate license for each machine on which you intend to use TrafficDirector.

You can obtain a permanent license agreement through the Cisco Connection Online (CCO) Web server or by sending a fax to Cisco Systems.

Getting a License through the CCO Web Server

To obtain a permanent license agreement through the Cisco Connection Online Web server, follow these steps:

Step 1 Access the Cisco Connection Online Web server at http://www.cisco.com.

Step 2 Access the Software Library. Enter the required information to generate your permanent password. Be sure to use the Registration Serial Number and the Registration Password provided.

Getting a License by Fax

To obtain a permanent license agreement by fax send a fax to Cisco Systems at 408 526-8898 addressed to "Attention: Software Licensing." Include the IP address of the machine on which you will be using TrafficDirector as well as your "Registration Serial Number," "Registration Password," and return fax number. You will receive your permanent password within 48 hours.

Configuration Limits

TrafficDirector for UNIX (Solaris, SunOS, HP/UX and IBM-AIX) has the following configuration limitation:

Configuration Parameter Maximum Number Supported
Agents 1000
Agent groups 100
Agents per agent group 60
Interface number (ifIndex number) 999

Cisco RMON Agents

The Catalyst 1200 series switch embedded RMON agent and the SwitchProbe agents provide full seven-layer monitoring for all RMON groups. The Catalyst 2900 and 5000 embedded RMON agents provide four groups of RMON (Statistics, History, Alarms and Events) on all Ethernet and Fast Ethernet ports. The 2500 series routers with Cisco IOS v11.1 provide all nine groups of RMON as specified in RFC 1757.

Catalyst 5000 Group Switching Ethernet Module

The Group Switching Ethernet Module of the Catalyst 5000 supports one RMON agent on each of its 12-port segments for a total of four agents. Use only the ifIndex of the first port in each 12-port segment group when configuring the RMON agent from TrafficDirector.

Catalyst 1200 RMON Agent Configuration Guidelines

The Catalyst 1200 DMP and NMP version 3.1 or higher include an embedded EnterpriseRMON agent. You need to purchase an agent license from Cisco before enabling this RMON agent. The embedded RMON agent can NOT be configured to monitor the FDDI interface.

To use RMON within the Catalyst 1200 switch you must first create an agent and install domains for each interface that you wish to monitor. When configuring a new agent be sure to set the Interface Number field to a port number between 3 and 10, indicating which Ethernet port/segment you want to monitor. Also, be sure that the SNMP community strings in the Catalyst 1200 match those configured in TrafficDirector for each agent. Cisco ships the Catalyst 1200 with the following default community strings: Read = public, Write = private.

The Catalyst 1200 series switch reserves slightly less than 1MB of RAM for use by the embedded RMON agent. Each enabled agent group within an installed domain consumes both memory and CPU cycles on the NMP to monitor that domain. You should remove any unused domains and only install the groups and domains that you plan to monitor. Use the following memory consumption guidelines when configuring groups and domains:

RMON Groups Memory Used (bytes) Assumptions
Statistics 100
Short History 5K for 50 buckets
Long History 5K for 50 buckets
Host Table 25K for fewer than 256 hosts
Conversations
(Matrix Table)
30K for fewer than 1024 conversations
Fully enabled domain 75K maximum (not including data capture buffer)

Note If you receive the error message "Error: No resources in agent" or experience other problems when using the Catalyst 1200 RMON agent, check to make sure that the above memory guidelines have not been exceeded.
Most customer problems are caused by the installation of too many domains and groups

Color Resources

On some machines, after you launch CiscoView from VlanDirector and then launch TrafficDirector from CiscoView, there are not enough color resources for TrafficDirector to launch, so it launches in black and white mode.

Workaround: Quit VlanDirector and launch TrafficDirector from a standalone CiscoView.

Cisco Connection Online

Cisco Connection Online (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, Internet e-mail, and fax download options, 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:

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.

APPENDIX A: HPOV and Solaris

You need a patch to make HPOV 4.1 work with Solaris 2.5. The info we received from HP is below.

There is now a patch for Software Distributor and I4LS to allow you to install and run NNM 4.1 on Solaris 2.5.

The patch for Software Distributor is PSOV_1090. This is required to install NNM 4.1 on Solaris 2.5 and must be installed prior to installing NNM 4.1. Then be sure to follow the modified installation instructions described in PSOV_1090.text.

The patch for the I4LS licensing software is PSOV_1138. This is required to run a license server on Solaris 2.5. If your license server is on a different machine, this patch is not necessary.

Both patches consist of a tar file and a text file describing the patch.

These files can be obtained via ftp from fcext3.external.hp.com. Login as "tr" with the password "ava1anche" (that's a numeral 1 instead of a letter L in the word avalanche).

Then cd to the "patches" directory where you will find:

-rw-r-----   1 tr       nsmd     7802880 Aug 15 10:04 PSOV_1138.tar
-rw-r-----   1 tr       nsmd      217908 Aug 15 10:04 PSOV_1138.text
-rw-r-----   1 tr       nsmd    11991040 Jul  2 15:48 PSOV_1090.tar
-rw-r-----   1 tr       nsmd     1374787 Jul  2 15:48 PSOV_1090.text

Be sure to set binary mode when retrieving the tar files.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.