Management::EM::set_device_context¶
Introduced : BIG-IP_v9.0
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.
Parameters¶
Parameter | Type | Description |
ip_address | String | This parameter specifies the IP address of the F5 device that you want to access via the Enterprise Manager. |
Exceptions¶
Exception | Description |
Common::AccessDenied | Raised if the client credentials are not valid. |
Common::InvalidArgument | Raised if one of the arguments is invalid. |
Common::OperationFailed | Raised if an operation error occurs. |
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¶
- Adding or deleting a pool member - Using iControl proxy to add or delete a pool member
- Retrieve platform version using iControl Proxy (C# code sample) - C# client code sample to disable virtual servers using iControl Proxy.
- Enabling or disabling a pool member - Using iControl proxy to enable or disable a pool member
- Retrieve platform version using iControl Proxy (Java code sample) - Java client code sample uses the iControl Proxy to disable the virtual servers for each device managed by the referenced Enterprise Manager.
- Retrieve platform version using iControl Proxy (Perl code sample) - Perl client code sample uses iControl Proxy to get plaform version for each device managed by the referenced Enterprise Manager.
- Retrieve platform version using iControl Proxy (Python code sample) - Python client code sample uses the iControl Proxy to disable the virtual servers for each device managed by the referenced Enterprise Manager.
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.