BIG-IP F5Install

Summary

Runs a ping from the BIG-IP itself to a target IP or hostname by POSTing to the iControl REST util/ping endpoint, to test connectivity from the device's management plane.

Inputs

• Target Host (required) — IP address or hostname to ping from the BIG-IP. It is sent as the utilCmdArgs body field, with " -c 3" appended so the ping sends 3 packets.
• Request Options — Optional node settings: batching (items per batch and interval in ms), ignore SSL issues, HTTP proxy URL, and timeout in ms (default 10000).

Output shape

One item per input item, containing the JSON response from the BIG-IP POST /mgmt/tm/util/ping call. This is typically the command result, including the ping output text.

The source does not define post-processing, so the response is returned as the API sends it. The request body also includes the fixed field command: "run". The packet count is fixed at 3 and can't be changed. Authentication and base URL come from the bigIpF5Api credential.

Examples

Example 1: Check that the BIG-IP can reach a pool member before a deployment.

Resource: System, Operation: Ping, Target Host: 192.168.1.10

Example 2: Verify DNS resolution and outbound connectivity from the device.

Resource: System, Operation: Ping, Target Host: example.com, Timeout: 30000

Example 3: Ping a target taken from an upstream node's data.

Resource: System, Operation: Ping, Target Host: ={{ $json.ip }}

Links

• n8n community nodes installation guide