Solved: f5 ELB load balancer does not load balance with ip... - Page 2

sjm2000 · 12-14-2016 12:44 PM

We are having a strange problem , which you might have encountered

Below is our quality default host having public dns also api.qa.**** .

The setup is a 5 node private cloud with 2 routers- routers being 1*.**.***.105 and 1*.**.***..100.

The f5 load balancer is load balancing between 1*.**.***.105:9001 and 1*.**.***.100:9001

Strangely enough

From intranet:

a) curl -X GET 1*.**.***.100:9001 -h internaldns works fine

b) curl -X GET internaldns:9001 works fine

c) curl -X GET 1*.**.***..100:9001 gives 404

From public Internet

We are getting 404 error code for all api's.

d) ELB is in DMZ and it will load balance between both the ip address of router.

My assumption is due to the ip address which ELB sees , its getting 404 error code.

Load balancer is f5.

Do you have any suggestions how to resolve this? I am sure this scenario is nothing new in apigee.

Regards

Sujith Mathew

Report Inappropriate Content

hmm...

An f5 load balancer - if im not mistaken - will use the API address and PORT (aka 10.3.244.100:9001) to route traffic - so this is sort of consistent if you cannot call that address directly.

I assume you are seeing the same behavior against BOTH servers? If you are great. If not, dont forget to check out what load balancing algo you are using. Least connections is a nasty foe sometimes.

Maybe you should re-set the host aliases and double check that you dont have any evil windows characters in the strings? in THEORY this should not impact a JSON or XML put but it might be worth checking.

If you are 16.x you might need to get some support insight into whats going on with the router.

View solution in original post

f5 ELB load balancer does not load balance with ip address