Skip to main content

Associate extra-capacity per-node licenses with a Cloud Volumes ONTAP system

POST /license/extra-capacity-licenses/cvoId/{cvoId}

Associates extra-capacity per-node licenses with a Cloud Volumes ONTAP system either by providing NetApp License Files (NLF) in the licenseFiles body field or a value for both serialNumbers and nssKeyId body fields. A Cloud Volumes ONTAP resource is represented by the cvoId parameter. If it's a single-node Cloud Volumes ONTAP resource, only one license file or a serial number and a NetApp Support Site key should be provided. For high-availability (HA) Cloud Volumes ONTAP resource, two license files or two serial numbers and a NetApp Support Site key should be provided.

Note:

  • The cvoId parameter is required.

  • If you use a NetApp Console service token, accountId is not a required field.

  • If you use a NetApp Console user token, accountId is a required field.

  • serialNumbers is a required field when using this site. In general, you can specify its value as null.

  • licenseFiles is not a required field if values for serialnumbers and nssKeyId are provided.

  • nssKeyId is a required field unless you provide a value for the licenseFiles body field. In the latter case, nssKeyId must be omitted.

  • accountId is a required field unless you use a service token.

  • The serialNumbers and licenseFiles fields are mutually exclusive - one must have a value but not both.

Token usage: Either a NetApp Console user token or service token.

Parameters

Name Type In Required Description

cvoId

string

path

True

X-Service-Request-Id

string

header

False

Request identifier

Request Body

Name Type Required Description

accountId

["string", "null"]

False

serialNumbers

array[["string", "null"]]

False

licenseFiles

array[["string", "null"]]

False

nssKeyId

["string", "null"]

False
Example request 
{
  "serialNumbers": [
    [
      "string",
      "null"
    ]
  ],
  "licenseFiles": [
    [
      "string",
      "null"
    ]
  ]
}

Response

Status: 200, Success response

Response

Status: 4xx, Error response
Name Type Required Description

errorCode

string

False

Error code

error

string

False

Error code/category

message

string

False

Error description message
Example response 
{
  "errorCode": "string",
  "error": "string",
  "message": "string"
}

Response

Status: 5xx, Error response
Name Type Required Description

errorCode

string

False

Error code

error

string

False

Error code/category

message

string

False

Error description message
Example response 
{
  "errorCode": "string",
  "error": "string",
  "message": "string"
}