-

Enable logging appflow flow information.

-

Backup load balancing method. Becomes operational if the primary load balancing method fails or cannot be used. Valid only if the primary method is based on either round-trip time (RTT) or static proximity.

-

Any comments that you might want to associate with the GSLB virtual server.

-

If the primary state of all bound GSLB services is DOWN, consider the effective states of all the GSLB services, obtained through the Metrics Exchange Protocol (MEP), when determining the state of the GSLB virtual server. To consider the effective state, set the parameter to STATE_ONLY. To disregard the effective state, set the parameter to NONE.

The effective state of a GSLB service is the ability of the corresponding virtual server to serve traffic. The effective state of the load balancing virtual server, which is transferred to the GSLB service, is UP even if only one virtual server in the backup chain of virtual servers is in the UP state.

boolean

When set to yes the GSLB Vserver state will be set to disabled.

When set to no the GSLB Vserver state will be set to enabled.

Note that due to limitations of the underlying NITRO API a disabled state change alone does not cause the module result to report a changed status.

-

Continue to direct traffic to the backup chain even after the primary GSLB virtual server returns to the UP state. Used when spillover is configured for the virtual server.

-

DNS record type to associate with the GSLB virtual server's domain name.

Default value: A

Possible values = A, AAAA, CNAME, NAPTR

-

List of bindings for domains for this glsb vserver.

-

Timeout, in minutes, for the GSLB site cookie.

-

Domain name for which to change the time to live (TTL) and/or backup service IP address.

-

TTL, in seconds, for all internally created site domains (created when a site prefix is configured on a GSLB service) that are associated with this virtual server.

Minimum value = 1

-

Time to live (TTL) for the domain.

-

Specify if the appliance should consider the service count, service weights, or ignore both when using weight-based load balancing methods. The state of the number of services bound to the virtual server help the appliance to select the service.

-

Load balancing method for the GSLB virtual server.

Default value: LEASTCONNECTION

Possible values = ROUNDROBIN, LEASTCONNECTION, LEASTRESPONSETIME, SOURCEIPHASH, LEASTBANDWIDTH, LEASTPACKETS, STATICPROXIMITY, RTT, CUSTOMLOAD

-

Include multiple IP addresses in the DNS responses sent to clients.

-

Name for the GSLB virtual server. Must begin with an ASCII alphanumeric or underscore _ character, and must contain only ASCII alphanumeric, underscore _, hash #, period ., space, colon :, at @, equals =, and hyphen - characters. Can be changed after the virtual server is created.

Minimum length = 1

-

IPv4 network mask for use in the SOURCEIPHASH load balancing method.

Minimum length = 1

string / required

The password with which to authenticate to the netscaler node.

string

Which protocol to use when accessing the nitro API objects.

float

310

Time in seconds until a timeout error is thrown when establishing a new session with Netscaler

string / required

The username with which to authenticate to the netscaler node.

string / required

The ip address of the netscaler appliance where the nitro API calls will be made.

The port can be specified with the colon (:). E.g. 192.168.1.1:555.

-

The persistence ID for the GSLB virtual server. The ID is a positive integer that enables GSLB sites to identify the GSLB virtual server, and is required if source IP address based or spill over based persistence is enabled on the virtual server.

Minimum value = 0

Maximum value = 65535

-

Use source IP address based persistence for the virtual server.

After the load balancing method selects a service for the first packet, the IP address received in response to the DNS query is used for subsequent requests from the same client.

-

The optional IPv4 network mask applied to IPv4 addresses to establish source IP address based persistence.

Minimum length = 1

boolean

If yes the module will save the configuration on the netscaler node if it makes any changes.

The module will not save the configuration on the netscaler node if it made no changes.

-

List of bindings for gslb services bound to this gslb virtual server.

-

Name of the GSLB service for which to change the weight.

-

Weight to assign to the GSLB service.

-

Protocol used by services bound to the virtual server.

-

Action to be performed if spillover is to take effect, but no backup chain to spillover is usable or exists.

-

Type of threshold that, when exceeded, triggers spillover. Available settings function as follows:

* CONNECTION - Spillover occurs when the number of client connections exceeds the threshold.

* DYNAMICCONNECTION - Spillover occurs when the number of client connections at the GSLB virtual server exceeds the sum of the maximum client (Max Clients) settings for bound GSLB services. Do not specify a spillover threshold for this setting, because the threshold is implied by the Max Clients settings of the bound GSLB services.

* BANDWIDTH - Spillover occurs when the bandwidth consumed by the GSLB virtual server's incoming and outgoing traffic exceeds the threshold.

* HEALTH - Spillover occurs when the percentage of weights of the GSLB services that are UP drops below the threshold. For example, if services gslbSvc1, gslbSvc2, and gslbSvc3 are bound to a virtual server, with weights 1, 2, and 3, and the spillover threshold is 50%, spillover occurs if gslbSvc1 and gslbSvc3 or gslbSvc2 and gslbSvc3 transition to DOWN.

* NONE - Spillover does not occur.

-

If spillover occurs, maintain source IP address based persistence for both primary and backup GSLB virtual servers.

-

Timeout for spillover persistence, in minutes.

Default value: 2

Minimum value = 2

Maximum value = 1440

-

Threshold at which spillover occurs. Specify an integer for the CONNECTION spillover method, a bandwidth value in kilobits per second for the BANDWIDTH method (do not enter the units), or a percentage for the HEALTH method (do not enter the percentage symbol).

Minimum value = 1

Maximum value = 4294967287

string

The state of the resource being configured by the module on the netscaler node.

When present the resource will be created if needed and configured according to the module's parameters.

When absent the resource will be deleted from the netscaler node.

-

Idle time, in minutes, after which a persistence entry is cleared.

Default value: 2

Minimum value = 2

Maximum value = 1440

-

Site selection tolerance, in milliseconds, for implementing the RTT load balancing method. If a site's RTT deviates from the lowest RTT by more than the specified tolerance, the site is not considered when the NetScaler appliance makes a GSLB decision. The appliance implements the round robin method of global server load balancing between sites whose RTT values are within the specified tolerance. If the tolerance is 0 (zero), the appliance always sends clients the IP address of the site with the lowest RTT.

Minimum value = 0

Maximum value = 100

-

Number of bits to consider, in an IPv6 source IP address, for creating the hash that is required by the SOURCEIPHASH load balancing method.

Default value: 128

Minimum value = 1

Maximum value = 128

-

Number of bits to consider in an IPv6 source IP address when creating source IP address based persistence sessions.

Default value: 128

Minimum value = 1

Maximum value = 128

boolean

If no, SSL certificates will not be validated. This should only be used on personally controlled sites using self-signed certificates.