A10 ADC Lab 4 HTTP Virtual Server

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

ADC Lab 4

HTTP Virtual Server


Lab 4 Overview
In this lab you will configure and verify functionality of a Layer 7 HTTP Virtual Server.

Device Preparation
Continuing from Lab 3: Load Balancing Concepts
When starting this lab immediately after successfully completing Lab 1, proceed to the
Initial Device Verification section.

HTTP Virtual Server


Servers and Service Group
The HTTP Virtual Server uses the servers and service group that were configured in the
first lab. The Initial Device Verification section included commands that verified these
objects were configured and functioning.
Health Check
To demonstrate a failed service group, create a health monitor that disables the server
group, then create and apply a different monitor that enables the group:
1. Create a layer 7 health monitor (named HM‐EXPECT1) that searches for text (brokenserver) that is
not listed on the target web page.
health monitor HM‐EXPECT1
method http expect broken‐server
exit
2. Create a second health monitor (named HM‐EXPECT2) that searches for text
(Temporibus) that the target web page includes.
health monitor HM‐EXPECT2
method http expect Temporibus
exit
3. Verify the new health monitors.
show run | sec health
4. Apply the HM‐EXPECT1 health monitor to the SG‐H TTP service group.
slb service‐group SG‐HTTP tcp
health‐check HM‐EXPECT1
5. Display the state of the service group.
show slb service‐group SG‐HTTP
The first line displays the service group name and state. Since broken‐server is not in
the text on the It Works webpage, the service group is down.
Scroll through the output to view the reason the group is down, monitor attributes, and
the method. Note the connection was successful at L4 (L4 conn made >0 ; L4 errors = 0).
6. Remove HM‐EXPECT1 and apply HM‐EXPECT2. Verify the new template restores the
service group state to UP.
no health‐check HM‐EXPECT1
health‐check HM‐EXPECT2
show slb service‐group SG‐HTTP
The Service Group state should be All Up with Up reason as HTTP Expected Response
Received ; HTTP errors is 0 (or very small) and Received OK is greater than 0.
Source NAT
7. Build an IP NAT pool named NAT‐H TTP . Verify its configuration.
ip nat pool NAT‐HTTP 10.254.251.x+4 10.254.251.x+4 netmask /24
show ip nat pool NAT‐HTTP
Note: Please verify it already create the object before.
Cookie Persistence
8. Create and configure a cookie persistence template. Verify its configuration.
slb template persist cookie TP‐CPERS
name ElvisLives
show slb template persist cookie
HTTP Templates
This section creates two HTTP templates. One template inserts a header; the second
specifies a failover address. The templates will be applied one at a time to verify
functionality. The settings could exist on the same template.
9. Create an HTTP Header Insert template named TP‐CLIENT‐IP. Verify its configuration
slb template http TP‐CLIENT‐IP
insert‐client‐ip
10.Creating an HTTP failover template.
slb template http TP‐FAILOVER
failover‐url http://1.0.0.210/
11. Verify the HTTP template configurations.
show slb template http
Virtual Server (VIP)
12. Create an HTTP Virtual Server named VIP‐H TTP:
slb virtual‐server VIP‐HTTP 10.254.251.x+5
13. Add the Virtual Port and the previously configured elements.
port 80 http
service‐group SG‐HTTP
source‐nat pool NAT‐HTTP
template persist cookie TP‐CPERS
template http TP‐CLIENT‐IP
14. Confirm the virtual server configuration.
show running‐config | sec VIP‐HTTP
15. Save the configuration for the next exercise:
write mem
Verifying functionality
Verify virtual server configuration.
show running‐config | sec VIP‐HTTP

You might also like