Configuration of bonding after VIM deployment
NOTE:
This procedure is applicable only if HPE ProLiant Edgeline EL4000 is used as VIM Controllers.
Procedure
- Log in to the Undercloud VM as the stack user.
-
Find the controller IP address using the following command:
source stackrc nova list
The controller IP address is displayed.
-
Log in to any one of the overcloud controllers as
heat-admin with controller IP address using the following command:
ssh heat-admin@<controller_ip>
-
Stop pcs clusters on all the controllers using this command. Run the command from the controller you are currently logged in.
sudo pcs cluster stop --all
Wait for some time for the
pcs cluster
to stop. -
Log in to each controller and verify the
pcs cluster
status using the following command:sudo pcs cluster status
The message Error: cluster is not currently running on this node is displayed.
-
Create bonding on the switch using the following:
- Log in to the Remote NPS VM.
- Export the environment variables.
export API_IP=<NPS Toolkit VM OAM/Customer Network IP address> export NPSADMIN=<user name of admin mentioned in the nps_secret.yaml file> export NPSPASSWD=<password of admin user mentioned in the nps_secret.yaml file> export TOPOLOGY_NAME=<value of the field "topology_name" in the input.json file> export VIM_TYPE=<VIM platform type like RHOSP/RHOCP/VMWARE>
- Update the bond using the following NPS CLI command:
nps update-switch --switch1 <data_switch1_ip> --switch2 <data_switch2_ip>
-
Log in to any one of the overcloud controllers as
heat-admin and run the following command to start the cluster service on all the controllers.
sudo pcs cluster start --all
-
Verify the status of the cluster service on the controller using the following command:
sudo pcs cluster status --all
All the cluster services are up and running.