Configuring BIG IP Load Balancer: Monitoring with WSO2 ESB - PART - 2

Licensing the BIG-IP

F5 provides a trial license to use it for 90-Days. Please follow the below steps to license the product we have downloaded.

Below is the license key, which we have requested when we download the product.

Use the Registration key and paste it in Base Registration Key section and change the activation method to "Manual".

Then click Next. 

Then in the above screen copy the "Dossier" section and click and open the F5 Licensing Server Web page. Paste the copied dossier in the below screen.

Then copy the above license key and paste it under the license in below screen.

After clicking continue will get the below page.

Above screen check whether Local Traffic is enabled and then click Next. It will move to the below page where you can provide a host name and change the account passwords. 

Click Next.

Click Finished. 

Now you have successfully licensed the product.

Configuring a Monitor for a WSO2 ESB Service Port

Before doing configuration at the BIG IP, setup a wso2 esb and host a service. Follow the below steps for it.

1) Download a ESB pack from wso2 website and up it in your local environment.
2) In our sample we are going to monitor the service port 8243. You can see already in ESB there is a echo service running on this port.

Now we can do the configuration at the BIG-IP side. Go to Local Traffic -> Pools and click "Create".

Here we have Selected Default TCP Monitoring option and added the Node with service port 8243.

We can see from the above screen, that our service at port 8243 is up and running. To check whether monitoring working fine, try to shutdown the ESB and check the same screen. You can observe the below.

 Confirming the TCP Handshake using Wireshark

 To confirm that the monitoring requests taking place between ESB 8243 port and the Monitoring system in BIG-IP, we can do a wireshark capture at the 192.168.1.1 router.

Below is the default tcp configuration at BIG-IP product. The monitoring calls will be taken place every 5 seconds interval.

We can confirm this using the below wireshark capture.

References

[1] https://www.youtube.com/watch?v=hxmCUnrC1bU