Hi,
We are using OpenSAF 5.2, and have been experiencing some anomalies with the
IMM when using Admin operations Node Lock, and Node Lock Instantiate.
1) On the ACTIVE system controller node (SC1), all the opensaf daemons are
up and running normally.
a. We Issue a Node Lock Command - This completes successfully.
b. We issue a Node Lock Instantiate Command - We've seen instances of one
of the following results:
i. The next IMM Poll
failed with error SA_AIS_ERR_BAD HANDLE , or
ii. The next IMM Poll
failed with error 2 on saImmOmSearchInitialize_2 (SA_AIS_ERR_LIBRARY).
Can someone please clarify if this is expected behavior? We are expecting the
OpenSAF deamons to remain up and running, through the LOCK, and
LOCK-INSTANTIATE operations. At some point, thereafter, we expect to issue an
UNLOCK-Instantiation, and an UNLOCK command, to restore the node to its
original operational condition. This gives an operator complete control of the
node.
If I am misinterpreting how the OpenSAF should operate in response to these
admin operations, can someone provide an explanation of how to achieve the
desired results?
Thanks.
Jim
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
