Add an Array Device
Payload
| Name | Description |
|---|---|
| name
|
(Mandatory) Name of the device. Constraints:
|
| vendor
|
(Mandatory) Vendor of the device - Array. |
| communicationAddressType
|
(Mandatory) Communication type to the device. The
possible values are:
|
| ip
|
(Mandatory) IP of the device. Constraints: Required only if communicationAddressType is IP. |
| fqdn
|
(Mandatory) FQDN of the device. Constraints: Required only if communicationAddressType is FQDN. |
| credentialType
|
(Mandatory) Type of credential to be associated for the
device. The possible values are:
|
| userName
|
(Mandatory) User name of the
device. Constraints: Required only if credential Type is Manual entry. It will not accept ‘,”,<,>. |
| password
|
(Mandatory) Encoded value of the password to
authenticate with the device. Constraints: Required only if credential Type is Manual entry. |
| credentialName
|
(Mandatory) Name of the credential to be associated
with the device. Constraints:
|
| module
|
(Optional) Modules with which the device is to be
added. The possible values are:
|
| isControllerDevice
|
(Optional) Boolean flag to denote if the device to be added is a
controller. Constraints: The value must be Yes, if the device to be added is Velos Controller. |
| sshPort
|
(Optional) Device communication port. The default value is 22. It must be between 1 and 65535. |
| certSync
|
(Optional) Certificate sync mode. The
possible values are:
|
| isAppViewXSyncRequired
|
(Optional) Boolean value to denote whether AppViewX
group is required. Only for applicable vendors. The default value is False. |
| isAutoDetectTenants
|
(Optional) Applicable only for modules - rSeries Host.
Boolean value to denote whether tenant devices should be
automatically discovered and added to AppViewX. The default value is True. |
| tokenBasedAuthentication
|
(Optional) Token Based authentication. The possible values are True/False. |
| dataCenter
|
(Optional) Data center with which the device is to be
added. Constraints:
|
| tenantProperties.credentialType
|
(Optional) Type of credential to be associated for the tenant
device. Applicable only for device with module rSeries Host. The
possible values are:
|
| tenantProperties.credentialName
|
(Optional) Name of the credential to be associated with the tenant device. Applicable only for device with module rSeries Host Constraints:
|
| tenantProperties.module
|
(Optional) Modules with which the tenant device is to be added.
Applicable only for devices with module rSeries Host. The possible
values are:
|
| tenantProperties.sshPort
|
(Optional) Device communication port for the tenant device. Applicable only for devices with module rSeries Host. The default value is 22. |
| tenantProperties.certSync
|
(Optional) Certificate sync mode for the tenant device.
Applicable only for devices with module rSeries Host. The possible values are Managed, Monitored, and Ignored The default value is Ignored. |
| tenantProperties.isAppViewXSyncRequired
|
(Optional) Boolean value to denote whether the AppViewX group is required for the tenant device. Only for applicable vendors. Applicable only for devices with module rSeries Host. The default value is False. |
Response Structure
- Status Code: 202 OK
- Message: Successful
- Headers:
- Content-Type: application/json
| Name | Description |
|---|---|
| response
|
Success message or failure description in case of error. |
| message
|
Success message or failure description in case of error. |
| appStatusCode
|
Application specific status code for the response. Will be non-null for failure response. |
| tags
|
More info in case of failure response. |
Status Codes
| HTTP Status Code | appStatusCode | Message | Possible remediation |
|---|---|---|---|
| 202 Accepted | - | Device has been successfully added and configuration parse is triggered | - |
| 400 Bad Request | ADC_INV_0004 | Validation error | One or more fields are invalid. Reason for validation failure and possible remediation will be available in ‘tags’ field of response. |
| 409 Conflict | ADC_INV_0001 | Device(s) Already Exists | Device already exists in AppViewX. Change the name of the device and IP/FQDN. |
| 409 Conflict | ADC_INV_0006 | Device Name Already Exists. | Change the name of the device and retry adding. |
| 409 Conflict | ADC_INV_0007 | IP Already Exists | Change the IP of the device and retry adding. |
| 409 Conflict | ADC_INV_0027 | FQDN already exists | Change the FQDN field of the device and retry adding. |
| 404 Not Found | ADC_INV_1076 | Device not available for the given details. | Check if the requested device is added in the inventory. |
Sample Request/Response
Use Case
Add an Array device of name testArrayDevice,with IP address 192.168.xxx.xx with both SLB and GSLB modules with username and password.
https://<IP/HostName/TenantName>:<GWPORT>/avxapi/avxapi/adc-device-add
{
"payload": {
"name": "testArrayDevice",
"communicationAddressType": "ip",
"deviceCommunicationPort": {
"apiPort": "9997"
},
"ip": "192.168.147.23",
"vendor": "Array",
"module": [
"SLB",
"GSLB"
],
"credentialType": "Manual Entry",
"userName": "admin",
"password": "YXBwdGFnQDEyMw=="
}
}
{
"response": "Device is added to the inventory.",
"message": "Device has been successfully added and configuration parse is triggered.",
"appStatusCode": null,
"tags": null,
"headers": null
}
Reference
- IP/HostName/TenantName: Replace with the actual IP address, hostname,
or tenant name based on the specific configuration in AppViewX.
- IP: A unique identifier assigned to each device connected to
a computer network that uses the Internet Protocol for communication
The IP address will be included in the endpoint URL for an on-prem deployment.
- HostName: A human-readable label assigned to a device (host)
on a network
The hostname will be included in the endpoint URL for an on-prem deployment.
- TenantName: An identifier label for a tenant given to
indicate which tenant's data the API request will
access/modify
The tenant name will be included in the endpoint URL for a SaaS deployment.
- IP: A unique identifier assigned to each device connected to
a computer network that uses the Internet Protocol for communication
- GWPORT: AppViewX gateway port
A gateway port refers to a network port through which data is sent and received to communicate with a gateway in an on-prem deployment.
Example: 31443
- avxapi: Path parameter value (static) that is part of the endpoint's URL
- Endpoint: Endpoint of the API, for example: execute-hook
- gwsource: Source or origin of a gateway, for example: external.