- **status**: review --> invalid
- **Comment**:
It is not as per Specs.
---
** [tickets:#363] Error incorrectly indicated in alarms after locking SIs, SGs**
**Status:** invalid
**Milestone:** 4.3.3
**Created:** Fri May 31, 2013 03:29 AM UTC by Nagendra Kumar
**Last Updated:** Thu Jul 17, 2014 09:45 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/1836
When locking an SI or an SG, an alarms is raised wherein the probable cause
(alarmNotification.probableCause) is set to SA_NTF_SOFTWARE_ERROR. Because the
alarm is raised as a result of an administrative action, the probable cause
should indicate something more appropriate. Giving credit where due, David Fick
suggested SA_NTF_OUT_OF_SERVICE, which is certainly more appropriate.
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
