|
|
Table Of Contents
Release Notes for Cisco Catalyst 8500 Manager
Release 1.0Obtaining Technical Assistance
Release Notes for Cisco Catalyst 8500 Manager
Release 1.0
Contents
This document is divided into the following sections:
•
Limitations and Restrictions
•
•
Introduction
The Cisco Catalyst 8500 Manager (C8500MGR) is an element management system (EMS) for the Cisco Catalyst 8500 Multiservice Switch Router (MSR) family. C8500MGR 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 Catalyst 8500 routers.
System Requirements
The EM can be deployed in a number of different configurations, from a single hardware system to a multisite distributed management system.
The EM has precise memory requirements, supports specific hardware components, and requires certain Cisco EMF versions. Refer to the following sections for details regarding these system requirements.
All Cisco EMF-based solutions run on Sun Solaris/SPARC hardware running the Solaris operating environment, release 8.
Server Requirements
The recommended minimum hardware requirements for servers are:
•
–
–
–
–
•
–
–
–
–
•
–
–
–
–
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. An appropriate amount of free disk space for database files is also required.
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.
Software Requirements
Use C8500MGR only with the supported Cisco Catalyst 8500 routers using Cisco IOS Releases 12.1.10(E), 12.1.10(EY), and 12.0(22)W5(25). Other IOS versions may be used; however, some C8500MGR functionality may not be compatible with other IOS software.
C8500MGR requires the following software:
•
•
•
Note
Hardware Supported
C8500MGR supports the following Cisco Catalyst 8500 routers:
•
•
•
The following table includes each module supported by C8500MGR. For descriptions of each router and module, refer to the Cisco Catalyst 8500 Manager User Guide.
Table 1 C8500MGR Modules Supported
Installation Notes
After you install Cisco EMF (and the required patches) and acquire a valid license, you can install C8500MGR using the C8500MGRinstall script.
Note
The C8500MGRinstall script can be used for first-time installations as well as upgrades to previously installed versions. Before loading the software, the C8500MGRinstall script checks the system for existing packages. If an existing package is found, the script compares the existing version to the version on the CD. If the version on the CD is more recent, the previously installed version is upgraded. If the version on the CD is older than the installed version, no system change occurs. If an existing package is not found, the version on the CD is installed.
Caution
Caution
Step 1
Step 2
cd /cdrom/cdrom0Step 3
./C8500MGRinstallThe installation script automatically detects what type of Cisco EMF installation exists (server or client) and whether Cisco EMF is initiated or not.
If the Cisco EMF server is initialized, the script stops and a message in the terminal window indicates that Cisco EMF server must be in the uninitialized state. In order to change the Cisco EMF server to uninitialized, you must stop the Cisco EMF server and reset the database.
Caution
To stop the Cisco EMF application and reset the database as required, enter the following:
cemf stopcemf resetAfter uninitializing the Cisco EMF application, you can continue the EM installation procedure after repeating Step 3.
If the Cisco EMF client has ever been started, the script stops and a message in the terminal window indicates that Cisco EMF client must be installed on a fresh Cisco EMF client installation. If this is the case, you must uninstall and reinstall the Cisco EMF client. Do not start the Cisco EMF client before installing the C8500MGR client. After reinstalling the Cisco EMF client, you may begin the C8500MGR client installation process at the beginning.
If Cisco EMF is not initialized, the terminal window lists the compatible installation option:
•
•
Because the EM installation must match that of the Cisco EMF application, if the Cisco EMF server is installed, then the EM client install will be incompatible and vice versa. The script hides the incompatible options on the terminal window. Furthermore, the script detects whether Cisco EMF is currently running and hides the invalid option.
The following depicts an example of a terminal window which would display when the Cisco EMF server package exists on a workstation and Cisco EMF is not initialized.
INSTALL PACKAGE:1) Cisco 8500 Series Manager Server and its required COM Components—(No CEMF Initialization Required)q) QuitWhich package do you wish to install? (Def:1) [?,q]
Tip
Step 4
The utility lists the packages to be installed, including COMs and the EM. First time EM installations displays a list all COM components and the selected EM component (e.g., C8500MGRm for server installation or C8500MGRc for client installation). If an earlier version of the EM exists on the workstation, only those components that are out of date are listed. A confirmation of the installation appears.
Step 5
The entry of no cancels the installation procedure and returns you to the previous installation terminal window, while yes proceeds with the installation of all components listed.
You cannot selected individual components for installation.
As installation of each package takes place, the following displays:
Installation of <package name> was successful
At the completion of the installation, the following displays:
Installation of "installation option" was completely successfully
Step 6
cd /You can start a user session, if needed, and begin using the installed package.
Note
Limitations and Restrictions
The following limitations and restrictions exist in this release:
•
–
–
–
•
Note
Caveats
The following caveats exist in C8500MGR release 1.0. Generally, caveats include unexpected behaviors or defects in the software release. This document addresses caveats which directly impact user functionality and indicates alternative approaches (workarounds) where available. A complete listing of caveats is available in the Cisco bug tracking tool ( http://www.cisco.com/support/bugtools).
Caveats included in this document are categorized as follows:
•
•
•
General
•
Symptom: Chassis deployment template does not include IOS password
Conditions: IOS password required on quick start chassis deployment template, but not the normal deployment template.
Workaround: Set the IOS password on the EM using the Management Information window.
•
Symptom: Once a module is deleted, it can not be re deployed or commissioned.
Conditions: Manual deployment is not supported at the module level.
Workaround: Remove the module from the device and reinsert it. The module will then be rediscovered through regular heartbeat polling as long as the chassis is in a post-commissioning state.
•
Symptom: Under certain conditions, such as unsupported IOS version, a device will discover as a network icon.
Conditions: When using auto discovery, rarely do certain devices show up as a network icon rather than a device icon.
Workaround: If the device is running a supported IOS, then deleting the object and rediscovering it should fix the problem.
•
Symptom: Card Images disappear when the 8540 chassis image is clicked (with the exception of the module in slot.subslot 0.0 and the power supply module PS-0.
Conditions: Rarely, when clicking on the blank space on a chassis in the chassis map, will all the card images disappear.
Workaround: Select a different object and then re select the chassis.
•
Symptom: CAMs will not be discovered if there are no PAMs within it.
Conditions: Carrier modules will not be discovered by the EM it they do not contain submodules. Since there are no operations that can be performed on carrier modules, this does not have a harmful effect.
Workaround: None
•
Symptom: Not all interfaces are discovered in a redundant RP chassis.
Conditions: Initial discovery of the secondary RP does not show the associated interfaces until it becomes the primary RP.
Workaround: None
•
Symptom: Trap descriptions for some environmental traps display as a fault rather than a partial fault in the Event Browser.
Conditions: Power supply, voltage, temperature, and fan status traps may display incorrect data in the descriptions available in the Event Browser indicating a fault as opposed to a partial fault.
Workaround: None
•
Symptom: The Gigabit Ethernet module goes to mismatched and the interfaces stay in lostcomms after insertion of an MSP.
Conditions: If the Gigabyte Ethernet module is removed and replaced prior to the MSP removal, the symptom occurs after inserting the MSP.
Workaround: Decommission and recommission the module.
•
Symptom: VCL status and performance data is missing for newly created VCL.
Conditions: When multiple connections are present under an interface, the VCL Status and Performance windows do not consistently display the information.
Workaround: None
•
Symptom: Application of a QoS Profile to a normal state PVC shows success when in fact it didn't apply.
Conditions: Attempt to apply or change the QoS Profile on a connected PVC will fail as one can only change the QoS Profile to a disconnected PVC. Despite this, the status in the Apply Profile Status field shows " Succeeded".
Workaround: Only apply QoS Profiles to PVCs in a decommissioned status.
•
Symptom: Re-commissioning takes approximately 5 minutes and says it fails.
Conditions: An existing submodule is deleted from the EMS and the chassis is rediscovered.The module and submodules are finally commissioned properly but it takes a long time and the commissioning process says it failed.
Workaround: None
•
Symptom: Performing a `cemf restore' or `cemf restoreDataset' command fails and the ObjectStore transaction log file (default location `/opt/transactionLog') is the maximum file size for Solaris (i.e., 2 GBs).
Conditions: A database restore is being performed where an incremental backup is greater than 2GB. Note this condition happens in test labs where huge object deployment happen over the space of a day. This is an issue with a 3rd party product (ObjectStore) that is used by Cisco EMF. ObjectStore does not support more than 2 GBs incremental backups.
Workaround: Restore the database from the most recent full backup file (typically written on Sunday). Furthermore, it is recommended to perform backups daily in order to reduce the incremental backup file size.
•
Symptom: ARM module graphic shows extra interfaces.
Conditions: The ARM module graphic shows two interfaces when there are actually no physical interfaces on the card. Currently, the ARM module is not supported.
Workaround: This is just a graphical representation issue which does not affect operation. Currently there is no workaround available.
•
Symptom: A core file is produced during backup/restore procedures when performance polling is on.
Conditions: One hundred chassis are polling performance when the backup/restore is performed.
Workaround: Limit performance polling to no more than twenty chassis at any given time.
•
Symptom: Each object within the chassis retains a copy of the local SNMP community string.
Conditions: Changes to the SNMP community string information at any level, other than the chassis, is not propagated to the other objects within the chassis.
Workaround: None
•
Symptom: PVC deployment and connection fails on ATM0 when using the auto-allocation feature.
Conditions: PVC deployment and connection fails on the ATM0 interface when auto-allocation for VPI/VCI is selected, thus the EM cannot allocate any VPI/VCI to or from the ATM0 interface.
Workaround: The VPI/VCI ATM parameters must be specified during deployment in order to complete a connection to the ATM0 interface.
•
Symptom: The system becomes unstable after one chassis goes into the lostcomm state.
Conditions: After one chassis proceeds into the normal state following discovery, all other chassis that are not in the synchronizing or discovery states go into the lostcomms state. The chassis that are not genuinely in a lostcomms state will return to their proper state within five minutes.
Workaround: None
•
Symptom: Manual deployment discovers an incorrect interface.
Workaround: Delete the incorrect object and utilize the auto-discovery feature rather than manual deployment.
•
Symptom: Performance Manager menu item available at the chassis level.
Conditions: Although the Tools > Performance Manager menu option is available from a chassis object, performance monitoring is not supported at chassis level.
Workaround: Disregard this menu option. Performance monitoring is not supported at the chassis level.
•
Symptom: The value of 'Backplane Type' for an LS1010 shows `atm" in Chassis Inventory dialog.
Conditions: The value of 'Backplane Type' for an LS1010 shows `atm" in Chassis Inventory dialog. Should be 'LS1010' instead of 'atm'.
Workaround: None
•
Symptom: Cisco EMF backup and restore may show devices in a normal state when they are not.
Conditions: If a Cisco EMF backup is taken when a device is in a non-normal state, upon restore it will show a state of normal or be stuck in a discovery state when in actually it is currently unmanaged.
Workaround: Decommission and recommission the chassis.
•
Symptom: Chassis will temporarily go to a lostcomms upon removal of a module.
Conditions: Upon removal of a decommissioned module, the chassis will temporarily go to lostcomms and then eventually back to normal and the modules will end up in their correct lost comms state.
Workaround: None
•
Symptom: ATM0 and ETH0 appear beneath both CPUs.
Conditions: After a CPU switch over, ATM 0 and ETH 0 are listed under both CPUs. Only the active ATM 0 and ETH 0, however, will contain PVC connections.
Workaround: None
•
Symptom: PVCs with non-default names revert to default names upon a CPU switchover.
Workaround: Use only default naming convention when deploying PVCs
•
Symptom: System performance is poor (i.e., slow) when a large number of chassis objects are under management.
Conditions: As the number of managed objects increases, the user will notice a decrease in performance. One hundred or more chassis objects are under management.
Workaround: In order to increase performance, decrease the number of managed objects. To maintain optimum performance, it is suggested not to exceed a threshold of 75managed chassis at one time.
•
Symptom: Auto discovery fails with only RW (read-write) SNMP community string.
Conditions: The EMS discovers the chassis, but discovery results in an abnormal state. Furthermore, when commissioning is attempted, a core file results and the action fails.
Workaround: None
•
Symptom: Chassis goes into sync before all modules are discovered.
Workaround: None
Impact: None
•
Symptom: PVCs show up under standby CPU.
Conditions: PVCs deployed against ATM0 show up listed under the standby CPU.
Workaround: None. There is no operational issue but may lead to some confusion.
•
Symptom: When backing up, the Cisco EMF application encounters the following error message:
pkgparam: ERROR: parsing error in parameter fileConditions: When performing a `cemf backup' command, the preceding error message displays even when the backup is successful.
Workaround: None
•
Symptom: Generic Interface Status window takes more than 5 minutes to open.
Workaround: None
•
Symptom: All well known VCs are still under the primary CPU in which they were discovered, they do not switchover to new Primary CPUs.
Workaround: Manually invoke sync to allow move of the VCs to the new primary CPU.
•
Symptom: Audit log files contain unencrypted password and community strings.
Conditions: If a password or the value of a community string is changed, the audit file may contain unencrypted version of the password and/or community string.
Workaround: None
•
Symptom: Attempt to change IOS Password settings appears to work but actually failed.
Conditions: Open the Management Information window and click the IOS Settings tab. Displays with the incorrect login username and password already or with correct login username and password, but incorrect exec password saved locally. Try to perform a save to device and the Action Report will report failure but gives unknown error.
Workaround: Telnet to the device and change the IOS password settings via IOS CLI.
•
Symptom: Removed decommissioned module goes to discovery lostcomms.
Conditions: A module that is in a decommissioned state in the EMS is removed in the chassis and the EMS will change its status to lostcomms. If the module is reinserted the module will go into a normal state instead of the decommissioned state.
Workaround: Manually put the module back into the decommissioned state.
•
Symptom: Slow response time bringing up Map Views.
Conditions: Supporting 100 chassis or more, the response time of views and map views takes longer than normal.
Workaround: None
•
Symptom: User attempts to discover a device using auto-discovery GUI. The device is not discovered. The GUI reports that "No new devices found".
Conditions: Devices have been configured with multiple IP addresses. The first of these devices discovered is modeled by a managed object. Other attempts at discovering the other devices which have shared addresses with first discovered device will not succeed. Auto-Discovery only creates one managed object per IP address. This scenario can arise for a HSRP configuration where a number of devices are responsible for a single address. HSRP ensures that only one of the devices is actively managing this address.
Workaround: None
•
Symptom: The Cisco EMF Process statusPropagationsServer allocates memory on a continual basis. All of this memory is not subsequently freed resulting in memory leaks.
Workaround: None
•
Symptom: The Cisco EMF process `discoveryServer' uses up more memory each time an auto- discovery is performed.
Conditions: An auto-discovery is performed.
Workaround: None
•
Symptom: A `cemf restore' or `cemf restoreDataset' command hangs indefinitely. For example, an output similar to the following is seen in the terminal:
Available: 11513183232 (bytes)
Required: 726647808 (bytes)
Verification: Sufficient disk space exists ...
Restoring /opt/Backup/08-11-2002/full_01.dir/increment0.1 ...
Restoring /opt/Backup/08-11-2002/full_01.dir/increment1.1 ...
Restoring /opt/Backup/08-11-2002/full_01.dir/increment2.1 ...Conditions: When `cemf restore' or `cemf restoreDataset' is performed. This can happen if an incomplete backup has been copied from one location to another.
Workaround: To interrupt the action, enter Control + C in the terminal window.
•
Symptom: During commissioning get invalid failure message with unknown error reason.
Conditions: During bulk commissioning of chassis, the chassis are commissioned fine but some go into a sync state right away. This results in the action report for commissioning to report failure on all chassis commissioning when the commissioning was actually successful. This is due to a time out within the commissioning process which is never met due to the synchronization process kicking in.
Workaround: Use the Map Viewer to check the state of the chassis icons. Hashed icons indicate the commissioning was unsuccessful; non-hashed icons indicate success.
•
Symptom: ciscoPlatformCon sets snmp-varbinds-per-packet to 4.
Conditions: The ciscoPlatformCon sets snmp-varbinds-per-packet to 4 for every COM chassis that gets deployed. This has an adverse effect on chassis discovery and ATM connection sync performance. Tables are fetched in pieces and then spliced back together, causing the asyncSnmpDrep processes to use large amounts of CPU. It should not be set, leaving the default of 25.
Workaround: None
•
Symptom: IOS upgrade failure on LS1010 from 12.1.10 EY to 12.0.22 W5 25
Conditions: Using IOS Version 12.1.10 EY 2, deploy and commission a LS1010. Leaving the chassis commissioned, upgrade the IOS version on the chassis to 12.0.22 W5 25. Reload. The chassis comes back with the power supplies stuck in discovery.
Workaround: None
•
Symptom:ATM0 shows no interface performance statistics
Conditions: The bandwidth utilization and rx tx statistics for the ATM0 interface are not displayed in the performance dialogs.
Workaround: None
•
Symptom: ATM Interface Configuration window hangs.
Conditions: If a CPU failover is performed with the ATM Interface Configuration window open, it will hang.
Workaround: Close window and re-open.
•
Symptom: Unable to change the IOS enable Password via the EMS.
Conditions: The IOS Enable password can be created via the EMS with a space in it. If this is done, you will no longer be able to set the password via the EMS.
Workaround: Do not create the password with a space in it. Or, if unable to set via the EMS, telnet to the device and set via IOS CLI.
•
Symptom: Objects contained within a higher level object may not change state with their parent object correctly.
Conditions: When a module goes into a lostcomms state the underlying interfaces and connections do no follow suit.
Workaround: None
•
Symptom: Cold Start trap does not result in warning severity alarm.
Conditions: If a device goes through a cold start, the generated trap does not generate an alarm as it should. The alarm severity should be warning level.
Workaround: None
•
Symptom: Client installation fails with errors when Cisco EMF server is not running
Conditions: The client package installation fails if the corresponding Cisco EMF server is not running.
Workaround: Start the Cisco EMF server before beginning the client Cisco EMF client installation.
Chassis
•
Symptom: Configuration Backup fails but shows success.
Conditions: In the event that communications to the device is lost during a configuration backup, the backup may in some cases show success when in fact it has failed.
Workaround: None
•
Symptom: Chassis configuration information at the site level does not automatically refresh.
Conditions: Launch the Chassis Configuration window from a site object. With the Chassis Configuration window open, delete and re deploy chassis objects. The chassis objects do not remove and reappear, respectively, when the actions complete.
Workaround: Manually refresh the display as needed.
•
Symptom: On the ATM QoS Profile window, bandwidth is specified in cells per second rather than KBs or MBs per second that the router uses.
Workaround: None. Must translate values from KBs or MBs per second to cells per second.
•
Symptom: On the Chassis Configuration window, both power supplies reflect a PS Admin status of enable when only one power supply exists in the chassis.
Conditions: PS Admin states are always set to enable even when there is not a power supply present.
Workaround: Rely on chassis map graphic and Map Viewer hierarchical tree view for an accurate status of the power supplies rather than the state shown in the PS Admin field.
•
Symptom: IOS image download will fail with "Aborting Download Invalid Image!" error when image name is valid.
Conditions: In the IOS Image download view, a user can inadvertently put a leading space in the file name leading to the failure.
Workaround: Remove leading spaces.
•
Symptom: Status does not automatically refresh on the Redundancy window.
Conditions: Processor status does not automatically refresh on the Redundancy window following a forced failover.
Workaround: Manually refresh the window.
•
Symptom: The Redundancy window does not offer on-help.
Workaround: Refer to the Cisco Catalyst 8500 Manager User Guide for information on using the Redundancy window.
•
Symptom: Synchronizing the running config only from the Redundancy window synchronizes both the running and start configurations.
Conditions: The running config synchronization option should only synchronize the running config, not the running and startup configs.
Workaround: Use IOS commands to synchronize only the running config.
•
Symptom: VCs not synchronized following a forced failover.
Conditions: Due to a timing issue, device created VCs might not synchronize after a forced failover.
Workaround: Synchronization is corrected during the next automatic synchronization.
•
Symptom: CiscoPlatformCon core dumps.
Conditions: If the Network View and Component Managed Views do not exist, CiscoPlatformCon may core dump.
Workaround: Do not manually delete objects from the Component Managed or Network View, instead delete them only from the Physical View.
•
Symptom: Profile menu and associated menu items display on the Redundancy dialog.
Workaround: Disregard the Profile menu and all associated options on the Redundancy window.
•
Symptom: "Data recovery operation failure" displays in the status bar following a route processor (CPU) forced failover.
Workaround: None
•
Symptom: Ethernet0 and ATM0 modules do not commission following a forced failover.
Conditions: Following a forced failover, the Ethernet0 and ATM0 interfaces in the active CPU may not commission.
Workaround: Commission the interfaces individually from the Interface Configuration window.
•
Symptom: Cisco PlatformCon core dumps.
Conditions: Commissioning chassis with incorrect SNMP community read/write settings crashes the Platform Con.
Workaround: None
•
Symptom: Some basic functionality, such as commissioning a chassis, will not work.
Conditions: If COM is installed while Cisco EMF is running, then some basic functionality, such as commissioning a chassis, will not work.
Workaround: Do not install COM while Cisco EMF is running. If this is done, then a cemf stop and then cemf start should be issued and normal operation will return.
Module
•
Symptom: The module is performance collection state but it is not reflected on the TGO icon.
Conditions: The performance collecting icon is not always displayed when performance polling is turned on for a module.
Workaround: Check the status bar for the object which should show a state of "PerformanceLoggingOn".
•
Symptom: The Performance Manager erroneously indicates the performance logging has stopped for modules which are currently polling
Conditions: After enabling global performance polling on a chassis, the Performance Manager may indicate that performance polling has stopped on a module when it has not. The Performance Manager will report that interfaces are polling.
Workaround: None
•
Symptom: Commissioning action report for power supplies always indicates success.
Conditions: When commissioning power supplies using the Module Configuration window, the action report always indicates success.
Workaround: Observe the state of the power supply in the lower left-hand corner of the Module Configuration window.
•
Symptom: When a module which is not present in the chassis but is deployed within the EM (lostcomms state) is commissioned, an alarm may not be raised on the module to indicate commissioning failure.
Conditions: The following steps present this issue to the user:
1. A commissioned chassis loses connectivity with the EMS server
2. During this time a module is removed from the chassis
3. Chassis comes back from lostcomms and goes through the commissioning procedure
4. The state of the above removed module is aptly changed to "lostcomms", but no alarm will be raised against this module. All other modules will have alarms raised to inform the user that "Module commissioning was successful".
Workaround: The state of the module and the "Status of last commission" field in the Module Configuration dialog will reflect the current state and status of last commission.
•
Symptom: Module Configuration window always displays failed commissioning status for power supplies.
Conditions: In the Module Configuration window, the "status of last commission" field always shows a value of "failed" for power supplies.
Workaround: None
Generic Interface
•
Symptom: Commissioning an interface reports success when in actuality it has failed.
Conditions: Commissioned chassis, decommissioned module, decommissioned interface contained within the module. If you commission the interface, the action report will say the commissioning succeeded when it really failed because it's parent module is in a decommissioned state.
Workaround: None
•
Symptom: Authentication Failure alarm is raised instead of a linkup/linkdown alarm.
Conditions: When multiple interface objects are selected and linkup/linkdown trap Enable field is enabled, when the interface is shutdown with IOS command the expected LinkDown trap is not raised. Instead an Authentication Failure alarm is raised.
Workaround: Do not use Bulk select when modifying linkup/link down traps on interfaces.
ATM Interface
•
Symptom: Some attributes on the ATM Interface Configuration window are grayed out, however the same attributes are activated in the ATM Interface Configuration Profile window.
Conditions: The ATM Interface Configuration Profile window supports a super set of attributes that are supported by the device and ATM Interface Configuration window.
Workaround: None
Ethernet Interface
•
Symptom: Applying an Ethernet HSRP Profile to an interface fails to update all fields on the HSRP Parameters Tab of the Ethernet Interface Configuration window.
Conditions: The following fields are affected:
a.
b.
As a result, only the HSRP Group Number successfully updates according to the profile data and displays on the HSRP Parameters tab of the Ethernet Interface Configuration window.
Workaround: Reset the Standby Hello Time and Standby Hold Time fields to the values desired on the HSRP Parameters Tab of the Ethernet Interface Configuration window, then click Refresh.
•
Symptom: IP Configuration and Ethernet Configuration windows do not display any values and always display "ERROR"
Conditions: This occurs when the following steps are repeated for awhile:
1. Deploy a chassis and provide the correct device passwords.
2. Commission this device.
3. Compare the window value and the device value.
4. Decommission and delete the chassis object.
Workaround: Using console port, use the following commands to clear outstanding telnet sessions not in use. Make sure the chassis is in normal state while performing this.
1. Use "show users" in exec mode to obtain a list of outstanding VTY sessions with line number.
2. Clear all outstanding VTY sessions from the manager station using "clear line vty <line number>"
IP Interface
•
Symptom: Cannot unset the IP MTU attribute.
Conditions: If the IP MTU attribute is set, it cannot be unset in the EMS.
Workaround: Telnet to the device and remove it via IOS CLI.
•
Symptom: the Interface State option sets the Administrative Status. So when you change the stated the admin state will change and the action will be successful. However the status that is displayed is the operational status and that can be disabled when the admin is enabled. Thus you can successfully change the status to enabled and when the dialog is refreshed, it will revert back to disabled.
Workaround: None
ATM Connection Manager
•
Symptom: Two different causes reported for failure of PVC upload.
Conditions: Loss of communication with device during PVC upload can result in different error messages; one indicates that the lost communications was the problem and another reports that the PVC table is empty.
Workaround: None
•
Symptom: Error message states failure of all or part of a bulk PVC creation.
Conditions: During bulk creation of connections when some or all of the creations fail, the error message does not tell you the correct number of creation failures and does not indicate which ones failed.
Workaround: Look in the Map Viewer to verify which connections were successfully created.
•
Symptom: Valid fields in QoS Profile window may be incorrectly greyed out.
Conditions: When creating a QoS profile, if a profile type is selected, some attributes in the profile may be greyed out as they are not applicable to that profile type. If a second profile type is selected before a save, the fields may not un-grey properly.
Workaround: Exit the window and bring it back up again.
•
Symptom: Connections show normal state when they should be in an error state.
Conditions: Connections in the EMS show normal state when the interface and module to which they are connected are removed from the chassis.
Workaround: None
•
Symptom: CEMF has two PVCs in the normal state both having the same VPI/VCI values.
Conditions: This can happen under the following scenario:
The user deploys a PVC (PVC-1) under ATM End-point on a subinterface with, say, VPI/VCI values of 40/41 with the auto connect option = 1. PVC-1 is deployed and goes into the `normal' state. Now the user deploys another PVC (PVC-2) with the auto connect option = 0. PVC-2 is deployed and goes into the decommissioned state. Next the user modifies the VPI/VCI values of PVC-2 to be the same as those of PVC-1 and connects PVC-2. The result is that PVC-1 and PVC-2 are now both in the `normal' state and managing the same physical connection on the device.
Workaround: When connecting a PVC ensure that a connection with the same VCI/VPI values is not already being managed by another Cisco EMF object which is in the `normal' state.
•
Symptom: New connections are not added to open ATM windows following an ATM connection upload action.
Conditions: With the ATM Connection Management and QoS Profile Management windows open, upload ATM connections and QoS profiles from the device to the EM. Note that the uploaded information does not display in the open windows.
Workaround: After an ATM connection upload, refresh the ATM Connections Management window in order to see the recently uploaded connections.
•
Symptom: For some PVCs, "Destination Port" in ATM Connection Management dialog is disabled and it has NSAP Address filled in like: 47.0091.8100.0000.0030.9466.ac01.4000.0c86.0010.00
Conditions: This symptom does not have fixed condition to cause it happens and happens rarely.
Workaround: Decommission these PVCs and delete them and upload again.
•
Symptom: Get error message upon trying to bulk deploy PVCs after the first time.
Conditions: The bulk deployment of PVC fails after the first time.
Workaround: Manually deploy PVCs one at a time.
•
Symptom: The Well-known VC Mode displayed on ATM interface configuration dialog could be either "automatic" or "manual". It can never be "manualDeleteUponEntry".
Conditions: The Well-known VC Mode can be configured to "manualDeleteUponEntry" which removes all existing signalling connections on the interface. If it is configured to "manual", any existing signalling connections are left intact on the interface. These two modes are available for configuration. Once it is configured, there is no distinction between "manual" and "manualDeleteUponEntry". The Well-known VC mode is simply "manual".
Workaround: None
•
Symptom: Apply QoS Profile to an existing connection and it shows a success in the status bar but a failure in the "last apply" field.
Workaround: Disconnect the connection before trying to apply a new profile.
•
Symptom: Failure to apply a QoS Profile to a newly created PVC with a Last Apply Profile status of "No Profile Name or Invalid Environment".
Conditions: If a PVC is deployed while the chassis to which it is associated is in a lostcomms state, the application of the QoS Profile will fail with a Last Apply Profile status of "No Profile Name or Invalid Environment".
Workaround: Wait until the chassis is in a non-errored state before attempting to apply the QoS Profile to the newly created PVC.
•
Symptom: Performing a chassis reset during a sync operation will cause sync to complete with no errors reported.
Conditions: The TableRetreiver code does not handle a table retrieval error correctly.
Workaround: None
•
Symptom: Core Dump Received from ATMCMController when Cisco EMF is stopped.
Conditions: Upon a cemf stop, the ATMCMController will core.
Workaround: None
Impact: None—Upon cemf start the ATMCMController will restart properly.
•
Symptom: Attributes may be applied to devices that are invalid. The device will not accept them but sets them to other valid default values.
Conditions: In Configuration Screens in attribute fields that have a pull-down list, the values may not be valid for a specific device but can still be selected. The device will be set to the default value on the device instead.
Workaround: Refer to the EMS user guide to determine which are valid attribute values for the specific device type.
•
Symptom: Changes of VPI/VCI in ATM VCL Configuration dialog cannot be propagated.
Conditions: In the ATM VCL Configuration window, on a decommissioned VCL, field VPI/VCI can be modified. When hit the save button, seems like the values have been saved. Open ATM Connection Management dialog, the VPI/VCI fields still show the old values though. Perform connect action in the ATM Connection Management dialog, the VPI/VCI values in ATM VCL Configuration dialog will be updated to whatever values in ATM Connection Management dialog.
Workaround: Delete the decommissioned VCL and recreate with different VPI/VCI values.
•
Symptom: User gets "Service Invocation Failure" when trying to access Source VCL from the VCL Configuration dialog.
Conditions: In ATM Connection Management dialog, select an SPVC. Only "Source Port" 1. In ATM Connection Management dialog, select an SPVC. Disconnect and reconnect this SPVC. Now "Source Port", "Source VCL", "Disconnect" and "Decommission" buttons are enabled.If you click "Source VCL", you always get "Service Invocation Failure".
Workaround: Look at the Source VCL by selecting it from the pull-down list instead.
•
Symptom: Failure to apply a QoS Profile to a connection.
Conditions: Invalid parameters are selected in the QoS Profile trying to be applied to a device.
Workaround: Use the EMS User Guide to help understand valid values when creating the QoS Profile that will be applied against a particular device type.
•
Symptom: Bulk deployment of PVCs fail.
Conditions: Use default name or CiscoPVC-1 as the PVC naming convention and it will fail if PVCs of those names had been previously deployed.
Workaround: Either individually deploy PVCs or select a starting name which does not end in a number or has been previously used.
•
Symptom: Attempt to create a connection on the RP or redundant RP results in failure.
Conditions: On ATM0 or on the ATM Interface associated with a Redundant Route Processor, attempt to connect a PVC will fail.
Workaround: Create connections on interfaces which are not on the route processors.
•
Symptom: Unpredictable inability to save ATM Interface and Connection Configuration Changes
Conditions: After opening the ATM Interface Configuration dialog, modifications were made to the `Interface Type', `ATM Interface side', etc. attribute fields. It was noticed that the save icon in the top left hand corner remained ghosted out, leaving the user unable to save any modifications. Also, changes were made to the `Number of VCs per VP' attribute field. This time the save icon was available for selection, however clicking on the icon does not result in attributes being saved.
Workaround: Exit window and re-open it and it should work correctly.
•
Symptom: ATM QoS Profile fails when applying the connection on the device. Error message provides no detail.
Conditions: If an ATM QoS profile is applied to a connection with invalid parameters it will fail only when attempting to be applied to the connection on the device. Application of the QoS profile against a newly created non-connected PVC will be successful. The error message upon connection to the device is not informative.
Workaround: Create ATM QoS Profiles with correct parameters. See the EMS User Guide for detail on acceptable parameters.
Related Documentation
The following Cisco EMF and C8500MGR documentation is available as additional resource materials.
•
–
–
–
–
•
–
–
–
–
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
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
Documentation CD-ROM
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.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
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-9883We appreciate your comments.
Obtaining Technical Assistance
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
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:
Technical Assistance Center
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.
Cisco TAC Web Site
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.
Cisco TAC Escalation Center
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 Oct 5 15:14:31 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
