Product Documentation

lbparameter

Sep 07, 2016

Configuration for LB parameter resource.

Properties (click to see Operations)

Name Data Type Permissions Description
httponlycookieflag
<String>
Read-write
Include the HttpOnly attribute in persistence cookies. The HttpOnly attribute limits the scope of a cookie to HTTP requests and helps mitigate the risk of cross-site scripting attacks.
Default value: ENABLED
Possible values = ENABLED, DISABLED
usesecuredpersistencecookie
<String>
Read-write
Encode persistence cookie values using SHA2 hash.
Default value: DISABLED
Possible values = ENABLED, DISABLED
cookiepassphrase
<String>
Read-write
Use this parameter to specify the passphrase used to generate secured persistence cookie value. It specifies the passphrase with a maximum of 31 characters.
consolidatedlconn
<String>
Read-write
To find the service with the fewest connections, the virtual server uses the consolidated connection statistics from all the packet engines. The NO setting allows consideration of only the number of connections on the packet engine that received the new connection.
Default value: YES
Possible values = YES, NO
useportforhashlb
<String>
Read-write
Include the port number of the service when creating a hash for hash based load balancing methods. With the NO setting, only the IP address of the service is considered when creating a hash.
Default value: YES
Possible values = YES, NO
preferdirectroute
<String>
Read-write
Perform route lookup for traffic received by the NetScaler appliance, and forward the traffic according to configured routes. Do not set this parameter if you want a wildcard virtual server to direct packets received by the appliance to an intermediary device, such as a firewall, even if their destination is directly connected to the appliance. Route lookup is performed after the packets have been processed and returned by the intermediary device.
Default value: YES
Possible values = YES, NO
startuprrfactor
<Double>
Read-write
Number of requests, per service, for which to apply the round robin load balancing method before switching to the configured load balancing method, thus allowing services to ramp up gradually to full load. Until the specified number of requests is distributed, the NetScaler appliance is said to be implementing the slow start mode (or startup round robin). Implemented for a virtual server when one of the following is true:
* The virtual server is newly created.
* One or more services are newly bound to the virtual server.
* One or more services bound to the virtual server are enabled.
* The load balancing method is changed.
This parameter applies to all the load balancing virtual servers configured on the NetScaler appliance, except for those virtual servers for which the virtual server-level slow start parameters (New Service Startup Request Rate and Increment Interval) are configured. If the global slow start parameter and the slow start parameters for a given virtual server are not set, the appliance implements a default slow start for the virtual server, as follows:
* For a newly configured virtual server, the appliance implements slow start for the first 100 requests received by the virtual server.
* For an existing virtual server, if one or more services are newly bound or newly enabled, or if the load balancing method is changed, the appliance dynamically computes the number of requests for which to implement startup round robin. It obtains this number by multiplying the request rate by the number of bound services (it includes services that are marked as DOWN). For example, if the current request rate is 20 requests/s and ten services are bound to the virtual server, the appliance performs startup round robin for 200 requests.
Not applicable to a virtual server for which a hash based load balancing method is configured.
monitorskipmaxclient
<String>
Read-write
When a monitor initiates a connection to a service, do not check to determine whether the number of connections to the service has reached the limit specified by the service's Max Clients setting. Enables monitoring to continue even if the service has reached its connection limit.
Default value: DISABLED
Possible values = ENABLED, DISABLED
monitorconnectionclose
<String>
Read-write
Close monitoring connections by sending the service a connection termination message with the specified bit set.
Default value: FIN
Possible values = RESET, FIN
vserverspecificmac
<String>
Read-write
Allow a MAC-mode virtual server to accept traffic returned by an intermediary device, such as a firewall, to which the traffic was previously forwarded by another MAC-mode virtual server. The second virtual server can then distribute that traffic across the destination server farm. Also useful when load balancing Branch Repeater appliances.
Note: The second virtual server can also send the traffic to another set of intermediary devices, such as another set of firewalls. If necessary, you can configure multiple MAC-mode virtual servers to pass traffic successively through multiple sets of intermediary devices.
Default value: DISABLED
Possible values = ENABLED, DISABLED
allowboundsvcremoval
<String>
Read-write
This is used, to enable/disable the option of svc/svcgroup removal, if it is bound to one or more vserver. If it is enabled, the svc/svcgroup can be removed, even if it bound to vservers. If disabled, an error will be thrown, when the user tries to remove a svc/svcgroup without unbinding from its vservers.
Default value: ENABLED
Possible values = ENABLED, DISABLED
retainservicestate
<String>
Read-write
This option is used to retain the original state of service or servicegroup member when an enable server command is issued.
Default value: OFF
Possible values = ON, OFF
sessionsthreshold
<Double>
Read-only
This option is used to get the upper-limit on the number of persistent sessions set by the administrator for this system.
Minimum value = 1
builtin
<String[]>
Read-only
.
Possible values = MODIFIABLE, DELETABLE, IMMUTABLE, PARTITION_ALL

