Citrix Systems, Inc.

Ravi Kondamuru

Josephine Suganthi

Murali Raja

Raghav Somanahalli Narayana

Anil N Shetty

Sergey Verzunov

Rishi Kaundinya Mutnuru

Sandeep Kamath

Abhishek Chauhan

Henk Bots

Youcef Laribi

Ratnesh Singh

Erik Brandsberg

The present solution allows users, such as administrators to configure slow start parameters for new services. These slow start parameters specify a rate at which requests should be given to a newly added or up service. The users can also chose to automatically increase the load in multiples of the chosen rate by specifying an increment interval. The services are given the configured rate for the interval, and once the interval is reached, the next multiple of the rate of requests is given. The increase of rate of requests is done automatically until an existing service request rate is reached. At that point in time this functionality is disabled and the existing and new services are treated the same.

Systems and methods for startup round robin enhancement

The present application is directed towards systems and methods for adaptive application provisioning for cloud services. An appliance deployed in a network as a gateway may be able to transparently monitor application activity in a cloud computing environment provided by one or more servers, including servers executed by virtual machines, bare-metal or non-virtual servers, or other computing devices. In some embodiments, the appliance may monitor one or more network metrics, including bandwidth usage, latency, congestion, or other issues; and/or may monitor application health or server or virtual machine statistics, including memory and processor usage, bandwidth usage, latency, or other metrics. Responsive to one or more metrics exceeding a threshold, the appliance may automatically provision or start, or deprovision or shut down, one or more virtual or physical machines from a cloud service provider, and may provide configuration information to the provisioned or started machines as needed.

Systems and methods for adaptive application provisioning

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.

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

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.

Systems and methods for managing domain name system security (DNSSEC)

A centralized configuration of a Global Server Load Balancing (GSLB) site hierarchy may be batched across a plurality of appliances in a multi-site deployment. A single GSLB site hierarchy configuration may be distributed and operated on each appliance at each site. This reduces the configuration maintained for the multi-site deployment. Furthermore, in this manner, each appliance across multiple sites has an understanding of the entire topology of the multi-site deployment. Responsive to this configuration and understanding, each appliance may perform and optimize operations according to the site topology. For example, the appliances may selectively determine which sites to establish connections with in order to share metrics. In another example, appliances may select which remote sites to monitor services according to the topology.

Systems and methods for batchable hierarchical configuration

Centralized system for synchronizing a Global Server Load Balancing (GSLB) site hierarchy across a plurality of appliances in a multi-site deployment. With synchronization, differences in configurations across appliances may be determined and changes to configurations may automatically be distributed and applied on each appliance at each site to operate all the sites with a common single GSLB site hierarchy configuration. This reduces the challenging in configuration maintenance for the multi-site deployment.

Systems and methods for GSLB auto synchronization

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.

Systems and methods for GSLB site persistence

Described are methods and systems for managing the connections between a client, an intermediary appliance and a server, so that asynchronous messages can be transmitted over HTTP from the server to a client. When a connection is established between a client and an intermediary, and the intermediary and a server to establish a logical client-server connection, that logical client-server connection is labeled and not maintained, while the connection between the client and the intermediary is maintained. Messages generated by the server and destined for the client are transmitted to the intermediary along with the connection label. The intermediary can then use the connection label to determine which client should receive the message.

Systems and methods for connection management for asynchronous messaging over HTTP

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.

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.

In a method and appliance for determining responsiveness of a service via a particular protocol, a device intermediary to a plurality of clients and a plurality of services determines response times from each of a plurality of services to respond to requests via a first type of protocol of a plurality of protocols. The device calculates an average response time for the first type of protocol from each of the response times of the plurality of services. The device establishes a predetermined threshold for which a response time of a service for the first type of protocol may deviate from the average response time. The device identifies a service as available responsive to determining that a deviation of the response time of the service from the average response falls within the predetermined threshold.

Method and appliance for using a dynamic response time to determine responsiveness of network services

The present invention provides improvements to the integration between a metric exchange protocol and a monitoring mechanism supporting load balancing by a Global Server Load Balancing (GSLB) appliance in a GSLB hierarchy of appliances, using a method for triggering a monitor on a remote service. The method includes receiving, by a first appliance, metrics of a second appliance via a metric exchange connection between the first and second appliances. The first appliance includes a GSLB service and identifies a service provided via the second appliance as a remote service for GSLB. The first appliance may identify via the metrics that a state of the service is up, and determine that the metric exchange connection is down. Responsive to the determination, the first appliance may trigger a monitor to monitor the status of the service. Further, the first appliance may obtain via the monitor a second status of the service.

Systems and methods for GSLB remote service monitoring

Systems and methods for load balancing services based on fewest connections by decreasing granularity of service selection as a number of fewest connections serviced by the services increases may include establishing, by an appliance, a set of identifiers corresponding to a number of connections serviced by a service, the set comprising a first plurality of identifiers each identifying a predetermined number of connections and a second plurality of identifiers each identifying a predetermined range of numbers of connections. The appliance assigns, to each service servicing connections, an identifier corresponding to the number of connections serviced by the service, at least one of the identifiers selected from the second plurality of identifiers. The appliance receives a request for a service, and forwards the request to a service assigned to the identifier corresponding to a fewest number of connections with at least one service assigned to the identifier.

Systems and methods for efficiently load balancing based on least connections

In a method and appliance for using a dynamic response time to determine responsiveness of one or more network services on a server, a monitor determines a response time for each of one or more network services. The monitor establishes an average response time based on the determined response time for each of the one or more network services. The monitor associates with the established average response time a predetermined threshold for which the response time of the one or more network services may deviate from the average response time and maintain an indication of responsiveness. The monitor monitors the response time of the one or more network services to one or more requests. The monitor determines that the response time of the one or more network services deviates from the average response time by the predetermined threshold. The monitor indicates that the one or more network services are unavailable.

Growing community of inventors

Santa Clara, CA, United States of America

Ravi Kondamuru