In this page:

Change All-in-One Appliance IP Address

The appliance IP address is configured as a static IP address. Hence, changing the IP address of the appliance requires the following steps:

1. Login to the DPOD server’s console using dpodadm or rootuser. It is recommended not to use SSH, since the connection will disconnect during the configuration changes and you might lose access to the server.

2. Set a static hostname:

   sudo nmcli general hostname $(hostname)

3. Make sure eth0 is up and connected:

   nmcli device status

   Expected output:

   DEVICE TYPE STATE CONNECTION eth0 ethernet connected eth0 lo loopback connected (externally) lo

4. Change the IP address of the network interface, including the CIDR (numeric network subnet mask, e.g.: 24 for the subnet mask 255.255.255.0):

5. [Optional] Change the gateway IP address:

6. [Optional] Change the DNS servers:

7. Verify the changes:

8. Restart the network connection:
   The following command will restart the network interface. Make sure you have the DPOD server console available (not SSH) in case additional changes are needed.

9. Update the hosts file and replace the old IP address with the new IP address:

10. Switch to the DPOD application user:

11. Update DPOD’s configuration file:

12. Update the configuration database:

    1. Start the configuration database CLI in interactive mode:

    2. Run the following SQL statements:

7. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

8. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

Change All-in-One Non-Appliance IP Address

1. In Non-Appliance installations, the operating system and network configuration is under the responsibility of the customer, so the IP address should be changed by the team that is managing this server.
   (If you need an example, have a look at steps 1-8 in the Appliance mode procedure described earlier in this document.)
   Once the IP address has been changed, continue with the following steps to configure the DPOD application with the new IP address.

2. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions).

3. Update the hosts file and replace the old IP address with the new IP address:

4. Switch to the DPOD application user (usually dpodsvc or storeadm):

5. Update DPOD’s configuration file:

6. Update the configuration database:

   1. Start the configuration database CLI in interactive mode:

   2. Run the following SQL statements:

7. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

8. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

Change Cell Manager's Internal IP Address

On the Cell Manager

1. Change the cell manager’s internal IP address:

   1. For Appliance mode:

      1. Login to the DPOD server via SSH using dpodadm user.

      2. Find the internal IP network interface name using the following command:

      3. Execute steps 1-8 of the Appliance mode procedure described earlier in this document (make sure to replace eth0 with the correct network interface name).

   2. In Non-Appliance installations, the operating system and network configuration is under the responsibility of the customer, so the IP address should be changed by the team that is managing this server.
      (If you need an example, have a look at steps 1-8 in the Appliance mode procedure described earlier in this document.)
      Once the IP address has been changed, continue with the following steps to configure the DPOD application with the new IP address.

2. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

3. Update the hosts file and replace the old IP address with the new IP address:

4. Switch to the DPOD application user (usually dpodsvc or storeadm):

5. Update DPOD’s configuration file:

6. Update the configuration database:

   1. Start the configuration database CLI in interactive mode:

   2. Run the following SQL statements:

7. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

8. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

On Each of the Cell Members

1. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

2. Update the hosts file and replace the old IP address with the new IP address:

3. Switch to the DPOD application user (usually dpodsvc or storeadm):

4. Update DPOD’s configuration file:

5. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

6. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

Change Cell Manager's External IP Address

On the Cell Manager

1. Change the cell manager’s external IP address:

   1. For Appliance mode:

      1. Login to the DPOD server via SSH using dpodadm user.

      2. Find the external IP network interface name using the following command:

      3. Execute steps 1-8 of the Appliance mode procedure described earlier in this document (make sure to replace eth0 with the correct network interface name).

   2. In Non-Appliance installations, the operating system and network configuration is under the responsibility of the customer, so the IP address should be changed by the team that is managing this server.
      (If you need an example, have a look at steps 1-8 in the Appliance mode procedure described earlier in this document.)
      Once the IP address has been changed, continue with the following steps to configure the DPOD application with the new IP address.

2. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

3. Update the hosts file and replace the old IP address with the new IP address:

4. Switch to the DPOD application user (usually dpodsvc or storeadm):

5. Update DPOD’s configuration file:

6. Update the configuration database:

   1. Start the configuration database CLI in interactive mode:

   2. Run the following SQL statements:

7. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

8. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

On Each of the Cell Members

1. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

2. Update the hosts file and replace the old IP address with the new IP address:

3. Switch to the DPOD application user (usually dpodsvc or storeadm):

4. Update DPOD’s configuration file:

5. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

6. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

Change Cell Member's Internal IP Address

On the Cell Member

1. Change the cell member’s internal IP address:

   1. For Appliance mode:

      1. Login to the DPOD server via SSH using dpodadm user.

      2. Find the internal IP network interface name using the following command:

      3. Execute steps 1-8 of the Appliance mode procedure described earlier in this document (make sure to replace eth0 with the correct network interface name).

   2. In Non-Appliance installations, the operating system and network configuration is under the responsibility of the customer, so the IP address should be changed by the team that is managing this server.
      (If you need an example, have a look at steps 1-8 in the Appliance mode procedure described earlier in this document.)
      Once the IP address has been changed, continue with the following steps to configure the DPOD application with the new IP address.

2. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

3. Update the hosts file and replace the old IP address with the new IP address:

4. Switch to the DPOD application user (usually dpodsvc or storeadm):

5. Update DPOD’s configuration file:

6. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

7. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

Change Cell Member's External IP Address

On the Cell Member

1. Change the cell member’s external IP address:

   1. For Appliance mode:

      1. Login to the DPOD server via SSH using dpodadm user.

      2. Find the external IP network interface name using the following command:

      3. Execute steps 1-8 of the Appliance mode procedure described earlier in this document (make sure to replace eth0 with the correct network interface name).

   2. In Non-Appliance installations, the operating system and network configuration is under the responsibility of the customer, so the IP address should be changed by the team that is managing this server.
      (If you need an example, have a look at steps 1-8 in the Appliance mode procedure described earlier in this document.)
      Once the IP address has been changed, continue with the following steps to configure the DPOD application with the new IP address.

2. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

3. Update the hosts file and replace the old IP address with the new IP address:

4. Switch to the DPOD application user (usually dpodsvc or storeadm):

5. Update DPOD’s configuration file:

6. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

7. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)

On the Cell Manager

1. Login to the DPOD server via SSH using a privileged user (rootor a user with sudo permissions such as dpodadm in Appliance installations).

2. Switch to the DPOD application user (usually dpodsvc or storeadm):

3. Update the configuration database:

   1. Start the configuration database CLI in interactive mode:

   2. Run the following SQL statements:

4. Stop all the application services using /app/scripts/app-util.sh -> option 2 (stop all)

5. Start all the application services using /app/scripts/app-util.sh -> option 1 (start all)