BIG-IP F5Install

Summary

Create a new LTM load-balancing pool on an F5 BIG-IP by sending a POST to /mgmt/tm/ltm/pool through the iControl REST API, optionally with a monitor, description, and initial members.

Inputs

• Pool Name (required) — Name of the new pool, sent as name. A partition prefix is optional, e.g. Commonmy_web_pool.
• Load Balancing Mode — Algorithm for distributing connections, sent as loadBalancingMode. Defaults to round-robin. Choices include least-connections, ratio, fastest, observed, predictive and weighted least connections, each in member or node variants.
• Monitor — Health monitor path, sent as monitor. Defaults to /Common/http.
• Description — Free-text description for the pool, sent as description.
• Pool Members — Repeatable list of members to add at creation. Each has a Name in address:port form (e.g. 192.168.1.10:80) and an optional Description. Sent as the members array.
• Request Options — Node settings for batching (items per batch, interval), ignoring SSL certificate issues, an HTTP proxy, and a request timeout (default 10000 ms).

Output shape

The JSON response from the BIG-IP for the created pool, typically the new pool's configuration object. One item is returned per input item.

The source doesn't transform the response; the node uses declarative routing. The BIG-IP host and auth come from the bigIpF5Api credential. Monitor and Load Balancing Mode are always sent, using their defaults if you leave them unchanged. An empty Description is also sent, as an empty string. A BIG-IP error, such as a duplicate pool name, surfaces as a node error.

Examples

Example 1: Create a basic web pool with two backend servers

Pool Name: web_pool; Load Balancing Mode: Least Connections (Member); Monitor: /Common/http; Pool Members: 10.0.0.11:80 and 10.0.0.12:80.

Example 2: Create an empty pool in the Common partition to populate later

Pool Name: Commonapp_pool; leave Pool Members empty; Monitor: /Common/tcp; Description: Staging pool.

Links

• n8n community nodes installation guide