Table Of Contents
Release Notes for the Cisco 7600 Router Manager, Release 3.1
Server Requirements—Medium Deployments
Server Requirements—Large Deployments
Determining the Software Version
Resolved Caveats in Version 3.1
Cisco 7600 Router Manager Documentation
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for the Cisco 7600 Router Manager, Release 3.1
The Cisco 7600 Router Manager is an element management system (EMS) for the Cisco 7600 series internet routers. Cisco 7600 Router 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 7600 Router Manager, version 3.1.
Contents
This document is divided into the following sections:
•
Obtaining Technical Assistance
•
System Requirements
This section describes the system requirements for the Cisco 7600 Router Manager version 3.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:
•
•
•
•
•
•
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:
•
•
•
•
•
•
If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card.
Note
Typical Client Requirements
The recommended minimum hardware requirements for clients are Sun Microsystems ™ SunBlade 100, Ultra 10 or similar with the following:
•
•
•
•
•
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
Software Requirements
This section describes the framework/software requirements for the Cisco 7600 Router Manager version 3.1.
Standalone Manager
The Cisco 7600 Router Manager version 3.1 requires the following installation/patches of Cisco EMF to operate:
•
•
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
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
Supported Hardware
Table 1 lists the hardware that the Cisco 7600 Router Manager, version 3.1, supports:
Supported Software
The Cisco 7600 Router Manager, version 3.1, supports the following IOS software.
•
•
Note
Caveats
Caveats are described in the following sections:
•
Resolved Caveats in Version 3.1
The following limitations which existed in previous versions of the Cisco 7600 Router Manager, formerly known as Cisco 6500/7600 Series Manager, but have been resolved in version 3.1 of the Cisco 7600 Router Manager.
Table 2 Resolved Caveats
Open Caveats
This section describes known limitations that exist in the Cisco 7600 Router Manager, version 3.1.
•
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-window, chose an existing group and modify the timers. Verify that the action worked by checking the running config. Refresh the window.
2. Modifying Hello and Hold intervals on the OSM GE WAN interface HSRP Modify sub-window works, but the values don't update.
Workarounds: None. Modifying the Hello and Hold intervals of the OSM GE WAN interface HSRP Modify sub-window works (i.e. updates on the switch), but the values don't update in the GUI. There is no known workaround for this issue.
•
Symptoms: There is no Hybrid OS or Catalyst OS mapping for IF-MIB.ifAlias. The field (Interface Description) should be disabled on all interface windows
Conditions: Hybrid and Native IOS switches.
Workarounds: None.
•
Symptoms: VTP transparent mode cannot be set on Catalyst OS 6.3 MIBs.
Conditions: The values displayed in the VTP window 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.
•
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 window if the ports are L2 or L3, what VLAN they are part of. The user must open the Ethernet Interface window to check these as well as the duplex and speed. The user also needs the Ethernet Interface window to adjust any of these settings; he then needs to open the VLAN window to make any changes to the VLANs that the ports belong to.
Workarounds: None.
•
Symptoms: In the Ethernet Interface window, 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:
–
–
–
–
Workarounds: None.
•
Symptoms: When attempting to do bulk updates on the VTP objects of several software objects displayed via the VTP window (i.e., selecting several objects from the VTP windows 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.
•
Symptoms: The Operational Status field of the status tab and the Duplex field of the configuration tab in the OSM Channelized SONET Interface window, 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.
•
Symptoms: EIGRP always looks applied to etherchannel/interface even when not.
Conditions: The EIGRP frame of the Routing Protocol tab in any Interface window 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.
•
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:–
–
–
Workarounds: None.
•
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.
•
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.
•
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.
•
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.
•
Symptoms: During deletion/removal allow for selection than asking user for specific.
Conditions:
1. Deploy and commission a chassis
2. Open BGP window
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.
•
Symptoms: Propagation delay for redistribution table.
Conditions:
1. deploy/commission a chassis.
2. open BGP window, 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.
•
Symptoms: Redistributing OSPF in BGP required additional parameters.
Conditions: IOS 6509 Switch.
1. Deploy / commission a chassis.
2. Open BGP window, 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.
•
Symptoms: Network recovery time from management loss over 10 minutes (PRD).
Conditions: It took the system approx. 40 minutes to go from normal to lostcomms on interface shutdown, with a database of only 50 7609s. C6576MCntrllr cored with memory size close to 2GB near the end of the 40 minutes.
•
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 window 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.
None of the 50 recovered after 30 minutes of bringing the interface back up. The first chassis recovered around 47 minutes after interface up, and a second one recovered after 62 minutes. Six other chassis had Hardware discovered okay, but software stuck in discovery. The rest are stuck in lostcomms and could not recover overnight.
Workarounds: None.
•
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.
•
Symptoms: EM keeps telnet queries after deleting chassis.
Conditions: After removing decommissioning the chassis the telnet queries persisted, and after deleting the chassis from the EM the telnet sessions remained open. It appears to just be holding the telnet session.
Workarounds: None.
•
Symptoms: When you uninstall a client EM, the containers and chassis are left behind on the Cisco EMF installation of the client box. Since the EM is no longer there, the icons no longer show up properly. The menus are also errored once the EM has been removed.
The client uninstall should delete all containers and chassis from the client side, and basically leave a clean install of Cisco EMF.
Conditions: Install the EM client, deploy some objects, uninstall client.
Workarounds: None.
•
Symptoms: Cannot change VTP mode using EM's window
Conditions: VTP Management window, Details tab - change the mode from the current value to any other value and click on the 'Update VTP' button.
Workarounds: None.
•
Symptoms: Backup Switch Fab Module shouldn't be on Switch Fabric Module Performance window.
Conditions: The backup switch fabric module should not be included in the Performance tab of the Switch Fabric Module window under statistics.
Workarounds: None.
•
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.
•
Symptoms: EMS does not recover when Sup moved from slot 1 to slot 2 on hybrid.
Conditions:
–
–
–
Workarounds: None.
•
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.
•
Symptoms: Creating QoS class map on 2950 with match-any clause not valid.
Conditions: When creating a class map in the QoS window 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.
•
Symptoms: QoS Policy Map window not supported on Catalyst OS needs to be grayed out.
Conditions: QoS Policy Map window not supported on Catalyst OS. The window should be disabled when dealing with Catalyst OS.
Workarounds: None.
•
Symptoms: Fields need graying out in QoS Policy Map window for Hybrids.
Conditions: The "Microflow Policing" and "Named Aggregate" fields need to by grayed out on Hybrids in Qos Policy Map window, Policy Map Classes tab.
Workarounds: None.
•
Symptoms: Microflow Enabled not available on 2950 in QoS Policy Map window.
Conditions:
–
–
–
Workarounds: Telnet to the device and get various details.
•
Symptoms: Can only add one class map ACL match; window reports failure when you attempt adding multiple ACL matches
Conditions: QoS Management window, 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.
•
Symptoms: EM does not install with uninitialized Cisco EMF.
Conditions:
1. Load the Cisco EMF environment
2. Load 5.11 patch
3. Try to install the EM without starting Cisco EMF.Actual Results: Installation fails.
Expected Results: The EM should install.Workarounds: Install the EM after Cisco EMF has been started.
•
Symptoms: EM 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, the EM opens a telnet session to the device and sits at the password prompt.
When using manual deployment and entering passwords, the EM opens a telnet session and starts issuing show commands, before commissioning.
Steps to Reproduce:
1. From a CLS on the management server snoop your interface:
snoop <IP of chassis> port 23
2. Deploy the chassis
3. Watch the output of snoop.
4. Open the Network Element window but don't hit commission
5. Watch the output of snoop.Workarounds: None.
•
Symptoms: EM issues commands multiple times during discovery
Conditions: 6513 IOS chassis c6sup2_rp Software (c6sup2_rp-PS-M), Version 12.1(13)E.
Problem was found while preparing for soak test.After hitting commission, the EM issues the following commands several times before completing the discovery. It should only need to issue each command once.
show ip cef
show mpls interfaces
show ip mroute
show boot
show version
show running-config
show access-listsSteps to Reproduce:
1. From a CLS on the management server snoop your interface:
snoop <IP of chassis> port 23
2. Deploy the chassis
3. Open the Network Element window and hit commission
4. Watch the output of snoop.Workarounds: None.
•
Symptoms: Link up/down trap enable/disable fails
Conditions: On the Ethernet Interface window, enabling/disabling the link status traps does not work for 2950 and 3550 series chassis. In config mode, from the interface, the command: no snmp trap link-status will give the desired result. There is no error message to indicate it failed.
Workarounds: None.
•
Symptoms: EIGRP window does not function properly.
Conditions: 4506 deployed and commissioned
–
ISSUE 1: Value in "Stuck in Active" field was 3 according to the window however when looking in IOS on the device, no "stuck in active" time was shown.
–
ISSUE 2: Attempted to modify the stuck in active time to be 4294967295 (the upper value of this field as indicated in the test case. A value with this many digits cannot be entered into this field.
–
ISSUE 3: The window allowed this value to be entered and saved (indicated by field being highlighted in blue). However, when looking in IOS at the value, it was 45406.
ISSUE 4: The window, when refreshed with the refresh button or waiting for auto-refresh, showed the 45406 value.
Workarounds: None.
•
Symptoms: EIGRP Local Network Configuration window does not detect existing n/w.
Conditions: 4506 deployed and commissioned
1. Open the EIGRP local network configuration window
2. Click the add/remove local network button
3. Enter an existing local network in the windowAn error should be reported but the action window says the action completed successfully.
Workarounds: None.
•
Symptoms: Should not be allowed to modify HSRP for 2950
Conditions: Ethernet Interface window for the 2950.
Under the HSRP tab, you should not be able to modify, or configure the attributes for the 2950 chassis since it is not supported.Workarounds: Ignore the attributes.
•
Symptoms: Network Element failed to move to lostcomms
Changed the passwords on a normal Network Element to invalid passwords, and waited over 30 minutes. The network element never moved to lostcomms.Conditions: Chassis 2950/3550, OS IOS 12.1(12c)EA1, 12.1(12c)EA1
Deploy and commission a 2950 chassis. After the 2950 moves to normal, change the IOS passwords to invalid passwords.
Workarounds: None.
•
Symptoms: Modify standard ACL filter reports success but fails in action
Conditions: 4503, IOS 12.1(12c)EW1
The ACL Add Filter window lists options that apply to Extended ACLs. Including filtering by port and Destination address. These options are not supported on Standard ACLs. When choosing these options for a standard ACL and applying I get a success report, but the Destination address and ports are ignored. These fields should be greyed out when the window is opened against a standard ACL.
Workarounds: Ignore the filtering by port and destination address fields when the ACL Add Filter window is opened against a standard ACL.
•
Symptoms: VLANs not listed under STP tab of Ethernet Interface window
Conditions: ems3550a, cyber2950a, ems6513a; Ethernet Interface window, STP tab
No VLANS show up under the Per VLAN STP setting.
There is no purpose to having modifiable Priority and Cost settings on this screen when you have to open up another window (with the Modify Per VLAN STP setting button)? Perhaps these fields should be Read only.
Workarounds: None.
•
Symptoms: Redistribution tab on the EIGRP window does not handle ranges.
Conditions: 4506 deployed and commissioned
Opened the EIGRP window and clicked on the redistribution tab
ISSUE 1: Attempted to put the highest allowed value in for each field in the Default Metric box. The values were accepted by the window after hitting save but once the window refreshed, a "0" value appeared and that was the value on the device when checked via IOS.
ISSUE 2: Edit redistribution table of the window. The reliability field and the Loading field can be configured via IOS to be 255 however, the window will only allow 2 digits to be entered.
Workarounds: None.
•
Symptoms: Distribution tab on EIGRP window does not work properly.
Conditions: 4506 deployed and commissioned
Opened the EIGRP window and clicked on the distribution list tab
ISSUE 1: Attempted to delete an entry from the table by adding the ACL ID of an entry in the table and clicking the delete button. Action window indicated the deletion was successful however, after refreshing the window the deleted entry was still there and it was still present on the device as checked via IOS.
ISSUE 2: Attempted to enter data according to the following:
ACL ID: any alpha string not present
Direction: out
Protocol: any (tried OSPF and BGP)
Source id: can only enter 2 digits here (I think this should allow more from testing it via IOS)Action window always gives an error saying improper syntax as follows:
C6576M:0736_0 Invalid distribute-list configuration. The correct syntax is distribute-list <acl_id> out [<bgp|eigrp|ospf> <source id>] or distribute-list <acl_id> out [<static>].
However via IOS the following command works: distribute-list aaa out BGP 444
Steps to verify this bug will include checking all protocols and all directions for both adding and deleting.
Workarounds: None.
•
Symptoms: OSPF Object picks up values from wrong process ID
Conditions: Chassis: ems4506a, IOS 12.1.13EW
1. Deploy/Commission a chassis
2. Open OSPF window (From Chassis: Right Click: Logical -> Routing -> OSPF)
3. Make sure you have an OSPF process on your real chassis. For example: in this case, I had "router
OSPF 55".
4. In the OSPF window details tab, you can see the parameters related to OSPF tab.
5. Go to the chassis, REMOVE the OSPF with process ID 55 (i.e., no router OSPF 55)
6. Refresh the GUI, all the associated values become grayed out as expected, though the object is
still there.
7. Create a new OSPF process, router OSPF 668. Refresh the GUI. The GUI picks up the values associated with the process ID 66, though the
Process ID still mentions "55".
9. So the process ID: 55 object is wrongly being associated with values for process ID: 66, until that
1 minute sync with IOS config on the chassis happens.Workarounds: Wait until the next discovery cycle finishes. (1 to 5 mins)
•
Symptoms: Performance Status for the ATM T3 are not even reported and populated.
Conditions:
1. Deploy a 6509 switch a ATM/T3 Port Adapter
2. Verify the chassis reach normal state
3. Access the interface ATM/T3 window
4. Click on the Performance tab
5. Perform a refresh on the Screen
6. verify there is no values on the tab.Workarounds: None.
•
Symptoms: Chassis window, Performance tab: Action report issues
Conditions: Chassis: ems4006a, IOS 12.1(12c)EW1
From a site object that contains multiple chassis, start performance logging on one chassis object that is in normal state and on one chassis object that is in performance logging state. Got the following action report:
Failed to stimulate (1) object(s) with performance stimulus.Successfully stimulated (1) object(s) with performance stimulus.
Expecting Result:
a) Specify on which chassis object the performance has been started/stopped and failed to be started/stopped.
b) Specify failure reason.
c) Specify the action names - e.g. start/stop performance loggingWorkarounds: None.
•
Symptoms: Ethernet Interface window - confusing items in Actions
Conditions:
Chassis: ems4006a, IOS 12.1(12c)EW1
In the Ethernet Interface window, from menu bar click 'Actions', the following items are shown.Clear IP Address
Disable
Enable
Start
Stop
Disable
Enable
Disable
Enable
Add/Remove per VLAN setting
Configure
Modify
Remove Policy
Select PolicyIt is really hard to figure out which actions some items will invoke.
Workarounds: Read the help page from the help menu.
•
Symptoms: Remove multiple ACLs is inconsistent
Conditions: 4503, IOS 12.1(12c)EW1
We selected multiple ACLs from the left pane of the ACL Configuration window and hit Remove Current ACL. We got a success report but only the very bottom ACL was removed. We tried selecting multiple ACLs and removing them a second time and got the following error:
C6576M:0260_1 Mandatory attribute ACL ID missing.Every time after the initial attempt I got the above error.
Workarounds: Select only one ACL at a time from the list.
•
Symptoms: One chassis, 6 ACLs, selecting an ACLs takes 25 seconds
Conditions: 4503, IOS 12.1(12c)EW1
This was not a performance test but these performances stats of only one chassis with 6 ACLs indicates a potential problem when many chassis are commissioned, each with over 100 ACLs/filters.With the ACL Configuration window opened, click an ACL in the bottom left pane, then click another, and then another. Each time you select an ACL the cursor will turn to a clock and take approximately 25 seconds to recover.
Workarounds: Wait 25 seconds.
•
Symptoms: Bulk remove QoS Policy Map does not work
Conditions: Chassis: ems4006a, IOS 12.1(12c)EW1
1. Open QoS Policy Map Configuration window.
2. In "QoS Policy Map" panel, select 2 objects, then click "Remove Policy Map".Only 1 is removed from GUI. The other one's name is grayed out in the right panel, but if you do a refresh, it's enabled again. It's not removed from device either.
Workarounds: Select only one object at a time from "QoS Policy Map" panel.
•
Symptoms: NDE window does not work on 4K devices.
Conditions:
4506 deployed and commissioned running IOS 12.1(13)EW
4507 deployed and commissioned running IOS 12.1(13)EWThe NDE window is available for the 4K devices but it appears that it does not function properly. The commands that are being sent to the device by the window do not actually work on the device. It could be the case that NDE is only applicable to devices running Catalyst OS as these commands do exist for a 6500 device running Catalyst OS. If this is the case, the window needs to be disabled for the 4K.
Workarounds: Do not use the NDE window.
•
Symptoms: Catalyst OS set length command issued against IOS
Conditions: Chassis: ems4506a, IOS 12.1.13 EW
1. Deploy / Commission a chassis
2. Do a snoop for the chassis above
3. You can see the following:ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 ems4506a#
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964 set length 0\r\nems4506a.cisco.com -> ems-svr252 TELNET R port=47964 s
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 e
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 t
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 l
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 e
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 n
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 g
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 t
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 h
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964 0
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964ems4506a.cisco.com -> ems-svr252 TELNET R port=47964
ems4506a.cisco.com -> ems-svr252 TELNET R port=47964
ems-svr252 -> ems4506a.cisco.com TELNET C port=47964The "set length 0" command is specific to Catalyst OS, and should not be issued against IOS. Not sure how much performance impact this is. Though must be causing some performance issues based on how frequently it gets issued
Workarounds: None.
•
Symptoms: Default Cost not valid for default area type selection
Conditions: Chassis: ems4506a, IOS 12.1.13 EW
1. Deploy / Commission a chassis
2. Open OSPF window: From Chassis: Logical -> Routing -> OSPF
3. Provide Area Type as "default"
4. Try changing the "Deaf. Cost" to anything other than the "1" in the field.
5. Save
6. No return action report signifying the failure.
7. But, the value reverts back to 1
8. Now change the Area Type to "NSSA" or "stub", and then you can change the Def. Cost and see it propagate to device.Workarounds: None.
•
Symptoms: EM executes show version too often
Conditions: 4503, IOS 12.1(12c)EW1
1. When the EM executes show version it does so 2 or more times within a second.
2. When the EM tries to execute a command it also does show version many times, I counted 9 times within 3 seconds.
3. When the EM is idle, it executes show version/show running-config every 50 seconds; depending on how this is handled when many devices are commissioned this may or may not be a bug
4. When executing a command the EM executes show running-config 3 times, sometimes consecutively.Workarounds: None.
•
Symptoms: Software moves from normallostcomms to discovery
Conditions: Chassis 2950, OS 12.1(12c)EA1
When the network element goes from lostcomms to normal, the Software goes back into discovery. It should go right to normal state.
Workarounds: Wait for the discovery cycle to finish.
•
Symptoms: Ethernet Interface - Configuration tab issues
Conditions: Chassis: ems4006a, IOS 12.1(12c)EW1
In Ethernet Interface window under Configuration tab, the following issues were found.
–
–
Object /Site-1/IOS4006a/IOS4006a-Chassis/FastEthernet-4/FastEthernet4-20:
C6576MCntrllrExt-MIB.inQueueLength- FAILEDWhile the save failed for this attribute, no failure code was returned.
Expecting Result: Since the max number allowed is 4096, either do data validation on the field or specify the failure reason.
–
For example:
a) Change the Max. Input Queue length and save the value
b) Change Link Up/Link Down field, save button remains inactive.–
Workarounds: (Issue 2) Use values that are equal to, or less than 4096. No workarounds for other issues
•
Symptoms: wrong MTU range in EtherChannel Configuration tab
Conditions: dd4503a (12.1.13EW)
From the test plan or the EtherChannel window, it seems for Layer-2 "MTU", the range of 1-9216n are acceptable. But in fact, the correct range for the 4K switches is 1500-9198.
Workarounds: None.
•
Symptoms: change error reports from 6500M to CCSM
Conditions: 4503, IOS 12.1(12c)EW1
In the BGP window, We get the following error:
C6576M:1015_1 IP routing process, ISIS 55, is not running on the device.
Failed to complete action.Instead of C6576M:1015_1, this should read something like CCSM:1015_1. When working on a 4K or 3550 it may confuse the user to see 6500.
Workarounds: None.
•
Symptoms: Decommission while lostcomm transition does not trickle to software children
Conditions: Chassis: ems4506a, IOS 12.1.13 EW
1. Deploy / Commission a chassis
2. Stimulate lostcomms on the chassis, in my case chassis was oscillating between lostcomms and
normal.
3. Decommission the chassis
4. All the objects except the ones underneath the "software" tree, went to decommission. The objects
underneath the software tree are in normal state.Workarounds: None.
•
Symptoms: Several options from Syslog menu bar do not work.
Conditions: Chassis 4506
ISSUE 1: when the "Paste and Save Configuration" menu item is chosen from the menu bar of the Syslog window the following error message is received:
Object /Site-1/Cisco4500NE-1-172.18.175.75/Cisco4500NE-1-172.18.175.75-Software /SysLog:
C6576MManagermodule.c6576MSysLogClogHistoryTable- FAILEDThe SNMP data repository reports everything OK.
Returned Message: error-status unmatchedISSUE 2: Apply pro
Guest
