|
|
This publication consists of these sections:
This section describes the system requirements for the Cisco 6500/7600 Series Manager version 2.1.
A small deployment consists of a CEMF server monitoring fewer than twenty Catalyst 6500 series switches or fewer than twenty Cisco 7600 series Internet Routers, and it requires a Sun Ultra 60 configured as follows:
A large deployment consists of a CEMF monitoring twenty or more Catalyst 6500 series switches or twenty or more Cisco 7600 series Internet Routers, and it requires a Sun Enterprise 450 configured as follows:
 |
Note A typical server installation requires 1Gb of free disk space in a file system (for example, /opt). An appropriate amount of free disk space for database files is also required (100 Mb + approximately 3Mb per device). |
A typical deployment consists of a Sun Ultra 60 configured as follows:
|
Note If you are planning to run graphically intensive applications on this workstation, we recommend that you use a Sun color card (for example, 24-bit color). |
|
Note Use the Solaris commands swap -s and prtconf to determine the available amount of swap space and RAM on your system. |
This section describes the framework/software requirements for the Cisco 6500/7600 Series Manager version 2.1.
The Cisco 6500/7600 Series Manager version 2.1 requires the following installation/patches of CEMF to operate:
The Cisco 6500/7600 Series Manager version 2.1 has been verified to be coresident with the Cisco 12000 Series Manager. In order to utilize these two managers in a coresident fashion, the following installations/patches are required:
|
Note Due to caveat CSCdx73999, the Cisco 12000 Manager must be installed before the Cisco 6500/7600 Manager in order for a coresident installation to operate properly. |
To determine installed CEMF package names and version numbers, enter this CEMF command:
|
Note <CEMF ROOT> is the location where the CEMF packages were installed. Typically, the location for <CEMF ROOT> is /opt/cemf. |
To determine installed CEMF package names, 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 CEMF packages. |
Table 1 lists the hardware that the Cisco 6500/7600 Series Manager, version 2.1, supports:
| 1MSFC = Multilayer Switch Feature Card
2QoS = quality of service 3GBICs = Gigabit Interface Converters 4SONET = Synchronous Optical Network 5SDH = Synchronous Digital Hierarchy 6OSM = Optical Services Module 7MM = multimode 8SM-IR = single mode-intermediate range 9SM-LR = single mode-long range 10SM-SR = single mode-short range |
The Cisco 6500/7600 Series Manager, version 2.1, supports Native IOS Release 12.1(3a)E3 to Release 12.1(11)E. It also supports Hybrid OS in the following combinations:
|
Note The Cisco 6500/7600 Series Manager does not support Catalyst 6000 family switches or Cisco 7600 series Internet Routers running only Catalyst software (no Multilayer Switch Feature Card installed). |
This section describes known limitations that exist in the Cisco 6500/7600 Series Manager, version 2.1.
When you use the dialogs to create a new VLAN, EtherChannel, EIGRP, and OSPF objects, the new objects are not automatically added to the object list.
Workaround: To refresh the object list, reselect the correct software after the object has been created.
During autodiscovery, the system sets the read/write community strings to the first community string to which a device responds. By default, this configuration is public. The device fails to save any configuration changes while the write community is set to this value. You cannot save configuration changes to autodiscovered devices.
Workaround: To avoid this problem, remove the public community string and add the private community string to the community list in the autodiscovery dialog. Autodiscovery sets both community strings to private so that you can make configuration changes.
To resolve this problem, set the write community to private by using the relevant object configuration dialog for the device.
For the Catalyst 6509-NEB chassis, the type attribute on the details tab of the power supply dialog is reported as "other."
The firmware version attribute on the inventory tab of the supervisor engine dialog is empty for the WS-X6K-SUP1A-MSFC and WS-X6K-S1A-MSFC2 modules.
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 engine dialog displays -1 for Flash devices that have been removed from the system.
Changing the MAC address attribute in the Ethernet interface dialog has no effect. The attribute is read-only, but CEMF cannot display the attribute correctly as read-only.
stpxSpanningTreePortCostMode always returns short(1)
Workaround: This is a Cisco IOS caveat appeared in Release 12.1. The problem is resolved in Release 12.2 only.
STACK-MIB.moduleStandbyStatus always returns "other." Cisco IOS caveat CSCdt54959 has been resolved in Cisco IOS Release 12.1(8a)EX and above.
Workaround: Upgrade Cisco IOS software—no other workaround is available.
When deploying a chassis, if an invalid IP address is specified (e,g, the address of an MSFC card or a different type of chassis) no error message is immediately reported.
Workaround: None. When the network element is commissioned the object will go into the mismatched state and an alarm will be generated at that time to notify the user of the problem.
Network elements deployed in a decommissioned state and never commissioned will not appear in the selection list in chassis, module and interface selection dialogs. Network elements which have been commissioned and then decommissioned will appear (inconsistent behaviour).
Workaround: Utilize the map view to view all network element instances, or always deploy specific chassis with network element during initial deployment.
A decommissioned network element that was deployed to be autoDiscovered does not resemble a decommissioned manually deployed network element. When looking at these deployed objects via the map viewer, the manually deployed object will display two icons, one for the chassis object and another for the software object. The auto- discovered chassis will only display a single icon for the software object.
Workaround: This discrepancy occurs because the chassis of the auto-discoverd chassis is not known until the discovery task has been initiated by commissioning. Therefore, once both network elements are commissioned, they will appear as expected
When commissioning a network element, the network element object will immediately appear as though it is in a normal state, even before any of its child objects. The user can only invoke actions on objects that are in the normal state. Therefore this behaviour may mis-inform the user as to the network element's actual state.
Workaround: Before executing any action, the user should wait until the Software and Chassis objects are in a normal state. This can be done by observing the software and chassis object states via their dialogs and/or the map viewer.
When a network element object is commissioned with incorrect or missing passwords and/or SNMP communities, the object will briefly go into a "normal" state. After a few seconds the object will eventually transition into the appropriate "lostcomms" state.
Workaround: None. During the few seconds of the abovementioned transition, any dialogs which are opened may display ERROR. Once the "lostcomms" alarm is raised, correcting the passwords will return the network element and all associated objects to the normal state.
Toggling between two opposing actions (ex. enable/disable a routing protocol) may report an incorrect message if the anti-action is issued too soon. Even though the Manager reports the success of the first action, the ems is not updated immediately and thus the user may have to wait up to 1 minute before successfully issuing the opposing action.
Workaround: Wait for the resynchronization to occur (over 1 minute) at which point the Manager has resynchronized the internal configurations with the switch.
Modifying the Hello and Hold intervals of the OSM GE WAN interface HSRP modify sub-dialog works (i.e. updates on the switch), but the values don't update in the gui.
Workaround: There is no known workaround for this issue.
The values displayed in the VTP dialog for a Hybrid OS network element running CatOS 6.3 does not match with the output of the IOS command #show vtp status. Also, clicking the "Update VTP" button reports action failed.
Workaround: The only workaround is to view and configure the VTP attributes from the switch (for a Hybrid switch running CatOS 6.3).
When attempting to do bulk updates on the VTP objects of several software objects displayed via the vtp dialog (i.e. selecting several objects from the vtp dialogs picklist),only the first object selected will be updated.
Workaround: Update each software object's VTP object separately.
The OperationalStatus field of the status tab and the Duplex field of the configuration tab in the OSM Channelized SONET Interface dialog, display invalid values. This issue is observed in the IOS 12.1(11b)E SNMP Agent.
Workaround: The work around is to ignore the Duplex field (since OSM Channelized Sonet interfaces are always full duplex), and telnet to the switch to check the operational status via the running-config.
Bad error handling when trying to restore an image that is too large for the storage filesystem. When attempting to restore an image to the device that is larger than the amount of space available on the device the following error message is displayed:
Workaround: If the above messsage is observed, verify the amount of space available for the image.
The EIGRP frame of the Routing Protocol tab in any Interface dialog displays all EIGRP routing processes running on the device. The user cannot easily determine which routing processes are actually configured for the interface.
The Manager will fail to connect to a device when the device prompt has no special characters (eventually ends up in lostcomms). When connecting to a device, the Manager expects the prompt to be any text ending with `$', `%', `#' or `>'.
Workaround: Ensure the definition of the prompt on the managed switches ends with one of the abovementioned characters.
Refer to these additional publications for Cisco 6500/7600 Series Manager information:
Refer to these additional publications for CEMF information:
These sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped 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 through an annual subscription.
You can order Cisco documentation in these ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
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 online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Feb 25 06:50:44 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
