[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring Inheritance for a VRRP Group

JUNOS Software 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. By configuring inheritance, you can prevent VRRP groups other than the active group from sending out VRRP advertisements. 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 VRRP advertisements; the groups inheriting the state do not send any VRRP advertisements, because the state is maintained only on the group from which the state is inherited.

If the vrrp-inherit-from statement is not configured, each of the VRRP master 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]:

[edit interfaces interface-name unit logical-unit-number family inet address address vrrp-group group-id]vrrp-inherit-from vrrp-group;

When you configure a group to inherit a state from another group, note the following conditions:

  • Both inheriting groups and active groups must be on the same physical interface and logical system. However, the groups need not necessarily be on same VLAN or logical interface.
  • Both inheriting groups and active groups must be on the same routing instances; however, this limitation does not apply for groups on the integrated routing and bridging (IRB) interfaces.

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.


Published: 2010-04-28

[an error occurred while processing this directive]