Skip to content

lbmonbindings

Configuration for monitro bindings resource.

Properties

(click to see Operations )

Name Data Type Permissions Description
monitorname <String> Read-write The name of the monitor.

Minimum length = 1
type <String> Read-only The type of monitor.

Possible values = PING, TCP, HTTP, TCP-ECV, HTTP-ECV, UDP-ECV, DNS, FTP, LDNS-PING, LDNS-TCP, LDNS-DNS, RADIUS, USER, HTTP-INLINE, SIP-UDP, SIP-TCP, LOAD, FTP-EXTENDED, SMTP, SNMP, NNTP, MYSQL, MYSQL-ECV, MSSQL-ECV, ORACLE-ECV, LDAP, POP3, CITRIX-XML-SERVICE, CITRIX-WEB-INTERFACE, DNS-TCP, RTSP, ARP, CITRIX-AG, CITRIX-AAC-LOGINPAGE, CITRIX-AAC-LAS, CITRIX-XD-DDC, ND6, CITRIX-WI-EXTENDED, DIAMETER, RADIUS_ACCOUNTING, STOREFRONT, APPC, SMPP, CITRIX-XNC-ECV, CITRIX-XDM, CITRIX-STA-SERVICE, CITRIX-STA-SERVICE-NHOP
state <String> Read-only The state of the monitor.

Possible values = ENABLED, DISABLED
boundservicegroupsvrstate <String> Read-only The state of the servicegroup.

Possible values = ENABLED, DISABLED
__count <Double> Read-only count parameter

Operations

(click to see Properties )

  • GET (ALL)
  • GET
  • COUNT

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>

Note:

Mandatory parameters are marked in red and placeholder content is marked in green

get (all)

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

Query-parameters:

args

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? args= monitorname:<String_value>,

Use this query-parameter to get lbmonbindings resources based on additional properties.

attrs

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

filter

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? filter=property-name1:property-val1,property-name2:property-val2

Use this query-parameter to get the filtered set of lbmonbindings resources configured on NetScaler.Filtering can be done on any of the properties of the resource.

view

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? view=summary

Use this query-parameter to get the summary output of lbmonbindings resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

pagination

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? pagesize=#no;pageno=#no

Use this query-parameter to get the lbmonbindings resources in chunks.

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 Header:

Content-Type:application/json

Response Payload:

{ "lbmonbindings": [ {
<b>monitorname:<String_value>,</b>      "type":<String_value>,
      "state":<String_value>,
      "boundservicegroupsvrstate":<String_value>
}]}

get

URL: http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings/ monitorname_value<String>

Query-parameters:

attrs

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings/ monitorname_value<String> ? attrs=property-name1,property-name2

Use this query parameter to specify the resource details that you want to retrieve.

view

http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings/ monitorname_value<String> ? view=summary

Use this query-parameter to get the summary output of lbmonbindings resources configured on NetScaler.

Note: By default, the retrieved results are displayed in detail view (?view=detail).

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 Header:

Content-Type:application/json

Response Payload:

{  "lbmonbindings": [ {
<b>monitorname:<String_value>,</b>      "type":<String_value>,
      "state":<String_value>,
      "boundservicegroupsvrstate":<String_value>
}]}

count

URL: http:// <netscaler-ip-address> /nitro/v1/config/lbmonbindings? args= monitorname:<String_value>, ;count=yes

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 Header:

Content-Type:application/json

Response Payload:

{ "lbmonbindings": [ { "__count": "#no"} ] }