OCF_HEARTBEAT_SENDAR(7)

πŸ’… ocf_heartbeat_SendArp β€” from the OCF_HEARTBEAT_SENDAR(7) girlies ✨

okay bestie, sit down, hydrate, and let me tell you about the most unserious-but-actually-iconic resource agent in the cluster: SendArp. yes that's the name. yes it's capitalized like that. we don't ask questions, we just vibe πŸ¦‹


🌸 NAME 🌸

ocf_heartbeat_SendArp β€” it Broadcasts unsolicited ARP announcements πŸ’Œ no cap, that's literally the whole job.


✨ SYNOPSIS ✨

SendArp [start | stop | monitor | meta-data | validate-all]

that's the whole menu, bestie. five actions, zero drama πŸŽ€


🫢 DESCRIPTION 🫢

okay so this is the part where it gets good πŸ‘‘

This RA can be used instead of the IPaddr2 or IPaddr RA to send gratuitous ARP for an IP address on a given interface, without adding the address to that interface. like, it just... tells the network "hey, this IP lives here now" and then dips. main character energy fr πŸ’…

For example β€” and this is the example the manpage gives, I'm not inventing lore β€” if for some reason you wanted to send gratuitous ARP for addresses managed by IPaddr2 or IPaddr on an additional interface. that's it, that's the use case. lowkey niche, highkey useful 🌈


πŸŽ€ SUPPORTED PARAMETERS πŸŽ€

three params. three. we love a minimal icon ⭐

  • ip β€” The IP address for sending ARP packet. it's required, it's a string, and there's no default β€” you gotta bring your own, bestie πŸ™ˆ
  • nic β€” The NIC for sending ARP packet. also required, also a string, also no default. no NIC, no ARP, no service 😭
  • background β€” Send ARPs in background. it's optional, it's a boolean, and it defaults to true. > set it to false if you want to test if sending ARPs succeeded β€” that's the tradeoff, don't come for me πŸ’€

πŸ”₯ SUPPORTED ACTIONS πŸ”₯

This resource agent supports the following actions (operations) β€” grab a snack, we're going through all five πŸ“

  • start β€” Starts the resource. Suggested minimum timeout: 20s.
  • stop β€” Stops the resource. Suggested minimum timeout: 20s.
  • monitor β€” Performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 10s.
  • meta-data β€” Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s. it said internal use only so don't be nosy 🧚
  • validate-all β€” Performs a validation of the resource configuration. Suggested minimum timeout: 20s.

🌟 EXAMPLE CRM SHELL 🌟

The following is an example configuration for a SendArp resource using the crm(8) shell β€” copy it exactly, don't be creative in here:

primitive p_SendArp ocf:heartbeat:SendArp \
  params \
    ip=string \
    nic=string \
  op monitor depth="0" timeout="20s" interval="10s"

πŸ’œ EXAMPLE PCS πŸ’œ

The following is an example configuration for a SendArp resource using pcs(8) β€” different tool, same energy:

pcs resource create p_SendArp ocf:heartbeat:SendArp \
  ip=string \
  nic=string \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s"

(and yes, note that depth="0" vs OCF_CHECK_LEVEL="0" difference β€” that's not me being messy, that's exactly how the original has it πŸ‘€)


πŸ¦‹ SEE ALSO πŸ¦‹


πŸ‘‘ AUTHOR πŸ‘‘

ClusterLabs contributors (see the resource agent source for information about individual authors) 🫢


anyway that's the whole page, mwah πŸ’‹ this was resource-agents version UNKNOWN, dated 10/01/2026 β€” slay, no cap, periodt πŸŒˆπŸ’–

πŸ“¦ where this page comes from