Operations (click to see Properties)

Some options that you can use for each operations:

  • Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:

    http://<netscaler-ip-address>/nitro/v1/config/login?warning=yes

    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:

    X-NITRO-USER:<username>

    X-NITRO-PASS:<password>

    Note: In such cases, make sure that the request header DOES not include the following:

    Cookie:NITRO_AUTH_TOKEN=<tokenvalue>

메모

Mandatory parameters are marked in red and placeholder content is marked in <green>.

update

URL: http://<netscaler-ip-address>/nitro/v1/config/lbparameter

HTTP Method: PUT

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue>
Content-Type:application/json

Request Payload:

{"lbparameter":{
      "httponlycookieflag":<String_value>,
      "usesecuredpersistencecookie":<String_value>,
      "cookiepassphrase":<String_value>,
      "consolidatedlconn":<String_value>,
      "useportforhashlb":<String_value>,
      "preferdirectroute":<String_value>,
      "startuprrfactor":<Double_value>,
      "monitorskipmaxclient":<String_value>,
      "monitorconnectionclose":<String_value>,
      "vserverspecificmac":<String_value>,
      "allowboundsvcremoval":<String_value>,
      "retainservicestate":<String_value>
}}

Response:

HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

unset

URL: http://<netscaler-ip-address>/nitro/v1/config/lbparameter?action=unset

HTTP Method: POST

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue>
Content-Type:application/json

Request Payload:

{"lbparameter":{
      "httponlycookieflag":true,
      "usesecuredpersistencecookie":true,
      "cookiepassphrase":true,
      "consolidatedlconn":true,
      "useportforhashlb":true,
      "preferdirectroute":true,
      "startuprrfactor":true,
      "monitorskipmaxclient":true,
      "monitorconnectionclose":true,
      "vserverspecificmac":true,
      "allowboundsvcremoval":true,
      "retainservicestate":true
}}

Response:

HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

get (all)

URL: http://<netscaler-ip-address>/nitro/v1/config/lbparameter

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue>
Accept:application/json

Response:

HTTP Status Code on Success: 200 OK
HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the error

Response Headers:

Content-Type:application/json

Response Payload:

{ "lbparameter": [ {
      "httponlycookieflag":<String_value>,
      "usesecuredpersistencecookie":<String_value>,
      "cookiepassphrase":<String_value>,
      "consolidatedlconn":<String_value>,
      "useportforhashlb":<String_value>,
      "preferdirectroute":<String_value>,
      "startuprrfactor":<Double_value>,
      "monitorskipmaxclient":<String_value>,
      "monitorconnectionclose":<String_value>,
      "vserverspecificmac":<String_value>,
      "sessionsthreshold":<Double_value>,
      "builtin":<String[]_value>,
      "allowboundsvcremoval":<String_value>,
      "retainservicestate":<String_value>
}]}