Manage Subcloud Network Parameters

Use the following procedures to manage an optional admin network on a subcloud for IP connectivity to the system controller management network where the IP addresses of the admin network can be changed.

Prerequisites

  • Ensure that the subcloud admin subnet does not overlap addresses already being used by the system controller or any of its subclouds.

  • Ensure that the subcloud has been backed up, in case a subcloud system recovery is required.

  • Ensure that the system time between system controllers and the subclouds are synchronized.

    ~(keystone_admin)]$ date -u

    If the time is not correct either on the system controllers or the subclouds, check the clock_synchronization configuration on the system.

    ~(keystone_admin)]$ system host-show controller-0

    Check the NTP server configuration or PTP server configuration sections to correct the system time based on the system’s clock_synchronization configuration (NTP or PTP).

Add an admin interface or network

About this task

This task is required only if an admin network/interface does not exist on the system, either via this procedure or at bootstrap time. The procedure is performed only on the subcloud.

Procedure

  1. For all the controller hosts of a subcloud, add the new admin interface as follows:

    1. Lock the host.

      ~(keystone_admin)]$ system host-lock <controller-host>

    2. Add a new platform interface.

      ~(keystone_admin)]$ system host-if-modify <host> <admin-interface> -c platform

      For example:

      ~(keystone_admin)]$ system host-if-modify <controller-host> enp0s9 -c platform

      Note

      To see all the available interfaces, use the system host-if-list -a <host> command.

    3. Unlock the host.

      ~(keystone_admin)]$ system host-unlock <host>

  2. Create an admin network address pool.

    ~(keystone_admin)]$ system addrpool-add --floating-address <floating-address> --controller0-address <controller0-address> --controller1-address <controller1-address> --gateway-address <gateway-address> <address-pool-name> <subnet> <prefix length>

    For example:

    ~(keystone_admin)]$ system addrpool-add --floating-address 192.168.102.2 --controller0-address 192.168.102.3 --controller1-address 192.168.102.4 --gateway-address 192.168.102.1 admin 192.168.102.0 24

  3. Create the admin network with the dynamic field set to false.

    ~(keystone_admin)]$ system network-add <network-name> admin false <admin-address-pool-uuid>

    For example:

    ~(keystone_admin)]$ system network-add admin admin false $(system addrpool-list | grep admin | awk '{print $2}')

  4. Assign the admin network to the admin interface.

    ~(keystone_admin)]$ system interface-network-assign <controller-host> <interface-name> <network-name>

    For example:

    ~(keystone_admin)]$ system interface-network-assign <controller-host> enp0s9 admin

Change the network parameters of the admin network

AIO-SX subcloud

About this task

This task is required only if the parameters of an admin network need to be changed, for example, to align with a new external network configuration. The procedure is performed only on the subcloud.

Procedure

  1. Modify the admin network address pool.

    For example:

    ~(keystone_admin)]$ system addrpool-modify <admin-pool-uuid> \
--network 192.168.103.0 --prefix 24 \
--floating-address 192.168.103.2 \
--controller0-address 192.168.103.3 \
--controller1-address 192.168.103.4 \
--gateway-address 192.168.103.1

  2. On the system controller, perform the following:

    1. Unmanage the subcloud.

      ~(keystone_admin)]$ dcmanager subcloud unmanage <subcloud-name>

    2. Update the subcloud with the new subnet parameters.

      For example:

      ~(keystone_admin)]$ dcmanager subcloud update --management-subnet 192.168.103.0/24 --management-gateway-ip 192.168.103.1 --management-start-ip 192.168.103.2 --management-end-ip 192.168.103.5 --bootstrap-address 10.10.10.12 subcloud1

      Note

      The subcloud will go offline for a short period.

    3. Manage the subcloud.

      ~(keystone_admin)]$ dcmanager subcloud manage <subcloud-name>

AIO-DX/Standard subcloud

About this task

This task is required only if the parameters of an admin network need to be changed, for example, to align with a new external network configuration. The procedure is performed only on the subcloud.

Procedure

  1. Modify the admin network address pool.

    For example:

    ~(keystone_admin)]$ system addrpool-modify <admin-pool-uuid> \
--network 192.168.103.0 --prefix 24 \
--floating-address 192.168.103.2 \
--controller0-address 192.168.103.3 \
--controller1-address 192.168.103.4 \
--gateway-address 192.168.103.1

    Note

    The endpoints associated with Distributed Cloud management will be updated to the endpoints of the new admin network. This can take a few minutes and can be obtained using the openstack endpoint list command on the subcloud.

  2. On the system controller, perform the following:

    1. Unmanage the subcloud.

      ~(keystone_admin)]$ dcmanager subcloud unmanage <subcloud-name>

    2. Update the subcloud with the new subnet parameters.

      For example:

      ~(keystone_admin)]$ dcmanager subcloud update --management-subnet 192.168.103.0/24 --management-gateway-ip 192.168.103.1 --management-start-ip 192.168.103.2 --management-end-ip 192.168.103.5 --bootstrap-address 10.10.10.12 subcloud1

      Note

      The subcloud will go offline for a short period.

    3. Manage the subcloud.

      ~(keystone_admin)]$ dcmanager subcloud manage <subcloud-name>

Switch back to the management network

About this task

This task is required only if an operator wants to switch back to the subcloud management network. This procedure can also be used to switch the subcloud back to an already existing admin network.

Procedure

  1. Unmanage the subcloud.

    ~(keystone_admin)]$ dcmanager subcloud unmanage <subcloud-name>

  2. Update the subcloud with the existing network parameters of the subcloud management network.

    For example:

    ~(keystone_admin)]$ dcmanager subcloud update --management-subnet 192.168.104.0/24 --management-gateway-ip 192.168.104.1 --management-start-ip 192.168.104.2 --management-end-ip 192.168.104.5 --bootstrap-address 10.10.10.12 <subcloud-name>

    Note

    Obtain the existing management network parameters on the subcloud using the system addrpool-show <management network uuid> command.

    Note

    The subcloud will go offline for a short period.

  3. Manage the subcloud.

    ~(keystone_admin)]$ dcmanager subcloud manage <subcloud-name>