OCF_HEARTBEAT_IFACE-VLAN(7)

💖 NAME 💖

okay bestie, welcome to ocf_heartbeat_iface-vlan(7) — the manual for iface-vlan, the resource agent that manages VLAN network interfaces. That's literally the NAME section: ocf_heartbeat_iface-vlan — manages VLAN network interfaces. Periodt. ✨

---

✨ SYNOPSIS ✨

iface-vlan [start | stop | status | monitor | meta-data | validate-all]

🦋 DESCRIPTION 🦋

This resource manages VLAN network interfaces. It can add, remove, configure VLANs. That's the whole vibe: add, remove, configure. Slay.

🎀 SUPPORTED PARAMETERS 🎀

• vlan_interface — define the interface where VLAN should be attached. (required, string, no default)
• vlan_id — define the VLAN ID. It has to be a value between 0 and 4094. (required, integer, no default)
• vlan_name — define the name of the VLAN interface (max 15 charaters). (unique, optional, string, default ".")
• vlan_reorder_hdr — enable or disable header reordering. (optional, boolean, default 1)
• vlan_gvrp — enable or disable GARP VLAN registration protocol. (optional, boolean, default 0)
• vlan_mvrp — enable or disable Multiple VLAN Registration Protocol. Please note that most distributions do not ship a version of iproute2 that supports mvrp yet, even if the kernel has support for it. Check output of link add type vlan --help in the FLAG section to verify if mvrp support is available. (optional, boolean, default 0)
• vlan_loose_binding — enable or disable VLAN loose bind. By default the VLAN interface admin status (UP/DOWN) follows the underneath interface status. Enabling loose bind allows the VLAN to disconnect from the interface status. (optional, boolean, default 0)

warning bestie — be very careful that enabling loose binding could invalidate this agent monitor operations. Please note that most distributions do not ship a version of iproute2 that supports loose_binding yet, even if the kernel has support for it. Check output of link add type vlan --help in the FLAG section to verify if loose_binding support is available.

👑 SUPPORTED ACTIONS 👑

This resource agent supports the following actions (operations):

• start — starts the resource. Suggested minimum timeout: 30s.
• stop — stops the resource. Suggested minimum timeout: 20s.
• status — performs a status check. Suggested minimum timeout: 20s. Suggested interval: 10s.
• 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.
• validate-all — performs a validation of the resource configuration. Suggested minimum timeout: 20s.

🌈 EXAMPLE CRM SHELL 🌈

The following is an example configuration for an iface-vlan resource using the crm(8) shell:

primitive p_iface-vlan ocf:heartbeat:iface-vlan \
  params \
    vlan_interface=string \
    vlan_id=integer \
  op monitor timeout="20s" depth="0" interval="10s"

🧚 EXAMPLE PCS 🧚

The following is an example configuration for an iface-vlan resource using pcs(8):

pcs resource create p_iface-vlan ocf:heartbeat:iface-vlan \
  vlan_interface=string \
  vlan_id=integer \
  op monitor timeout="20s" OCF_CHECK_LEVEL="0" interval="10s"

💜 SEE ALSO 💜

http://clusterlabs.org/

🌸 AUTHOR 🌸

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

---

okay that's the whole page, bestie 💖 — this was OCF_HEARTBEAT_IFACE-VLAN(7), and source/version and date aren't separately stamped on this copy (the footer only carried the manual name), so I'm not making them up. Bye! 💅✨