Forum Discussion
5 Replies
- JinshuCirrus
Sorry, I didn't understand that question.
Are you trying to connect to a virtual server from another Virtual server on different bigip?
Regards, Jinshu
You can create a policy where the target is a vip
- P_KAltostratus
You can create 2 VIPs and one pool. See below
If you just need a redirect from VIP1 to VIP2, you can use a irule or LTM policy.
Hope this make sense!
- brad_11480Nimbostratus
I'm looking for the same or similar solution.
It seems that you can only define one IP address for a virtual server.
Now mentioned above is to 'redirect' VIP1 to VIP2.. If you are thinking browser redirect or something, that isn't viable. I'm thinking of resourcing VIP1 to VIP2..
There is a 'virtual' irule command, but I'm not clear that will do it.
Other idea mentioned above is to have VIP2 as the pool for VIP1. How to minimize or standardize the virtual server configuration for VIP2 allowing the 'bulk' of the details (and Irules and SSL termination if needed, etc.) to be all on VIP1.
Worst case is to have to replicate the VIP1 configuration details in VIP2.. two matching virtual servers with the only difference being the IP address.
Very interested in good ways to accomplish this..
Thanks.
- brad_11480Nimbostratus
seems an irule that would do it is:
ltm rule /Common/rule_switch_vs { when CLIENT_ACCEPTED { virtual vs_mychart_https } }
and use it:
ltm virtual /Common/vs_VIP1 { destination /Common/10.10.10.1:0 ip-protocol tcp mask 255.255.255.255 profiles { /Common/fastL4 { } } rules { /Common/rule_switch_vs } source 0.0.0.0/0 translate-address enabled translate-port disabled }