Forum Discussion
NimbostratusGTM IP geolocation database issue
Hi ,
We have 2 DCs (216.x.x.x and 66.x.x.x) with 1 GTM each. We tried to use Topology Records (both at pool and WideIp level) to direct traffic to a wide-ip "mycompany.net" based on the Geolocation of the LDNS .This is not working and traffic is not being load-balanced as designed. Due to which every request is being sent to 66.x.x.x DC .
Upon debugging i have found that the GTM's default IP geolocation database is resolving both subnets 66.x.x.x and 216.x.x.x to the same geographical area i.e. DC1 .
Has anyone seen this issue before ?
Is there a way to modify the Geo Database or make the GTM to Load Balance traffic as required?
Thanks, Manish.
2 Replies
MK04_258228GTM version : 11.5.3 HF1
Vijay_ECirrus
Have you tried looking up using the geolocation db in the F5: https://support.f5.com/kb/en-us/solutions/public/15000/000/sol15042.html
Have you tried to update the F5 geolocation db: https://support.f5.com/kb/en-us/solutions/public/11000/100/sol11176.html
