This document provides installation instructions for Unified CCE 12.6(2) ES37. It also contains a list of Unified CCE issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent Unified CCE behavior.
This document contains these sections:
In the Product
Alert Tool, you can set up profiles to receive email notification of new
Field Notices, Product Alerts, or End of Sale information for your selected
products.
The Product
Alert Tool is available at https://www.cisco.com/cisco/support/notifications.html.
This section lists the Unified CCE components on which you can and cannot install this engineering special.
You can install Unified CCE 12.6(2) ES37 on these Unified CCE components:
All
ICM servers that has websetup and admin client machines.
Do not install this engineering special on any components other than the following:
All
ICM servers that has websetup and admin client machines.
The installation or uninstallation of this patch requires a planned maintenance window with some expected downtime of a few seconds / minutes. No
Note: Remove patches in the reverse order of their installation. For example, if you installed patches 3, then 5, then 10 for a product, you must uninstall patches 10, 5, and 3, in that order, to remove the patches from that product.
This section provides a list of significant Unified CCE defects still open for this engineering special. It contains these subsections:
Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats which are still open in Unified CCE 12.6(2) ES37.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCwk05112 |
3 |
appd |
Agent
extention service not coming up when Fips is enabled |
Caveats are ordered by severity then defect number.
Defect Number: CSCwk05112
Component: appd
Severity: 3
Headline: Agent extention service not coming up when FIPS is enabled
Symptom:
When FIPS is enabled, Agent extension service is not coming up
Conditions: FIPS enabled
Workaround: Need to edit <InstallDrive> :\Cisco\AppDynamics\DotNetAgent\AppDynamics
ExtensionManager\ExtensionService.exe.config to add appdSettings section
which looks as below
<?xml
version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add
key="Encryption" value="basic"/>
</appSettings>
<startup><supportedRuntime version="v4.0"
sku=".NETFramework,Version=v4.5"/></startup></configuration>
And
then start the service AppDynamics.Agent.Extension_Service
This section provides a list of significant Unified CCE defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual Unified CCE defects using the Cisco Bug Search tool, located at: https://bst.cloudapps.cisco.com/bugsearch/search?null.
This section lists caveats specifically resolved by Unified CCE 12.6(2) ES37.
Caveats in this section are ordered by UNIFIED CCE component, severity, and then identifier.
|
Identifier |
Severity |
Component |
Headline |
|
CSCwf16719 |
2 |
web.config.api |
Tomcat
memory usage keeps growing during pcb bulk import |
|
CSCwe94791 |
2 |
web.config.api |
Contacts
are not getting uploaded for API Campaign due to Tomcat Java OutOfMemory |
|
CSCwi62030 |
3 |
web.config.api |
Tomcat
gets stopped with process memory exceeded |
|
CSCwh81453 |
3 |
security |
Assessment
of Apache Struts version 2.5.31 to vulnerability CVE-2023-41835 |
|
CSCwi35912 |
3 |
install |
Performance
impact in AW as tomcat param JvmMs and JvmMx not updated to 512 MB after
fresh install |
Caveats are ordered by severity then defect number.
|
ES# |
Identifier |
Severity |
Component |
Headline |
|
ES7 |
CSCwf65121 |
|
appd |
Vulnerabilities for AppD Client JDK on UCCE/PCCE |
|
CSCwf76535 |
|
security |
Critical CVE in component tomcat. Upgrade to latest version. |
|
|
CSCwf84197 |
|
security |
Vulnerabilities in openjdk 1.8.0 |
|
|
ES9 |
CSCwf76534 |
2 |
security |
Critical CVE in component struts. Upgrade to latest version. |
|
CSCwe46792 |
2 |
security |
Vulnerabilities in commons-beanutils |
|
|
CSCwf62523 |
3 |
dbconfig |
Unable to select a Sip Server Group for a Routing Pattern |
|
|
CSCwf09605 |
3 |
web.config.api |
PCCE 2K Inventory not loading "INTERNAL_SERVER_ERROR |
|
|
CSCwe46797 |
3 |
security |
Vulnerabilities in jackson-mapper-asl |
|
|
CSCwf17667 |
4 |
security |
Evaluation of CVE-2023-24998 against Cisco Contact Center Enterprise |
|
|
CSCwb58429 |
6 |
dbconfig |
PCCE upgrade from 11.X to 12.6 fails if CVP configuration steps missed in PCCE SPOG 12.0 |
|
|
CSCwf27937 |
7 |
security |
Vulnerabilities in snake-yaml 1.33 CVE-2022-1471 |
|
|
ES16 |
CSCwf21364 |
2 |
web.config.api |
JVM Out Of Memory due to caching too many copies of same X509 certificates |
|
ES19 |
CSCwi11163 |
2 |
dbconfig |
PCCE 12.6.2 Inventory file failing on updating PG |
|
ES27 |
CSCwi76535 |
6 |
web.config.api |
Dynamic AXL schema support for both the CUCM version vis-a-vis 11.5 and
12.5 |
|
ES29 |
CSCwd97991 |
3 |
smart-license |
SmartLicense Registration and Authorization attempts fail with error
"Failed to verify signature" |
|
CSCwe61674 |
4 |
web.config.api |
PersonalCallBack API Search returns internalServerError if CallStatus =
"I" |
Defect Number: CSCwf16719
Component: web.config.api
Severity: 2
Headline: Tomcat memory usage keeps growing during pcb bulk import Tomcat memory usage keeps growing during personal call back bulk import.
Symptom:
Tomcat memory usage keeps growing during personal call back bulk import.
Conditions: 1. Run 1000 requests of pcb bulk import (number of records 1 to
3) 2. Monitor memory and CPU usage, if possible monitor response time average
value, median etc (you need to run test from Jmeter for that).
Workaround: NA
Further Problem Description: Tomcat memory usage keeps growing during
personal call back bulk import.
Defect Number: CSCwe94791
Component: web.config.api
Severity: 2
Headline: Contacts are not getting uploaded for API Campaign due to Tomcat Java OutOfMemory
Symptom: Contacts
are not getting uploaded in bulk for API Campaign. System gets into out of
memory and halts
Conditions: CCE 12.5/12.6 PCB Bulk Import API, normal Import works CCBU
Tomcat ran into Java OutOfMemory on the Logger server
Workaround: Restart the Logger tomcat services.
Further Problem Description: This issue is regression of CSCvz50705.
Customers are trying to upload the contacts Via the API Import process,Prior to
the JavaOutOf Memory could see the delay in updating the database records.
CCBU_ajp-nio-127.0.0.1-8009-exec-5-6-REST_API_INFO: Time to take to write into
the database for 6 records is 484
CCBU_ajp-nio-127.0.0.1-8009-exec-7-6-REST_API_INFO: Time to take to write into
the database for 30 records is 1141 0000009022: 10.1.47.46: Mar 09 2023
12:47:47.969 +0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-9-6-REQUEST_END:
%[PARAM_TIME_ELAPSED=2738924]: Request complete 0000025755: 10.1.47.46: Mar 09
2023 12:47:50.844 +0530:
%CCBU_ajp-nio-127.0.0.1-8009-exec-9-3-REST_API_EXCEPTION: %[exception=java.lang.OutOfMemoryError:
Java heap space][message_string=uncaught exception thrown by the api]: The REST
API has caught an exception 0000025756: 10.1.47.46: Mar 09 2023 12:47:52.750
+0530: %CCBU_ajp-nio-127.0.0.1-8009-exec-9-3-EXCEPTION_INFO: %[build_date=Sep 06,
2022 7:13 AM][build_type=rel][exception=java.lang.OutOfMemoryError: Java heap
space
Defect Number: CSCwi62030
Component: web.config.api
Severity: 3
Headline: Tomcat gets stopped with process memory exceeded
Symptom: Tomcat
gets stopped with Memory Error. The issue is random and happens once in a week.
Need to find the RCA why this memory error occurs and needs the fix 0001127057:
DC-AW-DDS-A: Dec 12 2023 00:30:10.421 +0700:
%CCBU_pool-1-thread-49-Infrastructure-318989-3-REST_API_EXCEPTION:
%[exception=null][message_string=AsyncExecutor: process memory exceeded,
shutting down]: The REST API has caught an exception 0001127059: DC-AW-DDS-A:
Dec 12 2023 00:30:10.421 +0700: %CCBU_pool-1-thread-49-Infrastructure-318989-6-REST_API_INFO:
Terminating windows process Error 12/12/2023 12:30:10 AM Service Control
Manager 7034 None The Apache Tomcat9 service terminated unexpectedly. It has
done this 4 time(s).
Conditions: P/UCCE 12.6(1) ES P/UCCE 12.6(2)
Workaround: Recovery tab of the Apache Tomcat Service to ?Restart the
Service? for First Failure, Second Failure and Subsequent failures.
Further Problem Description: None
Defect Number: CSCwh81453
Component: security
Severity: 3
Headline: Assessment of Apache Struts version 2.5.31 to vulnerability CVE-2023-41835
Symptom:
Packaged Contact Center Enterprise includes a version of Apache Struts that is
affected by the vulnerabilities identified by the following Common
Vulnerability and Exposures (CVE) IDs: CVE-2023-41835 This bug was opened to
address the potential impact on this product.
Conditions: Device with default configuration.
Workaround: Not available or not applicable.
Further Problem Description: Additional details about the vulnerabilities
listed above can be found at https://www.cve.org/.
Defect Number: CSCwi35912
Component: install
Severity: 3
Headline: Performance impact in AW as tomcat param JvmMs and JvmMx not updated to 512 MB after fresh install
Symptom:
Tomcat params JvmMs and JvmMx not getting set to 512 in case AW is configured
after fresh install. Due to this there is a performance impact in AW, slowness
would be observed in SPOG.
Conditions: Distributor is added on a Fresh system
Workaround: set the registry to 512
Further Problem Description: None
You can access current Cisco documentation on the Support pages at the following sites:
To provide comments about this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
Cisco.com is 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 site.
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. You can also resolve technical issues with online technical support and download software packages. 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.
The Cisco TAC site 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 https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.
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 site: https://mycase.cloudapps.cisco.com/create/start/
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 sites:
P1 and P2 level problems are defined as follows: