After SC absence, active amfd will reject messages from 'veteran' amfnds until
its local amfnd has started. During this period, if a PG track action msg
is sent and rejected by amfd, it will cause the sending amfnd to lose sync
with amfd. So we should also queue this message to be re-sent.
Oct 11 18:06:01 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 3, msg type 8, from 2030f should be 2
Oct 11 18:06:01 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 4, msg type 8, from 2030f should be 2
Oct 11 18:06:10 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 5, msg type 6, from 2030f should be 2
Oct 11 18:06:20 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 6, msg type 8, from 2030f should be 5
Oct 11 18:06:20 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 7, msg type 8, from 2030f should be 5
Oct 11 18:06:20 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 8, msg type 8, from 2030f should be 5
Oct 11 18:06:20 SC-1 osafamfd[12545]: WA avd_msg_sanity_chk: invalid msg id 9, msg type 8, from 2030f should be 5
After set_leds event is received by amfnd, it can be seen that msgs with id 3 and 4 are retransmitted, but 5 is not received by amfd.
changeset: 8222:0fbc9742846a
branch: opensaf-5.0.x
tag: tip
parent: 8217:810f6dde01cb
user: Gary Lee gary.lee@dektech.com.au
date: Fri Oct 14 17:41:00 2016 +1100
summary: amfnd: queue PG track action msgs [#2115]
changeset: 8221:362d30af4503
branch: opensaf-5.1.x
parent: 8219:d4c05e5a66e5
user: Gary Lee gary.lee@dektech.com.au
date: Fri Oct 14 17:23:57 2016 +1100
summary: amfnd: queue PG track action msgs [#2115]
changeset: 8220:ae6805b74777
parent: 8218:3565b16a8f88
user: Gary Lee gary.lee@dektech.com.au
date: Fri Oct 14 17:23:37 2016 +1100
summary: amfnd: queue PG track action msgs [#2115]
Related
Tickets:
#2115