Lab 1.4 - Deploy Second Application Instance with Global Resiliency

In the previous lab exercise we deploy Global Resiliency for an application located on a single instance.

In this exercise we will expand the application to run on a second instance.

Lab 1.4.1 - Edit Application

  1. Navigate to Applications

    Navigate to Applications by clicking the workspace switcher next to the F5 icon

    ../../_images/top-left.png

    Then click on Applications

    ../../_images/central-manager-menu.png

  2. Click on “gr_app” (previously created)

    In the upper right click on “Edit”

    ../../_images/gr-app-edit.png

    Click on “Review & Deploy”

    ../../_images/gr-app-review-and-deploy.png

  3. Add Instance

    Under “Add Instance/Locations” select “big-ip-next-02” and click “+ Add to list”

    ../../_images/gr-app-edit-add-instance.png

  4. Enter a Virtual Address

    Enter the Virtual Address of “10.1.40.100”

  5. Under “Members” for big-ip-next-02 click on the down arrow and select “+Pool Members”

  6. Click on “+ Add Row”

    Use the following values

    Property Value
    Name node2
    IP Address 10.1.50.101

    Click on “Save” to return to the “Deploy” screen

  7. Click on “Deploy Changes”

  8. When prompted, press “Yes, Deploy”

    ../../_images/gr-edit-yes-deploy.png

Lab 1.4.2 - Open Web Shell

We will use the “dig” utility to verify our DNS records

  1. Within your UDF Deployment, go to the WEB SHELL access method that is under the Ubuntu Jump Host

  2. Type the following command

    # dig @10.1.10.53 gr.example.com +short

  3. repeat the command (you can use the up arrow to auto-complete) several times

    You should see both 10.1.10.100 and 10.1.40.100 being returned

    ../../_images/gr-webshell.png

  4. try using @10.1.40.53 and see if you get similar results

In this example we were connecting directly to the DNS listeners on BIG-IP Next to query the DNS records