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.
Earlier today while responding to a comment in an older article I requested that the person leaving the comment provide information to show what repositories were enabled in YUM. I figured printing out the configured YUM repositories could be useful to others so below is an example command and example output to display what YUM repos are configured on a CentOS Linux server.
I have been using the Amazon Machine Tags WordPress plugin on numerous sites for a long time and have been happy with the results up until the last couple of months. I believe that Amazon has made some changes to their API over the last year or so and it has caused a lot of issues with the Amazon Machine Tags plugin. I even wrote this article in mid February discussing a work around that would allow the Amazon Machine Tags plugin to continue working until the developer was able to make some changes. Since that time I have been monitoring my posts to see if the Amazon products are always displaying and unfortunately even with the fix mentioned in the February article items were still not displaying at all times. Below I noted an alternative that provides solid functionality.