9. LB Methods

Modify the GSLB configuration so that siteb is a standby DR site.

Introduce a network problem that causes the app1 link monitor to fail.

A network outage can automatically cause DR activation.

  1. On dns.sitea navigate to: DNS ›› GSLB : Pools : Pool List ›› Members : www.f5demo.com_pool

    ../../_images/gslb_pool_persistence_flyout.png

  2. Modify the “Load Balancing Method” -> “Preferred” to “Global Availability”

    ../../_images/gslb_pool_global_availability_details.png

    TMSH

    tmsh modify gtm pool a www.f5demo.com_pool load-balancing-mode global-availability

  3. Introduce a network problem at sitea and disable the virtual server

    On ltm.sitea navigate to: Local Traffic ›› Virtual Servers: Virtual Server List ›› Virtual Server: app1_sitea_www.f5demo.com_tcp_https_virtual

    ../../_images/router_disable_isp1_site_interface.png

    TMSH command to run on ltm.sitea to simulate a failure

    TMSH

    tmsh modify ltm virtual app1_sitea_www.f5demo.com_tcp_https_virtual disabled

  4. View the effect

    On the jumpbox, open chrome, and navigate to https:www.f5demo.com:

    ../../_images/dns_gslb1_site2_links.png

  5. Set the sitea virtual server back up and enable the virtual server

    On ltm.sitea navigate to: Local Traffic ›› Virtual Servers: Virtual Server List ›› Virtual Server: app1_sitea_www.f5demo.com_tcp_https_virtual

    ../../_images/router_enable_isp1_site_interface.png

    TMSH

    tmsh modify ltm virtual app1_sitea_www.f5demo.com_tcp_https_virtual enabled

Note: Even though you re-enabled the primary site1, a persistence record from the previous lab is still in place.