docs/doc/source/dist_cloud/kubernetes/manage-subcloud-management-network-parameters-ffde7da356dc.rst
Elisamara Aoki Goncalves a46bf0c65f Platform Management Network Reconfiguration - AIO-SX
Add procedure to configure management network after install for AIO-SX only.

Story: 2010722
Task: 50146

Change-Id: I50d323b903e83be46f01917619f0ee90179d1e69
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
2024-08-27 19:11:19 +00:00

2.8 KiB

Manage Subcloud Management Network Parameters

You can change the management IP addresses for an subcloud.

  • 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 server configuration or server configuration sections to correct the system time based on the system's clock_synchronization configuration ( or ).

Change the Network Parameters of the Management Network for AIO-SX Subcloud Only

This task is required only if the management network needs to be changed for an subcloud.

  1. Lock the controller.

    system host-lock controller-0
  2. Obtain the UUID of the management pool.

    system addrpool-list
  3. Modify the management address pool.

    For example:

    system addrpool-modify <uuid> \
      --network              192.168.103.0 \
      --prefix                    26 \
      --floating-address         192.168.103.2 \
      --controller0-address  192.168.103.3 \
      --controller1-address  192.168.103.4 \
      --gateway-address       192.168.103.1 \
      --ranges                192.168.103.1-192.168.103.50
  4. Unlock the controller.

    system host-unlock controller-0
  5. Wait for the subcloud to recover and to have all alarms cleared.

  6. 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/26 --management-gateway-ip 192.168.103.1 --management-start-ip 192.168.103.2 --management-end-ip 192.168.103.5 --bootstrap-address 10.33.1.3 <subcloud-name>
    3. Manage the subcloud.

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