aXAPI Configuration for ACOS Objects

BEF

aXAPI (aXAPI RESTful API) is a programmatic interface for configuring and managing ACOS devices (such as SLB, CGN, and others) from A10 Networks. To configure an ACOS object using aXAPI, you need the following three items:

1. Endpoint with parameters: An endpoint is the target resource on the ACOS device that you want to configure. For example, if you want to configure a virtual server (VS), the endpoint would be /axapi/v3/slb/virtual-server/ followed by the VS name. The endpoint can also include parameters, which are additional settings that modify the behavior of the endpoint. For example, if you want to enable logging for the VS, you would add the log parameter to the endpoint.

2. Authorization signature: To authenticate and authorize the API request, you need to include an authorization signature in the API call. The authorization signature is a combination of the user's API key, secret key, and other data, such as the current timestamp and the HTTP method (GET, POST, PUT, or DELETE). The signature is calculated using a hash function and included in the API call as a custom HTTP header.

3. Device's management/data IP: To send the API request to the ACOS device, you need to know its IP address or hostname. This can be either the management IP address or the data IP address, depending on the configuration of the device. The management IP address is used for management traffic, such as SSH or SNMP, while the data IP address is used for data traffic, such as SLB or CGN traffic.

Therefore, the correct answers are A (Endpoint with parameters), E (Device's management/data IP), and F (Encrypted connection to device). Option B (Authorization signature) is also correct, as it is required to authenticate and authorize the API request. However, options C (Device's VIP URL) and D (Device's serial number) are not required to configure an ACOS object using aXAPI.