VRRP 
Router Configuration Guide 439
It is possible for a required ARP request to succeed or timeout after the message timeout timer expires. 
In this case, the message request is unsuccessful.
If an ICMP echo reply message is not received prior to the timeout period for a given ICMP echo 
request, that request is considered to be dropped and increments the consecutive message drop counter 
for the priority event.
If an ICMP echo reply message with the same sequence number as an outstanding ICMP echo request 
message is received prior to that message timing out, the request is considered successful. The 
consecutive message drop counter is cleared and the request message no longer is outstanding.
If an ICMP Echo Reply message with a sequence number equal to an ICMP echo request sequence 
number that had previously timed out is received, that reply is silently discarded while incrementing 
the priority event reply discard counter.
The no form of the command reverts to the default value.
Default 1
Parameters seconds — The number of seconds before an ICMP echo request message is timed out. Once a 
message is timed out, a reply with the same identifier and sequence number is discarded.
Values 1 to 60
Priority Policy Route Unknown Event Commands
less-specific
Syntax [no] less-specific [allow-default]
Context config>vrrp>policy>priority-event>route-unknown prefix/mask-length
Description This command allows a CIDR shortest match hit on a route prefix that contains the IP route prefix 
associated with the route unknown priority event.
The less-specific command modifies the search parameters for the IP route prefix specified in the 
route-unknown priority event. Specifying less-specific allows a CIDR shortest match hit on a route 
prefix that contains the IP route prefix.
The less-specific command eases the RTM lookup criteria when searching for the prefix/mask-length. 
When the route-unknown priority event sends the prefix to the RTM (as if it was a destination 
lookup), the result route table prefix (if a result is found) is checked to see if it is an exact match or a 
less specific match. The less-specific command enables a less specific route table prefix to match the 
configured prefix. When less-specific is not specified, a less specific route table prefix fails to match 
the configured prefix. The allow-default optional parameter extends the less-specific match to include 
the default route (0.0.0.0).