Download full document:

nsdiameter

Configuration for Diameter Parameters resource.

Properties

(click to see Operations)

Name Data Type PermissionsDescription
identity<String>Read-writeDiameterIdentity to be used by NS. DiameterIdentity is used to identify a Diameter node uniquely. Before setting up diameter configuration, Netscaler (as a Diameter node) MUST be assigned a unique DiameterIdentity. example =;gt; set ns diameter -identity netscaler.com Now whenever Netscaler system needs to use identity in diameter messages. It will use netscaler.com as Origin-Host AVP as defined in RFC3588 .<br>Minimum length = 1
realm<String>Read-writeDiameter Realm to be used by NS. example =;gt; set ns diameter -realm com Now whenever Netscaler system needs to use realm in diameter messages. It will use com as Origin-Realm AVP as defined in RFC3588 .<br>Minimum length = 1
serverclosepropagation<String>Read-writewhen a Server connection goes down, whether to close the corresponding client connection if there were requests pending on the server.<br>Default value: NO<br>Possible values = YES, NO

Operations

(click to see Properties)

UPDATE | UNSET | GET (ALL)

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>.

update

URL: http://<NSIP>/nitro/v1/config/

HTTP Method: PUT

Request Payload: 

{
"params": {
      "warning":<String_value>,
      "onerror":<String_value>"
},
sessionid":"##sessionid",
"nsdiameter":{
      "identity":<String_value>,
      "realm":<String_value>,
      "serverclosepropagation":<String_value>,
}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

unset

URL: http://<NSIP>/nitro/v1/config/

HTTP Method: POST

Request Payload: 

object={
"params":{
      "warning":<String_value>,
      "onerror":<String_value>,
      "action":"unset"
},
"sessionid":"##sessionid",
"nsdiameter":{
      "serverclosepropagation":true,
}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": }

get (all)

URL: http://<NSIP>/nitro/v1/config/nsdiameter

HTTP Method: GET

Response Payload: 

{ "errorcode": 0, "message": "Done", "severity": <String_value>, "nsdiameter": [ {
      "identity":<String_value>,
      "realm":<String_value>,
      "serverclosepropagation":<String_value>

}]}