Abstract: The present invention provides maintains site persistence in a hierarchical Global Server Load Balancing (GSLB) deployment. Via configuration of GSLB services locally and remotely on each of the GSLB appliances and LB appliances at a site, a site appliance identifies and associates requests from the GSLB with the site. Furthermore, the site appliance may receive a GSLB cookie with the client request and confirms the request is from the expected GSLB in the site hierarchy. When the load balancers receives a response from a server, the appliance may include the GSLB cookie with the response back to the client. The appliance may also include an LB cookie to identify the server selected by the LB. When the client sends another request, the request may include the GSLB and LB cookie.

Abstract: The present invention is directed towards systems and methods for spillover threshold management in a multi-core system. A pool manager divides the spillover threshold limit of connections for vServers into an exclusive quota pool and a shared quota pool. Each vServer operating on a core is allocated an exclusive number of connections from the exclusive quota pool. If a vServer wishes to create connections beyond its exclusive number, the vServer can borrow from the shared quota pool. When the vServers are using at least a first predetermined threshold of their exclusive number of connections and the number of available connections in the shared quota pool has reached a second predetermined threshold, the multi-core system establishes a backup vServer.

Abstract: The present invention is directed towards systems and methods for monitoring services in a multi-core system. The systems and methods distribute the monitors for a service and the ownership of a service across the cores of the multi-core device. The greater resources of the multi-core device process the workload of the monitors for the services and the workload for monitoring the states of the services more efficiently than a single packet engine on a core.

Abstract: The present disclosure presents systems and methods for obtaining metric information by a multi-core GSLB intermediary device and providing global server load balancing services using the obtained information. A first core of a multi-core GSLB appliance establishes a transport layer connection to a remote load balancer at a site of a plurality of sites. The first core transmits a message to each of the other cores of the multi-core GSLB appliance that the first core is a master core for receiving metric information from the load balancer. The first core receives metric information of the remote site from the load balancer. The first core propagates the metric information to each of the other cores of the GSLB appliance. A GSLB virtual server on a slave core receives a DNS request. The GSLB virtual server determines a DNS resolution for the DNS request based on the metric information.

Abstract: The present invention is directed towards systems and methods for spillover threshold management in a multi-core system. A pool manager divides the spillover threshold limit of connections for vServers into an exclusive quota pool and a shared quota pool. Each vServer operating on a core is allocated an exclusive number of connections from the exclusive quota pool. If a vServer wishes to create connections beyond its exclusive number, the vServer can borrow from the shared quota pool. When the vServers are using at least a first predetermined threshold of their exclusive number of connections and the number of available connections in the shared quota pool has reached a second predetermined threshold, the multi-core system establishes a backup vServer.

Abstract: The present disclosure presents systems and methods for obtaining metric information by a multi-core GSLB intermediary device and providing global server load balancing services using the obtained information. A first core of a multi-core GSLB appliance establishes a transport layer connection to a remote load balancer at a site of a plurality of sites. The first core transmits a message to each of the other cores of the multi-core GSLB appliance that that the first core is a master core for receiving metric information from the load balancer. The first core receives metric information of the remote site from the load balancer. The first core propagates the metric information to each of the other cores of the GSLB appliance. A GSLB virtual server on a slave core receives a DNS request. The GSLB virtual server determines a DNS resolution for the DNS request based on the metric information.

Abstract: The present invention provides maintains site persistence in a hierarchical Global Server Load Balancing (GSLB) deployment. Via configuration of GSLB services locally and remotely on each of the GSLB appliances and LB appliances at a site, a site appliance identifies and associates requests from the GSLB with the site. Furthermore, the site appliance may receive a GSLB cookie with the client request and confirms the request is from the expected GSLB in the site hierarchy. When the load balancers receives a response from a server, the appliance may include the GSLB cookie with the response back to the client. The appliance may also include an LB cookie to identify the server selected by the LB. When the client sends another request, the request may include the GSLB and LB cookie.

