GSLB Policy – internal VIP, keep folks local

Community Forum Forums Thunder and AX Series General GSLB Policy – internal VIP, keep folks local


This topic contains 1 reply, has 2 voices, and was last updated by avatar Anonymous 3 weeks, 5 days ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #16572

    Here’s what our server folks are asking me …

    We will have 2 internal access only VIPs in each of 3 sites: and The VIPs are for internal user access to OWA (2016 Exchange). A10 has a nice doc on setting up a single site for Exchange 2016. We will have 3 sites with a couple hundred users at each site. GSLB should be pretty standard across all 3 sites but we would prefer to keep folks hitting their local VIP if possible and only go across the wire internally if the local site is down. Each site has a definitive IP range. We will delegate the sub-domains and to the a10s and the default A records will be the VIPs at each site.

    What do you think is the best way to accomplish this?


    Assuming you have multiple A10 Thunders, you can define your gslb sites with different priorities, such that the site closest to each Thunder gets the higher priority, and thus sends the users there.

    So, for example: Site1 is setup like so:
    glsb site Site1
    admin-preference 200
    slb-dev site1-10.x.x.x 10.x.x.x
    vip-server VS-10.x.x.x

    gslb site Site2
    admin-preference 180
    slb-dev site2-10.x.x.x 10.x.x.x
    vip-server VS-10.x.x.x

    At Site2, the admin-preference value are reversed.

    Make sense?

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Comments are closed.