- **status**: unassigned --> accepted
- **assigned_to**: Praveen
- **Milestone**: future --> 4.5.FC



---

** [tickets:#108] AMF - Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms 
automatically**

**Status:** accepted
**Milestone:** 4.5.FC
**Created:** Mon May 13, 2013 05:39 AM UTC by Nagendra Kumar
**Last Updated:** Mon May 13, 2013 05:56 AM UTC
**Owner:** Praveen

Migrated from http://devel.opensaf.org/ticket/1801
--------------------------------------------------------

I caused this alarm to be raised by rendering the component non-executable. 
Once satisfied with the result (alarm generated) I re-enabled the component. 
The component was eventually recovered, comes up and assumes standby - but the 
alarm remains. 


If I lock an SG, I get alarms raised that automatically clear upon unlock of 
the SG. Should the behavior be consistent? My expectation was that once the 
affected component started, the alarm would automatically clear.
--------------------------------------------------------

Changed 2 years ago by hafe ¶
  ■owner changed from nagendra to hafe 
■status changed from new to accepted 
■version changed from 4.0.1 to 4.2.0 
■type changed from defect to enhancement 
■summary changed from SA_AMF_NTFID_COMP_INSTANTIATION_FAILED fails to clear 
automatically to Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms 
automatically 
Will be published together with #1194.


Changed 2 years ago by hafe ¶
  ■summary changed from Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms 
automatically to AMF - Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms 
automatically 
■version changed from 4.2.0 to 4.0.1 
■milestone set to 4.2.0.GA 
Changed 2 years ago by hafe ¶
  My patch produces this output:


May 3 7:05:15 - Alarm


eventType = SA_NTF_ALARM_PROCESSING
notificationObject = 
"safComp=AmfDemo?,safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.2 (0x2)
additionalText = "Previous raised alarm of 
safComp=AmfDemo?,safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?1 is now cleared"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_CLEARED


OK?


Changed 2 years ago by hafe ¶
  ■patch_waiting changed from no to yes 
Changed 2 years ago by creid ¶
  Looks good to me. Seems consistent with other auto-behaviour.


Changed 20 months ago by hafe ¶
  ■milestone changed from 4.2.0.GA to 4.3.GA 
Changed 2 months ago by hafe ¶
  ■milestone changed from 4.3.GA to future_releases 




---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to