The F5 BIG-IP hardware line is fairly amazing so needless to say I was really excited to find out that there was a VMware image and VirtualBox image available to trial. This allows people not only to check out the BIG-IP software, which is built on top of CentOS Linux, but also the ability to easily test configurations. Below I describe the process all the way from downloading the actual VMware image and launching the image in VMware Player to logging into the BIG-IP LTM VE instance and enabling the trial license.
One of the requirements for initial configuration of the F5 BIG-IP LTM VE is to enter a license key. In this example we are configuring a BIG-IP LTM VE VMware image 90 day trial for testing. The way to accomplish this task is first login to the console using these instructions, next login to the BIG-IP LTM VE GUI using these instructions, and then follow the steps below which will walk you through activating the F5 BIG-IP LTM VE trial using the license key that was emailed to you by F5.
Yesterday I wrote an article relating to logging into the F5 BIG-IP LTM VE VMware image console using the default username and password however some people may prefer to perform their configurations using the BIG-IP LTM VE GUI which has a different default user and password. First you will need to locate the IP address of he BIG-IP LTM instance from the console and then you can type that IP address into your favorite web browser to then login as explained in more detail below. Please also note the supported web browser versions below for BIG-IP LTM version 10.1.
Recently I have started working a lot more with various F5 hardware including BIG-IP LTM’s or BIG-IP Local Traffic Managers. F5 provides a VMware image so you can have a test environment running as a virtual machine. This is a great place to complete testing, example configurations, etc. Once you start the F5 BIG-IP LTM VE virtual machine you will need to login with the default username and password which is noted below along with screenshots so you can ensure you are logging in via the correct console prompt.