Add an Amazon ELB Device
Payload
| Name | Description |
|---|---|
| name
|
(Mandatory) Name of the device. Constraints:
|
| vendor
|
(Mandatory) Vendor of the device. |
| communicationAddressType
|
(Mandatory) Communication type to the device. The
possible values are:
|
| ip
|
(Mandatory) IP of the device. Constraints:
|
| 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
|
(Mandatory) Modules with which the device is to be added. |
| certSync
|
(Optional) Certificate sync mode. The
possible values are:
|
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. |
| isAutoDetectSecondary
|
(Optional) Boolean value to denote whether secondary
devices should be automatically discovered and added to
AppViewX. The default value is False. |
| dataCenter
|
(Optional) Data center with which the device is to be added. |
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
NA
Sample Request
NA
Sample Response
NA