Use the following command to change management IP, gateway, and network mask details on the primary EMS server.sbceconfigurator.py change-ip-gw-mask <MGMT_IP> <GW_IP> <NW_MASK>
The script does the following:
-
Checks if the database is functional.
-
If the database is functional, proceeds with stopping application processes.
-
Checks if all the Avaya SBC servers connected to EMS are reachable. If any Avaya SBC server is unreachable, exits or proceeds with changing the EMS IP address on the reachable Avaya SBC servers. Later, when the devices are reachable from EMS, users can regenerate or change the EMS IP addresses on the devices.
-
Prints out the log messages, which shows the current status on screen.
-
The EMS server then reboots. The user needs to ssh using the new EMS IP address.
-
EMS generates certificates automatically and sends it to all Avaya SBCs.
Change in management IP requires a change in the NTP address configuration on all Avaya SBC servers connected to EMS.
Note:
All Avaya SBC servers must have the changed EMS IP address.
Note:
NTP or Chrony configuration Starting with release 10.1.2, SBC has been replaced by Chrony. Although the documentation may refer to "NTP," the Chrony service is used for time synchronization. When configuring NTP/Chrony, use a reliable NTP source, and ensure time is synchronized consistently across all EMS-managed nodes. If EMS is configured to use a specific NTP server, configure the same appropriate NTP server on all SBCs, especially in HA pairs. Do not use the EMS server IP as the NTP server.
