This article describes the issue of Junos being unable to generate the VRRPv4 mastership change syslogs, when it generates the VRRPv6 logs; if it does not have the SNMP configuration.

When both VRRPv4 and v6 are being used in the same interface, VRRP mastership switchover occurs, and there is no SNMP related configuration, then no VRRPv4 logs are generated; instead, only VRRPv6 logs are generated.

This issue occurs if the following condition exists:

VRRP-Traps: disabled

As per the code, syslog will not occur, if traps are disabled. There is no such check in the code for IPv6; so IPv6 syslogs are generated normally. The generation of errmsg/syslog should not be dependent on the SNMP configuration. Junos will fix this in 12.3R1.

xxx@routername> show vrrp detail
Physical interface: ge-1/0/1, Unit: 0, Address: 100.0.0.2/24
Index: 334, SNMP ifIndex: 542, VRRP-Traps: disabled

Physical interface: ge-1/0/1, Unit: 0, Address: fec0::5:0:0:5/64
Index: 334, SNMP ifIndex: 542, VRRP-Traps: disabled

Aug 29 14:02:10 routername vrrpd[1637]: VRRPD_NEW_MASTER: Interface ge-1/0/1.0 (local address 100.0.0.2) became VRRP master for group 1

As a workaround, perform the following procedure to generate the VRRPv4 mastership change syslogs:

1. Set the SNMP configuration:
   

   xxx@routername> show configuration snmp 
   community public;

2. Check the VRRP interface's VRRP-Trap status:
   

   xxx@routername> show vrrp detail
   Physical interface: ge-1/0/1, Unit: 0, Address: 100.0.0.2/24
   Index: 334, SNMP ifIndex: 542, VRRP-Traps: enabled
   
   Physical interface: ge-1/0/1, Unit: 0, Address: fec0::5:0:0:5/64
   Index: 334, SNMP ifIndex: 542, VRRP-Traps: enabled

3. Check if both VRRP IPv4 and IPv6 messages are generated in syslog:

   Aug 29 14:07:43 routername vrrpd[1637]: VRRPD_NEW_MASTER: Interface ge-1/0/1.0 (local address 100.0.0.2)
   became VRRP master for group 1
   Aug 29 14:07:43 routername vrrpd[1637]: VRRPD_NEW_MASTER: Interface ge-1/0/1.0 (local address fec0::5:0:0:5) 
   became VRRP master for group 2