Lesson 03: Build an Isolated F5 ASM Lab and Understand BIG-IP Traffic Flow
F5 ASM CLASSROOM • LESSON 03
Level: Beginner | Suggested study and lab time: 75 minutes
Instructor: Harpreet Singh Virdi, CISSP, CCSP
Start Here / Course Guide · All lessons
What we are building
We will use a fictional bookshop throughout the course. The lab has a test client, a licensed BIG-IP environment with ASM or the required Advanced WAF capabilities, and an application server. Keep the management interface on a restricted management network. Put the test application on an isolated network and use synthetic accounts and data.
Use a release supported for your environment and follow its installation requirements. CPU, memory, hypervisor support, licensing, and provisioning requirements depend on the chosen image. An unlicensed virtual machine is not a complete working ASM lab.
Meet the BIG-IP building blocks
- Node: an application server's address.
- Pool member: an address and service port, such as a test server's HTTP service.
- Pool: the collection of members that can serve the application.
- Health monitor: a check used to determine service availability.
- Virtual server: the address/port clients connect to, with associated traffic settings.
- HTTP profile: configuration that enables HTTP processing on the traffic path.
- SSL profiles: settings for client-side and, where required, server-side TLS.
- ASM policy: application security checks associated with the relevant virtual server or policy-selection configuration.
Plan the path before clicking
Test client → lab virtual IP → pool member → test application Management workstation → management interface
These are different paths. Being able to sign in to the management interface does not prove application traffic reaches the virtual server. Likewise, a healthy pool does not prove a client can reach the virtual address.
Guided lab
- Record the BIG-IP version, provisioned modules, license capabilities, and your lab network diagram.
- Start a simple application with a homepage, a search endpoint, and an application health endpoint.
- Create its pool member and a monitor matching the application's expected response.
- Create the lab virtual server with the appropriate HTTP processing and pool.
- For HTTPS, configure a certificate trusted by your lab client and the necessary SSL profiles.
- Arrange return routing. Use SNAT only when the design calls for it, rather than treating it as a universal fix.
- Resolve
books.example.testto the virtual IP using your lab DNS or a local test mapping. - Load the application through that hostname and record a baseline response before adding ASM protection.
Expected result: the homepage and search work through the virtual server, the pool is available, and your diagram explains both directions of traffic. No public exposure is needed.
If it does not work
Connection timeout: check client routing, network ACLs, the virtual address, and listener port. TLS error: examine certificate name, trust, and the TLS configuration. Unavailable service: check pool selection, member reachability, and monitor results. Request leaves BIG-IP but no response returns: inspect origin routing and whether the return path traverses BIG-IP.
A monitor can fail even while a server responds to a browser if the monitor uses a different host header, path, or expected response. Make the monitor represent service health deliberately.
Knowledge check
Is an available pool proof that ASM is protecting the application?
Instructor answer
No. It proves only the availability information represented by that pool's monitoring. Verify the client path, the correct virtual server, the attached policy, and actual ASM events separately.
Lab record: save your version, topology, baseline requests, and rollback notes. They will make the next lesson much easier.
Further reading
Independent educational material. Menus, defaults, and feature availability vary by BIG-IP release and license. Use the documentation for your installed version. Perform exercises only in your authorized lab. Examples and expected results are instructional; these labs have not been executed on a BIG-IP device for this blog.
Comments
Post a Comment