Configuring VRRP Creating VRRP Tracking Policies
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 23-17
Creating VRRP Tracking Policies
To create a tracking policy, use the vrrp track command and specify the amount to decrease a virtual
router’s priority and the slot/port, IP address, or IP interface name to be tracked. For example:
-> vrrp track 3 admin-state enable priority 50 address 20.1.1.3
In this example, a tracking policy ID (3) is created and enabled for IP address 20.1.1.3. If this address
becomes unreachable, a virtual router associated with this track ID will have its priority decremented by
50. Note that the enable keyword administratively activates the tracking policy, but the policy does not
take effect until it is associated with one or more virtual routers (see the next section).
Similarly, to create a tracking policy ID (3) for IPv6 address 213:100:1::56, use the following command:
-> vrrp track 3 admin-state enable priority 50 address 213:100:1::56
If this address becomes unreachable, a virtual router associated with this track ID will have its priority
decremented by 50.
When creating a policy to track a remote IP address, the following optional parameter settings are
available to configure:
• BFD status: The status of Bidirectional Forwarding Detection for IPv4 address tracking policies (not
supported with IPv6 address tracking policies). Use the bfd-state parameter with the vrrp track
address command to enable or disable the BFD status. See “VRRP Tracking with BFD” on page 23-7
for more information.
• Delay time: Use the delay parameter with the vrrp track address command to specify the amount of
time to wait after a VRRP address track is detected as operationally up and before the associated
virtual router's priority value is incremented by the tracking policy's priority value. Setting a delay
value can help to prevent the loss of device connectivity that may occur before a virtual router
prematurely becomes the master.
Note the following:
• VRRPv2 and VRRPv3 tracking policies are created using the same vrrp track command; there isn’t a
separate command option for VRRPv3 policies.
• A virtual router must be administratively disabled before a tracking policy for the virtual router can be
added.
• VRRP tracking does not override IP address ownership (the IP address owner will always have priority
to become master, if it is available).
Associating a Tracking Policy with a Virtual Router
There are two vrrp|vrrp track-association command options for associating a tracking policy with a
virtual router:
• vrrp track-association—associates a tracking policy with a VRRPv2 virtual router.
• vrrp3 track association—associates a tracking policy with a VRRPv3 virtual router.
To associate a tracking policy with a VRRPv2 or VRRPv3 virtual router, use the vrrp track-association
or the vrrp3 track-association command option with the tracking policy ID number. For example:
-> vrrp 6 4 admin-state disable
To Next Page
Loading...
