204 |
|
High availability settings were applied successfully |
400 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Bad request. One or more fields have violated a constraint. The request should not be resubmitted
without correcting the field(s).
|
401 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Invalid credentials. |
403 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Unable to get permission. Updating high availability config requires administrator role. |
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
group-password field cannot be null or empty
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
local-node is read-only and does not match the server's value.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Node list cannot be empty.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
cidr-mask field is read-only and cannot be modified -- this is only validated from the HA Agent
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
gateway field is read-only and cannot be modified -- this is only validated from the HA Agent
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
associated-device-name field is not a recognized device or order of interfaces has changed.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
physical-address mismatch. physical-address field is read-only.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Crossover link cannot have a virtual address or virtual hostname.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
No peer address specified for HA link.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Peer address specified for HA link is not within the same subnet as the paired physical address.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
virtual-address must be on the same subnet as the physical-address
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
virtual-hostname was not a valid hostname.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
An invalid or empty virtual-address was specified on an interface that
did not have an HA link specified.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Configuration must contain at least one HA link and one virtual address to be valid.
|
409 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
Configuration must contain at least one HA link and one virtual address to be valid.
|
412 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The high availability config resource has changed on the server.
Note: The response will contain the ETag value and link that reflects
the server's user resource in the HTTP response header.
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-high-availability-config.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|
428 |
application/vnd.plcm.plcm-error+xml application/vnd.plcm.plcm-error+json
|
The API client must supply the ETag in the message body that is bounded by
the "entity-tag" XML tag. Refer to the "plcm-high-availability-config.xsd" for details.
If the message body does not contain the ETag value, the server will
look for the ETag in the "If-Match" header.
|