This section describes some common issues found with SBC SWe in Public Cloud environments, and the action needed to verify or troubleshoot the issues.


The SBC Application did not come up on both the active and standby nodes after reverting to a pre-11.0 release.

Use the following procedure to recover the SBC SWe HA on public cloud after reverting to a pre-11.0 release if the SBC application does not come up on both the active and standby nodes.

Note

This procedure is only applicable if the system is upgraded from a pre-11.0 release to this release using the following method:

  • Bring up the SBC HA application with a pre-11.0 release on public cloud (For example, AWS).
  • Upgrade both the active and standby SBC to this release using the recommended upgrade method.


StepAction
1
  1. Revert the SBC application to pre-11.0 release.

  2. Once complete, check to see if application is coming up fine on both active and standby nodes.

  3. If the SBC application is stuck and unable to receive the assigned role, stop the SBC application on both active and standby nodes using the
    command sbxstop.
2

If present, remove the following file/directories from both the active and standby SBC:

  • rm -rf /home/cnxipmadmin/peerDynamicHANewComps
  • rm -rf /opt/sonus/sbx/openclovis/var
3
  1. Start the SBC application on both the active and standby nodes using the ‘sbxstart’ command.

  2. Check to make sure that the application starts up on both nodes. 

    Note

    If you are using the RAF for upgrade/revert, perform the steps 1.3 to 3.1 within 30 minutes after running the revert operation. This ensures that the RAF can detect the correct state of VNF and mark the operation as complete.


The sbcDiagnostic tool specifies "cloud-init.service failed with the result 'exit-code'", and my SBC application is not coming up

Ribbon's cloudinit modules use information retrieved from the Public Cloud provider. Occasionally, the provider fails to return, or only partially returns, the information. When this occurs, the modules cannot obtain all of the information needed by the SBC.

StepAction
1Reboot the instance through the cloud provider.
2

Follow other Debugging information if the problem persists:

3

Contact Ribbon Global Support if the issue persists.