Test Type: Specifies the router entity to be monitored and implies the method used to monitor the entity.
“vrrp state” test: Tests the router’s VRRP state (master or backup) in a given LAN segment.
“ethernet port state” test: Tests state of the Ethernet ports. “wan device state” test: Tests state of WAN devices.
“route exist” test: Tests the existence of route in a given routing table. “bgp peer” test: Tests if a given BGP peer exists.
ICMP echo (ping) response: Tests if a host responds to pings.
“custom” test: It allows internal services or SDK apps to add new test cases without a formal test type definition.
Test Instance: There can be one or more instances of a given test type. For example, user can create one test instance to test "ethernet port state" on port x, and another test instance to test "ethernet port state" on port y. Each test instance runs independently within router's test engine. On completion of the test iteration, test engine will generate an event specifying the result of test execution.
Test Action
The Test Type definition does not specify any action based on test result (other than method to log test pass/fail result).
test instance identifier
test result (pass/fail)
Any entity within the router can listen to the above event and take action.
vrrp – Based on test result, adjust VRRP priority.
vpn – Based on test result, connect or disconnect IPsec tunnel.
bgp – Based on test result, switch out a list of prefixes.
Note
There is no implied relation between test type and test action. A VPN entity can choose to take action (connect/disconnect tunnel) based on result of "vrrp state" type test.