Scribd
Upload
20 views40 pages

Load Balancing WebSphere with BIGIP

LB

Uploaded by

Akash Mhetre
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
20 views40 pages

Load Balancing WebSphere with BIGIP

LB

Uploaded by

Akash Mhetre
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

Load Balancing WebSphere with BigIP (F5) in VMware Workstation

Lab topology
VMware workstation 17.

Networks configurations:

1. Auto Bridge for Management access (F5 console) – IP address 192.168.1.100

2. Custom Vmnet1 for External client vm – IP address 100.1.1.0

3. Custom Vmnet2 for internal WAS/Webserver vms - 200.1.1.0 (Rocky Linux servers)

Install VMware 17 with default option and open with Admin privileges
Open network editor go to Edit -> Virtual Network Editor
Delete default networks apart bridged network(vmnet0)

Create new networks as below. (Do not change anything)

Vmnet1 – host only – subnet ip 100.1.1.0 – for external

Vmnet2 – host only – subnet ip 200.1.1.0 for internal


Sign up in F5 and download BigIP VE LTM
Activate f5 account by logging into outlook
Launch VMware workstation and open the BIGIP OVA
Delete the “Network Adapter 4”

Update “Network Adapter 2 “ with vmnet1 and “Network Adapter 3 “ with vmnet2
Start VM and set up Management IP – 192.168.1.100
Login with default credentials root/default and change password

Execute “config” command to setup


Click No and edit IP address Manually 192.168.1.100
Activate with License.

Log into f5 console https://192.168.1.100 and log in with user “admin” and password last time changed

Change the password


Set up utility and active trail license

Registration keys will come to our email once trail is approved also we can see the keys in myf5 account
Click Next and follow screens
Click on Next

Click Next and Update hostname as bigipf5test.com, Time Zone and change root password
Click Next

Click on Finished
Setup External and Internal VLANs

Click on Network on Left Navigation

Click on Create

Give Name External-vlan and Interfaces 1.1 Untagged


Click on Finished and create again for internal
Click on Finished

Create Self IP for External and Internal by Navigating Network -> Self IPs

Click On create and Enter details

Name: External-Self-IP, Ip address: 100.1.1.100, Net Mask : 255.255.25.0 and Select External-VLan
Click on Finished and create for Internal Vlan

Click On Finished

Test the Self IPs connectivity from F5 (ping ips from console)
Create WebSphere/Webserver Nodes

Navigate to “Local traffic”


Click on Create and give the below details (IBM HTTP Servers IP addresses)

Name: Server-1 , Address 200.1.1.10


Click on Finished and create another Node
Create Pool by navigating in Local traffic

Click on Create and provide the details

Name: WebspherePool,

Health Monitor : http

“New Members” section add existing 2 nodes from “Node List”


Create A virtual Server in External network cidr 100.1.1.150
Details

Name: Was-VS-1

Source Address Empty

Destination Address: 100.1.1.150

Service Port : 80
Default Pool : WebSpherePool

Click On Finished

Virtual Server, Pool and Nodes are down because IBM HTTP servers are not configured the IP addressed and not
started

Configure 200.1.1.10 and 200.1.1.20 in IBM Http server nodes

Open the VM and map the Network adapter vmnet2 (Internal) to them
Resume/Start and change the IP address

Click On Network
And Move to IPV4 Tab and update the details
Make Sure Internal Self IP should pingable from Nodes

And restart the VM, start IBM HTTP Server and WAS

Similarly change in Second Node and Start WAS services.

Now the pool turned into Green Status


We need a VM in External Network to test the connectivity. I have Windows 10 in external LAN

Let’s add required IP address

Network Adapter should

be vmnet1 and Manually set

IP address: 100.1.1.20

Netmask: 255.255.255.0

Gateway: 100.1.1.100
Click on Change your network Settings

Click on IP V4 properties
Open the Virtual Server IP address from Windows 10
Ty,

You might also like