Table Of Contents
Release Notes for Cisco 12000/10720 Manager
(Release 3.0)Cisco 12000/10720 Manager Features
New Features in C12k/10720M Release 3.0
Determining the Software Version
Known Limitations in this Release
Important Notes: Adding Additional Swap Space
Obtaining Technical Assistance
Release Notes for Cisco 12000/10720 Manager
(Release 3.0)
Contents
This document contains the following information:
•
"Cisco 12000/10720 Manager Features" section
•
•
•
•
•
•
•
•
Introduction
Cisco 12000/10720 Manager is an Element Manager (EM) that works in conjunction with the Cisco Element Management Framework (Cisco EMF) to enable service providers to plan, provision, configure, and monitor network services on Cisco 12000/10700 series Internet routers. C12k/10720M is designed to meet the operator business requirements for the control and operation of the Cisco 12000/10700 series Internet routers. C12k/10720M eases and accelerates device deployment and enables efficient operation of Cisco 12000/10700 series Internet router network environments; for example, by supporting template-based QoS interface configuration and complex fault isolation applications for efficient maintenance of Cisco 12000/10700 series Internet router based services.
Cisco 12000/10720 Manager Features
C12k/10720M features include the following:
•
•
•
•
•
•
•
•
•
–
•
•
•
•
C12k/10720M delivers these management functions within Cisco EMF. Cisco EMF provides consistency across a common user interface, operational event management, auto map building, and common data management for various Cisco element managers. Cisco EMF also provides a robust foundation and toolkit for building scalable CORBA-based provisioning integration modules for customer's specific Operational Support System (OSS) environments.
C12k/10720M and Cisco EMF are part of the Cisco Service Management (CSM) suite, a strategic component of Cisco's products and solutions for New World Operations.
Note
New Features in C12k/10720M Release 3.0
Release 3.0 of C12k/10720M adds the following functionality to release 2.2:
•
•
System Requirements
Table 1 details the system requirements for C12k/10720M release 3.0.
Note
Please contact Cisco for advice and constancy on planning large scale deployments (>50 Cisco 12000 series Internet routers).
Caution
Note
swap -sandprtconfto determine the available amount of swap and RAM (respectively) on your machine.
Software Compatibility
This software release has been tested on release 2.6/2.8 of the Solaris operating environment, for Sun SPARC workstations, and for Year 2000 Compliance.
Table 2 details software compatibility for C12k/10720M release 3.0.
Determining the Software Version
To determine installed Cisco EMF packages, and version numbers, use the Cisco EMF command:
<CEMFROOT>/bin/cemf install -show
Note
/opt/cemf
Version Supported
For this C12k/10720M release, the following components must be installed:
•
•
(On CCO, the filename corresponding to this patch is CEMF3.2SP4.tar.Z)•
(On CCO, the filename corresponding to this patch is CEMF3.2P4.1.tar.Z)
Note
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cemf/3_2/install/index.htm
Known Limitations in this Release
The following Cisco 12000 series Internet router modules are not supported by this release:
•
Important Notes: Adding Additional Swap Space
C12k/10720M release 3.0 running on Cisco EMF v3.2 requires 2GB of swap space. In general, if your machine requires additional swap space, you are advised to re-partition one of the disks to allocate a new swap partition.
Use the Solaris command format (1M) and in particular, the partition option of this command to partition appropriate swap space.
Note
A simple, but less efficient (in performance terms) method of increasing swap space is to create a file and add it to your available swap. The following example shows how to add 1GB swap to your Sun workstation (assuming sufficient available free disk space):
mkfile 1000m /opt/MY_EXTRA_SWAP_FILE
swap -a /opt/MY_EXTRA_SWAP_FILETo ensure that this file is added to your swap after a system reboot, please remember to add it to the
/etc/vfstabfile on your machine. If in doubt, please consult a Solaris system administrator.
Note
Caveats
This section describes known issues with C12k/10720M Release 3.0.
C12k/10720M Issues
This section describes the known C12k/10720M issues.
CSCat20411
Problem: There must be a provision to determine the alarms that have been raised from within EM as opposed to which have been raised from receiving traps. Currently, the domain is always being shown as internal.
Workaround: none
CSCdx53849
Problem: If an attempt is made to delete any existing Cos Queue Group or ToFab Policy from a decommissioned interface or module through Map Viewer, then the usage count is decremented even though Cancel operation is selected in the deletion dialog. On recommissioning and applying a different CosQ Group or ToFab Policy, there are more than 1 object under the interface or module.
Workaround: Cancel should not be used while deleting CosQ groups/ToFab policies.
CSCin27856
Problem: Running configuration is not copied to startup-configuration on performing the download operation through configuration editor dialog.
Workaround: Force a Write Mem operation through the Chassis Configuration Dialog for the chassis.
CSCdz62993
Problem: The RPR Mode supported table in LC Status tab of RPR Status dialog shows some extra information in the table when both RPs have different images. This exists when redundancy mode is RPR.
Workaround: None
CSCat21181
Problem: The use of the Edit Map Service from the Site object to deploy chassis and module fails.
Workaround: Manually deploy the chassis and the modules or auto discover instead of using the Class Palette to create Maps.
CSCin16884
Problem: When associating CosQ group or Tofab policy the IOS shows % WARNING during the process of configuration if the device is running in "12.0(21)S1, 12.0(21)ST1 and 12.0(22)S". But association is successful on the device. But in the EM the status shown is association failed.
Workaround: Modify the Mark .Prob Denominator value to less than Max. Threshold value and save the changes and re-apply the same.
CSCdz59224
Problem: The newly created CosQ Groups and ToFab policies are not listed in the WRED-Tx and WRED-Rx configuration dialogs dynamically.
Workaround: Close and re-launch the Tx and Rx configuration dialogs.
Upgrade Issues
This section describes the issues with Upgrading C12kM software.
CSCdx61385
Problem: The usage count of Applied CAR Policies gets decremented by 2 instead of 1 while deleting some CAR policies. This behavior is observed when existing CAR policies that were present before the upgrade are removed from the interfaces. The usage count gets decremented correctly while removing newly applied CAR policies after upgrade.
Workaround: None
CSCdx60212
Problem: The order of Access lists are reversed in the CAR Policy configuration dialog after C12kM 2.2 to C12k/10720M Release 3.0 upgrade.
Workaround: After upgrade, remove the CAR policies with Access lists applied for an interface, re-order the Access lists and re-apply to any interface.
CSCin25501
Problem: Module does not go into the performance polling state during global performance polling after upgrade
Workaround: Start the performance polling for modules through the module performance dialog.
Chassis Manager
This section describes the known Chassis Manager issues.
CSCat21053
Problem: Unable to select Multiple chassis objects from the Chassis Management Information window for performing bulk operations.
Workaround: Single select chassis from Chassis Management Information window for performing any configuration changes.
CSCat21055
Problem: Unable to select multiple chassis objects from the object selector box in the SNMP Management window.
Workaround: Single select chassis from Chassis SNMP Management window for performing any configuration changes.
CSCin27852
Problem: Auto-discovered chassis can be deployed manually with the same IP address. The EM allows the user to have same chassis object deployed twice.
Workaround: Auto discovered chassis should not be re-deployed manually.
CSCdz55687
Problem: Wrong notification about IOS image download and Global Performance Logging On actions, while chassis is in synchronization state.
Workaround: Perform the IOS image download and Global Performance Logging when the chassis is in normal state.
Generic Module
This section describes the known generic module issues.
CSCin25501
Problem: When a linecard of incorrect type has been deployed under a managed chassis against a TANGO card, commissioning the module in the EM, not only moves the incorrectly deployed modules and interfaces to mismatched state but also deploys the sub-modules and its interfaces of the TANGO card.
Workaround: Decommission and delete the additional deployed TANGO sub-modules and its interfaces.
Generic Interface
This section describes the known generic interface issues.
CSCdy63379
Problem: Normal alarm is raised for the interface that is administratively up and operationally down. The incoming Normal alarm clears the outstanding major alarm against the interface but theEM retains the interface in the Errored state.
Workaround: When the EM performs the interface status polling, the major alarm is raised against the interface object if it is administratively up and operationally down.
CSCin21441
Problem 1: Commissioning SRP interface and bulk commissioning SRP interface and side interfaces results in commissioning only the SRP interface. The SRP side interfaces remains in decommission state.
Workaround: Commission the SRP side interfaces separately.
Problem 2: The Generic Interface Configuration dialog attributes i.e., the alias, Administration Status and Link Up/Down Trap status attributes cannot be set for the SRP side interfaces. This is due to MIB support not being present.
Workaround: None
CSCdy68703
Problem: In the Generic Interface Configuration dialog, the status cannot be set to value "Testing". This is due to MIB support not being present.
Workaround: None
CSCin20688
Problem: Performance polling state is not rippled down to SRP side interfaces from SRP main interface.
Workaround: Start the performance polling on SRP side interfaces individually.
CSCin20404
Problem 1: On applying a profile to SRP side interface, the framing attribute does not get refreshed.
Problem 2: After applying a profile to SRP side interface, when a user modifies the clock source and IPS management request mode attributes through SRP side interface configuration dialog, an error message pops up even though the value is saved in the device correctly.
Workaround: Manually refresh the SRP Side Interface Configuration dialog for the values to be populated correctly.
ATM Connection Manager
This section describes known ATM connection manager issues.
CSCdw94362
Problem: After having successfully uploaded the ATM connections, if any of the uploaded PVCs are decommissioned and the VPI/VCI value is modified, then performing an upload again does not create a new PVC object but the upload summary displays that the object has been submitted for creation. Also, further ATM connections are not uploaded on the device.
Workaround: Do not change the VPI/VCI values for any uploaded connections after decommissioning the same. If it is done, delete the connection objects from the EM.
CSCdx53825
Problem: C12kM allows the user to create duplicate PVCs and SVCs. The duplicate objects also get moved to the normal state during a connect action, though in the router, only one connection is available.
Workaround: Avoid creating duplicate PVCs and SVCs under the same interface or sub-interface.
CSCuk26784
Problem: Bulk deployment of PVC will fail due to naming conventions followed, if carried out more than once under the same interface.
Workaround: Change the default PVC name for each bulk deployment by either changing the prefix or by making sure that the increment number is greater than all other PVCs that have been bulk deployed previously.
CSCdx17370
Problem: The status of CiscoATMCMUpload always displays as "no value" in the status bar of ATM Connection Upload Dialog. The status remains at "no value" even after an Upload or Synchronization operation.
Workaround: None
CSCds28762
Problem: In PVC Status Dialog, only Last Change and Operational State attributes populate values and the rest of the fields do not display any information.
Workaround: none
CSCdx65832
Problem: Bulk deployment with Auto-Connect option enabled for PVCs and SVCs on a chassis will fail when this task is carried out when the chassis is in Synchronization State.
Workaround: Bulk deployment Auto-Connect option enabled for PVCs and SVCs on a chassis can be done when chassis is in Normal State.
CSCdy51382
Problem: Bulk ATM Connection upload will fail when the selected chassis list has chassis objects in Managed and Non-Managed state.
Workaround: Bulk ATM Connection upload can be done on bulk selecting chassis only in Managed state or single select the chassis in Managed state.
CSCdz51755
Problem: After reinserting an ATM Linecard to a different slot from a managed chassis the ATM Connection upload process still uploads the connection objects under the removed modules object's interfaces.
Workaround: The connection objects will be correctly uploaded to reinserted module's interfaces if the removed module object is decommissioned and deleted from the EM.
CSCdy63696
Problem: Re-connecting a decommissioned PVC Object with a different sub-interface number will create dummy sub-interface in the device.
Workaround: Disconnect the PVC deployed under the sub-interface and reconnect the connection after modifying the Sub-Interface number.
CSCdy59747
Problem: An ATM connection upload process overwrites the manually deployed connection object's QoS profiles.
Workaround: None
CSCdz38475
Problem: Uploaded PVC connections under sub-interfaces does not show the Sub-Interface number in the VCL Configuration dialog.
Workaround: None
CSCdy58919
Problem: The Summary information in the deployment Wizard is shown incorrectly during bulk deployment of PVC and SVC connections. But the deployment of all the connections are successful.
Workaround: None
IP
This section describes known IP issues.
CSCdw36447
Problem: Instances of CAR Policies under interfaces can be deleted after re-commissioning (i.e. Decommission and Commission again) the corresponding Module. This causes problems in the usage count of corresponding Access Lists and CAR Policies. Even though the CAR Policy is deleted, the corresponding usage counts are not decremented.
Workaround: Do not delete CAR Policies which are present under interfaces whose modules have been re-commissioned.
CSCdv91056
Problem: Bulk selecting interfaces for CAR policy apply fails if any of the selected interfaces has got the selected CAR policy already applied.
Workaround: Bulk select interfaces that has got no CAR policy applied or single select the interfaces and apply the policies.
CSCdv55016
Problem: Engine 4 linecard (10 Port GigabitEthernet and 1 Port OC-192 Linecard) has got limitations on CAR Policy configurations.
Workaround: Since the 10 Port GigabitEthernet and 1 Port OC-192 linecard supports only the following options to configure a CAR Policy, the user needs to ensure that none other than the following options have been configured in the Selected CAR Policy before applying to a 10 Port GigabitEthernet or 1 Port OC-192 interface.
The options supported are:
1.
2.
3.
4.
5.
CSCuk22774
Problem: The CAR policy status dialog is not updated dynamically.
Workaround: Select a different interface and re-select the original interface to get the "Current CAR Policies" field updated correctly.
CSCdy39918
Problem 1: IP Multicast Fast Switching attribute is populated as "disabled" in the IP configuration dialog against the GSR and YB chassis interfaces.
Problem 2: The IP Multicast Fast Switching attribute cannot be set for YB chassis interfaces through IP configuration dialog.
Workaround: None
CSCin20686
Problem: The IP manager process restarts when the attributes are modified in the IP configuration dialog launched against the chassis having no management passwords set.
Workaround: Configure the management passwords for the chassis through Chassis Management Information window and re-launch the IP configuration dialog.
CSCdx29371
Problem: When the chassis or the modules are bulk selected from the IP configuration dialog, the ip address and subnet mask fields are not available for editing.
Workaround: Single select chassis and modules from the IP configuration dialog.
Cisco IOS
CSCdt50500
Problem: CosQ group gets applied to all the interfaces of the ATM module even though it has been applied to the first interface.
Workaround: none.
ATM
This section describes known ATM issues.
CSCdx17448
Problem: When a profile is applied to an interface in the ATM Interface Configuration Dialog, the values are applied to the interface, however the dialog is not refreshed for the following attributes: Max VCCs, Configuration, Framing Mode, Keepalive time.
Workaround: Manually refresh the ATM interface configuration dialog to get all the attributes populated correctly after applying the profile.
Ethernet/HSRP
This section describes the known Ethernet/HSRP issues.
CSCdx35448
Problem 1: When a HSRP profile with all the profile attributes correctly set is applied to an interface, except the IP address field, all the attributes are correctly applied and refreshed.
Problem 2: When a HSRP profile with incorrect values for profile attributes is applied to an interface then except the Group number field, none of the attributes are refreshed.
Workaround: Manually refresh the HSRP configuration dialog to get all the attributes populated correctly.
IOSDRep
This section describes known IOSDRep issues.
CSCdx20895
Problem: In any Interface configuration dialog that uses IOSDRep for configuring the values, if one of the values cannot be set on the device while modifying a set of attributes, then an incorrect failure information is displayed that indicates the failure for all the fields. Also, the running configuration is not copied to the startup configuration.
Workaround: After the failure message, click on button "writeMem" in the Chassis Configuration Dialog for the particular Chassis to copy running configuration to startup configuration.
POS
This section describes known POS issues.
CSCdu75763
Problem: When the APS Status dialog is launched against a chassis having more than eight APS configurations, the details are not shown correctly in the APS Status dialog.
Workaround: Use sh aps command in the IOS CLI for viewing the APS circuits.
CSCdw90475
Problem: The initial display of Revert Mode field is incorrect when Protect radio button is selected in the APS Configuration Dialog. The field Revert Mode is populated as "NotApplicable" where as valid values are "Revertive" or "Non-Revertive".
Workaround: Modify the Revert Mode to correct value after selecting Protect radio button.
CSCdx47600
Problem: POS SPE Scrambling field is not refreshed in the POS config dialog while applying a POS profile.
Workaround: Perform a manual Refresh to get all the attributes populated correctly.
VLAN
This section describes the known VLAN issues.
CSCdw75175
Problem: If the VLAN Performance dialog is launched against a chassis having more than 50 VLANs, the dialog displays junk characters.
Workaround: None
Cisco EMF
This section describes the known Cisco EMF issues.
In the bottom part of every window there is a status bar that displays full hierarchy of the object that is managed by the form, with the status of every object of the hierarchy: this message is truncated so that only the first part of the hierarchy is fully readable.
CSCdu29988
Problem: If the first octet of the MAC address is set to 20 to 7e in the ACL configuration dialog for MAC address based Access lists then the MAC address value stored by the EM is the ASCII value of the whole MAC address.
Workaround: Configure the MAC address values with the first octet having the range before 20 and after 7e for the MAC address based Access Lists in the ACL configuration dialog.
CSCdy35132
Problem: When an interface profile is either created through Create action or deleted by conventional means for the first time from any interface profile dialog then all the attributes in the dialog is greyed out.
Workaround: Re-launch the dialog to get all the profiles and its attributes to be displayed correctly.
Related Documentation
The documentation supporting this release is:
•
–
•
–
•
–
•
–
Obtaining Documentation
The following 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 the following URL:
Translated documentation is available at the following 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
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write 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 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 to
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you 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 the following URL:
All customers, partners, and resellers who have a valid Cisco services 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 the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; 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 will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following 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). In addition, 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.
Guest
