Alcatel-Lucent 6850-48 ネットワークガイド

ページ / 1162
Configuring VRRP
Creating Tracking Policies
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
page 32-25
Creating Tracking Policies
To create a tracking policy, use th
 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 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 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.
Note the following:
• 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 prior-
ity to become master, if it is available).
Associating a Tracking Policy with a VRRPv2/VRRPv3 Virtual 
Router
To associate a tracking policy with a virtual router, use the 
 command with the 
tracking policy ID number. In this example, virtual router 6 on VLAN 4 is disabled first so that tracking 
policy 3 may be associated with it:
-> vrrp 6 4 disable
-> vrrp 6 4 track-association 3
When the virtual router is re-enabled, tracking policy 3 will be used for that virtual router.
A tracking policy should not be associated with a virtual router on the same port or interface. For example:
-> ip interface vlan-4 address 10.1.1.1 vlan 4
-> vrrp track 2 ipv4-interface vlan-4
-> vrrp 5 4 track-association 2
This configuration is allowed but will not really have an effect. If the associated interface goes down, this 
virtual router goes down as well and the tracking policy is not applied.
Note. A master and a backup virtual router should not be tracking the same IP address; otherwise, when 
the IP address becomes unreachable, both virtual routers will have their priorities decremented, and the 
backup may temporarily take over if the master discovers that the IP address is unreachable before the 
backup.