table of contents
OCF_HEARTBEAT_ROUTE(7) | OCF resource agents | OCF_HEARTBEAT_ROUTE(7) |
NAME¶
ocf_heartbeat_Route - Manages network routes
SYNOPSIS¶
Route [start | stop | monitor | meta-data | validate-all]
DESCRIPTION¶
Enables and disables network routes.
Supports host and net routes, routes via a gateway address, and routes using specific source addresses.
This resource agent is useful if a node´s routing table needs to be manipulated based on node role assignment.
Consider the following example use case:
- One cluster node serves as an IPsec tunnel endpoint.
- All other nodes use the IPsec tunnel to reach hosts in a specific remote network.
Then, here is how you would implement this scheme making use of the Route resource agent:
- Configure an ipsec LSB resource.
- Configure a cloned Route OCF resource.
- Create an order constraint to ensure that ipsec is started before Route.
- Create a colocation constraint between the ipsec and Route resources, to make sure no instance of your cloned Route resource is started on the tunnel endpoint itself.
SUPPORTED PARAMETERS¶
destination
(unique, required, string, no default)
device
(unique, optional, string, no default)
gateway
(unique, optional, string, no default)
source
(unique, optional, string, no default)
table
(optional, string, no default)
SUPPORTED ACTIONS¶
This resource agent supports the following actions (operations):
start
stop
monitor
reload
meta-data
validate-all
EXAMPLE¶
The following is an example configuration for a Route resource using the crm(8) shell:
primitive p_Route ocf:heartbeat:Route \
params \
destination=string \
op monitor timeout="20" interval="10" depth="0"
SEE ALSO¶
AUTHOR¶
Linux-HA contributors (see the resource agent source for information about individual authors)
03/22/2017 | resource-agents 3.9.2 |