osaf/services/saf/amf/config/amf_classes.xml | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
If the SI Unassigned Alarm is raised before headless by locking SU for
instance, then
after cluster recovers from headless and unlocking the SU, this alarm is not
cleared.
As the application can reside in PL nodes and it's right to expect the previous
raised
alarm should be cleared once the SI gets back assignments. The patch adds new
attribute
saAmfUnassignedAlarmStatus attribute to SaAmfSI class to memorize the variable
alarm_sent
for headless.
diff --git a/osaf/services/saf/amf/config/amf_classes.xml
b/osaf/services/saf/amf/config/amf_classes.xml
--- a/osaf/services/saf/amf/config/amf_classes.xml
+++ b/osaf/services/saf/amf/config/amf_classes.xml
@@ -641,6 +641,14 @@
<type>SA_UINT32_T</type>
<category>SA_RUNTIME</category>
</attr>
+ <attr>
+ <name>saAmfUnassignedAlarmStatus</name>
+ <type>SA_UINT32_T</type>
+ <category>SA_RUNTIME</category>
+ <flag>SA_PERSISTENT</flag>
+ <flag>SA_CACHED</flag>
+ <default-value>0</default-value>
+ </attr>
</class>
<class name="SaAmfSvcType">
<category>SA_CONFIG</category>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
