How to add generic SD-WAN device to GSLB

Follow the steps to add the generic SD-WAN device to GSLB.

1. Create FQDN in GSLB Services > Create FQDN Member > Create new Virtual Server Pool > Create new generic connector > Create new connector member (add Generic SD-WAN device IP).
2. The virtual server from the generic SD-WAN connector will be added into Pool and Connector directly and will work in GSLB Services.

Example solution

This example assumes the following:

• You have two ISP routers.
• The generic SD-WAN has two members for each ISP. The SD-WAN will do the out-going load balance for App1 (as shown on the right side of the diagram). But sometimes,the incoming traffic may come always from ISP2, which means that the ISP2 link is very busy while ISP1 link is very free.
• The GSLB can load balance the incoming traffic to ISP1 link and ISP2 link from the DNS level, thus solving this issue.

Steps:

1. Create FQDN App1-www.fsdwan.com in GSLB services.
2. Create FQDN member > Create new Virtual Server Pool ISP1-pool > Create new generic connector sdwandevice > Create new Connector member VIP1-ISP1. Add generic SD-WAN device Virtual IP App1 ISP1 Public IP 202.0.20.21 and enable health check Default_HLTHCK_HTTP.
3. Create FQDN member > Create new Virtual Server Pool ISP2-pool > Select Connector sdwandevice > Create new Connector member VIP2-ISP2. Add generic SD-WAN device Virtual IP App1 ISP2 Public IP 54.20.0.22 and enable health check Default_HLTHCK_HTTP).
4. The virtual server from the generic SD-WAN device will be added into Pool and Connector directly and will work in GSLB services.

Sample topology view of GSLB

We have added 2 pools to perform the load balancing and each pool has a VIP.

After completing these steps, the customer can monitor the App1 status for both ISP1 link and ISP2 link on the FQDN service detail page. The GSLB will load balance the traffic to two links. If one of the links is down, the GSLB will direct the traffic to the available link. If both of the links are down, the GSLB will direct the traffic to the App1 default server.