2.4.1. Check Declarative Onboarding (DO) is Ready

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 1: Check DO - BIGIP1” => [Send].

Status 200 OK response signals that Declarative Onboarding iControl LX is ready on Big-IP1.

../../_images/1_postman_bigip1_check_do.png

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 2: Check DO - BIGIP2” => [Send].

Status 200 OK response signals that Declarative Onboarding iControl LX is ready on Big-IP2.

../../_images/2_postman_bigip2_check_do.png

2.4.2. Basic network plumbing and services

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 3: DO - Network Plumbing and Module Provisioning - BIGIP1” => [Send]

../../_images/3_postman_bigip1_do.png

Change the HTTP method from POST to GET and click “Send”. You can do this often to track the status of the DO declaration in the Response. Status 202 indicates the declaration was successfully submitted and is being processed, Status 200 indicates the declaration has successfully completed.

../../_images/4_postman_bigip1_get_do_status.png

Eventually, the status will be 200 OK. Our DO declaration has successfully created the network plumbing on Big-IP1.

../../_images/5_postman_bigip1_do_completed.png

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 4: DO - Network Plumbing and Module Provisioning - BIGIP2” => [Send]

../../_images/12_postman_bigip2_do.png

Change the HTTP method from POST to GET and click “Send”. You can do this often to track the status of the DO declaration in the Response. Status 202 indicates the declaration was successfully submitted and is being processed, Status 200 indicates the declaration has successfully completed.

../../_images/13_postman_bigip2_get_do_status.png

Eventually, the status will be 200 OK. Our DO declaration has successfully created the network plumbing on Big-IP2.

../../_images/14_postman_bigip2_do_completed.png

On Big-IP1, Network => VLANs. traffic VLAN was created via DO.

../../_images/6_bigip1_do_vlan.png

On Big-IP1, Network => Self IPs. traffic-self VLAN was created via DO.

../../_images/7_bigip1_do_self_ip.png

On Big-IP1, Network => Interfaces. Interface 1.1 is UP.

../../_images/8_bigip1_do_interfaces.png

On Big-IP1, System => Configuration => Device => NTP was configured.

../../_images/9_bigip1_do_ntp.png

On Big-IP1, System => Configuration => Device => DNS was configured.

../../_images/10_bigip1_do_dns.png

On Big-IP1, Network => Routes. No routes.

../../_images/11_bigip1_do_no_route.png

On Big-IP2, Network. => Routes. No routes.

../../_images/13_postman_bigip2_get_do_status.png

2.4.3. Default route in LOCAL_ONLY partition for Cloud Failover

For cloud fail-over we need to create routes in a dedicated “LOCAL_ONLY” partition.

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 5: REST API - Create LOCAL_ONLY Partition - BIGIP1” => [Send].

../../_images/15_postman_bigip1_create_local_only_partition.png

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 6: REST API - Create default route - BIGIP1” => [Send].

../../_images/16_postman_bigip1_create_default_route.png

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 7: REST API - Create LOCAL_ONLY Partition - BIGIP2” => [Send].

../../_images/18_postman_bigip2_create_local_only_partition.png

From Postman, “Lab - Declarative Onboarding - Basic Plumbing” => “Step 8: REST API - Create default route - BIGIP2” => [Send].

../../_images/19_postman_bigip2_create_default_route.png

On Big-IP1, Network => Routes => Select the “LOCAL_ONLY” partition from the drop down in the upper-right-hand corner. The Default route was created.

../../_images/17_bigip1_default_route.png

Confirm the a default route was created in the LOCAL_ONLY partition of Big-IP2 as well.