VIP to VIP communications on the same BigIP LTM

I am probably missing something here. Pool can't communicate with anything as pool is not IP object, it's just container for pool memebers which in turn has IP:port assigned. Still pool member is not something existing as an server on LTM it's just object allowing to direct traffic to some backend server outside LTM. So if: Pool members (DS1 & DS2) as defined on LTM are pointing to the same VIP of VS that a bit do not make sense, two pool members pointing to one IP:Port are not something that will LB any traffic as well as not possible to be configured as separate entities, there is no way to create two separate pool members with same IP:port. You can of course use given pool member in different pools but those will be instances of the same service (IP:port) by pool members (DS1 & DS2) you mean actual servers to which LTM is LB traffic and you need those servers to access another VIP (means another VS) on LTM that should be completely doable, you just need to enable those VS (that should be accessible to servers) on the VLAN where servers are connected (by default VS is enabled on all VLANs defined on LTM, so it should not be issue). In this case you will have flow looking something like that: Client traffic -> VIP (VS with pool containing DS1&DS2) -> DS1 server or DS2 server (based on LB decision inside pool) -> VIP (SG) -> SG1 or SG2 server (based on LB decision inside pool) Piotr