Table Of Contents
Release Notes for the Cisco Catalyst Switch Manager, Release 3.0.1
Server Requirements—Medium Deployments
Server Requirements—Large Deployments
Determining the Software Version
Resolved Caveats in Version 3.0.1
Cisco Catalyst Switch Manager Documentation
Obtaining Technical Assistance
Release Notes for the Cisco Catalyst Switch Manager, Release 3.0.1
The Cisco Catalyst Switch Manager is an element management system (EMS) for the Catalyst switches. Cisco Catalyst Switch Manager works in conjunction with the Cisco Element Management Framework (Cisco EMF) to provide element management that enables service providers to plan, provision, and monitor network services on Cisco devices.
This document describes system and software requirements, hardware and software support, known limitations, and available documentation for the Cisco Catalyst Switch Manager, version 3.0.1.
Contents
This document is divided into the following sections:
•
Obtaining Technical Assistance
System Requirements
This section describes the system requirements for the Cisco Catalyst Switch Manager version 3.0.1.
Server Requirements—Medium Deployments
A medium deployment consists of a Cisco EMF server monitoring fewer than twenty devices, and it requires a Sun platform configured as follows:
•
Solaris 2.8 for Cisco EMF 3.2, Patch 6
•
Sun Microsystems ™ SunBlade 2000, SunBlade 1000, Netra 20, Ultra 60, Sun Ultra 220R or similar
•
17-inch color monitor
•
2 GB RAM
•
2 processors (440 MHz or above; typically 750 MHz)
•
4 GB swap space
Server Requirements—Large Deployments
A large deployment consists of a Cisco EMF monitoring twenty or more devices, and it requires a Sun platform configured as follows:
•
Solaris 2.8 for CEMF 3.2, Patch 6
•
Sun Microsystems ™ SunFire V880, SunFire V480, Netra 1405, Enterprise 450, Enterprise 420 or similar
•
17-inch color monitor
•
4 to 8 GB RAM
•
4 processors (440 MHz or above; typically 750 MHz)
•
4 to 8 GB swap space
If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card.
Note
A typical server installation requires 1 GB 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).
Typical Client Requirements
The recommended minimum hardware requirements for clients are Sun Microsystems ™ SunBlade 100, Ultra 10 or similar with the following:
•
Solaris 2.8 for Cisco EMF 3.2., Patch 6
•
17-inch color monitor
•
512 MB RAM minimum, 1 GB RAM recommended
•
1 processor (440 MHz or above; typically 500 MHz)
•
2 GB swap space
If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card. A typical manager installation requires 500 MB of free disk space in a file system.
Tip
Use the Solaris commands swap -s and prtconf to determine the available amount of swap space and RAM on your system.
Software Requirements
This section describes the framework/software requirements for the Cisco Catalyst Switch Manager version 3.0.1.
Standalone Manager
The Cisco Catalyst Switch Manager version 3.0.1 requires the following installation/patches of Cisco EMF to operate:
•
Cisco EMF Version 3.2
•
Cisco EMF Version 3.2 Patch 6
•
Cisco EMF Version 3.2 Patch 6.2
Determining the Software Version
To determine installed Cisco EMF package names and version numbers, enter the following Cisco EMF command:
<CEMF ROOT>/bin/cemf install -show
Note
<CEMF ROOT> is the location where the Cisco EMF packages were installed. Typically, the location for <CEMF ROOT> is /opt/cemf.
To determine installed Cisco EMF package names, use the following Solaris command sequence:
pkginfo | grep -v CSCOTo determine the versions of installed Cisco EMF packages, use the following Solaris command:
pkginfo -l <package name>
Note
Replace <package name> with the name of the Cisco EMF packages.
Supported Hardware
Table 1 lists the hardware that the Cisco Catalyst Switch Manager, version 3.0.1, supports:
Supported Software
The Cisco Catalyst Switch Manager, version 3.0.1, supports the following IOS and Catalyst OS software.
The following IOS releases are supported as listed by chassis family:
•
Catalyst 2950 series switch—12.1(11)EA1 and 12.1(12c)EA1
•
Catalyst 3550 series switch—12.1(11)EA1, 12.1(12c)EA1, and 12.1(12)EA1
•
Catalyst 4000/4500 series switch—12.1(12c)EW1 and 12.1(13)EW
•
Catalyst 6500 series switch—12.1(13)E, 12.1(13)E1, and 12.1(13)E4
The following Catalyst OS version is supported by the Catalyst 6000/6500 series switch: 7.5(1).
The following table identifies the Hybrid OS combinations supported by device.
Table 2 Supported Hybrid OS Combinations
IOS Version Catalyst OS Version12.1(12c)
6.3(10)
12.1(12c)E4
6.3(8)
12.1(12c)E4
6.3(9)
12.1(12c)E4
7.5(1)
12.1(12c)E4
7.6(1)
12.1(13)E
7.5(1)
Note
The above versions of Catalyst OS and IOS have been extensively tested with the Cisco Catalyst Switch Manager software. Other versions and combinations of Catalyst OS/IOS should interoperate with the manager, although there may be unanticipated incompatibilities or errors.
Caveats
Caveats are described in the following sections:
•
Resolved Caveats in Version 3.0.1
Resolved Caveats in Version 3.0.1
The following limitations which existed in previous versions of the Cisco Catalyst Switch Manager, formerly known as Cisco 6500/7600 Series Manager, but have been resolved in version 3.0.1 of the Cisco Catalyst Switch Manager.
Table 3 Resolved Caveats
Open Caveats
This section describes known limitations that exist in the Cisco Catalyst Switch Manager, version 3.0.1.
•
CSCdx66874
Symptoms: HSRP on OSM GE WAN Inter (Hybrid): hello and hold intervals do not update.
Conditions: Hybrid and Native IOS switches.
1. From the modify sub-dialog, chose an existing group and modify the timers. Verify that the action worked by checking the running config. Refresh the dialog.
2. Modifying Hello and Hold intervals on the OSM GE WAN interface HSRP modify sub-dialog works, but the values don't update.
Workarounds: None. 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. There is no known workaround for this issue.
•
CSCdx66943
Symptoms: There is no Hybrid OS or Catalyst OS mapping for IF-MIB.ifAlias. The field (Interface Description) should be disabled on all interface dialogs
Conditions: Hybrid and Native IOS switches.
Workarounds: None.
•
CSCdx67688
Symptoms: VTP transparent mode cannot be set on Catalyst OS 6.3 MIBs.
Conditions: The values displayed in the VTP dialog for a Hybrid OS network element running Catalyst OS 6.3 does not match with the output of the IOS command #show vtp status. Also, clicking the "Update VTP" button reports action failed. The workaround is to view and configure the VTP attributes from the switch (for a Hybrid switch running Catalyst OS 6.3).
Workarounds: None.
•
CSCdx67692
Symptoms: There are certain preconditions that must be met before ports can be added to an etherchannel, for example, they must all either be configured as L2 or L3 ports not a mix, they must be the same duplex mode, and they must all be in the same VLAN.
Conditions: Problem on 6506 running native IOS c6sup_rp-JSV-M Version 12.1(8a)E. The user has no way of knowing from the etherchannel dialog if the ports are L2 or L3, what VLAN they are part of. The user must open the Ethernet Interface dialog to check these as well as the duplex and speed. The user also needs the Ethernet Interface dialog to adjust any of these settings; he then needs to open the VLAN dialog to make any changes to the VLANs that the ports belong to.
Workarounds: None.
•
CSCdx68103
Symptoms: In the Ethernet Interface Dialog, Configuration tab, the user can change the port Speed, duplex mode, mac address MTU size, and trunking mode. Most of them are drop down menus where the user can choose a value and save. The problem is these values are not supported on all interfaces.
Conditions: Hybrid and Native IOS switches.
Problem on device running native IOS and hybrid OS. Often times a user can choose a certain duplexing option from the drop down, a specific speed from another drop down, edit the mac address and choose a trunking mode. If two of these are not supported by the interface the user will get the following error:
C6576Managermodule.c6576MEtherInterfacePortTable- FAILEDThe SNMP data repository returned the code snmpWrongValue:
Returned Message: wrongValueC6576Managermodule.c6576MEtherInterfacePortTable- FAILED
The SNMP data repository returned the code snmpWrongValue:
Returned Message: wrongValueThere is an error for each unsupported action. There are several issues here:
–
The user doesn't know which items were unsupported. He just knows out of the 4 actions 2 failed.
–
Giving a message about the SNMP table is good for the developer but doesn't offer much to the user. An better error report would be for example, the MAC address is read only for this interface, or the interface supports speeds of 100Mb/s and 1000Mb/s only.
–
Having drop down items where the user can select from a list and then having the action fail because the users selection from the list is unsupported is contradictory of the EM. Unsupported items in a drop down menu should be greyed out.
–
Field boxes that allow users to enter values should be greyed out for read only attributes. For example, when the MAC address is read only the user shouldn't be able to change it and attempt to save.
Workarounds: None.
•
CSCdx69454
Symptoms: 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 pick list), only the first object selected will be updated.
Conditions: 6506 12.1(11b)E
Workarounds: Multi select does not work. Change one object at a time.
•
CSCdx70541
Symptoms: The Operational Status field of the status tab and the Duplex field of the configuration tab in the OSM Channelized SONET Interface dialog, display invalid values.
Conditions: This issue is observed in the IOS 12.1(11b)E SNMP Agent.
Workarounds: The workaround 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.
•
CSCdx72649
Symptoms: EIGRP always looks applied to etherchannel/interface even when not.
Conditions: 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.
Workarounds: None.
•
CSCdx76259
Symptoms: Show chassis image even if chassis decommissioned.
Conditions:
1. Deploy a chassis.
2. If the chassis is not commissioned then only the Cisco Image is available. Make available chassis image with blank module slots (i.e., nothing discovered) for the following reasons:–
Since this will help user identify the chassis type
–
Common look and feel with other EMs
–
If decision is made later to take away Cisco Image, then there will be no image in Map Viewer application for the chassis
Workarounds: None.
•
CSCdx76357
Symptoms: Action vs. Invocation report.
Conditions:
1. Deploy a chassis
2. Commission the chassis
3. The report received here is actually for invocation of the action, not the success of the actual action.
4. The report should reflect what is the end result. i.e. wait until the chassis has completely transitioned to normal state before informing the user that commissioning was successful.Workarounds: None.
•
CSCdx76548
Symptoms: Inconsistencies between auto discovery and manual discovery.
Conditions: A decommissioned network element that was deployed to be auto Discovered 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. This discrepancy occurs because the chassis of the auto-discovered 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.
Workarounds: None.
•
CSCdx76725
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.
•
CSCdx79847
Symptoms: Local propagation delay - change 1 min. sync model.
Conditions: 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 ems 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.
Workarounds: Give enough give enough time for EM to get updated.
•
CSCdx79861
Symptoms: During deletion/removal allow for selection than asking user for specific.
Conditions:
1. Deploy and commission a chassis
2. Open BGP dialog
3. During deletion/removal of networks, neighbors, or anything the user is asked to enter specific values.
4. Allow user to select from the list rather than making him provide specific field values again.Workarounds: None.
•
CSCdx80122
Symptoms: Propagation delay for redistribution table.
Conditions:
1. deploy/commission a chassis.
2. open BGP dialog - redistribution tab.
3. provide entries for fields in "Edit Redistribution Table" section.
4. Click Add and then click refresh screen.
5. on the device you can see the entries present, but you have to hit refresh several times for the screen to show me the value.Workarounds: None.
•
CSCdx80138
Symptoms: Redistributing OSPF in BGP required additional parameters.
Conditions: IOS 6509 Switch.
1. Deploy / commission a chassis.
2. Open BGP dialog - redistribution tab.
3. Here for redistribution, if "OSPF" is chosen as an option, there are insufficient parameters for configuration.
4. The default behavior is to not redistribute any routes from OSPF into BGP.In other words, the simple redistribute command, such as redistribute OSPF 1 under router BGP 1 does not work. Therefore additional parameters need to be provided for configuration of OSPF.
Workarounds: None.
•
CSCdy01467
Symptoms: Dialog update time under 5 seconds (as per PRD).
Conditions: As per PRD, standard dialog response should be under 5 seconds in full performance mode. Performance testing finds approximately 8 second response time with 250 chassis operational. May be tied to simulator load, will investigate further in next release.
Workarounds: None.
•
CSCdy52942
Symptoms: ISIS Hello-Interval shown for Interfaces is default rather than actual.
Conditions: When an interface's ISIS hello interval has been configured with a value of minimal, the value displayed in the routing protocol tab of any interface dialog is the default value and not the string 'minimal'. This not an issue when the hello interval is set as an integer. This behavior may mislead the user into unknowingly changing this value thinking it was set to the default rather than minimal.
Workarounds: None.
•
CSCdz03502
Symptoms: Second level chassis object should be removed.
Conditions: Currently when a 6500 or 7600 chassis is deployed, a second level chassis object is deployed below the main chassis object. This second chassis should be removed and all modules & software placed below the top level chassis object.
Workarounds: None.
•
CSCdz03510
Symptoms: Deployed chassis name should be prepended with chassis type.
Conditions: When a chassis is auto-discovered, the top level chassis object is named by the IP address. The chassis type should be prepended to this IP address.
Example: 192.168.133.145 should be C6509-192.168.133.145
This behavior is consistent with the C12K Manager.
Workarounds: None.
•
CSCdz79526
Symptoms: CCSM keeps telnet queries after deleting chassis.
Conditions: After removing decommissioning the chassis the telnet queries persisted, and after deleting the chassis from CCSM the telnet sessions remained open. It appears to just be holding the telnet session.
Workarounds: None.
•
CSCdz80221
Symptoms: When you uninstall a client CCSM, the containers and chassis are left behind on the CEMF install of the client box. Since CCSM is no longer there, the icons no longer show up properly. The menus are also errored once CCSM has been removed.
The client uninstall should delete all containers and chassis from the client side, and basically leave a clean install of CEMF.
Conditions: Install CCSM client, deploy some objects, uninstall client.
Workarounds: None.
•
CSCdz81704
Symptoms: Cannot change VTP mode using EM's dialog
Conditions: VTP Management Dialog, Details tab - change the mode from the current value to any other value and click on the 'Update VTP' button.
Workarounds: None.
•
CSCdz87315
Symptoms: Hybrid 6509 discovered as Catalyst OS when Sup mod in slot 2.
Conditions: When the Supervisor is in slot 2 the EM deploys the device as a Catalyst OS only. The MSFC is not discovered.
Actual Results: A Hybrid 6509 should be discovered.
Workarounds: None.
•
CSCdz87332
Symptoms: EMS does not recover when Sup moved from slot 1 to slot 2 on hybrid.
Conditions:
–
When the Supervisor on a hybrid 6509 is moved form slot 1 to slot 2 the em goes to lostcomms and does not recover.
–
The 6509 goes to lostcomms and does not recover.
–
An alarm should indicate that supervisor in slot 1 is in lostcomms and a new supervisor should be discovered - the EM show the device in normal state. (after some time)
Workarounds: None.
•
CSCea00778
Symptoms: Module GIF not changed after decommissioning and deletion.
Conditions: When decomissioning and deleting a module the GIF should change to an empty slot GIF and the user should be able to right click on the slot and get a generic menu. In this case the GIF does not change and the right click has no effect.
A GIF showing an empty slot should be displayed. Right click should be enabled.
Workarounds: None.
•
CSCea02437
Symptoms: Creating qos class map on 2950 with match-any clause not valid.
Conditions: When creating a class map in the qos dialog on the 2950, the match-all option is not valid. Also the only match condition is the DSCP. IP Precedence is not valid. Finally the valid ranges for DSCP are 0,8,16.... not 0,1,2,3,.... like it is for the 6K and the 3550. Only match-all with DSCP should be available.(gray out the rest).
Workarounds: None.
•
CSCea02568
Symptoms: QoS Policy Map Dialog not supported on Catalyst OS needs to be grayed out.
Conditions: QoS Policy Map dialog not supported on Catalyst OS. The dialog should be disabled when dealing with Catalyst OS.
Workarounds: None.
•
CSCea03922
Symptoms: Fields need graying out in QoS Policy Map Dialog for Hybrids.
Conditions: The "Microflow Policing" and "Named Aggregate" fields need to by grayed out on Hybrids in Qos Policy Map dialog - Policy Map Classes tab.
Workarounds: None.
•
CSCea04244
Symptoms: Microflow Enabled not available on 2950 in QoS Policy Map dialog.
Conditions:
–
Microflow enabled in Qos Policy Map Dialog, Policy Map Classes tab, is not available and it should be grayed out on the 2950 and the 3550. It should also be grayed out in the Qos Policy Map Add Dialog that is invoked when the Add action is executed.
–
Starting Ranges are incorrect in the Qos Policy Map Add Dialog.
–
Named aggregate is not available in the 2950, so it should be grayed out also in both dialogs.
Workarounds: Telnet to the device and get various details.
•
CSCea06120
Symptoms: Can only add one class map ACL match; dialog reports failure when you attempt adding multiple ACL matches
Conditions: QoS Management Dialog, Class Maps tab - change a class map to have more than one ACL match by changing the 'Match ACL' field to hold a space separated list of ACL matches that are preset on the device.
Workarounds: None.
•
CSCea07868
Symptoms: EM does not install with uninitialized CEMF.
Conditions:
1. Load the cemf environment
2. Load 5.11 patch
3. Try to install the EM without starting CEMF.Actual Results: Installation fails.
Expected Results: The EM should install.Workarounds: Install the EM after cemf has been started.
•
CSCea08776
Symptoms: CCSM opens telnet and issues commands before commissioning
Conditions: One 6513 IOS chassis c6sup2_rp Software (c6sup2_rp-PS-M), Version 12.1(13)E.
Problem was found while preparing for soak test.When using autoDiscovery to deploy a chassis, th


