GlobalLB::PoolV2::add_non_terminal_member_srv¶
Introduced : BIG-IP_v12.0.0
Adds SRV type non-terminal members with their specified orders, and
RDATA ports. The parent pools must be of type SRV. In the PoolV2
interface members can now also be non-terminal type members (no longer
only virtual servers). Non-terminal members are specified with a
required dname. The dname of the non-terminal member is non-folderized
and must be a fully-qualified domain name. The dname of the
non-terminal member must match (exactly or via wide IP wildcard match)
the name of a corresponding wide IP of the correct type (without the
folder name). The dname of SRV type non-terminal members must match
the name of an existing A or AAAA type wide IP. The members are
reordered starting with 0, with no gaps, so the system maintains the
relative order but not the absolute numbers originally specified for
ordering. The RDATA port must be specified. RDATA is a field in a DNS
resource record (RR). The contents of the RDATA field depend on the
type of RR. For example an A type RR would contain an IPv4 address in
the RDATA section while a CNAME type RR would contain the string name
of an alias domain name.
Prototype¶
add_non_terminal_member_srv(
in GlobalLB__PoolID [] pools,
in String [] [] members,
in long [] [] orders,
in long [] [] ports
);
Parameters¶
Parameter | Type | Description |
pools | PoolID [] | The list of pools to modify. |
members | String [] [] | Non-terminal members to create for each specified pool. |
orders | long [] [] | Order for each specified non-terminal member of each specified pool. |
ports | long [] [] | RDATA ports for each specified non-terminal member of each specified pool. |
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¶
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.