Hi, Does anyone here deployed A10 AX as Link Load Balancer with GSLB inbound traffic server mode or subdomain mode? can you please share your running configuration as a reference.
FYI...LLB is an old term which A10 now calls it as Next Hop Load Distribution(NHLD) feature. See the instructions below as to how NHLD is deployed in inbound mode. FYI A10 can also support outbound mode.
When the Thunder appliance receives a client query for www.abc.com, the Thunder device responds with link VIPs 30.30.30.100 and 40.40.40.100, in round-robin fashion. If a link is down (for example, router 30.30.30.1), the Thunder appliance responds only with the up link (in this case, 40.40.40.100).
Configuration on Thunder device used to load balance server traffic at Site slb server Router1 30.30.30.1 slb server Router2 40.40.40.1 slb server server1 30.30.30.10 port 80 tcp slb server server2 40.40.40.10 port 80 tcp slb service-group http1 tcp member server1:80 slb service-group http2 tcp member server2:80 slb virtual-server ip1 30.30.30.100 port 80 tcp service-group http1 slb virtual-server ip2 40.40.40.100 port 80 tcp service-group http2 gslb protocol enable device Configuration on Thunder device used as GSLB controller Server Mode: slb virtual-server dns 20.20.20.100 port 53 udp gslb-enable Service IP: gslb service-ip ip1 30.30.30.100 port 80 tcp gslb service-ip ip2 40.40.40.100 port 80 tcp Site: gslb site link1 slb-dev local1 127.0.0.1 gateway 30.30.30.1 vip-server ip1 gslb site link2 slb-dev local2 127.0.0.2 gateway 40.40.40.1 vip-server ip2 Policy: gslb policy abc dns best-only dns server Zone: gslb zone abc.com policy abc service http www dns-a-record ip1 static dns-a-record ip2 static Global: gslb protocol enable controller gslb protocol status-interval 5
Comments
FYI...LLB is an old term which A10 now calls it as Next Hop Load Distribution(NHLD) feature. See the instructions below as to how NHLD is deployed in inbound mode. FYI A10 can also support outbound mode.
When the Thunder appliance receives a client query for www.abc.com, the Thunder device responds with link VIPs 30.30.30.100 and 40.40.40.100, in round-robin fashion. If a link is down (for example, router 30.30.30.1), the Thunder appliance responds only with the up link (in this case, 40.40.40.100).
Configuration on Thunder device used to load balance server traffic at Site
slb server Router1 30.30.30.1
slb server Router2 40.40.40.1
slb server server1 30.30.30.10
port 80 tcp
slb server server2 40.40.40.10
port 80 tcp
slb service-group http1 tcp
member server1:80
slb service-group http2 tcp
member server2:80
slb virtual-server ip1 30.30.30.100
port 80 tcp
service-group http1
slb virtual-server ip2 40.40.40.100
port 80 tcp
service-group http2
gslb protocol enable device
Configuration on Thunder device used as GSLB controller
Server Mode:
slb virtual-server dns 20.20.20.100
port 53 udp
gslb-enable
Service IP:
gslb service-ip ip1 30.30.30.100
port 80 tcp
gslb service-ip ip2 40.40.40.100
port 80 tcp
Site:
gslb site link1
slb-dev local1 127.0.0.1
gateway 30.30.30.1
vip-server ip1
gslb site link2
slb-dev local2 127.0.0.2
gateway 40.40.40.1
vip-server ip2
Policy:
gslb policy abc
dns best-only
dns server
Zone:
gslb zone abc.com
policy abc
service http www
dns-a-record ip1 static
dns-a-record ip2 static
Global:
gslb protocol enable controller
gslb protocol status-interval 5
Goodluck!
Genard