Configuring Inheritance for a VRRP Group
Junos OS enables you to configure VRRP groups on the various subnets of a VLAN to inherit the state and configuration of one of the groups, which is known as the active VRRP group. When the vrrp-inherit-from configuration statement is included in the configuration, only the active VRRP group, from which the other VRRP groups are inheriting the state, sends out frequent VRRP advertisements, and processes incoming VRRP advertisements. The groups that are inheriting the state do not process any incoming VRRP advertisement because the state is always inherited from the active VRRP group. However, the groups that are inheriting the state do send out VRRP advertisements once every 2 to 3 minutes to facilitate MAC address learning on the switches placed between the VRRP routers.
If the vrrp-inherit-from
statement is not configured, each of the VRRP primary groups in the various subnets on the VLAN sends out separate VRRP advertisements and adds to the traffic on the VLAN.
To configure inheritance for a VRRP group, include the vrrp-inherit-from
statement at the [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-id]
hierarchy level.
[edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-id] vrrp-inherit-from active-group group-index; vrrp-inherit-from active-interface active-interface-name;
When you configure a group to inherit a state from another group, the inheriting groups and the active group must be on the same physical interface and logical system. However, the groups do not need to necessarily be on the same routing instance (as was in Junos OS releases earlier than 9.6), VLAN, or logical interface.
When you include the vrrp-inherit-from
statement for a VRRP group, the VRRP group inherits the following parameters from the active group:
advertise-interval
authentication-key
authentication-type
fast-interval
preempt | no-preempt
priority
track interfaces
track route
However, you can configure the accept-data | no-accept-data
statement for the group to specify whether the interface should accept packets destined for the virtual IP address.