-
-
-
-
-
-
-
-
-
-
clusterinstance_clusternode_binding
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
clusterinstance_clusternode_binding
Binding object showing the clusternode that can be bound to clusterinstance.
Properties
(click to see Operations)
Name | Data Type | Permissions | Description |
---|---|---|---|
nodeid |
|
Read-write | The unique number that identiies a cluster. Minimum value = 0 Maximum value = 31 |
clid |
|
Read-write | Unique number that identifies the cluster. Minimum value = 1 Maximum value = 16 |
state |
|
Read-only | Active, Spare or Passive. An active node serves traffic. A spare node serves as a backup for active nodes. A passive node does not serve traffic. This may be useful during temporary maintenance activity where it is desirable that the node takes part in the consensus protocol, but not serve traffic. Default value: PASSIVE Possible values = ACTIVE, SPARE, PASSIVE |
nodersskeymismatch |
|
Read-only | This argument is used to determine if there is a RSS key mismatch at cluster node level. |
nodelicensemismatch |
|
Read-only | This argument is used to determine if there is a License mismatch at cluster node level. |
effectivestate |
|
Read-only | Node effective health state. Possible values = UP, NOT UP, UNKNOWN, INIT |
islocalnode |
|
Read-only | This argument is used to determine whether it is local node. |
isconfigurationcoordinator |
|
Read-only | This argument is used to determine whether the node is configuration coordinator (CCO). |
nodejumbonotsupported |
|
Read-only | This argument is used to determine if Jumbo framework not supported at cluster node level. |
health |
|
Read-only | Node Health state. Possible values = UNKNOWN, INIT, DOWN, UP, Some enabled and HAMON interfaces of the node are down, All interfaces of the node are down or disabled, SSL card(s) of the node have failed, Route Monitor(s) of the node have failed, Service state is being synchronized with the cluster, The backplane interface is either not set or it is down or is disabled, The CLAG member(s) of the node are down, Persistence sessions are being synchronized with the cluster, The Syn Cookie is being synchronized with the cluster, Unknown Health, AAA keys are being sychronized with the cluster, Cluster health is not up due to config sync is in progress |
clusterhealth |
|
Read-only | Node clusterd state. Possible values = UP, Configurations of the node are lagging behind the cluster by more than 256 commands, The config sync operation has exceeded the time limit of 60 seconds, The config sync operation (full sync) is in progress, The node is not in sync with the cluster configurations as sync is disabled on this node, The execution of a configuration command has failed on this node, UNKNOWN |
masterstate |
|
Read-only | Master state. Possible values = INACTIVE, ACTIVE, UNKNOWN |
ipaddress |
|
Read-only | The IP Address of the node. |
__count |
|
Read-only | count parameter |
Operations
(click to see Properties)
GET | 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 Citrix ADC appliance, the URL is as follows:
http://<Citrix-ADC-IP-address(NSIP)>/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 Citrix ADC 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 redand placeholder content is marked in <green>.
get
URL:http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding/clid_value<Double>
Query-parameters:
filter
http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding/clid_value<Double>?filter=property-name1:property-value1,property-name2:property-value2
Use this query-parameter to get the filtered set of clusterinstance_clusternode_binding resources configured on Citrix ADC. Filtering can be done on any of the properties of the resource.
pagination
http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding/clid_value<Double>?pagesize=#no;pageno=#no
Use this query-parameter to get the clusterinstance_clusternode_binding 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 Citrix ADC specific errors). The response payload provides details of the errorResponse Headers:
Content-Type:application/json
Response Payload:
{ "clusterinstance_clusternode_binding": [ {
"nodeid":<Double_value>,
"clid":<Double_value>,
"state":<String_value>,
"nodersskeymismatch":<Boolean_value>,
"nodelicensemismatch":<Boolean_value>,
"effectivestate":<String_value>,
"islocalnode":<Boolean_value>,
"isconfigurationcoordinator":<Boolean_value>,
"nodejumbonotsupported":<Boolean_value>,
"health":<String_value>,
"clusterhealth":<String_value>,
"masterstate":<String_value>,
"ipaddress":<String_value>
}]}
<!--NeedCopy-->
get (all)
URL:http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding
Query-parameters:
bulkbindings
http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding?bulkbindings=yes
NITRO allows you to fetch bindings in bulk.
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 Citrix ADC specific errors). The response payload provides details of the errorResponse Headers:
Content-Type:application/json
Response Payload:
{ "clusterinstance_clusternode_binding": [ {
"nodeid":<Double_value>,
"clid":<Double_value>,
"state":<String_value>,
"nodersskeymismatch":<Boolean_value>,
"nodelicensemismatch":<Boolean_value>,
"effectivestate":<String_value>,
"islocalnode":<Boolean_value>,
"isconfigurationcoordinator":<Boolean_value>,
"nodejumbonotsupported":<Boolean_value>,
"health":<String_value>,
"clusterhealth":<String_value>,
"masterstate":<String_value>,
"ipaddress":<String_value>
}]}
<!--NeedCopy-->
count
URL:http://<Citrix-ADC-IP-address(NSIP)>/nitro/v1/config/clusterinstance_clusternode_binding/clid_value<Double>?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 Citrix ADC specific errors). The response payload provides details of the errorResponse Headers:
Content-Type:application/json
Response Payload:
{"clusterinstance_clusternode_binding": [ { "__count": "#no"} ] }
<!--NeedCopy-->
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.