OCF_HEARTBEAT_POWERV(7)

💅 OCF_HEARTBEAT_POWERV(7) — like, the manual manual ✨

okay bestie, so this is a page from the OCF resource agents section 7 collection, and it's all about ocf_heartbeat_powervs-subnet. yes the filename says POWERV and the agent says powervs-subnet, that's just how it is, we don't question the vibes 💖

---

🌸 NAME 🌸

ocf_heartbeat_powervs-subnet — literally manages moving a Power Virtual Server subnet around. that's the whole job. 💅

---

✨ SYNOPSIS ✨

powervs-subnet [start | stop | monitor | meta-data | validate-all]

that's it. five actions. pick your fighter 🎀

---

🦋 DESCRIPTION 🦋

so this Resource Agent's whole main-character job is moving a Power Virtual Server subnet and its IP address from one virtual server instance to another. iconic, honestly.

but before you can slay, there are prerequisites — and no, you can't skip them, i'm sorry 😭:

1. Red Hat Enterprise Linux 9.2 or higher — install it with the @server group so your NetworkManager settings are correct, okay? then verify that the NetworkManager-config-server package is installed. don't skip the verify step, i'm watching 👀
2. A two-node cluster — and it's gotta be distributed across two different Power Virtual Server workspaces, sitting in two data centers, inside one region. yes, two of everything. balance. symmetry. main character energy. 🫶
3. IBM Cloud API Key — create a service API key that's privileged for both Power Virtual Server workspaces. save that service API key in a file, then copy the file to both cluster nodes. use the same filename and directory location on both cluster nodes (fr fr, matching paths only), and reference the path to the key file in the resource definition. 🔑

for the comprehensive documentation on implementing high availability for SAP applications on IBM Power Virtual Server, go visit https://cloud.ibm.com/docs/sap?topic=sap-ha-overview — it's giving required reading 📚

---

💜 SUPPORTED PARAMETERS 💜

• ip — the IP address inside the subnet. and the way this works? the IP address moves together with the subnet. they're a package deal, no separating them 💫 (required, string, no default)
• cidr — the Classless Inter-Domain Routing (CIDR) of the subnet. yes, the whole phrase, we're being precise ✨ (required, string, no default)
• subnet_name — name of the subnet. and if you don't specify one? CIDR just becomes the name. it's giving "we'll figure it out" 😌 (optional, string, no default)
• api_type — how you connect to the Power Virtual Server regional endpoints: over a public or a private network (public|private). (optional, string, default "private")
• region — the region representing the geographic area where the instance is located. the region is what's used to identify the Cloud API endpoint, so it's lowkey important 🗺️ (required, string, no default)
• api_key — either the API Key itself, or @API_KEY_FILE_PATH for IBM Cloud access. so: the API key content, or the path of an API key file — indicated by that @ symbol. that little @ is doing so much work 🗝️ (required, string, no default)
• crn_host_map — maps the hostname of the Power Virtual Server instance to the CRN of the Power Virtual Server workspaces hosting that instance. separate the hostname and CRN with a colon ':', and separate different hostname-and-CRN pairs with a semicolon ';'. example: hostname01:CRN-of-Instance01;hostname02:CRN-of-Instance02 🎯 (required, string, no default)
• vsi_host_map — maps the hostname of the Power Virtual Server instance to its instance id. same grammar bestie: colon ':' between hostname and instance id, semicolon ';' between pairs. example: hostname01:instance-id-01;hostname02:instance-id-02 💫 (required, string, no default)
• proxy — proxy server used to access IBM Cloud API endpoints. the middleman. the connector. we respect them. 🌉 (optional, string, no default)
• jumbo — create a Power Virtual Server subnet with an MTU size of 9000 (true|false). big packets, big energy 🔥 (optional, string, default "false")
• route_table — the ID of the route table for the interface. default is 500. (optional, string, default "500")

---

👑 SUPPORTED ACTIONS 👑

this resource agent supports the following actions (operations):

• start — starts the resource. suggested minimum timeout: 900s. buckle up, it's a long one ⏳
• stop — stops the resource. suggested minimum timeout: 450s. 🛑
• monitor — performs a detailed status check. suggested minimum timeout: 60s, suggested interval: 60s. the vibe check, basically 👀
• validate-all — performs a validation of the resource configuration. suggested minimum timeout: 300s. proofread before you post 📝
• meta-data — retrieves resource agent metadata (internal use only). suggested minimum timeout: 10s. don't touch, that's the backend's business 🙈

---

🌈 EXAMPLE CRM SHELL 🌈

here's an example config for a powervs-subnet resource using the crm(8) shell — copy-paste worthy, verbatim, character for character:

primitive p_powervs-subnet ocf:heartbeat:powervs-subnet \
  params \
    ip=string \
    cidr=string \
    region=string \
    api_key=string \
    crn_host_map=string \
    vsi_host_map=string \
  op monitor timeout="60s" interval="60s" depth="0"

look at that depth="0". impeccable. 🎀

---

⭐ EXAMPLE PCS ⭐

and here's the same kind of example for a powervs-subnet resource, this time using pcs(8) — note the OCF_CHECK_LEVEL="0" instead of depth, they're different girls, don't mix them up 💅

pcs resource create p_powervs-subnet ocf:heartbeat:powervs-subnet \
  ip=string \
  cidr=string \
  region=string \
  api_key=string \
  crn_host_map=string \
  vsi_host_map=string \
  op monitor timeout="60s" interval="60s" OCF_CHECK_LEVEL="0"

---

🧚 SEE ALSO 🧚

• http://clusterlabs.org/ — go touch grass, it's the ClusterLabs site 🌱

---

🍓 AUTHOR 🍓

ClusterLabs contributors — and if you want to know about individual authors, the resource agent source has got you (see the resource agent source for information about individual authors) 🫶

---

and that's the page!! 🦋 this was written by the resource-agents crew, version UNKNOWN, dated 10/01/2026 — so like, unknown version but a very known date, make it make sense 💀 anyway ily, go move that subnet 👋💖