starlingx/docs
Code Issues Proposed changes
docs/doc/source/system_configuration/kubernetes/converting-a-duplex-system-to-switch-based-connection.rst
Stone ecae991cca System Configuration reorg 
Organized SysConf Kubernetes and OpenStack content into subdirs and modified
index along lines of Planning layout.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: Ia17c015b2083a39fcae4ac545fa10cb5445b4cb2
2021-01-29 09:41:28 -05:00

2.3 KiB
Raw Blame History

Convert a Duplex System to Switch-Based Connection

On a Duplex system configured to use direct connections for the management and cluster host networks, you can convert to switch-based connections.

The connection type is initially configured at installation. You can change it at any time. You must use the CLI to make the change.

Extra network cables are required to connect both controllers to the switch.

The switch must be configured correctly for communication with the controllers.

  1. Use the system modify command to specify switch-based connection (duplex).

    ~(keystone_admin)$ system modify --system_mode=duplex

    This raises Config-out-of-date alarm messages on both controllers.

  2. Lock the standby controller.

  3. Disconnect the management and infrastructure cables from the standby controller.

    This raises Port failed and Interface failed alarms on the active controller for the management and infrastructure interfaces.

  4. Connect both controllers to the switch.

    Connect the existing cables from the active controller to the switch. Use additional cables to connect the standby controller to the switch.

    Wait for the network interface alarms on the active controller to be cleared.

  5. Unlock the standby controller to update its configuration.

    Wait for the controller to be reported as Unlocked, Available, and Online, and for its Config-out-of-date alarm message to be cleared.

  6. Swact the controllers.

  7. Lock and then unlock the new standby controller to update its configuration.

    Wait for the controller to be reported as Unlocked, Available, and Online, and for its Config-out-of-date alarm message to be cleared.

The system is now reconfigured to use switch-based connections for the internal networks.