Verify F5 Cloud Failover is Ready

The Cloud Failover Extension is becoming the default mechanism for BIG-IPs to failover in the cloud. This becomes a standard method and standard API to operate against so the configuration is similar amongst all clouds and lightens the complexity of understaning the underpinnings of HA Options pertaining to each cloud.

Navigate to the GCP console and search for your BIG-IP1 device. It will be named studentX-Y-ZZZZ-f5vm01 - where X is the studentID you are using for this lab. You will notice that there is a “Labels” section of this device which contains the label of “f5-cfe-failover-label” and the value of “studenX,” again where X is the student ID you are using.

Labels

You can see that the CFE package is installed by navigating to “iApps => Package Management LX” and note “f5-cloud_failover” package has been installed on both devices.

../../_images/00_service_discovery_check1.png

POST F5 Cloud Failover Declaration

From the files tab click on “Lab4.4-CFE” => highlight all of the text in “as3_cfe.json”. => right click then select Make HTTP Request.

../../_images/01_Select_and_Make_HTTP_Request.png

A “message:success” response indicates the f5-cloud-failover declaration was successfully posted.

../../_images/02_cfe_declaration_validation.png

Post the declaration to BIG-IP2 as well. The CFE configuration is not synchronized as part of the DSC synchronization mechanism.

Test Failover

From Big-IP1, Device Management => Devices => bigip1(Self).

../../_images/11_device_bigip11.png

Force bigip1 to standby. Click [Force to Standby].

../../_images/12_device_bigip1_force_to_standby1.png

Warning

If you are not in the “Common” partition, the [Force to Standby] button will be greyed out. Select /Common and it will now be active.

On Big-IP1, in the upper-left-hand corner, note “ONLINE (STANDBY)”.

../../_images/13_device_bigip1_standby1.png

From Big-IP2, in the upper-left-hand corner, note “ONLINE (ACTIVE)”. Big-IP2 was immediately promoted to active and Big-IP1 demoted to standby.

../../_images/14_device_bigip2_active1.png

From Big-IP2, Device Management => Devices => bigip2.f5lab.dev.

Force bigip2.f5lab.dev to standby. Click [Force to Standby].

../../_images/18_device_bigip2_force_to_standby1.png

On Big-IP2, in the upper-left-hand corner, note “ONLINE (STANDBY)”.

../../_images/19_device_bigip2_standby1.png

From Big-IP1, in the upper-left-hand corner, note “ONLINE (ACTIVE)”. Big-IP1 is now back to active.

../../_images/20_device_bigip1_active1.png

Back to the browser tab with the example application. [CTRL] + [F5] a few times to refresh the browser. We are using self-signed certificates in the lab. Bypass the TLS warnings. “Accept the Risk and Continue”.

../../_images/22_example_app_bigip1_bypass_warning1.png ../../_images/23_example_app_bigip11.png