Change the IP Address for an SL1 Appliance While Retaining the License

The IP address for an appliance is configured at installation. To change the IP address for an appliance after installation and preserve your SL1 license, use the procedures in this section.

If you are running SL1 on a cloud-based service like AWS or Azure, the following change procedures do not apply. The IP settings are provided automatically by DHCP, and configuration changes must be made in the DHCP provider’s settings.

Moving an SL1 appliance to a new network requires pre-planning. If your SL1 configuration includes one or more Administration Portals, PhoneHome Collectors, or is configured for High Availability or Disaster Recovery, you must perform additional steps after changing IP addresses. The steps in this section allow you to change the IP address for an SL1 appliance with minimal downtime.

This procedure requires downtime, so plan to perform this procedure during a maintenance window.

Ensure console access to the appliance you are migrating in case of typographical or other errors that might prevent network access when changing IP addresses.

Use the following menu options to navigate the SL1 user interface:

To view a pop-out list of menu options, click the menu icon ().
To view a page containing all of the menu options, click the Advanced menu icon ().

Changing the IP Address on an All-In-One Appliance

To change the primary IP address of an All-In-One Appliance :

Step 1. Stop the EM7 Service

Before changing the IP address, you must stop the EM7 service. To stop the EM7 service:

Either go to the console of the SL1 appliance or use SSH to access the server.
Login as user em7admin with the appropriate password.
Type the following at the command line:

sudo systemctl stop em7

Step 2. Change the IP Address in the silo.conf File

You must change the ipaddress value in the silo.conf configuration file.

Either go to the console of the SL1 appliance or use SSH to access the server.
Type the following at the command line:

sudo visilo

Change the following line in the [LOCAL] section of the file to specify the new IP address:

ipaddress = new_IP_address

Save and quit the file (:wq).

Step 3. Change the IP Address in the /etc/hosts File

If the /etc/hosts file includes an entry for the appliance, update the entry with the new IP address.

Either go to the console of the SL1 appliance or use SSH to access the server.
Type the following at the command line:

sudo vi /etc/hosts
If you see an IP address for the All-In-One Appliance, change the IP address to the new IP address.

Updating the /etc/hosts/ file automatically restarts the dnsmasq service to ensure the service can read the updated file.

Step 4. Change the IP Address in the Network Interface Configuration File

Be sure to set the IPADDR, PREFIX, GATEWAY and DNS# variables to the appropriate values for the new network. The PREFIX is the subnet mask in CIDR notation.

To change the IP address, Netmask, Gateway address, and DNS Server for an appliance in the ifconfig file:

Either go to the console of the SL1 appliance or use SSH to access the server.
Login as user em7admin with the appropriate password.
Type the following at the command line:

sudo ifconfig

Your output will look like this:

