- **Component**: amf --> unknown


---

** [tickets:#2880] amf: Payload is out of control from active AMFD**

**Status:** fixed
**Milestone:** 5.18.09
**Created:** Mon Jun 18, 2018 06:13 AM UTC by Thuan
**Last Updated:** Thu Aug 30, 2018 12:45 PM UTC
**Owner:** Thuan


During SC failover, new active by somehow got PL-16 left cluster, but PL-16 
still see Active AMFD.
From that, any message from PL-16 will be invalid since msg_id reset to 0.

May  3 12:59:54 SC-1 tipclog[5917]: Lost link <1.1.1:eth1-1.1.16:eth1> on 
network plane A
May  3 12:59:54 SC-1 tipclog[5917]: Established link <1.1.1:eth1-1.1.16:eth1> 
on network plane A
...
May  3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active
May  3 13:05:51 SC-1 osafimmd[17537]: NO Old active NOT present => send discard 
node payload 2100f
May  3 13:05:51 SC-1 osafamfnd[17765]: NO AVD NEW_ACTIVE, adest:1
May  3 13:05:51 SC-1 osafamfd[17733]: NO Node 'SC-2' left the cluster
May  3 13:05:51 SC-1 osafamfd[17733]: NO FAILOVER StandBy --> Active DONE!
May  3 13:05:51 SC-1 osafamfd[17733]: WA avd_data_update_req_evh: node 2100f, 
receive msg_id(4389) in invalid node state 0
May  3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
4390, msg type 8, from 2100f should be 4389
May  3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
4391, msg type 8, from 2100f should be 4389
May  3 13:05:51 SC-1 osafamfd[17733]: NO Node 'PL-16' left the cluster 
May  3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
4394, msg type 8, from 2100f should be 1
May  3 13:05:51 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
4395, msg type 8, from 2100f should be 1
…
May  3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
5043, msg type 8, from 2100f should be 1
May  3 14:09:28 SC-1 osafamfd[17733]: WA avd_msg_sanity_chk: invalid msg id 
5044, msg type 8, from 2100f should be 1

PL-16 operational state become disable but it’s still available.
The problem is not reproducible but customer claim that OPENSAF cannot recover 
it automatically.
Customer has to reboot manually to recover PL-16.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to