Management::EM¶
Introduced : BIG-IP_v9.0
The EM interface enables the user to perform enterprise management
daemon requests.
Methods¶
Method | Description | Introduced |
delete_devices | Delete devices from the EM. | BIG-IP_v11.2.0 |
discover_devices | Initiate a device discovery. | BIG-IP_v11.2.0 |
get_context_id | Use the get_context_id API to retrieve a unique context ID. The context ID serves as a unique identifier that the iControl web proxy can use either for client/user session management, or for interaction with one specific BIG-IP device at a time. | BIG-IP_v9.0 |
get_device_proxy_configuration | Get the proxy settings used by the EM to communicate with devices. | BIG-IP_v9.0 |
get_device_token | The iControl Proxy uses the get_device_token API to obtain a device token. The token is a URL to the iControl interface on the F5 device accessed by the Enterprise Manager. | BIG-IP_v9.0 |
get_devices | When the Enterprise Manager through which you establish an iControl-proxied connection manages multiple BIG-IP devices, use the get_devices API to retrieve a list of the those BIG-IP devices. | BIG-IP_v9.0 |
get_task_status | Get the status of a task. | BIG-IP_v11.2.0 |
sendRequest | Send a daemon request. | BIG-IP_v9.0 |
set_device_context | Use the set_device_context API to establish a device context. The iControl Proxy uses this context to identify the specific client that is initiating the connection. | BIG-IP_v9.0 |
Aliases¶
Alias | Type | Description |
TaskStatusSequence | TaskStatus [] | A sequence of TaskStatus enumeration values. |
See Also¶
iControl ::
Warning
The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.
Sample Code¶
The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.