Virtual Server IP address on F5 not accessible outside of the F5 itself???
I have two Lab F5 running in AWS as prototype lab. The 1st F5 which I am calling the external F5 currently can route http to an inner web server which goes through to a app server and I have this setup up for a couple of applications/services. Now I have built the 2nd F5 as an internal F5, so this internal F5 I am looking to use as an internal load balancer for app traffic. I have set up virtual servers and monitors which all work ok on this F5 outbound to the app layer. The issue I have is that the virtual server IP addresses I have defined are NOT accessible outside of this internal F5?? I have several subnets setup within AWS and the internal F5 has an interface on a subnet for incoming traffic from the external F5 (10.0.6.x) and an interface on the application subnet (10.0.2.x). So for example, the external i/f is 10.0.6.222 for the internal F5, I defined a virt server on this F5 at 10.0.6.224 which connects up to a back end app server (say 10.0.2.118) ok - i.e. i have a monitor associated to the pool member for this vs which is GREEN. Yet on another server on the SAME 10.0.6.x subnet I can't ping the 10.0.6.224 ... but I can the 10.0.6.222 address. From the external F5 I also can ping the 10.0.6.222 address but not the 10.0.6.224... ?!?!? There must be something obvious which is causing this but I can't for the life of me figure out what? The external F5 has a similar setup yet I can ping the ip addresses of the virtual servers defined on this F5 ok... Both F5s are running Version 11.5.4 Any suggestions of where to look for resolving this??? Many thanks Neil