Moving an HA SBC from one EMS to another EMS

Last Updated : Jun 12, 2023 |
Prolog information
Metadata
Keywords:
Caution:
Configuration changes are service affecting. Do these procedures during a planned maintenance window when there is no traffic on the system. Inform all users that calls cannot be placed during this time frame, and that any active calls will be dropped.
Before you begin
Collect the following information:
  • IPv4 IP address of the EMS server
  • (Optional) Network Passphrase
    This was the passphrase used when the system was first deployed. For more information, see Deploying Avaya Session Border Controller on a Hardware Platform, Deploying Avaya Session Border Controller on a Virtualized Environment Platform, or Deploying Avaya Session Border Controller on an Avaya Aura® Appliance Virtualization Platform.
  • (Optional) - IPv4 IP address of the system NTP server
  • (Optional) - IPv6 address of the EMS server
Confirm that the EMS IP address can be pinged from the SBC network.
Take a backup of your system.
  1. Log in to the CLI with administrator credentials.
  2. Enter the following command:
    ADDITIONAL INFORMATION:
    sbceconfigurator.py re-configure <EMS_IP> [<Network_Passphrase> <NTP_IP> <V6_EMS_IP>]
    Where:
    • <EMS_IP> is the IPv4 IP address of the EMS server
    • (Optional) <Network_Passphrase> is optional, the network passphrase
    • (Optional) <NTP_IP> is optional, the IPv4 IP address of the deployment NTP server
    • (Optional) <V6_EMS_IP> is optional, the IPv6 IP address of the EMS server
    STEP RESULT:
    If the conversion is successful, you will see a message similar to the following example and the system reboots:
    Rebooting the system for changes to take effect
    SBCE Re-configure Successful. Check the IPCS CM log for more information..
    If the system does not reboot and you see error messages on the screen, contact Avaya support.
    Important:
    If the EMS is unreachable, or if the EMS version does not match the SBC version, the command stops and no changes are made.
  3. After the system reboots and processes successfully restart on current SBC , repeat these steps on the other SBC in the HA pair.
    ADDITIONAL INFORMATION:
    Note:
    After the second SBC reboots and processes restart, if the HA pair are not shown as Primary / Secondary under Device ManagementDevices, restart the processes on both servers using the following command:
    /etc/init.d/ipcs-init restart
Next steps
For EMS to manage the license on the new SBC pair, navigate to Device ManagementLicensing and update the license.