|
|
These release notes describe the features, modifications, and caveats for the Cisco 6500/7600 Series Manager (C65/76M). The caveats apply to Catalyst 6500 switches and Cisco 7600 OSR systems that are monitored by the Cisco 6500/7600 Series Manager with Cisco Element Management Framework (CEMF) version 3.1 with Patch 1.
 |
Note The most current version of these release notes can be found at the following World Wide Web address: http://www.cisco.com/univercd/cc/td/doc/lan/cat6000/6500ems/index.htm |
This publication consists of these sections:
This section describes the system requirements for the Cisco 6500/7600 Series Manager release 1.0.
A small deployment consists of a CEMF monitoring fewer than three Catalyst 6500 switches or fewer than three Cisco 7600 OSR systems, and it requires that the CEMF server be a Sun Ultra 60, configured as follows:
A large deployment consists of a CEMF monitoring three or more Catalyst 6500 switches or three or more Cisco 7600 OSR systems, and it requires that the CEMF server be a Sun Enterprise 450, configured as follows:
A typical deployment consists of Sun Ultra 60 configured as follows:
|
Note If you are planning to run graphically intensive applications on this workstation, we recommend that you to use a Sun color card (for example, 24-bit color). A typical server installation requires 300 MB of free disk space in a file system (for example, /opt). An appropriate amount of free disk space for database files is also required. |
|
Note Use the Solaris commands swap -s and prtconf to determine the available amount of swap space and RAM, respectively, on your machine. |
The Cisco C6M supports the following Catalyst 6500 equipment:
This software release runs on the CEMF release 3.1 platform with CEMF release 3.1 patch 1. The C65/76M also uses the version of Perl that is installed with CEMF.
|
Note The Supervisors must be running Supervisor IOS. The C65/76M does not support Catalyst 6500 switches running CATOS. |
Use the C65/76M with the following Cisco Supervisor IOS releases:
To determine installed CEMF packages and version numbers, use the following CEMF command:
|
Note Replace <CEMFROOT> with the location where the CEMF packages were installed. For example, the standard location for <CEMFROOT> is /opt/cemf |
Alternatively, to determine installed CEMF packages, use the following Solaris command sequence:
To determine the versions of installed CEMF packages, use the following Solaris command:
|
Note Replace <package name> with the name of the package for which information is required. |
To determine which Perl binary is being used by the C65/76M, perform the following:
Step 2 Execute the following command:
Step 3 Execute the following command:
The following command should return:
If this command returns another value, then the C65/76M software may not function correctly. To correct this problem, remove the existing Perl binary path from the super-user's PATH environment variable. Please contact the system administrator for more information.
This section describes known limitations that exist in the Cisco 6500/7600 Series Manager.
When you use the dialogs to create new VLAN, EtherChannel, EIGRP, and OSPF objects, the new objects are not automatically added to the object list.
Workaround: Reselect the correct software after the object has been created to refresh the object list.
The incorrect object is automatically selected in the object list when you launch a sub-dialog. When you launch a sub-dialog, the default object selection is based on the selection in the main dialog when you first launched it. Changing the object selection in the main dialog before launching the sub-dialog will not change the default selection of the sub-dialog.
Workaround: Select the correct object in the sub-dialog before making any configuration changes.
Dialogs take a long time to return values for attributes when the object is in the lostcomms or the discoverylostcomms state. Although connectivity has been lost, the dialogs attempt to retrieve data.
Workaround: There is no workaround.
The following error is reported during the installation when you select the upgrade package:
ObjectFileParser: create/delete failure
ERROR: Action returned an error.
Workaround: No workaround is necessary because this error message has no negative effects. The package is successfully installed.
During auto discovery, the system sets the read/write community strings to the first community string to which a device responds. By default, this configuration will be public. The device fails to save any configuration changes while the write community is set to this value. You can not save configuration changes to auto-discovered devices.
Workaround: To avoid this condition, remove the public community string and add the private community string to the community list in the auto-discovery dialog. Auto discovery sets both community strings to private so that you can make configuration changes.
To resolve this condition, set the write community to private by using the relevant object configuration dialog for the device.
After you delete some objects, they continue to appear in persistent maps. These objects have names such as 0x00000101:0x0000126d and appear in persistent maps (not in views). These objects can not be deleted.
This problem occurs after you restart the EventChannelManager process while the MapServer process is running. This problem does not occur under normal CEMF use, including a CEMF stop followed by a CEMF stop.
Workaround: Restart the MapServer using SysMgrClient or restart CEMF by performing a CEMF stop followed by a CEMF start.
Changes to the SNMP community strings in the SNMP tab of the Network Element dialog do not propagate down to child objects.
Workaround: Redeploy objects with the correct SNMP community strings.
On the Catalyst 6006 and Catalyst 6506 chassis, the number of slots on the inventory tab of the chassis dialog is set to 9.
Workaround: There is no workaround.
For the 6509NEB chassis, the type attribute on the details tab of the power supply dialog is reported as "other."
Workaround: There is no workaround.
The model on the inventory tab of the supervisor module dialog is reported as WS-X6K-SUP1A-2GE for the WS-X6K-SUP1A-MSFC and WS-X6K-S1A-MSFC2 cards and WS-X6K-SUP2-2GE for the WS-X6K-S2-MSFC card.
Workaround: There is no workaround.
The Firmware version attibute on the inventory tab of the supervisor module dialog is empty for the WS-X6K-SUP1A-MSFC and WS-X6K-S1A-MSFC2 cards.
Workaround: There is no workaround.
The performance tab of the supervisor module dialog reports non-zero CPU usage values for a redundant supervisor. These are the values for the primary supervisor.
Workaround: There is no workaround.
On releases before Cisco IOS Release 12.1(6)E, the size (bytes) column of the system flash memory inventory table on the inventory tab of the supervisor module dialog will display -1 for flash devices that have been removed from the system.
Workaround: There is no workaround.
Changing the MAC address attribute in the Ethernet interface dialog has no effect. The attribute is read-only, but CEMF can not display the attribute correctly as read-only.
Workaround: There is no workaround.
Values of greater than 100% are reported for the bandwidth utility attribute on the performance tab of the Ethernet interface dialog. Such a report can happen when the 32-bit counters wrap back to 0.
Workaround: The value will correct itself on the next polling interval.
An empty file is created in the TFTP directory of the CEMF server host when the IOS image or configuration backup action is executed and the TFTP host is not the CEMF server. The correct file is created on the TFTP host specified.
Workaround: There is not workaround.
The message text column truncates the syslog message.
Workaround: Resize the message text column manually by moving the mouse to the right side of a column header; it will become a double-headed arrow.
You can not save changes to the additional notes tab on the VTP dialog.
Workaround: There is no workaround.
No details are logged to the controller log file as indicated by the error message when you add or remove interfaces from an EtherChannel. The details are logged to the asyncSnmpDataRepository.log file.
Workaround: There is no workaround.
No error message is reported when you add duplicate entries or delete non-existent entries from the global neighbor routers table in the neighbor table of the OSPF dialog.
Workaround: There is no workaround.
No error message is displayed when you add duplicate entries or remove non-existent entries from the EIGRP local network table. No error message is displayed when you create or delete EIGRP processes.
Workaround: There is no workaround.
Refer to the following additional documentation for C65/76M information:
Refer to the following additional documentation for CEMF information:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
Posted: Sat Jan 18 09:16:02 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.