Currently, there is no direct way to detect if there is already another node running with the same TIPC node_id.
If we could query say the TIPC routing table before doing stuff that within nid_tipc, then we could fail the opensaf startup when duplicate slot_id is configured.
This can fix known issues like http://devel.opensaf.org/ticket/2802
Correction http://devel.opensaf.org/ticket/2948
This ticket can also see if there are any cleanups required in nid_tipc script.
changeset: 6844:ff30714b16bb
tag: tip
user: A V Mahesh mahesh.valla@oracle.com
date: Fri Sep 18 11:00:14 2015 +0530
summary: opensaf: prevented cluster re-start on misconfigured slot_id [#464/#414]