Forum Discussion
iRule on GTM to allow a specific IP to a specific node
- Feb 04, 2017
You need to understand it would never be the Client IP's which would be querying for Wide IP instead it would be the DNS servers from clients which will be querying for the wide IP.
You can choose Topology based loadbalancing and try specific DNS Server to land go to specific DC, if you are sure about the DNS Servers configured on the clients.
But again you want specific Source IP to talk to specific Server, hence best would be if possible to put all 4 server in a single pool and attach it to both the VIP's on LTM's and then put an i-rule which forces specific Source IP to talk to specific node.
This approach would rule out GTM from the journey let GTM send to any of the DC and irule logic on the LTM takes care of the requirement.
You need to understand it would never be the Client IP's which would be querying for Wide IP instead it would be the DNS servers from clients which will be querying for the wide IP.
You can choose Topology based loadbalancing and try specific DNS Server to land go to specific DC, if you are sure about the DNS Servers configured on the clients.
But again you want specific Source IP to talk to specific Server, hence best would be if possible to put all 4 server in a single pool and attach it to both the VIP's on LTM's and then put an i-rule which forces specific Source IP to talk to specific node.
This approach would rule out GTM from the journey let GTM send to any of the DC and irule logic on the LTM takes care of the requirement.
You can certainly use static persist to increase the chances.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com