Hi Nagendra, Yes, your assumptions are correct. We had a component with a recovery policy of NODE_FAILOVER, and Node Auto Repair disabled. The component did NOT fail due to INSTANTIATION_FAILURE, or TERMINATION_FAILURE.
What we need is a way to ADMINISTRATIVELY recover the node, without rebooting the node. The most straightforward way of doing this is "Repair the Node", but currently, this feature is not supported by the product. As a workaround, we tried to walk through each of the SUs on the node, and repair them. But we were prevented from doing this as well. Jim -----Original Message----- From: Nagendra Kumar <[email protected]> Sent: Tuesday, January 01, 2019 9:13 AM To: Carroll, James R (US) <[email protected]>; [email protected] Cc: [email protected] Subject: EXTERNAL: RE: [users] Need for Repair at Node Level Hi Jim, I assume the following, please confirm: 1. The component(say ABC) which faulted has recovery either of SA_AMF_NODE_SWITCHOVER(4) or SA_AMF_NODE_FAILOVER(5) configured, which leads saAmfNodeOperState to SA_AMF_OPERATIONAL_DISABLED(2). 2. saAmfNodeAutoRepair for that node is set to disabled(because if saAmfNodeAutoRepair is enabled then the node will be rebooted). 3. The component(ABC), which faulted, didn't go into SA_AMF_PRESENCE_INSTANTIATION_FAILED(6) or SA_AMF_PRESENCE_TERMINATION_FAILED(7). >> So, given this limitation, we have tried to work around this by >> issuing a administrative Repair operation to each of the Sus on the node. >> However, these operations also fail. We believe this is because the Operational State of the node is Disabled. True, since saAmfNodeOperState is DISABLED(2), so the admin repair at SU(having faulted components) is also failing to repair. Ideally, the node should be repaired by SA_AMF_ADMIN_REPAIRED admin command(should also repair the SUs faulted and in SA_AMF_PRESENCE_INSTANTIATION_FAILED(6) or SA_AMF_PRESENCE_TERMINATION_FAILED(7)). Thanks -Nagendra High Availability Solutions www.hasolutions.in [email protected] Hyderabad, India: +91-9866424860 | Delaware, USA: +1 508-422-7725 -----Original Message----- From: Carroll, James R [mailto:[email protected]] Sent: 04 December 2018 00:10 To: [email protected] Subject: [users] Need for Repair at Node Level Hi all, We are using OpenSAF 5.2.0, and have come up against the need for Administrative Node Repair. According to the Compliance Report for AMF, 9.4.10 SA_AMF_ADMIN_REPAIRED Yes, Partly This administrative operation is applicable to AMF node and service unit. Only repair of service unit is supported. So, given this limitation, we have tried to work around this by issuing a administrative Repair operation to each of the Sus on the node. However, these operations also fail. We believe this is because the Operational State of the node is Disabled. Is there any suggestion or recommendation on how to repair a node that has become disabled, though administrative commands? Or, is it possible that this limitation has been resolved in a later release of OpenSAF? Thanks Jim _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