inet6 fe80::250:56ff:fe84:455f  prefixlen 64  scopeid 0x20<link>
ether 00:50:56:84:45:5f  txqueuelen 1000  (Ethernet)
RX packets 1774927  bytes 161985469 (154.4 MiB)
RX errors 0  dropped 861  overruns 0  frame 0
TX packets 1586042  bytes 158898786 (151.5 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10<host>
loop  txqueuelen 0  (Local Loopback)
RX packets 13406577  bytes 4201274223 (3.9 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13406577  bytes 4201274223 (3.9 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Examine the output, find the interface that uses the old IP address, and note its name.

Use the vi editor to edit the settings for the interface. To do this, enter the following at the command line:

sudo vi /etc/sysconfig/network-scripts/ifcfg-interface name you noted in step #5

For example, from our output, we could enter:

sudo vi /etc/sysconfig/network-scripts/ifcfg-ens32

The ifcfg file will look like this:

TYPE=Ethernet
BOOTPROTO=none
DNS1=10.64.20.33
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=ens32
UUID=d471435d-9adf-47c9-b3f3-32f61dccbad8
DEVICE=ens32
ONBOOT=yes
IPADDR=10.64.68.20
PREFIX=24
GATEWAY=10.64.68.1
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

You can edit one or more of the following settings:

DNS1=IP address of the DNS server that will be used by the SL1 appliance.
IPADDR=New IP address of the SL1 appliance.
PREFIX=netmask for the SL1 appliance.
GATEWAY=IP address of the network gateway that will be used by the SL1 appliance.

Save your changes and exit the file (:wq)
At the command line, enter the following:

service network restart

Step 5. Update the IP Address in the MySQL Database

In this step, you must set the new IP address in the master.system_settings_licenses table so that when SL1 is restarted, the new IP address is recognized as licensed.

Either go to the console of the SL1 appliance or use SSH to access the server.
Login as user em7admin with the appropriate password.
Enter the following at the command line:

silo_mysql

At the mysql prompt, enter the following query:

UPDATE master.system_settings_licenses SET ip="[new IP address]" WHERE ip="[old IP address]" LIMIT 1;

For example:

[em7admin@hostname ~]$ silo_mysql
 
MariaDB [(none)]> UPDATE master.system_settings_licenses SET ip="192.168.10.22" WHERE ip="10.1.1.240";
Query OK, 1 row affected (0.01 sec)
Rows matched: 1 Changed: 1 Warnings: 0
 
MariaDB[(none)]>

Type "exit" to exit the MySQL session.

Step 6. Reboot the Appliance

Reboot the appliance to apply all of the changes you made.

The system will boot up and will start the interface with the new IP address. SL1 will start up and will learn from the database that the new IP address matches its configuration file and the value in the database table. Therefore, SL1 will keep the current license for the appliance.

Step 7. Confirm the Change in SL1

After changing the IP address for your SL1 appliance, go to the Appliance Manager page (System > Settings > Appliances) and confirm that the correct IP address for that appliance appears in the IP Address column. If it does not, you must update it.

Changing the IP Address on a Database Server

Changing the primary IP address of a Database Server requires additional steps if

the Database Server resides in a High Availability configuration or a Disaster Recovery configuration
the Database Server might connect to Data Collectors configured for PhoneHome

In addition, when you change the primary IP address of a Database Server, you must update the configurations for any Data Collectors, Message Collectors and Administration Portals that communicate with that Database Server.

For Clustered Database Appliances (using HA, DR, or HA+DR), ScienceLogic recommends that you place the cluster into maintenance mode. Also, ScienceLogic recommends that you wait to wait to change the virtual IP address until all of the Database Servers have been moved to its new location, if applicable.

To change the IP address of a Database Server:

Step 1. Stop the EM7 Service

Before changing the IP address, you must stop the EM7 service. To stop the EM7 service:

Either go to the console of the Database Server or use SSH to access the server.
Login as user em7admin with the appropriate password.
Enter the following at the command line:

sudo systemctl stop em7

Step 2. Change the IP Address in the silo.conf File

You must change the ipaddress value in the silo.conf configuration file. To do so:

Either go to the console of the SL1 appliance or use SSH to access the server.
Enter the following at the command line:

sudo visilo

Change the following line in the [LOCAL] section of the file to specify the new IP address:

ipaddress = new_IP_address
Save and quit the file (:wq).

Step 3. Change the IP Address in the /etc/hosts File

If the /etc/hosts file contains an entry for the appliance, update the entry with the new IP address.

Either go to the console of the SL1 appliance or use SSH to access the server.
Enter the following at the command line:

sudo vi /etc/hosts
If you see an IP address for the Database Server, change the IP address to the new IP address.

Step 4. Change the IP Address in the Network Interface Configuration File

Be sure to set the IPADDR, PREFIX, GATEWAY and DNS# variables to the appropriate values for the new network. The PREFIX is the subnet mask in CIDR notation.

To change the IP address, Netmask, Gateway address, and DNS Server for an appliance in the ifconfig file:

Either go to the console of the Database Server or use SSH to access the server.
Login as user em7admin with the appropriate password.
Enter the following at the command line:

sudo ifconfig

Your output will look like this:

ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500inet 10.64.68.20  netmask 255.255.255.0  broadcast 10.64.68.255
inet6 fe80::250:56ff:fe84:455f  prefixlen 64  scopeid 0x20<link>
ether 00:50:56:84:45:5f  txqueuelen 1000  (Ethernet)
RX packets 1774927  bytes 161985469 (154.4 MiB)
RX errors 0  dropped 861  overruns 0  frame 0
TX packets 1586042  bytes 158898786 (151.5 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10<host>
loop  txqueuelen 0  (Local Loopback)
RX packets 13406577  bytes 4201274223 (3.9 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 13406577  bytes 4201274223 (3.9 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Examine the output, find the interface that uses the old IP address, and note its name.
Use the vi editor to edit the settings for the interface. To do this, enter the following at the command line:

sudo vi /etc/sysconfig/network-scripts/ifcfg-interface name you noted in step #5

For example, from our output, we could enter:

sudo vi /etc/sysconfig/network-scripts/ifcfg-ens32

The ifcfg file will look like this:

TYPE=Ethernet
BOOTPROTO=none
DNS1=10.64.20.33
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=ens32
UUID=d471435d-9adf-47c9-b3f3-32f61dccbad8
DEVICE=ens32
ONBOOT=yes
IPADDR=10.64.68.20
PREFIX=24
GATEWAY=10.64.68.1
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

You can edit one or more of the following settings:

DNS1=IP address of the DNS server that will be used by the Database Server.
IPADDR=New IP address of the Database Server.
PREFIX=netmask for the Database Server.
GATEWAY=IP address of the network gateway that will be used by the Database Server.

Save your changes and exit the file (:wq)
At the command line, enter the following:

sudo service network restart

Step 5. Update the IP Address in the MySQL Database

In this step, you must set the new IP address in the master.system_settings_licenses table so that when the Database Server is restarted, SL1 recognizes the new IP address as licensed.

Either go to the console of the SL1 appliance or use SSH to access the server.
Login as user em7admin with the appropriate password.
Enter the following at the command line:

silo_mysql

At the mysql prompt, enter the following query:

 UPDATE master.system_settings_licenses SET ip="[new IP address]" WHERE ip="[old IP address] LIMIT 1"

For example:

[em7admin@hostname ~]$ silo_mysql
 
MariaDB [(none)]> UPDATE master.system_settings_licenses SET ip="192.168.10.22" WHERE ip="10.1.1.240";
Query OK, 1 row affected (0.01 sec)
Rows matched: 1 Changed: 1 Warnings: 0
 
MariaDB[(none)]>

Enter "exit" to exit the MySQL session.

Step 5a: For Database Servers Configured with PhoneHome

If your Database Server is configured with PhoneHome, perform the following additional steps to change the IP address of the :Database Server.

If you add additional Database Servers with new IP addressees, wait for the Database Servers to migrate, and then the PhoneHome collectors will attempt to connect using the new Database Server IP addresses. After the databases reconnect, you can remove database entries with old IP addresses from the PhoneHome configuration.

Either go to the console of the Database Server or use SSH to access the server.
Enter the following at the command line:

phonehome status

If you are planning to change the IP address of multiple Database Servers, you will want to update all of the relevant IP addresses in PhoneHome in this step.

The output will look like the following:

Phone Home Client configuration:
  Config Revisions: Device: 2 Destinations: 7 Global: 9
 
Device Id Type     State  Status  Forwards   Name
---------------------------------------------------------------
  15    collector Enabled forwarded     Phone Home collector 15
 
Device Id Type     State  Host/Ip   Port   Name
---------------------------------------------------------------
 11    database Enabled  192.168.2.2  7705  Phone Home database 11
 12    database Enabled  192.168.2.4  7705  Phone Home database 12
 13    database Enabled  192.168.2.6  7705  Phone Home database 13

Note the Device ID for the Database Server. .
Run the phonehome set command to change the IP address for the device ID that corresponds to the Database Server. To do this, enter the following:
```
                    phonehome set <device_id> ip="<new_ip_address>"
                
```

where:

<device_id> is the device ID you noted in step #4.
<new_ip_address> is the new IP address.

For example

[root@<database_hostname username>]# phonehome set 11 ip="<new_ip_address>"

Reloading sshd configurations

For each Database Server that you want to change the IP address, perform step #5.

Step 5b For Clustered Database Appliances (using HA, DR, or HA+DR)

If your Database Servers are clustered for High Availability (HA), Disaster Recovery (DR), or both (HA+DR), to change the IP address of the Database Servers, you must also modify the clustering software configuration files, as described in this step.

Either go to the console of the Database Server or use SSH to access the server.

Changes to the running Cluster Resource Manager (CRM) configuration take effect immediately. ScienceLogic recommends that you wait to wait to change the virtual IP address until all of the Database Servers have been moved to its new location, if applicable.

You must edit the settings for the virtual IP for the cluster. At the command line, enter the following:

 crm resource stop virtual_ip
crm resource param virtual_ip set ip <new_IP_address>
crm resource param virtual_ip set cidr_netmask <new_subnet_mask_in_CIDR_notation>
crm resource start virtual_ip

In a High Availability configuration, the two Database Servers use two rings:

ring0 defines the private interfaces that are connected directly to one another via crossover cable.
ring1 defines the public interfaces that host the virtual IP and conduct the SL1 related tasks.

To update these values in a High Availability configuration, you must edit the file /etc/corosync/corosync.conf..

Use a file editor like vi to edit /etc/corosync/corosync.conf.

You will see something like this:

 nodelist {
 node {
  ring0_addr: 192.168.25.200
  ring1_addr: 10.1.20.25
  name: hardb1
  nodeid: 1
}
 node {
  ring0_addr: 192.168.25.201
  ring1_addr: 10.1.20.26
  name: hardb2
  nodeid:2
}

For the Database Server with the new IP address, edit the value for ring0_addr to match the new IP address. Save the file.

DRBD is the service that synchronizes the Database Servers in a High Availability or Disaster Recovery configuration. The DRBD file /etc/drbd.d/r0.res defines how data (on resource 0) is synchronized.

In SL1 configured for High Availability , DRBD uses the private IPs to synchronize high-availability data.
In SL1 configured for High Availability plus Disaster Recovery, DRBD uses the private interface to synchronize high-availability data and the virtual IP and the public IP addresses to synchronize data for disaster recovery.
In SL1 configured for Disaster Recovery, DRBD uses the virtual IP and the public IP addresses to synchronize data.=

Use a file editor like vi to edit /etc/drbd.d/r0.res. It will look something like this:

resource r0 {
 protocol A;
 device /dev/drdb1;
 stacked-on-top-of r0-L {
  address 127.0.0.1:7789;
  proxy on hadrdb1 hadrdb2 {
   inside 127.0.0.1:7790;
   outside 192.168.25.200:7788;
  }
 }
on hadrdb2
  disk /dev/mapper/em7vg-db;
  address 127.0.0.1:7789;
  meta-disk internal;
  proxy on hadrdb3 {
   inside 127.0.0.1:7790;
   outside 192.168.25.201:7788;
  }
 }

Replace instances of the old IP address with the new IP address and save the file.
Shut down the Database Server .
Upon reboot of the Database Server, run a discovery session to rediscover the Database Server with its new IP address.

Step 6. Reboot the Appliance

Reboot the Database Server to apply all of the changes you made.

If you are migrating a High Availability cluster, shut down the secondary first, then the primary, so that SL1 does not perform a failover. Restart up the primary first, and after it is up and running, restart on the secondary.

Step 7. Change the Database Appliance IP Address in the Administration Portals, Data Collectors, and Message Collectors

You must edit the configuration for each SL1 node that communicates with the Database Server. To do so, perform the following steps on each Administration Portal, Data Collector, and Message Collector in your SL1 system.

Perform the following steps to log in to the Web Configuration Utility:

You can log in to the Web Configuration Utility using any web browser supported by SL1. The address of the Web Configuration Utility is in the following format:

https://<ip-address-of-appliance>:7700

For AWS instances, ip-address-of-appliance is the public IP for the AWS instance. To locate the public IP address for an AWS instance, go to AWS, go to the Instances page, and highlight an instance. The Description tab in the lower pane will display the public IP.

When prompted to enter your user name and password, log in as the "em7admin" user with the appropriate password.
After logging in, the main Configuration Utility page appears.

Click the Device Settings button in the upper-right of the page. The Settings page appears.
In the Settings page, enter the following:

Database IP Address. The new IP address of the Database Server.
Database Username. Username for the database account that the Administration Portal will use to communicate with the Database Server.
Accept the default values in all other fields.

Click the Save button. You may now log out of the Web Configuration Utility.

Step 8. Confirm the Change in SL1

Changing the IP Address on a Data Collector or Message Collector

You can change the IP address of a Data Collector or Message Collector in two ways:

In the Web Configuration Utility
From the command line of the Data Collector or Message Collector

Regardless of the method you choose, SL1 will automatically update the IP address of the Data Collector or Message Collector in:

/etc.sillo.conf
/etc/sysconfig/network-scripts/ifcfg-ens160
/etc/hosts
the master.system_settings_licenses table, in the ip column

The following sections explain the necessary steps.

Using the Web Configuration Utility to Change the IP Address of a Data Collector or Message Collector

Perform the following steps to log in to the Web Configuration Utility:

You can log in to the Web Configuration Utility using any web browser supported by SL1. The address of the Web Configuration Utility is in the following format:

https://<ip-address-of-appliance>:7700

For AWS instances, ip-address-of-appliance is the public IP for the AWS instance. To locate the public IP address for an AWS instance, go to AWS, go to the Instances page, and highlight an instance. The Description tab in the lower pane will display the public IP.

When prompted to enter your user name and password, log in as the "em7admin" user with the appropriate password.
After logging in, the main Configuration Utility page appears.

Select the Interfaces tab.
In the Interfaces page, select the interface that you want to edit.
Enter values in the following field:

Interface IP Address. Required. Enter the IP address for the bonded interface in standard IPv4, dotted-octet format.

The IP address for the Data Collector or Message Collector will be automatically updated in all the necessary configuration file and database tables.

Using the Command Line to Change the IP Address of a Data Collector or Message Collector

Either go to the console of the Data Collector or Message Collector or use SSH to access the server.
At the shell prompt, enter:

update_ip <interface_ID> <new_IP>

where:
- interface_ID is the name of the interface, usually ensn32 or ens160.
- new_IP is the new IP address to assign to the interface.
The IP address for the Data Collector or Message Collector will be automatically updated in all the necessary configuration file and database tables.

Confirming the IP Address Change on the Appliance Manager Page

After changing the IP address for your SL1 appliance, go to the Appliance Manager page (System > Settings > Appliances) and confirm that the correct IP address appears for that appliance in the IP Address column.

If the Appliance Manager page does not display the new IP address, you can manually update the address. To do so:

Go to the Appliance Manager page (System > Settings > Appliances).
Click the wrench icon () of the appliance you want to update. Its values appear in the fields at the top of the page.
In the IP Address field, type the new IP address.
Click Save.