Systems and methods for GSLB MEP connection management across multiple core appliances

A system of obtaining metric information by a multi-core intermediary device for providing global server load balancing, the system comprising:

• a first core of a plurality of cores of a first intermediary device providing global server load balancing (GSLB) to a plurality of remote sites, establishing a first transport layer connection to a second intermediary device providing services to a first remote site of the plurality of remote sites and transmitting a message to each of the other cores of the plurality of cores of the first intermediary device that the first core is a master core for receiving metric information from the second intermediary device,
• wherein the first core receives, via the first transport layer connection, the metric information of the remote site from the second intermediary device and propagates the metric information to each of the other cores of the plurality of cores, each of the cores storing the metric information, the metric information comprising site metrics for the first remote site managed by the second intermediary device, the site metrics comprising a list of internet protocol addresses and corresponding domain names;
• a GSLB virtual server executing on a second core of the plurality of cores of the first intermediary device receiving a domain name (DNS) request for a domain name, the domain name corresponding to the first remote site, and determining a DNS resolution to an internet protocol address corresponding to the domain name of the first remote site of the plurality of remote sites for the DNS request based on the list of IP address and corresponding domain names of the metric information stored on the second core.

A method of obtaining metric information by a multi-core device for resolving a domain name service (DNS) request, the method comprising:

• (a) establishing, by a first core of a plurality of cores in a multi-core device, a first transport layer connection via a network to a second device in communication with a plurality of remote devices;
• (b) transmitting, by the first core of the first intermediary device, a core-to-core message to each of the other cores of the plurality of cores in the multi-core device, the core-to-core message identifying that the first core is designated a master core for the multi-core device for receiving metric information from the second device;
• (c) receiving, by the first core over the network via the first transport layer connection from the second device, metric information on the plurality of remote devices to which the multi-core device may resolve a domain name service (DNS) request;
• (d) transmitting, by the first core of the first intermediary via core-to-core messaging, the metric information received via the first transport layer connection from the second device to each of the other cores of the plurality of cores in the multi-core device, each of the cores storing the metric information, the core-to-core message comprising a transfer of data via a bus communicatively coupled between the plurality of cores;
• (e) receiving, by a second core of the multi-core device from a client, a domain name service (DNS) request;
• and
• (f) determining, by the second core, a remote device from the plurality of remote devices to provide as a DNS resolution to the DNS request based on the metric information stored on the second core and received by the second core from the first core via a core-to-core message and received by the first core over the transport layer connection via the network from the second device.