Problem Description

In the 1:1 HA pair and Standalone SBC SWe, the default (1.0) processor indices are populated in the /opt/sonus/conf/swe/capacityEstimates/.index.txt file after the operating system installation, due to the NUMA related issues in certain cases. These indices (1.0) do not reflect the actual capacity of the processor results incorrect session estimates.

Problem Identification

Run the following command to view the current processor indices: 

> show table system sweProcessorCapacity

Output Example

admin@vsbc1-10.0.1.15> show table system sweProcessorCapacity
cryptoIndex      117;
passthroughIndex 110;
signalingIndex   127;
transcodeIndex   121;
[ok][2021-06-04 09:39:51]
admin@vsbc1-10.0.1.15>

If the user encounters the issue, the following output displays: 

admin@vsbc1-10.0.1.15> show table system sweProcessorCapacity
cryptoIndex      100;
passthroughIndex 100;
signalingIndex   100;
transcodeIndex   100;
[ok][2021-06-04 09:39:51]
admin@vsbc1-10.0.1.15>

100 is displayed for all index entries.

Recovery Procedure for 1:1 HA SBC SWe

Perform the following recovery mechanism to recover from the default indices in the 1:1 SWe HA pair: 

  1. This procedure impacts the SBC service.
  2. Terminologies used:
    1. Primary VM: Installed Active SBC SWe VM.
    2. Secondary VM: Installed Standby SBC SWe VM.

Run the following command to delete the files from primary and secondary instances as a root user from the Linux shell: 

rm -f /opt/sonus/conf/swe/capacityEstimates/.index.txt
rm -f /opt/sonus/conf/swe/capacityEstimates/tmp/.index.txt
rm -f /opt/sonus/conf/swe/capacityEstimates/.indexMarker

Perform the following steps on the HA pair:

  1. Run sbxstop on the Primary and Secondary VMs.
  2. Reboot the Primary VM. Wait for the application to turn on in the active role.
  3. Reboot the Secondary VM once the application on the Primary VM turns on as active.
  4. Observe the Secondary VM turns on with its indices and estimates. 
  5. Observe the application on Secondary VM turns on as Standby.
  6. Reboot the Secondary VM instance again, after the application synchronization between the Primary and Secondary VMs.
  7. Observe the application on Primary and Secondary VMs synchronize with the latest calculated indices and with the corresponding matching estimates.