sdxvmspec
Configuration for Rescources in a sdxvm resource.
(click to see Operations)
Properties
(click to see Operations)
| Name | Data Type | Permissions | Description |
|---|---|---|---|
| memory | <String> | Read-write | Memory of sdx VM. |
| cpu | <String> | Read-write | cpu. |
| version | <String> | Read-write | Version of sdx VM. |
| name | <String> | Read-write | Name of sdx VM. |
| throughput | <String> | Read-write | Throughput of sdx VM. |
| id | <String> | Read-write | Id is system generated key for partition specs. |
| ssl_chips | <String> | Read-write | ssl_chips. |
Operations
(click to see Properties)
ADD| DELETE| GET (ALL)| GET| 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>.
add
URL: https://<MGMT-IP>/nitro/v1/config/sdxvmspec?onerror=<String_value>
HTTP Method: null
Request Payload:
{sdxvmspec: {
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"memory":<String_value>,
"id":<String_value>,
"throughput":<String_value>,
"ssl_chips":<String_value>}}
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "sdxvmspec":[{
"memory":<String_value>,
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"throughput":<String_value>,
"id":<String_value>,
"ssl_chips":<String_value>}]}
delete
URL: https://<MGMT-IP>/nitro/v1/config/sdxvmspec/id_value<String>
HTTP Method: null
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value> }
get (all)
URL: https://<MGMT-IP>/nitro/v1/config/sdxvmspec
HTTP Method: null
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "sdxvmspec":[{
"memory":<String_value>,
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"throughput":<String_value>,
"id":<String_value>,
"ssl_chips":<String_value>}]}
get
URL: https://<MGMT-IP>/nitro/v1/config/sdxvmspec/id_value<String>
HTTP Method: null
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "sdxvmspec":[{
"memory":<String_value>,
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"throughput":<String_value>,
"id":<String_value>,
"ssl_chips":<String_value>}]}
update
URL: https://<MGMT-IP>/nitro/v1/config/sdxvmspec/id_value<String>
HTTP Method: null
Request Payload:
{sdxvmspec:{
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"memory":<String_value>,
"id":<String_value>,
"throughput":<String_value>,
"ssl_chips":<String_value>}}
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "sdxvmspec":[{
"memory":<String_value>,
"cpu":<String_value>,
"version":<String_value>,
"name":<String_value>,
"throughput":<String_value>,
"id":<String_value>,
"ssl_chips":<String_value>}]}