This article describes the issue of the Virtual Router Redundancy Protocol (VRRP) backup changing to the master role, without any operation. Also, at this time, both devices running VRRP will become master.
In certain cases, as per VRRP traceoptions, it is seen that VRRP backup changes to the master role as it receives the PPMP_PACKET_ADJ_DOWN received message:
Dec 3 17:30:37 vrrpd_update_state_machine, vlan.000.054.000.0000:0000:0000:0000:0000:0000:0336:1085.001 state: backup Dec 3 17:30:37 vrrp_fsm_update IFD: vlan.000.054.000.0000:0000:0000:0000:0000:0000:0336:1085.001 event: transition Dec 3 17:30:37 vrrp_fsm_transition: vlan.000.054.000.0000:0000:0000:0000:0000:0000:0336:1085.001 state from: backup Dec 3 17:30:37 vrrp_fsm_update_for_inherit IFD: vlan.000.054.000.0000:0000:0000:0000:0000:0000:0336:1085.001 event: transition Dec 3 17:30:37 vrrpd_process_ppmd_packet : PPMP_PACKET_ADJ_DOWN received < Dec 3 17:30:37 vrrpd_update_state_machine, vlan.000.036.000.0000:0000:0000:0000:0000:0000:0324:1085.000 state: backup Dec 3 17:30:37 vrrp_fsm_update IFD: vlan.000.036.000.0000:0000:0000:0000:0000:0000:0324:1085.000 event: transition Dec 3 17:30:37 vrrp_fsm_transition: vlan.000.036.000.0000:0000:0000:0000:0000:0000:0324:1085.000 state from: backup Dec 3 17:30:37 vrrp_fsm_update_for_inherit IFD: vlan.000.036.000.0000:0000:0000:0000:0000:0000:0324:1085.000 event: transition Dec 3 17:30:37 vrrpd_process_ppmd_packet : PPMP_PACKET_ADJ_DOWN received <
To understand the cause of this issue, please collect the following logs:
- Enable VRRP traceoptions:
set protocols vrrp traceoptions flag all set protocols vrrp traceoptions file vrrp_logs size 2m files 10
- Enable PPM traceoptions. As this is a hidden command, make sure to type the complete commands:
set routing-options ppm traceoptions file ppm_logs set routing-options ppm traceoptions file size 2m set routing-options ppm traceoptions file files 10 set routing-options ppm traceoptions flag packet set routing-options ppm traceoptions flag pipe
- Add event-options to obtain the information when the backup became the master:
set event-options policy vrrp_master_change events vrrpd_new_master set event-options policy vrrp_master_change then execute-commands commands "show interfaces extensive | save /var/log/interfaces1.log" set event-options policy vrrp_master_change then execute-commands commands "show spanning-tree bridge | save /var/log/stp1.log" set event-options policy vrrp_master_change then execute-commands commands "show spanning-tree interface | save /var/log/stp2.log" set event-options policy vrrp_master_change then execute-commands commands "show spanning-tree bridge | save /var/log/stp3.log" set event-options policy vrrp_master_change then execute-commands commands "show spanning-tree interface | save /var/log/stp4.log" set event-options policy vrrp_master_change then execute-commands output-format text
If the issue occurs again, collect the output of request support information and all of the files under /var/log from both of the VRRP systems for further analysis.