Configuring the OVSDB Plugin When Deploying a New Controller

This appendix includes the following sections:

Configuring the OVSDB Plugin When Deploying a New Controller

Follow these steps to configure the OVSDB plugin when deploying a new controller (with a new IP address). These steps are recommended on an already installed pre-existing system to migrate to a new set of controllers.

Procedure

Step 1

Enter the guestshell run sudo ovsdb-plugin service stop command on the vPC primary switch.

Step 2

Enter the guestshell run sudo ovsdb-plugin service stop command on the vPC secondary switch.

Step 3

Enter the guestshell run sudo ovsdb-plugin config set commands to reconfigure the OVSDB plugin on both the vPC primary and secondary switches. Make sure to use the new controller IP address in these commands.

Step 4

Enter the guestshell run sudo ovsdb-plugin cert reset command on the vPC primary switch. Check if the files in the config/ssl/ directory have new updated timestamps.

Step 5

Enter the guestshell run sudo ovsdb-plugin cert reset command on the vPC secondary switch. Check if the files in the config/ssl/ directory have new updated timestamps.

Step 6

Enter the guestshell run sudo ovsdb-plugin cert reset --receive -v command on the vPC primary switch.

Step 7

Enter the guestshell run sudo ovsdb-plugin cert reset --send remote-vpc-primary-ip :6640 -v command on the vPC secondary switch. Copy the receiver side certificate on the sender side.

Step 8

Enter the guestshell run sudo ovsdb-plugin cert show command on the vPC primary switch.

Step 9

Enter the guestshell run sudo ovsdb-plugin cert show command on the vPC secondary switch.

Step 10

Check if the output in Steps 8 and 9 are showing the same content.

Step 11

Paste the cert show output in vCenter as the TOR vPC pair's certificate.

Step 12

Enter the guestshell run sudo ovsdb-plugin service start command to start the OVSDB plugin on both the vPC primary and secondary switches.