pqbinding¶
Configuration for PQ bindings resource.
Properties¶
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
vservername | <String> | Read-write | Name of the load balancing virtual server for which to display the priority queuing policy.
Minimum length = 1 |
policyname | <String> | Read-only | The name of the priority queuing policy. |
rule | <String> | Read-only | The condition for applying the policy. |
priority | <Double> | Read-only | The priority of queuing the request. |
weight | <Double> | Read-only | Weight. |
qdepth | <Double> | Read-only | Queue Depth. |
polqdepth | <Double> | Read-only | Policy Queue Depth. |
hits | <Double> | Read-only | Total number of hits. |
__count | <Double> | Read-only | count parameter |
Operations¶
(click to see Properties )
- GET (ALL)
- 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/pqbinding
Query-parameters:
args
http:// <netscaler-ip-address> /nitro/v1/config/pqbinding? args= vservername:<String_value>,
Use this query-parameter to get pqbinding resources based on additional properties.
attrs
http:// <netscaler-ip-address> /nitro/v1/config/pqbinding? 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/pqbinding? filter=property-name1:property-val1,property-name2:property-val2
Use this query-parameter to get the filtered set of pqbinding resources configured on NetScaler.Filtering can be done on any of the properties of the resource.
view
http:// <netscaler-ip-address> /nitro/v1/config/pqbinding? view=summary
Use this query-parameter to get the summary output of pqbinding 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/pqbinding? pagesize=#no;pageno=#no
Use this query-parameter to get the pqbinding 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:
{ "pqbinding": [ {
<b>vservername:<String_value>,</b> "policyname":<String_value>,
"rule":<String_value>,
"priority":<Double_value>,
"weight":<Double_value>,
"qdepth":<Double_value>,
"polqdepth":<Double_value>,
"hits":<Double_value>
}]}
count¶
URL: http:// <netscaler-ip-address> /nitro/v1/config/pqbinding? args= vservername:<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:
{ "pqbinding": [ { "__count": "#no"} ] }