Symptom
"After iMDR, fabio_svr(162) didn't regist as spoofer", we are seeing this log message during 424 to 432 image upgrade
Conditions
fabio_svr process is one of the critical processes in CRS SW Data path. Because fabio_svr was removed from spoofer tier and should be registered as forwarding tier.
From the fabio_svr POV, v2 process is removed the spoofer tier registration and should be in forwarding tier. But still the sysmgr thinks that the fabio_svr was a spoofer process and expects to register in spoofer tier. It seems that new tier mechanism not taken into effect after image upgrade.
As part of image upgrade this was not a big issue. But from 4.3.2 onwards there is support for lacp short and cisco extension. Also if fabio_svr not placed in proper tier and not restarted properly during issu, sure it'll flap the bundle interfaces. Kindly look into this and provide proper solution for this issue.
