Table Of Contents
Release Notes for Cisco 12000 Manager
(Release 2.1)New Software Features in C12kM Release 2.1
Determining the Software Version
Cisco EMF Installation Parameters
Known Limitations in this Release
Important Notes: Adding Additional Swap Space
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco 12000 Manager
(Release 2.1)
Contents
This document contains the following information:
•
"New Software Features in C12kM Release 2.1" section
•
•
•
•
•
•
•
•
Introduction
Cisco 12000 Manager (C12kM) 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 series internet routers.
C12kM is designed to meet operator business requirements for the control and operation of the Cisco 12000 series Internet routers. C12kM eases and accelerates device deployment and enables efficient operation of Cisco 12000 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 series internet router based services.
C12kM Features
C12kM features include the following:
•
•
•
•
•
•
•
•
•
–
•
•
•
C12kM delivers these management functions within the 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.
C12kM 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 Software Features in C12kM Release 2.1
Release 2.1 of C12kM adds the following functionality to release 2.0.1:
•
•
–
–
–
–
•
•
•
•
System Requirements
Table 1 details the system requirements for C12kM release 2.1.
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 workstation.
Software Compatibility
This software release has been tested on release 2.6 of the Solaris operating environment, for Sun SPARC workstations, and for Year 2000 Compliance.
Table 2 details software compatibility for C12kM release 2.1.
Determining the Software Version
To determine installed Cisco EMF packages, and version numbers, use the Cisco EMF command:
<CEMFROOT>/bin/cemf install -show
Note
<CEMFROOT>is the convention adopted in Cisco EMF documentation to indicate the installation directory for Cisco EMF and the C12kM software. This default location is:/opt/cemf
Version Supported
In particular, for this C12kM release, the following components must be installed:
•
•
Note
Note
Cisco EMF Installation Parameters
These are the installation parameters to use to install the Cisco EMF
disk layout
c0t0d0s0 50 /
c0t0d0s1 2048 swap
c0t0d0s3 256 /usr/openwin
c0t0d0s4 100 /var
c0t0d0s5 5000 /opt
c0t0d0s6 300 /usr
cluster type developer
Solaris patches none (but it is recommendation to use Sun's recommended patch set).
The multiple disk set-up is for performance/scale reasons only and for a small lab deployment is not essential.
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
C12kM release 2.1 running on Cisco EMF v3.1 requires 2GB of swap space. In general, if your workstation 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 workstation. If in doubt, please consult a Solaris system administrator.
Note
Caveats
This section describes known issues with C12kM release 2.1.
C12kM Issues
CSCat20411 (severity 3)
Problem: Require ability to determine which alarms have been raised from within EM as opposed to which have been raised from receiving traps. Currently, domain is always shown as internalCSCat20605 Severity 3 SnmpV3 option needs to be removed from the chassis deployment wizard.
Workaround: No workaround.
CSCds60943 (severity 3)
Problem: While testing interoperability of C12kM with CMNM and UGM, it was found that C12kM would not remove devices from the Cisco EMF viewer map when C12kM was uninstalled.
Workaround: No workaround.
CSCds60950 (severity 3)
Problem: While interoperability testing C12kM and UGM, after uninstall of C12kM, UGM device deployment failed. After performing a stop/reset/start of the Cisco EMF database server, UGM device deployment was successful. However at this point all previous deployments were deleted from the database due to the Cisco EMF reset.
No workaround.
CSCds60952 (severity 2)
Problem: While interoperability testing with C12kM and CMNM, when CMNM is loaded followed by C12kM, C12kM is unable to deploy devices. When C12kM is loaded followed by CMNM, C12kM is able to deploy devices.
No workaround.
CSCdt70953 (severity 3)
Problem: In the configuration Editor window, Criteria names list in list box not consistent when you launch the window from Chassis-1 and Chassis-2 one after another.
Workaround: Create a criteria names which is called search string separately for each chassis.
CSCdu10893 (severity 3)
Problem: On Configuration Editor window, Upload action does not stop at search criteria which was selected in the following pattern is available in Criteria name object list POS0/1, POS0/2 and etc.
Workaround: Use Search Criteria without slash ('/') special character.
CSCuk24224 (severity 3)
Problem: Deployed and commissioned 100 Cisco 12016 Chassis to Normal (5 at a time). Carried out user workflow tests against a real chassis - No issues. Removed the real chassis deployed. Launched Global Performance Polling on 50 Chassis. Many objects including chassis objects went to lostcomm state (though the Simulator are running), expected the objects to come back to Normal state, but the Abstraction Server crashed.
No workaround.
CSCdu18374 (severity 3)
Problem: Download fails when the vi editor (popped up during upload) is not quit after saving the changes and before doing Download.
Workaround: Save and quit the vi editor before clicking Download.
CSCdu04006 (severity 4)
Problem: In C12kM and Component Managed view the shelf objects are overlapping each other in right hand side of the Map viewer application while doing the below mentioned operation from the respective view. Deployed two chassis through auto-discovery under Site-1 object and deleted the shelf object which shown first in the right-hand side of the Map viewer. Then re-deployed the chassis through auto-discovery.
Workaround: Refresh Map-viewer application to display the object properly, or) from a Site object select Edit Map service (Site->Map->Edit Map) and launch Map Builder. In the Map Builder organise (Select and move) the objects properly.
CSCdt05209 - (severity 3)
POS OC3 module has been pulled out from the device and immediately "Remove Action" is invoked from WRED Tx-Configuration dialog. WRED Tx-CoS configuration dialog status displays Applied CoS-Q-Group has been removed. But, on the device CoS-Q-group is still associated and instance also exists under the interface object.
Work around:Don't remove the COS Queue group immediately after removing the line card. wait for the card and the interfaces to go to lostcomm state.
CSCdu20652 - (severity 3 )
Able to delete the CoS Queue Group instance after decommission / commission the interface object.
Chassis Manager
CSCdt48719 (severity 4)
Problem: When the Chassis is deleted from Map Viewer an action report pops up saying "deletion failed" though the chassis is deleted successfully. This behaviour is inconsistent.
Workaround: Close the Map Viewer and open it again.
CSCdt60829 (severity 4)
Problem: In Chassis Inventory window, observed that the value in Description, ROM ID fields are getting truncated. Not able to view the full description.
CSCat21053 (severity 3)
Problem: Unable to select Multiple chassis objects from the Chassis Management Information window for performing bulk operations.
No workaround.
CSCdt70955 (severity 3)
Problem: The Backup operation is successful while the tftp directory is full. The Backup file is created with 0 bytes.
Workaround: Verify that the enough memory space is available under tftp directory before starting Backup operation.
CSCdu09863 (severity 3)
Connection between EM and Cisco 12000 series internet router is lost during Restore operation, the action report shows successful.
No workaround.
CSCat21054 (severity 3)
Problem: Unable to select Multiple chassis object from the object selector list from the Chassis Backup Restore window to perform bulk operation.
No workaround.
CSCdu41866 (severity 3)
Problem: When the chassis goes to mismatch state, the child objects of the chassis like modules and interfaces still remains in their old state. i.e. Mismatch state is not propagated from the chassis to modules and interfaces.
Workaround: After commissioning the chassis don't change the IP address for the chassis.
CSCat21055 (severity 3)
Problem: Unable to select multiple chassis objects from the object selector box in the Chassis SNMP Management window.
No workaround.
CSCdu39404 (severity 3)
Problem: Web console did not open, while launching the web console application from the Client system.
No workaround.
CSCat21374 (severity 6)
SNMP V1 should not be used for this version of C12kM as it causes problems with commissioning and configuration of the chassis and its components.
Generic Module
CSCdt54190 (severity 3)
Problem: Some junk is getting displayed in all the Deployment Wizard-Views windows when tried to deploy multiple line cards, CSC and SFC Card.
No workaround.
CSCdt55623 (severity 3)
Problem: The C12kM view accepts incorrect values when deploying a line card from a chassis object in the Physical view.
No workaround.
Generic Interface
CSCdu29881 (severity 3)
Problem: Interface gets stuck in Discovery state on commissioning from the module (which is already commissioned).
Workaround: None.
CSCat21057 (severity 3)
Problem: Unable to select multiple chassis from the respective list box to perform bulk operations from the Generic Interface Configuration window.
No workaround.
CSCdu35285 (severity 2)
Problem: CiscoIFCon dumps core on commissioning interfaces under a decommissioned module deployed manually and which is not present in the physical device Action report on module commissioning and interface commissioning needs to be updated.
CSCdu31041 (severity 4)
Problem: Action report generated on commissioning a module has no information about success/failure status.
No workaround.
CSCdt63292 (severity 4)
Problem: Administration Status value "Testing" not getting saved for the Generic Interface Configuration window.
No workaround.
CSCdt79853 (severity 3)
Problem: In the Generic Interface Status window, select the Edit menu. Click copy configuration. The paste and save configuration menu gets enabled, click on it, then asyncSnmpDataRe dumps core.
No workaround.
CSCdu18342 (severity 3)
Problem: Occasionally link up/down traps are not raised against interfaces of a particular chassis.
No workaround.
CSCat20823 (severity 3)
Problem: Performance Manager does not accurately display stopped polling markers on the GRP Interface.
Workaround: Look at the detail data to see where the performance polling was stopped as well as looking at the individual interface status to make sure that performance polling is active.
ATM Connection Manager
CSCdt65850 (severity 5)
Problem: Start number is not correct for the multiple deployment of deployed PVC objects.
Workaround: Choose the start number such that number given is less than 1 of actual number i.e. if PVC-3, PVC-4, PVC-5 are to be deployed, enter the start number as 2 not 3.
CSCdu08710 (severity 4)
Problem: Unable to select multiple Chassis objects in QoS Profile Management window.
Workaround: Select chassis objects one after the other for applying the QoS Profile.
CSCdu14489 (severity 5)
Problem: After uploading the PVC connection with encapsulation as "ILMI", destination IP address, OAM parameters are set to "0" in the PVC Configuration window. They should be blank.
No workaround.
CSCuk23882 (severity 3)
Problem: If a chassis is the performance on state, an upload connections action cannot be performed on that chassis - the system reports that the chassis is in an unmanaged state.
No workaround.
CSCdu36241 (severity 3)
Problem: Uploaded the PVC Connections existing in the device and upload was successful. Then for the existing PVC's in the device changed the QoS profiles and Layer3 configuration attributes.Then after doing the second PVC upload for the same connections,Layer3 attributes are not updated in the PVC Configuration window. This problem is occurring during the second upload. First upload is uploading all attributes correctly.
Workaround: Decommission and delete the existing PVC's in EM and then do the PVC upload, if the layer3 configuration attributes are changed for the existing PVC's through IOS CLI.
CSCdu14411 (severity 3)
Problem: Created 5 PVC connections in the device with same QoS parameters and uploaded them in to EM using upload window. Then 5 QoS profiles are getting uploaded in to EM. But it should upload only one profile.
No workaround.
CSCdu24260 (severity 4)
Problem: OAM Manage option is always set to YES for uploaded PVC connections in the PVC Configuration window, even though its value in the device is "NO". This problem is for only uploaded PVC objects from the device. For PVCs created thrugh EM, it is set correctly in the device.
Workaround: Use "show running config" through Cisco IOS CLI to see if OAM manage is Yes or No for uploaded PVCs.
CSCdt52619 (severity 3)
Problem: PVC upload status information is not shown for multiple chassis objects. If multiple chassis are selected and upload is done, then upload status information is shown for only the first chassis object.
No workaround.
CSCuk23320 (severity 4)
Problem: With "None" option selected in the SVC Configuration window cannot connect the SVC object to the device.
Workaround: Select any value other than "None" option for the aal5Encapsulation attribute and connect the SVC to the device.
CSCdu28783 (severity 2)
Problem: ATMCM Manager will dump core while configuring PVC Object without any QoS Profile applied, if the QoS Management window is kept opened, while configuring the PVC object. This only happens when the QoS Management window is opened while configuring a PVC object without any QoS applied.
Workaround: Close the QoS Profile Management window, while configuring a PVC without a QoS in the device.
CSCdu03954 (severity 3)
Problem: PVC connection creation is not working correctly when 'Retry frequency' attribute is left blank (without any value). Ensure that all the OAM parameters are set correctly when OAM option is "YES" before making a PVC connection in the device.
No workaround.
CSCdu36281 (severity 3)
It is not possible to create a PVC with UBR as the QoS through C12kM if the Cisco IOS version running in the device is 12.0(16)ST. This problem is existing in IOS 12.0(16)ST only. In all other Cisco IOS version there is no problem in creating a PVC with the UBR as the QoS.
Workaround: Use Cisco IOS CLI for creating UBR PVC Connections.
CSCdu39648 (severity 4)
If PVC Objects under sub-interface and PVC Objects in main interface are choosen simultaneously and tried to create PVC connection in the device through the PVC Configuration window, then aal5encapsulation, IP address and broadcast are not set for the PVC under main interface in the device.
Workaround: Configure the PVCs under sub-interface and main interface separately.
IOS
CSCdu30920 (severity 2)
4 port ATM Over SONET OC-3c/STM-1 Multi Mode LC (CardType 544) crashes while associating a CoS Queue Group to that interface.
No workaround
CSCdu41857 (severity 4)
Environment Power supply table returns the description for the power supply as "Alarm Module" for the following:
•
•
IP
CSCdu11852 (severity 4)
Problem: Should not allow the creation of IP Precedence access list with an index of 100.
CSCdu11859 (severity 3)
Problem: It should not be possible to modify the values of attributes in CAR Policy Configuration and Access List Configuration window through Edit->Copy configuration and Edit->Paste and save configuration menu options provided the selected CAR policy or Access list is in "Applied" state. Edit menu needs to be greyed out or removed from CAR Policy Status and CAR Policy Apply windows.
No workaround.
CSCuk23920 (severity 3)
Problem: Select an interface (which has a CAR policy created using Cisco IOS CLI) and select another interface and associate a CAR Policy with Access List and Apply with "Force Synchro.. " option "NO".
1.
(Instances are created under the Interface)
2.
3.
No workaround.
CSCdt06716 (severity 3)
Problem: Able to delete chassis with applied CAR policies. Causes C12kM to lose synchronization with device.
Workaround: Ensure that remove QoS configuration from device before deleting chassis objects. If problem occurs, manually re-synchronize.
OIR
CSCdu07666 (severity 3)
Problem: Force fail over through CLI results both the primary route processor and secondary route processor interfaces move to normal state.
Cisco IOS
CSCds57081 (severity 3)
Problem: The IOS Image installed in the POS line card of type 530 POS-qoc3-mm is crashed on associating a CosQueueGroup to its interface.This problem occurs with the device running with the Cisco IOS versions 12.(0)13S and 12.(0)12S.
CSCdt50500 (severity 2)
Problem: COSQ group is getting applied to all the interface of ATM module though it has been applied to the first interface.
No workaround.
CSCat21006 (severity 2)
Problem: For ATM-OC3-4 Port Cards, Interface objects are not found and deployed after a Card insertion, Cisco IOS DDTS CSCdr77428.
Workaround: The only way to detect the change is to reboot the Cisco 12000 series internet router.
DS3
CSCdu39489 (severity 3)
Problem: In the DS3 card, in the Performance window, E3 Performance tab the interval E3 Status attributes do not populate, all the values are populated through the RFC1407 mib, saw the properties of the particular attribute it says "The counter associated with the number of Severely Errored Framing Seconds, encountered by a DS3/E3 interface in one of the previous 96, individual 15 minute, intervals.", so it gives 96 different values for a single interface,so that particular attributes are not populating.
No workaround.
ATM
CSCdu39492 (severity 4)
Problem: In the ATM Interface Status window, the attribute physical port is populating by the mib, but did not get any value for physical port through mib but it is populating the window as "oc3multimode fiber", for an oc12 single mode card for expected it would populate as oc12 singlemode fiber but it populates as oc12 Multimode fiber.
No workaround.
Ethernet/HSRP
CSCdu39623 (severity 3)
On Ethernet configuration window, the "IP Address" attribute does not set through apply profile action.
Workaround: After applying a profile to an interface object, re-type the value and save the value.
CSCdu39620 (severity 3)
On Ethernet Interface Configuration window, the "Group number.", "Standby Authentication" and "Authentication String" attributes does not display value when created the value for all attributes through CLI on device.
Workaround: Create value for all attributes through the window.
CSCdu39654 (severity 5)
Bulk operation support can be removed from Ethernet Configuration window. The HSRP Configuration window is not working correctly due to Bulk operation support because IP Address and Group Number has to be unique.
CSCuk23525
Workaround: Do not select multiple interfaces while applying the HSRP configuration.
Problem: Any databased performance data collected against objects in a CGM 2.0.1 installation will be lost during the upgrade process to C12kM 2.1.
Workaround: Performance data can be exported to a flat file prior to the upgrade so that a record can be maintained. There is a command line utility, historyAdmin, which should be used for this.
historyAdmin exports data on the basis of History Criteria. These are specifications of which performance data should be stored in the CEMF database and are defined in a series of files in the <CEMFROOT>/config/dataload/historyCriteria directory. The historyAdmin utility expects a criteria name as an argument. The following criteria names are relevant for C12kM:
CiscoIPOverATMEndpointOverSONETwithWREDhistoryCriteria - data for ATM interface objects
CiscoIPoverDS3withWREDhistoryCriteria - data for DS3 interface objects
CiscoIPoverEthernetwithWREDhistoryCriteria - data for Ethernet interfaceobjects
CiscoIPoverPOSoverSONETwithWREDhistoryCriteria - data for POS interface objects
gsrgrpHistoryCriteria - data for GRP Line Card objects
For each of these criteria, the following command should be used:
historyAdmin export <filename> <separator> <max file size(KB)> [all |
<number_of_days>] [summary|raw] <criteria name>
Example:
historyAdmin export ethernetPerfData TAB 500 all raw CiscoIPoverEthernetwithWREDhistoryCriteria
This will produce a file with contents similar to the following:
Object:
Physical:/Site-2/GSRShelf-10.51.20.105/GSR12008-10.51.20.105/RP5/Ethernet-5-0
Object Class:CiscoIPoverEthernetwithWRED
Attribute:SNMP:OLD-CISCO-INTERFACES-MIB.locIfOutPktsSec
Summary interval:Raw
06 Jun 2001 15:54:12 Started 2
06 Jun 2001 16:09:08 Polled 0
06 Jun 2001 16:32:21 Started 0
06 Jun 2001 16:47:40 Polled 1
06 Jun 2001 17:02:21 Polled 1
06 Jun 2001 17:17:37 Polled 1
06 Jun 2001 17:32:30 Polled 0
06 Jun 2001 17:47:54 Polled 0
06 Jun 2001 18:02:39 Polled 1
06 Jun 2001 18:17:48 Polled 0
06 Jun 2001 18:32:35 Polled 0
06 Jun 2001 18:47:44 Polled 0
06 Jun 2001 19:02:38 Polled 0
06 Jun 2001 19:17:39 Polled 0
06 Jun 2001 19:32:40 Polled 0
06 Jun 2001 19:47:42 Polled 0
06 Jun 2001 20:02:48 Polled 0
06 Jun 2001 20:17:33 Polled 1
06 Jun 2001 20:32:40 Polled 0
06 Jun 2001 20:47:41 Polled 0
06 Jun 2001 21:03:05 Polled 1
06 Jun 2001 21:17:51 Polled 0
06 Jun 2001 21:32:59 Polled 0
06 Jun 2001 21:47:50 Polled 0
06 Jun 2001 22:02:49 Polled 0
06 Jun 2001 22:18:00 Polled 0
06 Jun 2001 22:33:05 Polled 0
06 Jun 2001 22:48:01 Polled 0
06 Jun 2001 23:03:07 Polled 0
06 Jun 2001 23:17:57 Polled 0
06 Jun 2001 23:33:07 Polled 0
06 Jun 2001 23:47:57 Polled 0
07 Jun 2001 00:03:01 Polled 0
07 Jun 2001 00:17:51 Polled 0
07 Jun 2001 00:32:55 Polled 0
07 Jun 2001 00:47:51 Polled 0
07 Jun 2001 01:02:58 Polled 0
07 Jun 2001 01:17:54 Polled 0
07 Jun 2001 01:32:52 Polled 0
07 Jun 2001 01:47:51 Polled 0
07 Jun 2001 02:02:52 Polled 0
07 Jun 2001 02:17:57 Polled 0
07 Jun 2001 02:32:58 Polled 0
07 Jun 2001 02:47:52 Polled 0
07 Jun 2001 03:25:06 Polled 0
07 Jun 2001 03:40:02 Polled 0
07 Jun 2001 03:55:05 Polled 0
07 Jun 2001 04:10:06 Polled 0
07 Jun 2001 04:25:01 Polled 0
07 Jun 2001 04:40:00 Polled 0
07 Jun 2001 04:55:05 Polled 0
07 Jun 2001 05:10:00 Polled 0
07 Jun 2001 05:25:00 Polled 1
07 Jun 2001 05:39:59 Polled 1
07 Jun 2001 05:55:15 Polled 0
07 Jun 2001 06:10:00 Polled 1
07 Jun 2001 06:25:00 Polled 1
07 Jun 2001 06:40:02 Polled 1
07 Jun 2001 06:55:17 Polled 1
07 Jun 2001 07:10:21 Polled 1
07 Jun 2001 07:25:11 Polled 0
07 Jun 2001 07:40:09 Polled 0
07 Jun 2001 07:55:14 Polled 0
07 Jun 2001 08:10:07 Polled 2
07 Jun 2001 08:25:04 Polled 0
07 Jun 2001 08:40:16 Polled 0
07 Jun 2001 08:55:09 Polled 2
07 Jun 2001 09:11:49 Polled 9
07 Jun 2001 09:18:07 Started 0
Note
CEMF
If card removal/insertion on multiple chassis is performed in quick succession, then the event viewer may not clear alarms properly.
In the bottom part of every window there is a status bar which displays full hierarchy of the object which is managed by the form, with the status of every object of the hierarchy: this message is truncated so that only first part of the hierarchy is fully readable.
CSCuk23323 (severity 3)
Problem 1: Not able to commission a real Cisco 12000 series internet router 12008 Chassis after having 50 Cisco 12016 Chassis commissioned to Normal and 100% Performance Polling Enabled.The Module objects are going to Discovery Lost Comms/Mis-Matched state. Similar problems when a line card is Inserted to the Managed Chassis, the subsequent Sub-Rack discovery causes objects going to Mis-matched /DiscLostComms.
Workaround: De-Commission and Commission those objects in Discovery LostComms. Decommission and delete those objects in Mis-Matched state.Manually deploy those objects and commission the same.
Problem 2: Deploying 75 Cisco 12016 Chassis (No Performance Polling). Commission 75 Cisco 12016 Chassis to Normal. Commissioning another set of 5 Cisco 12016 Chassis causes line cards moving to DiscoveryLostComms and Mis-Matched states. Also for some chassis objects the POS and ATM line cards have got the Interfaces discovered as Generic-Interfaces. Chassis Commissioning is successful if you commission one or two Chassis at a time after having 75 Cisco 12016 Chassis in Normal State.
No workaround.
CSCdu38346 (severity 2)
Problem: TrapAlarmMapper dumped core-During deletion of chassis. It is inconsistent.
No workaround.
CSCdt52698 (severity 3)
The Map Viewer application hangs when deleting a module or modules or a Chassis object from Map viewer application. This problem is inconsistent.
Workaround: Close and re-open the Map Viewer application.
CSCdu29988 (severity 3)
Problem: MAC address values such as 222.2233.4455 are sometimes converted to garbage like '"""3.DU'.This happens when: MAC addresses are represented internally as a six bytes string. The garbage values only appear if all six bytes of the MAC address are 'displayable'. In this case cemf sometimes becomes confused and treats the MAC address as a displayable string.
Cisco EMF regards the following (hexadecimal) byte values as displayable: 09, 0A, 0B, 0C, 0D. Any value in the range 20-7E. If any one of your six MAC address bytes is outside this set then this problem does not apply.
Workaround: Avoid creating CAR policy with MAC access list.
Documentation Updates
Omissions
This section describes information that was omitted from the Cisco 12000 Manager User Guide (release 2.1).
ATM Interface Configuration
Reconfiguring the atm auto-configuration and atm address-registration fields require the interface to be re-started before the changes become effective.
To restart the interface proceed as follows:
Step 1
A popup menu will apear.
Step 2
The Generic Interface Configuration Window will be displayed.
Step 3
Step 4
Step 5
Step 6
The interface will have been re-started.
Caution
Configuration of atm uni-version 3.0 or atm uni-version 3.1 can only be performed when the interface is shut down.
Related Documentation
The documentation supporting this release is:
•
•
•
•
•
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as 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 the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
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:
Attn Document Resource Connection
Cisco Systems, Inc.
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. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0104R)
•
All rights reserved.
Guest
