|
|
This document discusses the CiscoView 4.0(1) release and includes the following information:
CiscoView 4.0(1) release includes support for Solaris 2.4, 2.5, and 2.5.1, AIX 4.1.5, 4.2, and HP-UX 10.1 and 10.2. CiscoView also runs optionally with HP OpenView 4.1 or 4.1.1 (on Solaris and HP-UX), Solaris SunNet Manager 2.2.3 or 2.3 (on Solaris), and NetView 3.1 or 4.1 (on AIX).
CiscoView 4.0 supports the following upgrade paths:
 | Caution Before installing CiscoView or CiscoView devices, read the caveats in "Installation Notes and Caveats" on page 8. |
Table 1 contains the list of supported CiscoView devices by product type.
| Small to Medium Business Products | Mid-Range Enterprise Products1 | High-End Enterprise Products |
|---|---|---|
Cisco and CiscoPro 761, 762, 765, 766, 771, 772, 775, 776 | Catalyst and CiscoPro switch models2 1200, 1400, 1600, 1700, 1800, 1900, 2100, 2600, 2800, 2820, 2900, 3000, 3200, 5002, CPW2200, and Catalyst 3100 | Catalyst 5000 and 5500
|
Cisco or CiscoPro 1003, 1004, and 1005 | EtherSwitch Pro16, EPS2015, 1200, 1220, 1400, and 1420 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
Cisco and CiscoPro 1601, 1602, 1603, 1604 | EtherSwitches: Pro16 and CPW16 | LS10103 |
Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2510, 2511, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525 | CiscoPro switch models CPW10-100, CPW1200, CPW1220, and CPW1400 |
|
CiscoPro 2501, 2502, 2503, 2504, 2505, 2507, 2509, 2511, 2513, 2514, 2516, 2520, 2521, 2522, 2523, and 2524 | Workgroup concentrators 1000, 1100, and 1400 |
|
Cisco and CiscoPro 3600 Series (includes 3620 and 3640) |
|
|
Cisco and CiscoPro 4000 series4 (includes 4000, 4000-M, 4500, 4500-M, 4700, and 4700-M) |
|
|
AS5200 Access Server |
|
|
NetBeyond Fasthub 300 and Fasthub 100+ Series |
|
|
EPS-500, EPS-1500, EPS2115, CPW-500, and CPW-2115 |
|
|
www.cisco.com) periodically for download information on the latest device support and upgrades.
Other CiscoView applications supported include:
| Application | Description | OS | Cisco IOS | Device Support |
|---|---|---|---|---|
Threshold Manager 1.1.2 | Threshold management application that monitors the availability and performance of Cisco devices | Solaris 2.4, with recommended patches as of 3/16/95, Solaris 2.5 and 2.5.1 | Cisco IOS 11.1 or 11.2 with RMON events and alarms group support | All devices with appropriate Cisco IOS or RMON features
|
StackMaker 1.0 | StackMaker manages the device membership in a Cisco stack. | Solaris 2.4, 2.5 and 2.5.1 | Cisco IOS 10.0 through 11.2 | Cisco and CiscoPro 1600, 3600, 3620, 3640, Catalyst 1900, Catalyst 2820, CPW1220, CPW1420, Fasthub 100+ and Fasthub 300 |
Flash File System | The Flash File System provides file copying and editing features for the 7000 Series routers. | Solaris 2.4, 2.5, 2.5.1 | Cisco IOS 10.0 through 11.2 | Cisco 7000, 7010, 7204, 7206, 7505, 7507, 7513 routers |
AS5200 Manager | Modem management application used to monitor, configure, and troubleshoot the AS5200 Access Server | Solaris 2.4, 2.5, 2.5.1 | Cisco IOS 10.2 or later except for 3600 devices which require Cisco IOS 11.1 or later.
| AS5200 Access Server |
TN3270 | Management module used to monitor/configure TN3270 capability embedded in Cisco devices with IBU feature set. | Solaris 2.4, 2.5, 2.5.1 | Cisco IOS 11.0(13)BT or 11.2 with cip22-14 | Cisco 7000 and 7500 (with a CIP card) |
This section contains the latest Cisco IOS (Internetwork Operating System) software version information at the time of printing.
CiscoView supports Cisco IOS Software Releases 10.0 through 11.2 with the exceptions of access servers, which require a minimum of Cisco IOS Software Release 10.2. Cisco 3600 devices require Cisco IOS Software Release 11.1 or later. Cisco 4000 series devices require Cisco IOS Software Release 10.3 or later.
New devices and further specifics on Cisco IOS support will be updated as devices become supported. For the online release notes, refer to one of the following:
The documentation for CiscoView 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 email comments to: bug-doc@cisco.com
The documents shipped with this release include:
Customer documentation can also be found on the Cisco Enterprise Customer Documentation CD or on CCO.
There are several ways to add (or incrementally install) new devices to CiscoView 4.0. For our direct customers, refer to the section "Cisco Connection Online." For our partner initiated customers, refer to the section "Partner Initiated Customer Accounts."
Customers can add new devices to CiscoView from CCO or from the Network Management Support CD. For more information, refer to the "Downloading Device Packages" chapter in the CiscoView Getting Started Guide. A quick reference version exists in the CiscoView CD Installation Instructions booklet.
For Solaris:
The pkgadd command is no longer used for installation.Please use setup.sh. See the CiscoView CD Installation Instructions booklet for the most up-to-date version of install.
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 "Downloading New Cisco Devices and Applications" for CiscoView for information on adding device support. It is ordered, or available on CCO or the Enterprise Customer Documentation CD.
If you cannot open a device in CiscoView 4.0, a message appears indicating that the device is unmanageable. This message indicates one of the following conditions:
This section lists notes and restrictions that apply to the CiscoView 4.0 release.
The installation caveats are described below.
The environment variable NMSROOT should be set to /usr/nms/CVapp. You should set this variable the right way when performing any operation related to CiscoView using SMIT. You may need to unset the environment variable once you leave the SMIT.
During integration with NetView, CiscoView adds files to the NetView directories. However, during deinstallation, if CiscoWorks is installed, then CiscoView does not remove the files added to the NetView directories. [CSCdj03332, CSCdj04418]
If CiscoView 4.0 is installed over CiscoWorks on AIX, then CiscoView is deinstalled, the menu entry CiscoView is not removed from the NetView Monitor menu. To resolve this, delete the file CiscoView from the /usr/OV/registration/C. [CSCdj12074]
CiscoView 4.0 does not detect the absence of HP OpenView or AIX NetView during deinstallation. [CSCdj11649]
If the default install directory has space limitations, you can soft link it to a different directory by using a ln -s bigdir prior to running the install. You must have super user (root) privilege to create links.
For example, enter the following:
# mkdir /bigdir/CSCOcwh
# mkdir /bigdir/CSCOcsh/CVapp
# ln-s /opt/CSCOcwh/CVapp /bigdir/CSCOcwh/CVapp
In this example, /bigdir already exists. Root creates /bigdir/CSCOcwh then /bigdir/CSCOcwh/CVapp. The /opt/CSCOcsh/CVapp is an alias name used to redirect programs to /bigdir/CSCOcwh/CVapp. Substitute your directory names where appropriate.
When CiscoView 4.0 is installed with CiscoWorks for Switched Internetworks (CWSI) 1.1 you are unable to read VlanDirector help. This error occurs when you select Help>VLAN or when you select Help>Contents. The workaround is to log in as root and enter the following at the command prompt:
# cp /cdrom/install/.config/vlanview.hlp /opt/CSCOcv/help
To use CiscoView 4.0 with CWSI 1.1 on AIX, you must first de-install CWSI, then install CiscoView 4.0 and then re-install CWSI. Another option would be to upgrade to CWSI 1.3 for AIX. [CSCdj08417]
Deinstalling CiscoView 4.0 removes CiscoWorks for Switched Internetworks 1.1.1 (CWSI) also. Currently, if you have CWSI 1.1.1 installed and try to remove CiscoView 3.x, the deinstall process removes Traffic Director and VlanDirector as well. You have to (re)install these two components after you install CiscoView 4.0. [CSCdj07672]
CiscoView 4.0 and CWSI 1.1 cannot co-exist on HP/UX. If you wish to upgrade CWSI with CiscoView 4.0, upgrade to CWSI 1.3. [CSCdj07672].
CiscoView 4.0.1 is not compatible with CiscoWorks 2.x. There are two solutions. You can upgrade to CiscoWorks 3.2.1 or later or remove it.
The CiscoView 4.0 install removes some Cisco router subclasses from the HP OpenView or NetView symbols directory. These router designations are necessary for HP OpenView or NetView to properly manage Cisco routers. The workaround for this problem is in a Software Module Update available on CCO. Download and install the "symbol" SMU from the Software Center (formerly the Software Image Library) on CCO at the following URL: http://www.cisco.com/kobayashi/sw-center/index.shtml . [CSCdj12055]
Some errors will be reported during the installation when loading MIBs into HP OpenView 4.x and 5.0/AIX NetView. For example, when you run cvinstall -f. For more information and workaround suggestions, refer to the following URLs:
http://www.cisco.com/public/mibs/app_notes/mib-compilers
or
ftp://ftpeng.cisco.com/pub/mibs/app_notes/mib-compilers
Update the path variable to include the path for the snm binaries and also set the SNMHOME environment variable.
C Shell:
setenv SNMHOME /opt/SUNWconn/snm
set path=($path /opt/SUNWconn/snm/bin)
Bourne Shell
SNMHOME=/opt/SUNWconn/snm
export SNMHOME
PATH=$PATH:/opt/SUNWconn/snm/bin
export PATH
The /opt/SUNWconn/snm is the default directory for SNM in Solaris. If SNM is installed elsewhere please change the SNMHOME and path variables accordingly.
The SNM Discover utility will not work if all the device packages are installed for CiscoView 4.0. This bug requires SNM patches for both SNM 2.2.3 and SNM 2.3. Contact Sun for the patch and reference Sun bug ID #4034954. However there are some workarounds which are given below.
SUN has released unofficial patches for this bug and they have been tested. The official patches are scheduled for the end of May. [CSCdj04391]
1. Do not use SNM Discover to create maps. Use statically created maps. If you want to add an object to the map use the Edit Menu of the SunNet Manager Console.
2. Do not install all the device packages. At install time, CiscoView will prompt for a list of device packages which you want to install. Select only those packages that you need. However, SNM Discover will still cause problems if the number of Cisco Devices entries in the /var/opt/snm/discover.conf file exceeds 100. After the installation you can manually edit this file so as to make the number of device entries less than 100.
The CiscoView installation on Solaris may fail if you do not install a Hewlett-Packard patch. This patch is required to install NNM 4.1 on Solaris 2.5 and must be installed prior to installing NNM 4.1. This patch 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. To obtain a patch
Step 1 Enter the following URL:
ftp://ovweb.external.hp.com/pub/cpe/patches/nnm/4.1x
Step 2 Click on the appropriate links to get to your software patch.
Patch numbers are not available because HP consolidates the patches periodically to contain all previous fixes. Select the one related to Network Node Manager. 4.1x by viewing the patch text files. If you have difficulty installing the patch, contact HP Service and Support.
The CiscoView installation uses the Solaris pkgadd utility. When pkgadd finishes installing CiscoView, the screen shows that the installation was successful but does not quit. Type Q to exit the pkgadd utility.
The general notes and caveats follow. They are divided into six sections:
General notes and caveats for Enterprise Network Management products are described below.
CiscoView does not support internationalization.
In high traffic situations, you might experience timeouts. To increase the timeout period, select Options>Properties from the CiscoView menu and change the value for the Timeout field.
You should not reduce the physical view polling interval below (retries*timeout), especially if you experience timeouts; this can exhaust resources on Windows and result in a general error.
CiscoView 4.0 has some community string restrictions for composite devices. A composite device is a device that contains modules that have their own IP addresses. For example, the LS1010 ASP module that can reside within the Catalyst 5500. The restriction is that the community strings of all the composite modules must match the CiscoView defaults (read-only: public, read-write: private) for the modules to be manageable. [CSCdj11583].
If you select Configure>port... from the menu, then select Interface and change Admin Status, you might see the error:
noSuchName. Could be one of:
invalid write community.
invalid MIB instance: portType.3.2
and the action is not performed.
This error occurs when CiscoView is unable to pick appropriate fonts because either or both of the following default fonts are not found in font path, or are not installed:
To verify that certain bold fonts are available in your X environment, type these commands, including the double quotes:
% xlsfonts -fn
"-dt-application-bold-r-normal-sans-12-*-*-*-*-*-*-*"
% xlsfonts -fn "-b&h-lucida
sans-bold-r-normal-sans-12-*-*-*-*-*-*-*"
Both commands should print matched fonts. If not, you need to contact your sysadmin to have the appropriate fonts installed and/or the correct font path set.
Note that NCD users may also need sysadmin's help to perform the above verification. [CSCdj38584, CSCdj07459]
For this release, use the middle mouse button to drag on UNIX. Only certain devices (such as the CAT1200, CAT1600, CAT5000, CPW16) have defined their ports for dragging across devices.
When a switch is configured as two or more domains, HP OpenView discovery might not work properly and might discover only one of the domains. If this occurs, use CiscoView to manage the domain directly rather than launching the switch from the map.
By default, SNMP standard traps are logged in the trapd.log file in HP OpenView 4.1. To view the standard traps in the event window, use the Option>Event Configuration menu to change the standard trap configuration. [CSCdi91796]
While invoking some devices, a number of MIB variables are queried and the NetView grapher is invoked. Some of the queries may time out quite often (three or more occurrences), and when this happens CiscoView does not exit gracefully and produces a core dump. [CSCdj04380]
SNM grapher doesn't display data. When you do a Monitor->Port and invoke the Grapher, the grapher doesn't display the data. Currently working with Sun Microsystems to resolve this problem. [CSCdj01623]
The CiscoView 4.0 install removes some Cisco router entries from the HP OpenView or NetView oid_to_sym file and oid_to_type file. These entries are only removed if CiscoWorks is already installed on the system. These entries are necessary for HP OpenView or NetView to properly populate the network map. The workaround is in a Software Module Update available on CCO. Download and install the "symbol" SMU from the Software Center (formerly the Software Image Library) on CCO at the following URL: http://www.cisco.com/kobayashi/sw-center/index.shtml .
CiscoView removes support for old Cisco routers from HP OpenView or NetView. [CSCdj03062]
CiscoView cannot be launched by non-root users on HP-UX 10.x [CSCdj03959]
For a Token Ring port, if you choose Monitor->Port and change the Category (default is Interface) to Token Ring Errors or Token Ring Unusual Errors, you don't see any data displayed in the monitor window. You will get an error message: expected integer but got "N/A".
Open Look caveats include:
Popup menu titles are raised; users might mistake them for menu items. [CSCdi53475]
CiscoView might fail to print to LaserJet III Printer, especially in the "LaserJet" format, due to this printer's limited memory.
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]
StackMaker caveats include:
Internal Debugging—When the StackMaker Debug option is set to On, debug messages print to the StackMaker Debug Log file. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is /tmp/.smDebugLog.
Internal Debugging—When the StackMaker Debug SNMP option is set to On, SNMP debug messages print to the StackMaker Debug Log file on the UNIX platform. The messages show the SNMP packets that have been sent and received. The default is Off. The StackMaker Debug Log file stores messages that are useful in troubleshooting problems. This log file is /tmp/.smDebugLog.
Log File from Apply Operations—The StackMaker log file stores the results of a saved stack configuration (Actions>Apply Stack Configuration). The log file is /tmp/stackmkr/sm.log. When the log file exceeds 1 MB, it automatically resets to 0 bytes.
Threshold Manager caveats include:
Some agents, most notably the Catalyst switches, impose a limit on the number of alarm and event entries that can be created. Applying a large number of thresholds to these devices will likely fail. In this case, some alarm entries might be successfully created but their associated event entries are not. These failed creations are marked as Failed in the Current Threshold Settings pane. If you attempt to delete those settings, Threshold Manager reports that the deletion failed (because it cannot delete nonexistent event entries.) In this case, you can ignore the error message, and can verify that the deletion occurred by retrieving the threshold settings after the deletion.
New policies are always added to the display list.To view the new policies, exit from the Configure Thresholds window, then reopen it. [CSCdi62741]
Policy file names won't match if IP address is used. To correct this, 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]
General notes and caveats for the Cisco Workgroup family of products follow.
When using 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 using the Segment Zoom menu from CiscoView to view the port segment, the default configuration for the Catalyst 1200 is to configure the Statistics, Short-Term history, Long-Term history and Host group. For the Catalyst 5000 it is Statistics, Short-Term history, and Long-Term history.
If you 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 be matched with 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.
If you launch Switch/Port Zoom from CiscoView and then delete one of the RMON Agents using TrafficDirector, you must re-launch CiscoView before attempting to launch Switch/Port Zoom again.
If you see "IP address is not set in sysIpAddr Mib variable," it is because the Catalyst 1200 SNMP agent does not store the correct IP address in the sysIpAddr 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.
TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
The device agent does not update the IP Address Table of MIB-II properly and does not reflect the correct IP Address information of all the device interfaces. So, the user will not be able to view the correct IP Address information of the device through Device>Configure>IP Address Table.
The user 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 being displayed, but the modification is done successfully.
The user will not be able to change the bridge type of the FDDI port to sr-only or srt.
The user 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 only supported for 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, though any particular Catalyst 2600 switch will respond to queries on only one of the MIBs based upon the release of software in the device. Cisco recommends that you upgrade your Catalyst 2600 switches to version 2.2.1 or later.
Under a heavy load condition, SNMP responses are slow. You 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 group for the new port. Use the Domain Manager to de-install 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 re-launch CiscoView before attempting to launch Switch/Port Zoom again.
TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
When multiple ports are selected, the Port>Configure window will not display the Broadcast Suppression category. This is only available for single port selection.
When enabling port security administration on a port, there may be timeouts. If this happens, increase the SNMP timeout value to approximately 10 seconds.
The WS-X2901 module will only show the speed LED lighted when the speed is configured as 100Mbps and the port is connected.
The Port Utilization tool has been removed from the Tools menu and is now available only on a per module basis on the Config>Module menu.
When reinstalling or performing a cvinstall -f CiscoView 4.0 and integrating with HP OpenView 4.1.1, you will see an error relating to the C3_2_0.my MIB file display. This error is due to duplicate definitions in the Catalyst 3000 MIB files. To correct this problem, download a new copy of the Catalyst 3000 package from the CCO web site. This package resolves CSCdj03981.
When the Catalyst 3200 is viewed using CiscoView 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, there may 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.
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 software does not allow the modification of the Parent VLAN number. [CSCdi76775]
You may 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.
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 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 re-launch CiscoView before attempting to launch Switch/Port Zoom again.
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.
Do not use the Grapher in the CiscoView Monitor 10BaseT Group Switching Ethernet window. Use the Monitor or TrafficDirector tools to see graphical views of the selected repeater ports.
When using the Switch Zoom menu from CiscoView to view multiple switch ports, the default configuration for the Catalyst 5000 is to configure Statistics only. To see the Short-Term or Long-Term history from traffic monitor, use the Domain Manager to configure the Short-Term and Long-Term group manually or use Segment Zoom to view the port first.
When using the Segment Zoom menu from CiscoView to view the port segment, the default configuration for the Catalyst 5000 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 be matched with 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, 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 100Mbps speed LED lighted if the speed is configured at 100Mbps and the port is connected.
Opening the FDDI/Ethernet Bridge category under Configure>Device can give an "unknown error." This is due to a problem with the device software.
If a general error (genErr) is displayed when changing vlanPortIslStatus, the selected port may not support ISL.
The values ifAdminStatus and ifLinkUpDownEnable 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.
Configuring ports to unsupported speeds returns a general error (genErr). This is due to a problem in the device software.
The following list details the availability of Broadcast Suppression in terms of pps (packets per second) or % (percentage) for modules on Catalyst 5000 series switches. A plus sign (+) indicates available, while a minus sign (-) indicates not. Modules not on this list do not have Broadcast Suppression. The Broadcast Suppression feature is not available on ATM and FDDI. [CSCdi90909]
| Module | Packets per Second (pps) | Percentage | Note |
|---|---|---|---|
|
|
|
|
WS-X5013 | + | + |
|
WS-X5011 | + | - |
|
| | | % available with newer hardware only |
WS-X5113 | + | - |
|
WS-X5111 | + | - |
|
WS-X5213 | + | - |
|
WS-X5020 | + | - |
|
WS-X5114 | + | - |
|
WS-X5223 | + | + |
|
WS-X5224 | + | + |
|
WS-X5213A | + | - |
|
For devices that have an expansion module, the port numbering is not consistent with the management console. Ports 17 through 32 are listed in CiscoView as Repeater 2: Port 1 through 16. [CSCdi77159]
After the first reset of the device, the user 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]
The CPW 1200/1400 and Cat 2100/2800 devices do not support the CDP and CGMP protocols. The CiscoView dialogs for these will return errors.
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.
When multiple ports of different types are selected, Port>Config may show duplicate categories.
The following firmware versions must be used in the switches:
If you configure EtherChannel or Virtual Domains in Kalpana switch models EPS2015RS, EPS2115RSM, and Pro16 while running version 9.0 firmware with STP active, the map icons become red, and you receive the following error message:
No response from the device
After restarting the system, deactivate STP before you attempt to reconfigure. This problem is fixed in version 9.1 of the device firmware. [CSCdi41317]
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 re-launch CiscoView before attempting to launch Switch/Port Zoom again.
TrafficDirector 3.3 cannot be launched for interfaces with ifIndex values greater than 1000.
General notes and caveats for the Cisco Access family of products follow.
The following WAN interface cards are supported:
The following Combo Port Modules (cpm) are supported:
The following Port Modules (pm) are supported:
The following WAN interface cards are supported:
The following network processor modules (npm) are supported:
For 4000 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 Cisco IOS 10.3 through 11.x, 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. [CSCdi28566]
| Status | Status color |
|---|---|
disabled | brown |
standby | brown |
connecting | blue |
active | green |
General notes and caveats for the Cisco High-end Business suite of products follow.
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]
CiscoView 4.0 always displays the multimode fiber SC type of ATM connector on AIPs, even when the media interface is of another type. [CSCdi53420]
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 Cisco IOS 10.3 through 11.x, 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. [CSCdi28566]
| Status | Status color |
|---|---|
disabled | brown |
standby | brown |
connecting | blue |
active | green |
When performing the Squeeze operation on a flash card, the error "Failed to Squeeze. Try increasing the timeout property under Options in the Main window" may be observed even though the operation succeeds. [CSCdj03172]
On 7513 and 7507 chassis, when the master RSP (route switch processor) is in use, the console port changes color on the CiscoView 4.0 display. However, when a slave RSP is installed, its console port mirrors that of the master, regardless of whether or not it is in use. [CSCdi49049]
To configure an LECS address for LS1010 from CiscoView, ServiceId needs to be the following: 10.1.3.6.1.4.1.353.1.5.1.<Index>, where Index is the row differentiator for configuring multiple LECS addresses. Index is an integer.
From CiscoView for LS1010, ATM Traffic Descriptor table does not show any rows. This is an agent bug. [CSCdj00685]
By default, CiscoView 3.1(1) displays two power supplies for a 7000 running Cisco IOS Release10.2 and earlier. With Cisco IOS Release 10.3 and later, power supplies are displayed based on ciscoEnvMonSupplyState values.
Following are notes and caveats for online help.
There is a problem with the online help viewer, HyperHelp, intermittently displaying the Help topic window when opening Help>Contents.
When you first open a help topic using Help>Contents and select the Back button, the HyperHelp viewer may display a blank window. This is a HyperHelp bug. [CSCdi04758]
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.
Posted: Wed Oct 9 10:39:50 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.