2.1.1. Lab 1: Pre-configured pools and virtual servers

A virtual server is used by BIG-IP to identify specific types of traffic. Other objects such as profiles, policies, pools and iRules are applied to the virtual server to add features and functionality. In the context of security, since BIG-IP is a default-deny device, a virtual server is necessary to accept specific types of traffic.

The pool is a logical group of hosts that is applied to and will receive traffic from a virtual server.

On your personal device

Look at the supplemental login instructions for:

• External Hostnames
• External IP addressing diagram
• Login IDs and Passwords are subject to change as well.

Note

Use the Chrome Browser to Connect to BIG-IP01— https://10.1.1.4 Credentials are displayed in the login screen

2.1.1.1. Inspect Application Pools

On BIG-IP

Verify the following pools using the following tabel of pool information.

Navigation: Local Traffic > Pools > Pool List

Name	Health Monitor	Members	Service Port
pool_www.site1.com	thttp	10.1.20.11	80
pool_www.site2.com	http	10.1.20.12	80
pool_www.site3.com	http	10.1.20.13	80
pool_www.site4.com	http	10.1.20.14	80
pool_www.site5.com	http	10.1.20.15	80
pool_www.dvwa.com	tcp_half_open	10.1.20.17	80

2.1.1.2. Inspect Application Virtual Servers

By using the term ‘internal’ we are creating the virtual servers on what is essentially a loopback VLAN which prevents them from being exposed. The EXT_VIP in this exercise is used to forward traffic with specific characteristics to the internal VIP’s. This is accomplished by assigning a traffic policy to the VIP. The traffic policy is described and inspected in the next section. For this class, the Wildcard Virtual servers (Blue Square status indicator) are not used.

Navigation: Local Traffic > Virtual Servers > Virtual Server List

Inspect the Local Traffic Network Map

Navigation: Local Traffic > Network Map

Note

The virtual servers should show a green circle for status.

Note

This completes Module 1 - Lab 1