---
**[tickets:#3342] amf: mismatch message during SC fail-over**
**Status:** assigned
**Milestone:** 5.23.12
**Created:** Mon Aug 21, 2023 01:00 AM UTC by Thang Duc Nguyen
**Last Updated:** Mon Aug 21, 2023 01:00 AM UTC
**Owner:** Thang Duc Nguyen
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!
~~~
- Then on new active SC-2, mismatch message happened
` 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.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
