Virtual Server & Self IP's on the same IP subnet

No, it isn't a requirement. That said, you have to educate your upstream router about the virtual server addresses that are being hosted on your F5, and it's usually easier to do this if all addresses are in the same address range.

If you use HA solution there will be some limitation "BIG-IP objects configured on a different subnet than the self IP address do not send gratuitous ARP requests on failover". About this

Hi Robert & Vitaliy

Thanks for your reply is there any document that shows such setup... also your comment "you have to educate your upstream router" what does that mean what do i have to configure in my router for that...??? Also I need to understand one thing if the SELF IP and the VS are on different IP subnet then how the IP communication will happen... as what I understand is that for two different IP subnet to communicate there should be a layer-3 device in the middle. So my F5 is connected to the network on subnet A (self ip) it receives a IP Packets for VS (which is on subnet B) so how this will be translated or how wil it work I am getting confused here... can you explain a bit more pls..

Regards,

That mean you need to write appropriate route. For example:

1. Self IP is 10.10.10.1

    

2. VIP is 10.10.20.1

    

On router you must add route (cisco): ip route 10.10.20.1 255.255.255.255 10.10.10.1 it's mean that your VIP is behind Self IP.

For communicating 2 different subnets there must be Layer-3 device in front of your F5 device.

Hi Vitaliy,

I agree with you to add the host route as you have wonderfully shown in the above example but what is my concern is that will F5 work as a later-3 device to relay to packets coming to Self IP-10.10.10.1 to VIP IP-10.10.20.1 and how will it do that coz we have separated the two on the VLAN level which is layer-2.

Regards

I forget to point that VS must be on the same VLAN with Self IP. For example, 1. Self IP 10.10.10.1 on VLAN 10 and VIP IP-10.10.20.1 must be on VLAN 10. It works, I have such VS in my configuration. Here short explanation about it, at the beginning.