Field Notice: FN - 72478 - Cisco Unified SIP Proxy Version 10.x Might Exhibit Service and Call Failures - Workaround Provided

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision	Publish Date	Comments
1.0	31-Aug-22	Initial Release

Products Affected

Affected OS Type	Affected Software Product	Affected Release	Affected Release Number	Comments
NON-IOS	Unified SIP Proxy Installation Software	Full install OVA	10.0.0, 10.1.0, 10.2.0, 10.2.1

Defect Information

Defect ID	Headline
CSCwa39323	OVA File only allocates 4GB of RAM instead of 6 GB
CSCvx90238	CUSP needs 6 GB of memory on 10.X versions
CSCvu71438	CUSP smart license shows as disabled and calls will be rejected

Problem Description

Affected versions of the virtualized Cisco Unified SIP Proxy (vCUSP) application that have been deployed with 4 GB of memory might experience resource exhaustion, which leads to service and/or call failures.

Background

vCUSP products with Version 10.x releases are allocated with 4 GB RAM for virtual machines (VMs) by default. When used in a production environment, the application requires more memory than the default allocated memory space of 4 GB. This causes the products to fail as VMs start to exhaust the resources. A workaround is provided.

Problem Symptom

The affected products might show any of these failure symptoms:

• The licensing shows as disabled and cannot be reregistered.
• The “kernel: java invoked oom-killer” message and other out of memory log messages are observed.
• Calls are rejected.
• The configuration is missing at system restart.

In order to view the memory assigned to a vCUSP application, complete these steps:

1. View the VMware vSphere/vCenter VM summary, as shown in this example:

   

2. From the vCUSP CLI, enter the show memory command. In this example, Synchronous DRAM (SDRAM) is listed as 3,840 MB (3.84 GB), which is the memory provided to the VM by the hypervisor. An upgraded system will list SDRAM as 5,888 MB.

   Note: The amount of memory might vary slightly between hypervisor versions.

   cusp101# show memory 
   
   SDRAM (MByte)         :     3840 
   
   Total Memory (kB)     :     3849144 
   
   Active Memory (kB)    :     1616632 
   
   Inactive Memory (kB)  :     299024 
   
   Other Memory (kB)     :     130616 
   
   MemoryPool (kB)       :     1802872
   
   

Failure Logs (Syslog) - Report Killing of a Process due to Memory Exhaustion

cusp01 java[1810]: INFO AAA jaas2pam Authorization: Finishsed authTracer init

cusp01 kernel: java invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0

cusp01 kernel: java cpuset=/ mems_allowed=0

cusp01 kernel: lowmem_reserve[]: 0 0 958 958

cusp01 kernel: Node 0 Normal free:17092kB min:17244kB low:21552kB high:25864kB active_anon:870944kB inactive_anon:17476kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1048576kB managed:981224kB mlocked:0kB dirty:0kB writeback:0kB mapped:16972kB shmem:20832kB slab_reclaimable:8660kB slab_unreclaimable:19444kB kernel_stack:2784kB pagetables:4896kB unstable:0kB bounce:0kB free_pcp:768kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:15 all_unreclaimable? yes

cusp01 kernel: lowmem_reserve[]: 0 0 0 0

cusp01 kernel: [ 6315] 89 6315 22932 260 46 0 0 pickup

cusp01 kernel: Out of memory: Kill process 1805 (java) score 310 or sacrifice child

cusp01 kernel: Killed process 1805 (java) total-vm:5791724kB, anon-rss:1228308kB, file-rss:0kB, shmem-rss:0kB

cusp01 kernel: java invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0

cusp01 kernel: java cpuset=/ mems_allowed=0

cusp01 kernel: CPU: 0 PID: 2808 Comm: java Kdump: loaded Not tainted 3.10.0-957.21.3.el7.x86_64 #1
 

Smart Licensing Disabled Logs - Calls Will Be Rejected

cusp01# show license smart status application cusp

    Smart Agent is Enabled: false

    Smart Agent current state: UNCONFIGURED


cusp01# show license smart summary

    Smart Agent is Enabled: false

    Current State of the Agent: UNCONFIGURED

    Evaluation Mode: NO 

    Registration Successful: YES 

    Authorization Successful: NO 

    
    CPS Count Requested: 0

    Configured destination address: https://tools.cisco.com/its/service/oddce/services/DDCEService

    HTTP Proxy Address: Not Set::

    Transport Mode: TransportCallHome

    License UDI: UC_CUSP:xyZJVKsXN3f

    Product Serial Number: xyZJVKsXN3f

    Product ID: UC_CUSP

    Product License Version: 10.0

    Licensing State: Not Available

    Registration expiry period: XXXX

    Latest Failure Reason String Notification: No recent Failure messages

    Auth period: XXXX

Workaround/Solution

Cisco has increased the minimum virtual memory requirement for all vCUSP Version 10.x releases to 6 GB in order to mitigate the possibility of resource exhaustion. 

For all new and existing setups: 

• During the new installation of vCUSP Version 10.x instances, Cisco advises to ensure that the VMs are configured with 6 GB of memory before they are powered on. vCUSP Versions 10.2.2 (cusp-k9.vmw.10.2.2.ova) and later are configured for 6 GB by default.
• Cisco strongly recommends to upgrade the VM for any currently deployed vCUSP Version 10.x release to 6 GB at the earliest possible opportunity.

An upgraded system will list SDRAM as 5,888 MB.

Note: The amount of memory might vary slightly between hypervisor versions.

See the vCUSP Installation Guide for Versions 10.0, 10.1, and 10.2 and the release notes for the software releases 10.0, 10.1 and 10.2.

In order to upgrade the memory size allocated, complete these steps:

1. During a maintenance window, access the vCUSP CLI.
2. Enter the write command to ensure the configuration is saved.
3. Enter the offline command to take the application offline.
4. It is recommended that a system backup is saved at this time. See the detailed steps in the CLI Configuration Guide for Cisco Unified SIP Proxy Release 10.2.
5. Power off the VM with vCenter/vSphere.
6. Choose Actions > Edit Settings for the VM.
7. Adjust the memory configuration from 4 GB to 6 GB and click ok.
8. Power on the VM with vCenter/vSphere to bring the application back in to service.
9. Access the vCUSP CLI and verify the upgraded memory with the show memory command.
10. Verify that the application licenses are authorized using the show license smart summary command.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email or telephone

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.