admin@T104_DUT1.Conductor (router[name=Conductor])# show
The first step is to configure the second Conductor node. If you start with the same basic configuration for the second node then you will see warnings below when you attempt to validate. The first warning states that a non-forwarding interfaces between the Conductor nodes needs to be configured to establish connectivity. For more information regarding non-forwarding interfaces please refer to this blog: Configuring Non Forwarding Interfaces. The second warning states that 128T needs to be restarted after creating a new node. This will be addressed later.
1. The field 'name' cannot be created while the system is running. To apply the configuration, 'T104_DUT1.Conductor' and
'T104_DUT2.Conductor' must be restarted after committing this change.
reported by router 'Conductor'
Candidate configuration is valid
Commit the configuration, then stop 128T on the standalone Conductor node by dropping into the Linux shell and executing systemctl stop 128T. Wait for 128T to completely stop. The user can monitor the status of the service with systemctl status 128T.
Once 128T is fully stopped, the user needs to make changes to the salt minion configuration file. Since the Conductor was installed as a Standalone Conductor, the salt minion config is initialized with the loopback address. The user need to fix it manually to be the IP address of our management interface because when the second Conductor node is installed, it uses the IP address in these files to learn the management IP address of its peer node. Here is what the salt minion config look like before any modification:
At this point, the first Conductor node is still stopped and it is time to install the second Conductor node. The user will launch the interactive installer to install the second node. You need to double check that the node name entered in the interactive installer matches the node name in the configuration. Wait for the interactive installer to finish then pick yes when it prompts the user to reboot. While the second node is rebooting, this is a good time to double check the global.init file and salt minion configuration file on the first Conductor node have been modified and the second Conductor node has been added:
When installing a new HA node (conductor or router), ensure that the same version is being installed on both nodes.
Now that the global.init and salt minion config look correct we can restart the salt-minion so it picks up the config changes and then start 128T. From the Linux shell first execute systemctl restart salt-minion then systemctl start 128T. Once they are up login and verify they both have connectivity to each other:
admin@T104_DUT1.Conductor# show system connectivity