Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When Router is master VRRP, client devices cannot ping to VIP even though ARP is resolved.
ifmgr process restart according to lab test. Possibly some other events which can trigger IM disconnection from clients (hsrp or vrrp). ifmgr restart is such an event. Shut/no shut of bundle interfaces is known to be another such a trigger (though not always). In the case of this bundle flap, sometimes a underlying need prompts ifmgr to resync with its clients (including hsrp and vrrp), and this triggers the issue. No other trigger is known as of now, based on experimental data. (Will be added to this list once known).
process restart vrrp. (or hsrp).
Traffic through affected sessions (affected sessions are in Master state) will be affected. Issue is Day 1 issue, present in 5.1.3, 5.3.3 (smu available) and 5.3.4 (smu available). Fixed from 6.1.4, 6.2.2 and 6.3.1 Issue is common to both hsrp and vrrp. Issue is not specific to any particular vrrp or hsrp config. Issue is platform independent, so can affect any XR router. Issue may not happen always, even with trying all the steps to reproduce (based on experimental data). Note that if router is in "standby/backup" state, there is no issue to the traffic. If the router gets affected to the bug, then when a affected router moves to "Master/Active" state, the traffic drop will happen (because then the virtual mac is not programmed on it, due to the issue). symptoms -------- In "show vrrp detail" or "show hsrp detail", the affected session is Master, but its virtual mac state is reserving or reserved. Example ----- TenGigE0/2/0/2.1042 - IPv4 vrID 142 State is Master ... Virtual MAC address is 0000.5E00.018e, state is reserving Master router is local another symptom is, in "show vrrp api-statistics" or "show hsrp api-statistics", a high error count will be seen for the entry "imc_register_callback" Show vrrp api-statistics .. im_disconnect 0/0 1/0 Never imc_control_server_bind 0/0 20050/0 Never imc_control_server_unbind 0/0 20049/0 Never imc_register_callback 0/0 2/20048 Jan 9 10:29:42.275 <<< 20048 errors. imc_conn_ctx_to_connid 0/0 20050/0 Never the output of above commands will be available in "show tech hsrp" or "show tech vrrp". Then IMC callback error counter increase is a necessary and sufficient symptom condition. The IMC callback error counter will restart after the process restart. The restart of the process is the minimal way to recover the issue. Reconfiguring of the vrrp/hsrp interface configu will not solve the issue.