Down Action object naming convention: The name of the down action object should be like '(DNACTION)(down action type)_(max number)'.For example a down action for disabling tunnel should look like 'DN_ACTION_tun-dn_11'. Here tun-dn is the action type and the last number should be the unique and generally it should be the increment of the max number used across all the existing Manager, Operation and Action objects.

Operation object naming convention: The name of the operation/monitor object should be like '(OPR)(operation type)(max number)'. For example an operation for monitoring interface should be like 'OPR_ip-monitor_11'. Here ip-monitor is the operation type and the last number should be the unique and generally it should be the increment of the max number used across all the existing Manager, Operation and Action objects.

HTTP/HTTPS Monitor

type: http-monitor,

Attributes

http-monitor-url: Single/List of URLs(separated by comma) to be monitored.

proxyAddress: Proxy address

proxyPort: Proxy port

user-agent:User agent to be added to the request header

http-timeout: Request time out in seconds (default is 0)

ka: Keep alive time in seconds

up-thresh: Mark up after X number of pings

dn-thresh: Mark down after X number of failed pings

port-name: Name of the interface to be monitored ex:lan0 or port-label: Name of the interface label to be monitored ex:MPLS

VRRP Monitor

type :vrrp-monitor,

Attributes

port-name: Name of the interface to be monitored ex:lan0 or port-label: Name of the interface label to be monitored ex:MPLS

Up Action object naming convention: The name of the up action object should be like '(UPACTION)(up action type)_(max number)'. For example an up action for enabling tunnel should look like 'UP_ACTION_tun-up_11'. Here tun-up is the action type and the last number should be the unique and generally it should be the increment of the max number used across all the existing Manager, Operation and Action objects.