Skip to content

server_boundaries

Configuration for Devices selected for a VIP and Pool should be wired to appropriate networks in order to start serving traffic. Server boundary tell if Control Center has to automatically configure networks on the device. resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
topology<String>Read-writeTopology of server_boundary. The possible values are 'L2' and 'L3'..
l3config<String>Read-writeL3config of server_boundary..

Operations

(click to see Properties)

GET (ALL)| UPDATE

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: https://<MGMT-IP>/nitro/v1/config/server_boundaries

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "server_boundaries":[{
"topology":<String_value>,
"l3config":<String_value>}]}

update

URL: https://<MGMT-IP>/nitro/v1/config/server_boundaries/

HTTP Method: null

Request Payload:

{server_boundaries:{
"topology":<String_value>,
"l3config":<String_value>}}

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "server_boundaries":[{
"topology":<String_value>,
"l3config":<String_value>}]}