CONFIG OBJECT ROUTER NEW

Level

object,modify

History

Appears in 2.0.0
monitor appears in 4.3.0
triesup appears in 4.3.0
slause appears in 4.3.0
slajitter appears in 4.3.0
slalatency appears in 4.3.0
slalossrate appears in 4.3.0
slaunreachablerate appears in 4.3.0

Description

Add router object

Usage

name=<router name> [monitor=<icmp|tcp_probe>] [port=<service_name>] [comment=<comment>] [tries=<int>] [triesup=<int>] [wait=<seconds>] [frequency=<seconds>] [gatewaythreshold=<int>] [activateallbackup=(on|off)] [loadbalancing=<none|connhash|srchash>] [onfailpolicy=(pass|block)] [slause=<0|1>] [slajitter=<milliseconds>] [slalatency=<milliseconds>] [slalossrate=<float>] [slaunreachablerate=<int>] [update=<0|1|2>]

Remark

With update=2, modules which use the object are not reloaded.
When load balancing is enabled, if there are less than GatewayThreshold principals active, backups will be used
Gatewaythreshold=0 means to use backups when at least one principal is down
Gatewaythreshold=1 means to use backups when all principals are down The port parameter is for TCP_PROBE monitoring only and must be the name or the port number of a tcp service object

Example

CONFIG OBJECT ROUTER NEW name=myrouter monitor=TCP_PROBE port=tcp_service comment="My router object" gatewaythreshold=1 tries=3 triesup=0 wait=2 frequency=15 loadbalancing=none onfailpolicy=pass CACHE_CATEGORY objects