This document provides installation instructions for ICM11.0(2) ES29. It also contains a list of ICM issues resolved by this engineering special. Please review all sections in this document pertaining to installation before installing the product. Failure to install this engineering special as described may result in inconsistent ICM behavior.
This document contains these sections:
The Product
Alert Tool offers you the ability to set up one or more profiles that will
enable you to receive email notification of new Field Notices, Product Alerts
or End of Sale information for the products that you have selected.
The Product
Alert Tool is available at http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice
ICM 11.0(2)
ICM11.0(2)
ES29 is compatible with and should be installed on these ICM components:
Do not
install this engineering special on any of the following components:
Installation of this patch requires the all ICM services to
be shut down during the entire period of installation. It is always recommended
to install this ES during a scheduled downtime.
· Using the
ICM Service Control, stop all the ICM services running on the system.
· Launch the
Installer provided for ES 5 and following the instructions on the screen.
· Using the
ICM Service Control, start all ICM services again.
To uninstall this patch, go to Control Panel.
Select "Add or Remove Programs". Find the installed patch in the list
and select "Remove".
Note: Patches have to be removed in the reverse order in which they were installed. For example, if you had installed patches 3, then 5, then 10 for a product, you will need to uninstall patches 10, 5 and 3 in that order to remove all patches for that product.
This section provides a list of significant ICM defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual ICM defects using the Cisco Bug Toolkit located at: http://www.cisco.com/support/bugtools/Bug_root.html
This section lists caveats specifically resolved by ICM11.0(2) ES29.
Caveats in this section are ordered by ICM component, severity, and then
identifier.
Be sure to include ALL of the resolved caveats for the files you're delivering,
i.e. all of the caveats from the release notes of the previous ES which
included these files.
Identifier |
Severity |
Component |
Headline |
CSCva91994 |
2 |
db.HDS |
Adding
of 2 new regeions from 8.5 to 11 is not handling customized ones |
Caveats are ordered by severity then defect number.
Be sure to include ALL of the resolved caveats for the files you're delivering,
i.e. all of the caveats from the release notes of the previous ES which
included these files.
Defect Number: CSCva91994
Component: db.HDS
Severity: 2
Headline: Adding of 2 new regeions from 8.5 to 11 is not handling customized ones
Symptom:
They ran the query to adjust high number (custom) regions by 2 in the
Region_Member table. I don't think there's a universal issue where anything is
off by a fixed number. The issue we're seeing now is that when the region IDs
were modified as described by the BU, they were only updated in the Region
table, not in the Region_Member table. We are seeing time of day routing issues
because of this. Looks like the discrepancy we are seeing is also not an issue.
All these are due to change in region IDs in 11.0. 64 in 11.0 is same as 66 in
8.5.4. It points to the same regions. All these issues have come due to
incorrect handling of customized regions.
Conditions: The fix that they have provided did not resolve the issue. During
Empirix testing this morning, we discovered that the system treated all their
Massachusetts 857 NPA calls as if they were coming from the HST (Hawaiian
Standard Time) region. See below. select * from Region where EnterpriseName =
'HST' select * from Region_Member join Region on Region_Member.RegionID =
Region.RegionID where Region_Member.ParentRegionID = 32006 RegionID
EnterpriseName Description RegionType ChangeStamp DateTimeStamp 32006 HST
Hawaiian Standard Time 3 3 NULL RegionID ParentRegionID RegionID EnterpriseName
Description RegionType ChangeStamp DateTimeStamp 35 32006 35 Maryland NULL 1 5
NULL 38 32006 38 West_Virginia NULL 1 3 NULL 46 32006 46 Rhode_Island NULL 1 5
NULL 50 32006 50 Massachusetts NULL 1 5 NULL 56 32006 56 Arkansas NULL 1 3 NULL
58 32006 58 Oregon NULL 1 3 NULL 32016 32006 32016 Arizona_MST Arizona_MST 3 2
NULL 32018 32006 32018 Idaho_MST Idaho_MST 3 2 NULL 32020 32006 32020
Kansas_MST Kansas_MST 3 2 NULL 32023 32006 32023 Nebraska_MST Nebraska_MST 3 2
NULL 32024 32006 32024 North_Dakota_MST North_Dakota_MST 3 2 NULL 32025 32006
32025 Oklahoma_MST Oklahoma_MST 3 2 NULL 32026 32006 32026 Oregon_MST
Oregon_MST 3 2 NULL 32027 32006 32027 South_Dakota_MST South_Dakota_MST 3 2
NULL 32029 32006 32029 Texas_MST Texas_MST 3 2 NULL The RPUT tool after we ran
the EDMT/ICM Upgrade. This is query was run update Region_Member set
ParentRegionID=ParentRegionID-2 where ParentRegionID>86 I applied this
change in Lab1, and while it made some improvements, the issue is still not
fixed. I think not only did the parent regions in that table increase by 2, but
also a lot of the regular region IDs changed. For example, RegionID 1-8 are the
same in 8.5 and 11 but then for ID 9, it shows as California in 8.5 and Wyoming
in 11. Then as a result, 10-18 are all offset by one before you get to
Mississippi at 19. In other words, the SQL query fixed the issue with all the
custom regions being offset by 2. But it did not fix the region to parent
region relationship of several other regions. We have 19 out of 85 regions that
don't match. All these issues have come due to incorrect handling of customized
regions.
Workaround: none at moment
Further Problem Description:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
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.
Cisco documentation is available in the following ways:
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-9883
We appreciate your comments.
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 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: http://www.cisco.com
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.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac
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
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: