starlingx/docs
Code Issues Proposed changes
docs/doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst
Ron Stone 2b62f49a9d Fix symlinks 
Changed paths to avoid '..', which breaks symlinks in newer versions of sphinx.
Consolidated installation include files under /_includes. Prefixed r5 versions with 'r5_'
Moved files that are used up/down, but at different paths under /shared/_includes
and /shared/figures
Move two include files to /_includes
Moved addtional images to /shared/figures/... Required for DS platform builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia38f4205c5803b3d1fc043e6c59617c34a4e5cbd
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-09-02 13:31:45 +00:00

5.1 KiB
Raw Blame History

Change the OAM IP Configuration Using Horizon

You can change the External subnet, floating IP address, controller addresses, and default gateway at any time after installation.

During installation, is configured with an O|AM network subnet and related IP addresses. You can change these addresses using the Horizon Web interface or the CLI. You can use IPv4 or IPv6 addresses.

Caution

Access to the network is interrupted during this procedure. When a swact is performed on the controllers, the newly active controller uses the changed IP addresses. The existing IP addresses are no longer valid, and you must use the new IP addresses to reconnect to the controller. Changes to external access routing settings may also be required. In addition, console access to worker-node hosts is interrupted until the hosts are locked and unlocked.

Once the IP addresses are changed, any existing server certificates (ssl, docker_registry, OpenStack etc.) that have the old IP addresses in their must be updated with new certificates reflecting the new addresses.

Before changing the IP configuration, review the Fault Management page and ensure that any existing system alarms are cleared.

  1. In the Horizon, open the System Configuration page.

    The System Configuration page is available from Admin > Platform > System Configuration in the left-hand pane.

  2. Select the OAM IP tab.

    The IP page appears, showing the currently defined network configuration.

  3. Click Edit OAM IP.

    The Edit OAM IP dialog box appears.

  4. Replace the IP Subnet and/or IP addresses with different ones as required.

    Note

    If you change the IP address version (IPv4 or IPv6), ensure that the same version is used for the DNS servers (see Specify DNS Servers Using Horizon <specifying-dns-servers-using-horizon>) and NTP servers (see Configure NTP Servers Using Horizon <configuring-ntp-servers-and-services-using-horizon>).

  5. Click Save.

    This saves the configuration change and raises Config out-of-date alarms on the controller and worker nodes.

  6. Lock and unlock the standby controller to apply the configuration change.

    1. Open the Host Inventory page, available from Admin > Platform > Host Inventory in the left-hand pane, and then select the Hosts tab.

    2. In the Hosts list, open the drop-down menu for the standby controller, and then click Lock Host.

      The host is reported as locked.

    3. Open the drop-down menu for the standby controller, and then click Unlock Host.

    4. Wait until the standby controller is reported as Unlocked, Enabled, and Available.

    The Config-out-of-date alarm for this controller is cleared.

  7. Perform a swact to change the active controller.

    Open the drop-down menu for the active controller, and then click Swact Host.

    Access to the Horizon Web interface is interrupted as control is transferred, and Horizon becomes unresponsive. Both controllers now use IP addresses on the new subnet. To restore Horizon access, you must connect the controllers physically to the new subnet.

  8. Update the system switch configurations or controller interface connections as required to place the controller interfaces on the new subnet.

  9. Reconnect to Horizon using the new floating IP address.

    The former active controller is now the standby controller. It is shown with a Config out-of-date alarm.

  10. Lock and unlock the new standby controller to clear

    the Config out-of-date alarm.

    Wait until the standby controller is reported as Unlocked, Enabled, and Available.

The worker node Config out-of-date alarms are cleared automatically as the system configuration is updated.

  • If alarms are not cleared after a few minutes, lock and unlock the worker nodes to apply any other incomplete configuration changes.
  • (Optional) If you are running Docker proxy on your system, you need to change the no_proxy service parameter using the CLI to append the new OAM IP. See, Change the OAM IP Configuration Using the CLI <changing-the-oam-ip-configuration-using-the-cli>.

Default Firewall Rules <security-default-firewall-rules>

Modify Firewall Options <security-firewall-options>