osaf/services/saf/amf/amfd/ndfsm.cc | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
When Amfd is comming up as Act, it is not sending data verify message to node,
which is in state AVD_AVND_STATE_NO_CONFIG and AVD_AVND_STATE_NCS_INIT.
This creates problem of marking the upcoming node in AVD_AVND_STATE_GO_DOWN and
this stops that node to join the cluster.
When node has just come up and sent node up message to Act amfd and at that time
if Act Amfd node goes for switchover or failover, then that node has to
contact to newly Act Amfd for further communication.
So, that node needs to get data verify message from newly Amfd.
diff --git a/osaf/services/saf/amf/amfd/ndfsm.cc
b/osaf/services/saf/amf/amfd/ndfsm.cc
--- a/osaf/services/saf/amf/amfd/ndfsm.cc
+++ b/osaf/services/saf/amf/amfd/ndfsm.cc
@@ -405,7 +405,9 @@ void avd_fail_over_event(AVD_CL_CB *cb)
* Check if we are in present state. If yes then send DATA
verify
* message to all the AVND's.
*/
- if (AVD_AVND_STATE_PRESENT == avnd->node_state) {
+ if ((AVD_AVND_STATE_PRESENT == avnd->node_state) ||
+ (AVD_AVND_STATE_NO_CONFIG == avnd->node_state)
||
+ (AVD_AVND_STATE_NCS_INIT == avnd->node_state)) {
/*
* Send verify message to this node.
*/
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
