- **Milestone**: 4.5.2 --> 4.6.2
---
** [tickets:#1306] AMF: notifications during various admin operations**
**Status:** assigned
**Milestone:** 4.6.2
**Created:** Tue Apr 07, 2015 06:32 PM UTC by Srikanth R
**Last Updated:** Tue May 26, 2015 05:57 AM UTC
**Owner:** Praveen
Changeset : 6377 ( 4.6 FC)
Application / Model : Observed in 2n and NoRed models
Below are the different issues observed in the notifications generated by AMF
during admin operation
1)If the nodegroup / node is hosting the entire application and if lock
operation is issued on the node group / node , alarm and notification order are
in improper order
Initially two state change notifications about the SI moving to partially
assigned state and quiesced state should be generated and later alarm should
be generated about SI being unassigned.
But the notification and alarm are in improper order :
=== Apr 3 22:28:12 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=TWONSI1,safApp=TWONAPP"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.111 (0x6f)
additionalText = "The Assignment state of SI safSi=TWONSI1,safApp=TWONAPP
changed"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_ASSIGNMENT_STATE
Old State: SA_AMF_ASSIGNMENT_FULLY_ASSIGNED
New State: SA_AMF_ASSIGNMENT_PARTIALLY_ASSIGNED
=== Apr 3 22:28:12 - Alarm ===
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=TWONSI1,safApp=TWONAPP"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=TWONSI1,safApp=TWONAPP has no current
active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
=== Apr 3 22:28:12 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU1,safSg=SGONE,safApp=TWONAPP"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=TWONSI1,safApp=TWONAPP assigned to
SU safSu=SU1,safSg=SGONE,safApp=TWONAPP changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=TWONSI1,safApp=TWONAPP"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCED
Incase of SI lock operation, initially two state change notifications and
later alarm are generated in proper way.
2) For the lock and shutdown operations, old state is not filled up when state
change notification is issued for HA state change.
Old state ( Active) is not filled up for shutdown operation
=== Apr 7 15:21:03 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject =
"safSu=Srikanth_nored_3,safSg=SG_Srikanth_nored,safApp=nored"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=Srikanth_nored_3,safApp=nored
assigned to SU safSu=Srikanth_nored_3,safSg=SG_Srikanth_nored,safApp=nored
changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=Srikanth_nored_3,safApp=nored"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCING
Old state should be quiescing
=== Apr 7 15:21:03 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject =
"safSu=Srikanth_nored_3,safSg=SG_Srikanth_nored,safApp=nored"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=Srikanth_nored_3,safApp=nored
assigned to SU safSu=Srikanth_nored_3,safSg=SG_Srikanth_nored,safApp=nored
changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=Srikanth_nored_3,safApp=nored"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCED
3) An invalid extra notification is generated, when SG / SI is locked with
no-redundancy SU in assigned,in-service and enabled state.
=== Apr 7 14:53:46 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSg=SG_Srikanth_nored,safApp=nored"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.103 (0x67)
additionalText = "Admin state of safSg=SG_Srikanth_nored,safApp=nored changed"
sourceIndicator = SA_NTF_MANAGEMENT_OPERATION
State ID = SA_AMF_ADMIN_STATE
Old State: SA_AMF_ADMIN_LOCKED
New State: SA_AMF_ADMIN_LOCKED
=== Apr 7 15:11:58 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=Srikanth_nored_3,safApp=nored"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.104 (0x68)
additionalText = "Admin state of safSi=Srikanth_nored_3,safApp=nored changed"
sourceIndicator = SA_NTF_MANAGEMENT_OPERATION
State ID = SA_AMF_ADMIN_STATE
Old State: SA_AMF_ADMIN_LOCKED
New State: SA_AMF_ADMIN_LOCKED
4) Alarm is generated even before csi quiesced callback is accepted by the
component, during the lock operation of SG . Until, the component responds
with in prescribed time period, si should stay in fully assigned state
=== Apr 4 3:41:53 - Alarm ===
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=srikanth_2n_1,safApp=2nApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=srikanth_2n_1,safApp=2nApp has no
current active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
5) Similarly, until the component doesn't accept the ACTIVE assignment during
unlock operation of SG / SI , alarm should not be cleared and state change
notifications should not be generated for moving the si to partially assigned
state.
6) For si-swap operation, si is moved to PARTIALLY_ASSIGNED even before the
component did not respond to quiesced callback. Once the new active component
accepts the ACTIVE callback, si is moved to FULLY_ASSIGNED even before the old
active ( which shall become standby) did not respond to standby callback. HA
state change notifications during si-swap are not filling up the older states.
7) Quiescing ha state change is not generated for shutdown operation on SG /
active SU / node ( but not for SI). Instead two quiesced ha state changes are
generated for operations on SU / node.
pr 4 3:42:37 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=srikanth_2n_1,safSg=SG_srikanth_2n,safApp=2nApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=srikanth_2n_1,safApp=2nApp assigned
to SU safSu=srikanth_2n_1,safSg=SG_srikanth_2n,safApp=2nApp changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=srikanth_2n_1,safApp=2nApp"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCED
=== Apr 4 3:42:37 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=srikanth_2n_1,safApp=2nApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.111 (0x6f)
additionalText = "The Assignment state of SI safSi=srikanth_2n_1,safApp=2nApp
changed"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_ASSIGNMENT_STATE
Old State: SA_AMF_ASSIGNMENT_FULLY_ASSIGNED
New State: SA_AMF_ASSIGNMENT_PARTIALLY_ASSIGNED
=== Apr 4 3:42:37 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=srikanth_2n_1,safSg=SG_srikanth_2n,safApp=2nApp"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=srikanth_2n_1,safApp=2nApp assigned
to SU safSu=srikanth_2n_1,safSg=SG_srikanth_2n,safApp=2nApp changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=srikanth_2n_1,safApp=2nApp"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCED
---
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
