|
|
Table Of Contents
Release Notes for Cisco 7000 Series Manager
Software Release 2.0Cisco 7000 Series Manager Documentation
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco 7000 Series Manager
Software Release 2.0
Contents
This document is divided into the following sections:
•
Caveats
•
•
Introduction
The Cisco 7000 Series Manager provides high reliability, availability, serviceability, and performance. The system supports multiprotocol, multimedia routing and bridging with a wide variety of protocols and any combination of Ethernet, Fast Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), serial, multichannel channel attachment, and High-Speed Serial Interface (HSSI) media. Network interfaces reside on modular interface processors, which provide a direct connection between the high-speed Cisco Extended Bus (CxBus) and the external networks.
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 Cisco 7000 Series Manager only with routers using the latest Cisco IOS releases as follows:
•
–
–
–
•
–
–
•
–
–
Note
Cisco 7000 Series Manager servers and clients operate with the following software:
•
•
•
Additionally, Cisco EMF 3.2 Service Pack 4, Patch 6.2 is required in support of Cisco 7000 Series Manager co-residency with Cisco Access Router Manager and Cisco 12000/10720 Manager:
Note
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_installation_and_configuration_guide_book09186a00800ffd0d.html.License Requirements
The EM uses Cisco EMF, which requires a license key to operate.
Note
http://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/products_user_guide_book09186a00800ffd02.html.Hardware Supported
Cisco 7000 Series Manager supports the following Cisco routers and modules:
•
•
•
•
The following table includes each module supported by Cisco 7000 Series Manager. For descriptions of each router and module, refer to the Cisco 7000 Series Manager User Guide.
Table 1 Modules Supported
Processor Modules
RSP2
RSP4+
RSP8
VIP2-40
VIP2-50
VIP4-50
VIP4-80
Generic Modules
PC-MC-E3
PA-MC-T3
PA-MC-2T3+
PA-2E3
PA-E3
PA-T3
PA-T3+
PA-2T3
PA-2T3+
PA-MC-STM-1MM
PA-MC-STM-1SMI1
PA-MC-2T11
PA-MC-4T11
PA-MC-8T1
PA-MC-2E1/120
PA-MC-8E1/120
PA-5FL
PA-H
PA-2H
PA-4T+
PA-8T-V35
PA-8T-232
PA-8T-X21
PA-4EIG/75
PA-4B-U
PA-8B-S/T
ATM/SONET Modules
PA-SRP-OC12MM
PA-SRP-OC12SMI
PA-SRP-OC12SML1
PA-A3-OC3SMI
PA-A3-OC3SML
PA-A3-OC3MM
PA-A3-OC12MM
PA-A3-OC12SMI
PA-A3-T3
PA-A3-E3
PA-A3-8E1IMA
PA-A3-8T1IMA
Ethernet Modules
PA-GE
PA-4E
PA-8E
PA-2FE-FX
PA-2FE-TX
PA-FE-FX
PA-FE-TX
Voice Modules
PA-MCX-4TE1
PA-MCX-8TE1
PA-VXA-1TE1-24+
PA-VXA-1TE1-30+
PA-VXB-2TE1
PA-VCX-2TE1+
1 This module was not fully tested for complete IOS support. A similar or variant card may have been tested instead.
Installation Notes
The Cisco 7000 Series Manager Installation Guide provides information to install, configure, and uninstall the Cisco 7000 Series Manager product. For any specific installation issues in this software release, see the "Caveats" section.
Caveats
The following caveats exist in Cisco 7000 Series Manager Release 2.0. Generally, caveats include unexpected behaviors or defects in the software release. This document addresses a subset of 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).
•
Symptom: No proper message seen when deleting wrong group #, time slot #
Conditions: From Group Creation window, if you fill in the incorrect group #, time slot #, and signaling type, then click Delete, you get an Action Finished message. Delete action is not applicable here; message should be corrected.
Workaround: No workaround is currently available
•
Symptom: Ethernet Port not shown for I/O FE card
Conditions: In ER manager view ( where the image of full device is shown) of an I/O FE card, no FE port is shown, only console and auxiliary ports are shown.
Workaround: No workaround is currently available
•
Symptom: Save button should not be highlighted without management information set
Conditions: Reload a router then insert a voice card. Auto Discover the router and then commission it (without setting the management information.) Go to Voice Card Configuration; Configurable Parameter shows card type as ERR which is correct. If you try to change the type to "T1", the save icon is highlighted. In this case, the Save button should not be highlighted.
Workaround: No workaround is currently available
•
Symptom: DS1 configuration can be done without router authentication information
Conditions: After deploying a chassis and discovering the interfaces, without setting the router authorization information, you can open the DS1 Configuration window and create voice groups.
Workaround: No workaround is currently available
•
Symptom: Generic interface performance option should be removed for voice interface
Conditions: For voice interfaces, the router does not return any perf.ormance stats; therefore, the Generic:Interface:Performance option should be removed for voice interfaces.
Workaround: No workaround is currently available
•
Symptom: Uninstallation of CERM fails to remove all the related objects
Conditions: Install CERM 1.1 over CEMF 3.1. Deploy and commission a device. Without deleting the commissioned objects, uninstall CERM1.1. Now reinstall CERM1.1 again. You can still see these objects existing under Network and Physical views. Uninstallation should take care of the removal of all the related objects from the database.
Workaround: No workaround is currently available
•
Symptom: Memory Leak in Controller base Action MyConvertAction
Conditions: Two leaks occur with any voice action performed in the DS1 Configuration dialog.
Workaround: No workaround is currently available
•
Symptom: Only 10 SPVcs are deployed at a time
Conditions: When attempting to deploy greater than 10 SPVCs on a chassis, only 10 are deployed.
Workaround:Deploy a maximum of 10 SPVCs in a single deployment.
•
Symptom: Loopback cannot be set to internal/external
Conditions: Attempts to set the loopback state of an ethernet interface to 'external' or 'internal' in the 'Configuration' page/tab of 'Ethernet Interface Configuration' dialog fail.
Workaround: Use CLI to configure the loopback state as follows:
Router(config-if)#loopback ?driver Loopback at the transceiver levelmac Loopback at the MAC controller level•
Symptom: Deployment and commissioning of chassis with wrong sysoid & class is allowed
Conditions: If the user attempts to deploy a chassis of one type with the template for another, the deployment will succeed. e.g. deploying a 12008 chassis using the template for the 12016. When the chassis is commissioned, the commission will succeed, but some of the modules may be deployed in the wrong slots.
Workaround: Ensure that the type of the chassis to deploy matches the template that is being used to deploy the chassis.
•
Symptom: ATM sync not allowed for multi-chassis when some non-managed
Conditions: Upload action fails if one or more chassis among the selected group of chassis are in Unmanaged State.
Workaround: Choose the chassis that is in Managed State for Connection Upload.
•
Symptom: Chassis configuration dialog fails to come up during soak.
Conditions: When the system is under a high amount of stress, the Chassis configuration dialog may fail to open. This problem occurs when the system is under extreme load, such as a full network outage. Even under severe stress conditions the occurrence of this issue is rare.
Workaround: Wait until the system is under less load before opening these dialogs.
•
Symptom: QoS Profile losing applying can not be removed
Conditions: QoS Profile which is uploaded from the device can not be deleted from CEMF. The Action-Report shows Failure because the QoS Profile is still being applied to some connection.
Workaround: No workaround is currently available
•
Symptom: QoS Profile uploading fails when index is the same
Conditions: ATM Connection upload does not upload certain QoS profiles and connections associated with those profiles.
Workaround: In Element Manager, decommission and delete all the associated connections for the profile under consideration. Delete the QoS profile and the associated connections. Now on upload, modified QoS profile and related connections will be successfully uploaded from the device to the Element Manager.
•
Symptom: Upload Status shows wrong infor when doing uploading
Conditions: When a user carries out an ATM Connection Upload manually (forced), the Upload Status panel shows the result. This result does not show the correct Values for Actual Connections, Connection Under Same Port and Unmanaged Interface(s).
Workaround: Telnet to the device through "Initiate Telnet Service" from the "Technology Specific Tools" menu. Issue command "show atm vc" from Exec Mode. User has to count the Actual Connections, Connection Under Same Port, and Unmanaged Interface(s) manually.
•
Symptom: Unable to select all alarm report for the POS interface
Conditions: The following alarm reports are not selected on the window: Signal Degrade BER, Signal Fail BER, Section Loss of Signal Error, LAIS of Interface Shutdown, and Signal Loss of Frame Error.
•
Symptom: ATM Connection Management- Can save different configuration to a connection (normal state)
Conditions: VPI/VCI values can be modified for a normal-state connection-object by carrying out a copy/paste operation on the page-configuration functions.
Workaround: No workaround is currently available
•
Symptom: ATM Connection Management: Can modify VPI/VCI of connection in normal state
Symptom: Modifying the VPI and VCI parameters of normal PVC/SPVC connections succeeds. However the correct behaviour is that it should not be possible to modify such values for PVC/SPVC connections when they are in the normal state. If a user multi-selects a number of PVCs/SPVCs while one or more of these connections is in the decommissioned state, then it is possible to amend the VPI and/or VCI parameters of those PVCs/SPVCs that are in the normal state. Once these parameters are changed then the user cannot disconnect these connections.
Workaround: The normal PVC/SPVC connections with the changed VPI and VCI parameters can be removed using the following steps.
–
–
•
Symptom: Cannot save POS Configuration dialog
Conditions: Unable to save on the POS Configuration dialog without entering a threshold for every alarm type.
Workaround: Enter a threshold for every alarm type, regardless of whether the button is selected.
•
Symptom: After global logging is started, four attributes return no data
Conditions: After deploying and commissioning a chassis, start global logging and let it run for at least 6 minutes. Open the Performance Manager and note that the following four attributes return no data - SNMP:IF:MIB:ifOutBroadcastPkts, SNMP:IF:MIB:ifinBroadcastPkts, SNMP:IF:MIB:ifOutMulticastPkts, SNMP:IF:MIB:inInMulticasePkts
Workaround: No workaround is currently available
•
Symptom: CiscoEnvMonFanStatusTable is empty on the 7200 chassis
Conditions: The table for the 7200 chassis shows that "No such Object is available on this agent."
Workaround: No workaround is currently available
•
Symptom: The send code parameter has no data present on DS3 interface
Conditions: The Send Code parameter has an incorrect value of No on the DS3/E3 Interface dialog.
Workaround: No workaround is currently available
•
Symptom: Tabs in DS1 dialog should be grayed out according to Service type
Conditions: For T1 card types, the ext-Sig Signaling type for the DS0 group creation does not work if the service type is cas-voice. Vice versa if the service type is ccs-voice, only ext-sig and none DS0 signaling type are valid options. Also, the PRI Group is not available if the service type is cas-voice. DS0 Group and TDM Group are not available if the service type is data. An E1 card does not have a service type.
Workaround: No workaround is currently available
•
Symptom: The operation of the No Force Sync failed on CAR Policy
Conditions: Select an interface that already has an Access List applied to it on the physical device, then move a suitable policy (one with an associated access list) from the "Available Policies" list box into the "Required order" list box; save the changes. With the Force Synchronization button set as No, select the apply button to roll the policy onto the physical device. Ensure that the operation fails because the interface already has a CAR policy assigned to it. In this case it allows the user to apply the new policy even though the Force Sync is set to No.
Workaround: No workaround is currently available
•
Symptom: Unable to update the applicable RW attributes
Conditions: In the ATM Interface Configuration dialog, update an applicable field such as Maximum VCCs and Number of VCS per VP. Trying to Save the changes produces an error message.
Workaround: No workaround is currently available
•
Symptom: DS1 Configuration dialog needs a better action report
Conditions: Currently if an action failed, the action report states "ACTION FAILED". The user needs to know what happened and why it failed.
Workaround: No workaround is currently available
•
Symptom: Should let user select and delete
Conditions: On the DS1 Configuration dialog, the user has to input required information, then click "Delete" to delete a group. Should let user select it in the table then delete.
Workaround: No workaround is currently available
•
Symptom: Disable the unsupported attributes in ATM Interface Configuration Profile
Conditions: The attributes that are disabled in the ATM Interface Configuration dialog are unsupported. When the Profile dialog is opened, the attributes that are disabled in the Configuration dialog are not greyed out in the profile dialog, appearing to be supported. Values can be entered for the unsupported attributes.
Workaround: Only fill in the supported attributes for the ATM Interface Configuration Profile.
•
Symptom: Problems with Profile menu items
Conditions: Change the "VCL Profile" option to "ATM QoS Profile" in the drop down menu. Also suggest changing "ATM" to "ATM Interface Configuration Profile", changing "POS Profile" to "POS Interface Configuration Profile".
Workaround: No workaround is currently available
•
Symptom: Problems with ATM Interface Configuration dialog
Conditions: If you enter some value for "Maximum Active VPI Bits" and "Maximum Active VCI Bits". "Save" menu and icon are grayed out; therefore, you can't save changes for these two fields. Changing the "Maximum VCCs" value, an error is displayed. In the "Configuration(2)" tab, change "Framing Mode" to anything other than "No label"; the changed value is saved without an error, but goes back to "No label" after refresh. Nothing can be saved in "Configuration(2)" tab.
Workaround: No workaround is currently available
•
Symptom: Perl Parser in atm7200.pm has problems for different chassis/IOS
Conditions: In the ATM Interface Faults dialog, you will not get correct values for SONET Frame Errors.
Workaround: No workaround is currently available
•
Symptom: DS3/E3 Interface Status: disable traffic lights
Conditions: On the DS3/E3 Interface dialog, the traffic light icon is not disabled when there is no interface selected on the dialog and when the chassis is in decommissioned or lostcomms.
Workaround: Ignore the value indicated by the traffic light icon under the above circumstances.
•
Symptom: Ethernet Interface Configuration: Loopback cannot be set for Gigabit Ethernet
Conditions: Trying to enable the loopback fails, but no error is reported. The EM needs to report an error when set fails. Valid options also need to be provided for Gigabit Ethernet interface.
Workaround: No workaround is currently available
•
Symptom: Can not apply CAR Policy with MAC type access list
Conditions: Applying CAR Policy having MAC type access list to an ATM interface fails.
Workaround: CAR Policy can be configured in the device using IOS CLI through "Initiate Telnet Service" from the "Technology Specific Tools" menu. An example configuration of CAR policy with MAC type access-list is as follows.
ems7507a#config tems7505a(config)#access-list 701 permit 0000.0000.0001ems7505a(config)#int atm2/1/0ems7505a(config-if)#rate-limit input access-group 701 8000 8000 8000 conform-action continue exceed-action continue•
Symptom: CAR Policy Apply: Average Transmission Rate not saved on device
Conditions: In the CAR Policy Apply dialog, the value of Average Transmission Rate is not getting saved on the device.
Workaround: No workaround is currently available
•
Symptom: Non-default QoS in deploy wizard fails connection
Conditions: When trying to deploy a valid QoS profile, an error is displayed.
Workaround: No workaround is currently available
•
Symptom: Default QoS profile data not showing in QoS Management dialog
Conditions: Default QoS profile values are not displayed in QoS Profile Management dialog. When a VCL is deployed using the default QoS profile, it is deployed successfully. However, when viewing this newly created VCL using the QoS Profile Management dialog it would appear that all values are blank. The default values for the VCL are not displayed, although they have been correctly set in the device.
Workaround: User needs to telnet to the device and look up the values manually via CLI.
•
Symptom: Wrong error message after applying CAR on controllers
Conditions: For devices, while applying a CAR Policy to a E1/T1/E3/T3 port, the error message generated is misleading. This error message is misleading because it implies that CAR Policy is supported on these ports. Since the CAR Policy is not supported on these ports in devices, the correct behaviour would be some error message stating that CAR is not supported.
Workaround: No workaround is currently available
•
Symptom: Current CAR policy is not updated in CAR Policy Status dialog
Conditions: The "Current CAR Policy" box in the CAR Policy Status Dialog is not getting updated, even if the dynamic updates are enabled.
Workaround: Close the currently open CAR Policy Status dialog. Open a new CAR Policy Status dialog and the updates will be correctly displayed.
•
Symptom: Applying QoS ok in CEMF does not mean ok on device
Conditions: For example, if you have one ABR QoS Profile created in the ATM QoS Profile Configuration dialog with only PCR value input as 1200 cells/sec, others with blank. If you try to connect it, it will fail. EM should make sure of the right combination for a QoS Profile to be sent to a device, for example, even if users do not set some values like MCR.
Workaround: No workaround is currently available
•
Symptom: MIB not supported, but attributes can be set through IOS
Conditions: In the ATM VCL Configuration dialog, the Configuration tab has many attributes that are not supported by 7x00 devices.
Workaround: No workaround is currently available
•
Symptom: VCL Configuration dialog Layer 3 Configuration tab not working
Conditions: Under the Layer-3 configuration tab of the VCL Configuration Dialog, if the first action a user takes is to set a value for the Encapsulation parameter then it is not then possible to set a value for AAL5Encapsulation. However, if AAL5Encapsulation is set first then it is possible to set a value for Encapsulation.
Workaround: Set AAL5Encapsulation parameter first before the Encapsulation parameter.
•
Symptom: No error message in SVC Configuration dialog when decommissioning SVC
Conditions: Under certain circumstances when saving NSAP address and Sub Interface numbers using the SVC Configuration dialog, the values are not saved nor is there an appropriate error message to the user.
Workaround: The Sub Interface Number field should not be left blank. If no value is to be applied then the field should be left at its default value of "Not-applicable".
•
Symptom: Add IOS passwords in chassis deployment template
Conditions: In Chassis Deployment Wizard (non-Quick Start), add IOS User Name/Login Password/Exec Password.
Workaround: No workaround is currently available
•
Symptom: SVC Management dialog -> Refresh fails
Conditions: Some changes are written successfully to a chassis. However, when switching to a second chassis and then coming back to the first, the changes disappeared from the dialog.
Workaround: No workaround is currently available
•
Symptom: Remove all unsupported attributes from Performance Manager
Conditions: Some attributes in ATM Interface Performance dialog may not be populated.
Workaround: No workaround is currently available
•
Symptom: Upgrade analysis incorrectly says CEMF version has changed
Conditions: When first executing the "BladeInstall -u", the script analyzes the system and comes back to say that "CEMF Version has changed". This is incorrect at this stage of the upgrade, as nothing has been accomplished yet. Please remove or change this statement.
Workaround: Statement can be ignored as invalid.
•
Symptom: DS1 Configuration dialog hangs after recommissioning
Conditions: The DS1 Configuration dialog hangs after decommissioning a chassis and attempting to recommission it. The cursor stays as a clock and you can't select anything.
Workaround: No workaround is currently available
•
Symptom: Module not discovered after CEMF restore
Conditions: Take a backup of the dataload in CEMF (i.e. using 'cemf backup' command), Stop CEMF, insert a module in one of the chassis of dataload, start CEMF, do a dataload restore(i.e. using 'cemf restore' command). The module that was inserted into the chassis is not discovered.
Workaround: No workaround is currently available
•
Symptom: r2-pulse compelled is not a valid option for DS0 signalling type
Conditions: Select an E1 port from the DS1 Configuration dialog. In the DS0 Group, select "r2-pulse compelled" as "DS0 Signaling Type" and create a DS0 group; an error is generated.
Workaround: No workaround is currently available
•
Symptom: Basic data validation needed in voice dialog
Conditions: If no interface is selected, the "Create" and "Delete" buttons should be grayed out. If no data is entered for "DS0 Group Number" and "DS0 Time Slots", if user click "Delete", the EM should report an error.
Workaround: No workaround is currently available
•
Symptom: No dynamic update in DS1 Configuration dialog
Conditions: From the DS1 Configuration dialog, click the "DS0" group tab. If you telnet to the device and configure some groups, the change is not updated in the DS1 Configuration dialog until you do a manual refresh, although it displays "Dynamic updates are enabled".
Workaround: No workaround is currently available
•
Symptom: ATM connections cannot be deleted post-upgrade
Conditions: After an upgrade, you are unable to delete any ATM connections successfully. You should be able to use the full functionality of the EM post-upgrade
Workaround: No workaround is currently available
•
Symptom: After upgrade, ATM interfaces appear with an SNMP icon
Conditions: After upgrade, ATM interfaces appear in the tree view with an "SNMP" icon beside them instead of with the usual ATM graphic beside them. The interfaces appear to be correctly named as "ATM 1-0" or their relevant name, but the icon is not the standard one used for ATM and Ethernet interfaces.
Workaround: No workaround is currently available
•
Symptom: Voice card status cardTypeNotSet post-upgrade
Conditions: After an upgrade, all voice cards are hashed out and their state is "cardTypeNotSet". This should not be the case, as the card type has been set on the chassis.
Workaround: No workaround is currently available
•
Symptom: Voice Group creation errors not presented in action report
Conditions: Action report does not provide the command-line failure information when a voice group creation fails.
Workaround: No workaround is currently available
•
Symptom: Show controllers needs a space between tech name and slot number
Conditions: When running the `show controllers' option on 7k devices, some ATM/POS interfaces need a space between the technology name and slot number.
Workaround: No workaround is currently available
•
Symptom: Two options to set clock source on ATM interface
Conditions: Option `clock source' has two types and option `atm clock' has one. For other ATM interfaces in 7k devices, there is only one option `atm clock'. But if using `atm clock' on ATM interfaces, it will generate a failure report.
Workaround: No workaround is currently available
•
Symptom: IOS command needs to be updated for Scrambling & Framing Mode values
Conditions: Payload scrambling is used in all 7k devices and supported ATM cards. Framing mode is used in almost all 7k devices and supported ATM cards. However, two cards (PA-A3-OC12MM and PA-A3-OC12SMI) do not return values while using this IOS command.
Workaround: No workaround is currently available
•
Symptom: Investigate and resolve differences in common files
Conditions: Conflicts were found between EM package files and other EMs or COM packages. These differences may affect interoperability and should be resolved. This may mean migrating changes into COM or moving these differences to EM-specific files that will not affect other EMs.
Workaround: No workaround is currently available
•
Symptom: 12k coresident install changes help for other EMs
Conditions: When more than one Element Manager is installed on a CEMF system, invoking help for a dialog brings up to the help page that was installed by the last installed Element Manager.
Workaround: No workaround is currently available
•
Symptom: PA-4B-xx and PA-8B-xx show no interfaces in tree view
Conditions: Interfaces should appear in the tree view for these cards.
Workaround: No workaround is currently available
•
Symptom: ATM interface failed to query attribute in ifTable
Conditions: The device is not replying with the correct data. If you ask for the whole table, it responds with the correct description. However, when you request the specific OID, it comes back with 'NO SUCH INSTANCE'.
Workaround: No workaround is currently available
•
Symptom: Show running configuration against 12.1(14)E causes config change trap
Conditions: A "show running-configuration" should not cause a config change trap to be sent.
Workaround: No workaround is currently available
•
Symptom: Unable to get the right Maximum Transmission Unit value
Conditions: After deploying a chassis, set the Maximum Transmission Unit. Open the IP Configuration dialog and select the interface; the Maximum Transmission Unit value is not right.
Workaround: No workaround is currently available
•
Symptom: Different deployment/commission step
Conditions: If you auto-discover or use manual deployment to deploy a chassis, then do the manual commissioning, the Slot Number is blank in the Module Inventory dialog.
Workaround: No workaround is currently available
•
Symptom: IP Multicast Fast Switching can be set and get in IP configuration
Conditions: For a device, the value of IP Multicast Fast Switching field in the IP Configuration dialog is not being retrieved correctly from the device.
Workaround: No workaround is currently available
•
Symptom: objectTypeFaileParser Fails
Conditions: CEMF fails to start after the uninstallation of the EM or after resetting the database when multiple EMs are installed.
Workaround: After installing the EMs, ensure that ENTITY-MIB provided is available in the <CEMFROOT>/config/mib directory.
•
Symptom: Wrong hardware version number for one 7505 module
Conditions: 7505 has one module whose slot number is 4-0. Its hardware version shows as 196865. Actually it should be 1.01.
Workaround: No workaround is currently available
•
Symptom: No action report for commission failure when quick start is used
Conditions: Failure of chassis commissioning due to wrong SNMP community strings is not reported through error message to the user.
Workaround: No workaround is currently available
•
Symptom: Voice interfaces go away and do not return if card type is set externally
Conditions: When managing a chassis with voice cards, if the voice cards are already set and if the card types are changed to their opposites (T1 -> E1, or vice-versa), then in the "complacent" copy, the interfaces simply disappear and do not return
Workaround: The chassis can be decommissioned and recommissioned to effect the card type change.
•
Symptom: Power Supply in decommissioned state while chassis in normal status
Conditions: Power supply is in decommissioned state while the chassis is in normal state.
Workaround: Commission the power supply manually.
•
Symptom: Channelized T3 interface stuck on discovery state
Conditions: When a device having Channelized T3 Port Adapter is commissioned, the interfaces under the port adapter are getting stuck in discovery state. Please note that management of channelised interfaces is not supported.
Workaround: No workaround is currently available
•
Symptom: No screen shots in voice related help files
Conditions: There are no dialog screen shots in the Voice Card Type Configuration and DS1 Configuration dialog help files.
Workaround: No workaround is currently available
•
Symptom: Voice Card Type dialog not working when no IOS password is set
Conditions: Use auto discovery to discover a chassis, then commission it without setting an IOS password. Open the Voice Card Type Configuration dialog. Set the Card Type field to e1 and save. Nothing is saved but no error message is returned. When IOS password is not set, either not allow user to edit Card Type field or return error message when user tries to set it to t1/e1.
Workaround: No workaround is currently available
•
Symptom: Error should be displayed when IOS password is not set
Conditions: C7KM should display "ERROR" for those dialogs that use IOS if the IOS passwords are not set.
Workaround: No workaround is currently available
•
Symptom: Modules are in normal state when chassis is in discovery lostcomms
Conditions: Deploy and commission a chassis; all modules are in the normal state. Pull out and reload devices, then configure Voice Card attributes. If you Power off the chassis at this point, only the chassis and two power supplies are in the discovery lostcomms state. One hour later, all other modules on the device are still in the normal state.
Workaround: No workaround is currently available
•
Symptom: NPE and RSP should not have interface level menus
Conditions: Currently if you right click on NPE or RSP modules, interface level menus. are provided although there are no interfaces discovered under it.
Workaround: No workaround is currently available
•
Symptom: Redundancy: Power supply is in discovery lostcomms after failover
Conditions: Set redundancy mode to rpr-plus on a device, then perform a forced failover. The chassis and all modules come back to normal except that power supply is in discovery lostcomms state.
Workaround: Decommission and recommission the power supply to bring it back to norma
•
Symptom: No SMDS option for Encapsulation in POS Profile dialog
Conditions: In the POS Profile or POS Interface Configuration dialog, the Encapsulation attribute in the General frame does not provide the SMDS (Switched Megabit Data Service) option.
Workaround: No workaround is currently available
•
Symptom: Only 2 interfaces discovered underneath PA-8T-V35
Conditions: There should be 8 serial interfaces under PA-8T-V35-3-1(ems7505a). Currently there are only 2 discovered.
Workaround: No workaround is currently available
•
Symptom: 7K EM needs to use Entity MIB
Conditions: 7K EM v2.0 uses OLD-CISCO-CHASSIS-MIB. ENTITY-MIB should be the replacement since many platforms no longer support OLD-CISCO-CHASSIS-MIB.
Workaround: No workaround is currently available
•
Symptom: VCL cannot be uploaded from device to CEMF
Conditions: Create one VCL with VPI/VCI value 26/26 on device and perform connection upload from CEMF. Verify the above VCL has been uploaded. Decommission the above VCL and modify and save VPI/VCI value from ATM VCL Configuration window. Create a new VCL with VCI value 28 on device and perform connection upload from CEMF. The VCL fails to be uploaded to CEMF.
Workaround: No workaround is currently available
•
Symptom: Framing Attribute on ATM Configuration dialog reflects NoLabel
Conditions: Framing Mode attribute fails to change on the dialog after set on the device.
Workaround: No workaround is currently available
•
Symptom: Gray out unsupported fields on the VCL Configuration dialog
Conditions: The following attributes are not supported: Encapsulation Flag, Encapsulation Protocol AAL, User Type, PD Mode, AIS Mode, RDI Mode, and UPC Mode.
Workaround: No workaround is currently available
•
Symptom: SVC/VCL Configuration: No attribute should change when decommissioning connection
Conditions: In VCL Configuration dialog, the following fields can still be changed on a connection in decommission state: Auto Suggestion, Subscriber ID, VPI, and VCI. Also, in SVC Configuration dialog, the following can be changed on a connection in decommission state: NSAP Address and Sub-Interface Number. These fields should not be editable on a connection object in the decommissioned state.
Workaround: Do not change any of the above fields on a connection object in the decommissioned state.
•
Symptom: Change encapsulation on POS Interface causes 7k device to become idol
Conditions: Each time you change encapsulation between SMDS and other options, this action causes the device to have "no response" for a period of time.
Workaround: No workaround is currently available
•
Symptom: Unable to get the right module type in Module Inventory dialog
Conditions: After deploying a chassis, open the Module Inventory dialog and you will see the module PA-2FE-TX type is "No label" Using the MIBbrowser, the object value is "573" which is the value of the module type. The value from the chassis does not match the value in the Module Inventory dialog.
Workaround: No workaround is currently available
•
Symptom: ATM dialog becomes unavailable after a period of inactivity
Conditions: The ATM config dialog becomes unavailable after a period of inactivity. After a period of time the dialog goes into busy mode (hourglass icon) and the dialog cannot be altered.
Workaround: Close and reopen the dialog.
•
Symptom: Issues with OIR alarms when module is in performance polling
Conditions: Module major outstanding alarms are not getting cleared when module object is in performance polling state.
Workaround: 1. Stop and start the performance polling on the module to clear the outstanding alarm. 2. Manually clear the outstanding major alarm.
•
Symptom: Issue when module going to discoverylostcomms state
Conditions: When a module goes to discoverylostcomms state for a Chassis already commissioned, no alarms are generated. When a module goes to discoverylostcomms state when commissioning a chassis, a major alarm with description "Deployed module does not match actual module" is raised.
Workaround: No workaround is currently available
•
Symptom: Clear corelation is not working for link up/down alarms
Conditions: Interface level link down alarms are not cleared when the device does not define the CEMF server as a trap server. If an interface is brought down, the trap server is removed, and then the interface comes back up, no event is received to clear the event. The polling in CEMF detects that the interface is up but the event is not cleared.
Workaround: Clear the alarms manually.
•
Symptom: Save icon on ATM Interface Configuration Profile dialog not active
Conditions: In the ATM Interface Configuration Profile dialog, when there are multiple profiles, some attributes fail to save for the second profile in the list.
Workaround: No workaround is currently available
•
Symptom: EMS appears to lose alarms
Conditions: For certain alarm types, the event browser opened against a chassis only shows the most current alarm raised in the working event view. This gives the impression that only one alarm has been raised of a given type, when there have been many alarms raised of that type on the chassis.
Workaround: The alarms can be viewed by using the history function of the Event Browser to view all of the alarms raised on the chassis.
•
Symptom: NSAP should not be there for SVC with CEMF endpoint deploy template
Conditions: The deployment template for SVC with CEMF endpoint used for SVC Deployment asks for the NSAP Address field to be filled in by the user. The NSAP address can be calculated automatically from the Destination Port but CEMF does not automatically do this.
Workaround: No workaround is currently available
Related Documentation
The following Cisco EMF and Cisco 7000 Series Manager documentation is available as additional resource materials.
Cisco EMF Documentation
The following documents are available for the Cisco EMF:
•
Cisco Element Manager November 2002 Upgrade•
Version 3.2 Service Pack 4 (Cisco Element Manager November 2002 Upgrade)•
(Cisco Element Manager November 2002 Upgrade)•
Cisco Element Manager November 2002 Upgradehttp://www.cisco.com/en/US/partner/products/sw/netmgtsw/ps829/prod_release_note09186a0080128a9c.html
Cisco 7000 Series Manager Documentation
In addition to this guide, the following Cisco 7000 Series Manager documentation is available for reference:
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from 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 may have 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.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top 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: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco 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 website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
You can use the Cisco TAC website 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 website, 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 website. Some services on the Cisco TAC website require 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://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
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.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2003, Cisco Systems, Inc.
All rights reserved.
Posted: Wed Dec 8 13:07:32 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