Abstract: The present disclosure is directed towards systems and methods for global server load balancing spillover. An intermediary device providing global server load balancing (GSLB) identifies a spillover threshold for a first GSLB virtual server of the intermediary device. The first GSLB virtual server resolving DNS requests to a remote site of a plurality of remote sites. The intermediary device monitors spillover related statistics of each of a plurality of services at the plurality of remote sites, establishes a first spillover aggregate statistic for the plurality of services, determines that the first spillover aggregate statistic exceeds the spillover threshold for the first GSLB virtual server, and receives a DNS request and directing the DNS request to a second GSLB virtual server of the intermediary device responsive to the determination.

Abstract: The present application relates to systems and methods for managing of Real Time Stream Protocol (RTSP) sessions by an intermediary located between a client and a server. An intermediary located between a client and a server receives a response from the server to a request of the client to setup a media stream. The response may include a first session identifier established by the server. The intermediary may encode a port of the server and an internet protocol address of the server into the first session identifier to form a second session identifier. The intermediary may modify the response to identify the second session identifier as the session identifier provided by the server. The intermediary may transmit the modified response to the client responsive to the request of the client to setup the media stream.

Abstract: The present invention provides systems and methods for maintaining site persistence in a hierarchical Global Server Load Balancing (GSLB) deployment. Via configuration of GSLB services locally and remotely on each of the GSLB appliances and LB appliances at a site, a site appliance identifies and associates requests from the GSLB with the site. Furthermore, the site appliance may receive a GSLB cookie with the client request and confirms the request is from the expected GSLB in the site hierarchy. When the load balancers receives a response from a server, the appliance may include the GSLB cookie with the response back to the client. The appliance may also include an LB cookie to identify the server selected by the LB. When the client sends another request, the request may include the GSLB and LB cookie. With this information, the GSLB and LB appliance may maintain site persistence for the client as well as server persistence at the site.

Abstract: The present invention is directed towards systems and methods for global server load balancing spillover. An intermediary device providing global server load balancing (GSLB) identifies a spillover threshold for a first GSLB virtual server of the intermediary device. The first GSLB virtual server resolving DNS requests to a remote site of a plurality of remote sites. The intermediary device monitors spillover related statistics of each of a plurality of services at the plurality of remote sites, establishes a first spillover aggregate statistic for the plurality of services, determines that the first spillover aggregate statistic exceeds the spillover threshold for the first GSLB virtual server, and receives a DNS request and directing the DNS request to a second GSLB virtual server of the intermediary device responsive to the determination.

Abstract: The present invention is directed towards systems and methods for providing dynamic proximity load balancing via a multi-core intermediary device. An intermediary device providing global server load balancing (GSLB) identifies a local domain name service (LDNS) entries database and assigns each LDNS entry in the LDNS entries database to one of the plurality of packet processing engine base on a source internet protocol (IP) address of each LDNS entry. The first packet processing engine on the appliance receives a LDNS request for an IP address, determines that the LDNS entry for the IP address is assigned to a second packet processing engine of the plurality of packet processing engines, transmits a request to the second packet processing engine for the LDNS entry for the IP address, and determines a response to the LDNS request based on the LDNS entry for the IP address received from the second packet processing engine.

Abstract: The present application relates to systems and methods for managing of Real Time Stream Protocol (RTSP) sessions by an intermediary located between a client and a server. An intermediary located between a client and a server receives a response from the server to a request of the client to setup a media stream. The response may include a first session identifier established by the server. The intermediary may encode a port of the server and an internet protocol address of the server into the first session identifier to form a second session identifier. The intermediary may modify the response to identify the second session identifier as the session identifier provided by the server. The intermediary may transmit the modified response to the client responsive to the request of the client to setup the media stream.

