Network labs Docs Open simulator →

BIG-IP — a virtual server, a pool and an HTTP monitor

A BIG-IP load balancer LB1 publishes one web address, the virtual server 10.1.0.100:80, in front of two web servers. Read how the virtual server, its pool and the pool's HTTP monitor fit together, then stop the web service on one server and watch the monitor take that member out while the virtual server stays up. Finally, build a second pool and virtual server yourself at the tmsh prompt and check that CLIENT reaches it.

Open this lab in your browser →

Free · no install · no account

Scenario

A load balancer gives many servers one address. On a BIG-IP that address is a virtual server: an IP address and a port that clients connect to. Three objects work together: - Virtual server (ltm virtual): the address clients use, here 10.1.0.100:80. It sends each new connection to a pool. - Pool (ltm pool): the servers that do the work. Each server is a pool member, an address and a port, here 10.2.0.11:80 and 10.2.0.12:80. - Monitor (ltm monitor): a health check. The http_200 monitor sends GET / to each member and expects 200 OK in the answer. A member that fails the check is marked offline and gets no new connections. The virtual server also has source-address-translation { type automap } (SNAT automap). The BIG-IP replaces the client's source address with its own self IP on the server side, so the servers answer the BIG-IP and not the client directly. LB1 is already configured. In this lab you read that configuration with tmsh, then you break one server and watch what the monitor does. The servers SRV1 and SRV2 are IOS boxes that run a web server (ip http server). At the end you build a second service yourself at the tmsh prompt: the pool app_pool with SRV2 as its only member, and the virtual server vs_app on 10.1.0.101:80.

Topology

3 × router, 1 × load balancer · Cisco IOS-style, f5-bigip

What you will do

  1. On LB1, list the virtual server's configuration with list ltm virtual. Note its destination and the pool it uses.

  2. Show the pool members and their health with show ltm pool members.

  3. Stop the web server on SRV1: in configuration mode, type no ip http server.

  4. On LB1, run show ltm pool members again, then show ltm virtual.

  5. On LB1, create the pool app_pool with SRV2 (10.2.0.12:80) as its member, checked by the http_200 monitor.

  6. Create the virtual server vs_app on 10.1.0.101:80. It sends connections to app_pool and uses SNAT automap, like vs_web.

  7. Check the new service with show ltm virtual vs_app, then save the configuration with save sys config.

Open this lab in your browser →

More labs on this topic

This lab in other languages

BIG-IP – ein virtueller Server, ein Pool und ein HTTP-MonitorBIG-IP: un servidor virtual, un pool y un monitor HTTPBIG-IP – um servidor virtual, um pool e um monitor HTTPBIG-IP – un serveur virtuel, un pool et un moniteur HTTPBIG-IP — एक वर्चुअल सर्वर, एक पूल और एक HTTP मॉनिटरBIG-IP — 虚拟服务器、池与 HTTP 监视器BIG-IP: un virtual server, un pool e un monitor HTTPBIG-IP — 仮想サーバ、プール、HTTP モニタBIG-IP — 가상 서버, 풀, HTTP 모니터BIG-IP — виртуальный сервер, пул и HTTP-мониторBIG-IP — bir sanal sunucu, bir havuz ve bir HTTP monitörüBIG-IP — một máy chủ ảo, một pool và một monitor HTTP