The scenario
* Turn off active SC-1
* SC-2 takes active
2023-08-14T01:23:54.857+02:00 SC-2 osafamfd[22078]: NO FAILOVER StandBy --> Active
...
2023-08-14T01:23:54.867+02:00 SC-2 osafamfd[22078]: NO Failing over OpenSAF components only
2023-08-14T01:23:54.874+02:00 SC-2 osafamfd[22078]: NO FAILOVER StandBy --> Active DONE!
2023-08-14T01:24:04.904+02:00 SC-2 osafamfd[22078]: WA avd_msg_sanity_chk: invalid msg id 377, msg type 5, from 2040f should be 376
Some information
When SC fail-overs, the new AMFD active will send AVSV_D2N_DATA_VERIFY_MSG message event to AMFND. When AMFND processes this event, it also send the protection group (PG) start message to new active AMFD. In case MDS has not updated its tables by this time, then AMFND can not send to AMFD.
Solution in this case is to force AMFND send to specified AMFD.
Diff:
commit b0f9985b8f37a93afa28c76ed409bf4847d6487e (HEAD -> develop, origin/develop, ticket-3342)
Author: thang.d.nguyen thang.d.nguyen@dektech.com.au
Date: Wed Aug 16 18:55:08 2023 +0700