F5 Public Cloud Solutions > Deploying F5 Solutions to GCP with Terraform and The F5 Automation Toolchain > F5 Declarative Onboarding (DO) - HA Config Sync Source | Edit on
Establish Device Trust between Big-IPs¶
Please click on the F5 plugin item at the left of the screen, and select bigip1.example.com.
Please ensure you are connected to the correct device with the F5 Plugin before posting a declaration. A failure to do so may result in an error.
From Agility2021_GCP_Terraform_ATC click on Lab4.2-DO_HA under the drop down menu, select “do_step1.json” request. Right Click “Post as DO Declaration”. The Status will be 202 RUNNING.
Wait a few minutes until status is 200 OK. Use the DO verification in the blue bar at the bottom of VS Code to refresh the status.
If the DO returns anything other than a “202 Accepted” or a “200 OK” then it is suggested to ssh as admin@<ip address> to the BIG-IP in question, and issue the command “bigstart restart restnoded” and once done, re-submit the DO declaration.
Now sign into BIG-IP Host 2 via the F5 VS Code extension. Click on Lab4.2-DO_HA under the drop down menu, select “do_step2.json” request. Right Click “Post as DO Declaration”. The Status will be 202 RUNNING.
Wait a few minutes until status is 200 OK
At the bottom of the VS Code window in the blue bar, you can click on the DO (1.18.0) to submit a “GET” request to get the status of the DO execution.
Make sure Big-IP1 is active and Big-IP2 is standby before proceeding. To force Big-IP2 to standby: “Device Management” => “Devices” => bigip2.example.com => [Force to Standby].
From the Big-IP1 Configuration Utility (WebUI), note that bigip1.example.com is the “ONLINE (ACTIVE)” device and “In Sync”.
From the Big-IP2 Configuration Utility (WebUI), note that bigip2.example.com is the “ONLINE (STANDBY)” device and “In Sync”.