Abstract: The present invention is directed towards systems and methods for providing multiple modes of a zone for DNSSEC by an intermediary device. The method includes providing, by a device intermediary to a plurality of clients and a plurality of servers, a plurality of modes of a zone for Domain Name Service. The device receives a selection of a first mode of the zone of the plurality of modes of the zone. The device receives information identifying to enable DNS Security for the selected first mode. The device establishes the zone for DNS in accordance with the selected first mode and with DNS Security enabled.

Abstract: The present application relates to systems and methods for managing of Real Time Stream Protocol (RTSP) sessions by an intermediary located between a client and a server. An intermediary located between a client and a server receives a response from the server to a request of the client to setup a media stream. The response may include a first session identifier established by the server. The intermediary may encode a port of the server and an internet protocol address of the server into the first session identifier to form a second session identifier. The intermediary may modify the response to identify the second session identifier as the session identifier provided by the server. The intermediary may transmit the modified response to the client responsive to the request of the client to setup the media stream.

Abstract: The present application is directed towards systems and methods for systems and methods for handling real-time streaming protocol sessions by an intermediary multi-core system. When a multi-core intermediary receives a setup request for a real-time streaming protocol session, the intermediary processes and forwards the request to a server providing the streaming media. The server sets up an RTSP session and transmits a session identification to the multi-core intermediary. A core of the intermediary receives the transmitted session identification and determines an owner core of the session, based on a hash of the session identification. The core transmits the session information to the determined owner core, which selects two consecutive ports on which to establish listening services. The owner core then notifies all other cores to establish listening services on the same consecutive ports, such that any core that receives an RTSP control message from a client can handle it properly.

Abstract: The present invention is directed towards systems and methods for providing dynamic proximity load balancing via a multi-core intermediary device. An intermediary device providing global server load balancing (GSLB) identifies a local domain name service (LDNS) entries database and assigns each LDNS entry in the LDNS entries database to one of the plurality of packet processing engine base on a source internet protocol (IP) address of each LDNS entry. The first packet processing engine on the appliance receives a LDNS request for an IP address, determines that the LDNS entry for the IP address is assigned to a second packet processing engine of the plurality of packet processing engines, transmits a request to the second packet processing engine for the LDNS entry for the IP address, and determines a response to the LDNS request based on the LDNS entry for the IP address received from the second packet processing engine.

Abstract: The present invention is directed towards systems and methods for global server load balancing spillover. An intermediary device providing global server load balancing (GSLB) identifies a spillover threshold for a first GSLB virtual server of the intermediary device. The first GSLB virtual server resolving DNS requests to a remote site of a plurality of remote sites. The intermediary device monitors spillover related statistics of each of a plurality of services at the plurality of remote sites, establishes a first spillover aggregate statistic for the plurality of services, determines that the first spillover aggregate statistic exceeds the spillover threshold for the first GSLB virtual server, and receives a DNS request and directing the DNS request to a second GSLB virtual server of the intermediary device responsive to the determination.

Abstract: The present disclosure presents systems and methods for obtaining metric information by a multi-core GSLB intermediary device and providing global server load balancing services using the obtained information. A first core of a multi-core GSLB appliance establishes a transport layer connection to a remote load balancer at a site of a plurality of sites. The first core transmits a message to each of the other cores of the multi-core GSLB appliance that that the first core is a master core for receiving metric information from the load balancer. The first core receives metric information of the remote site from the load balancer. The first core propagates the metric information to each of the other cores of the GSLB appliance. A GSLB virtual server on a slave core receives a DNS request. The GSLB virtual server determines a DNS resolution for the DNS request based on the metric information.

Abstract: The present invention is directed towards systems and methods for handling limit parameters for multi-core systems. A pool manager divides the limited number of uses of a resource into an exclusive quota pool and a shared quota pool. Each packet processing engine operating on a core is allocated an exclusive number of uses of the resource from the exclusive quota pool. If a packet processing engine wishes to use the resource beyond its exclusive number, the packet processing engine must borrow from the shared quota pool.