TC #46: Related to Alarms and Notification: Notification and alarms,
configuration and logs(TC 46) attached in the ticket.
1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3 and
SU2(Stb) on PL-4 as below:
immcfg -f /opt/amf_demo/AppConfig-2N.xml_2
amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
2. Keep sleep and exit 1 in instantiation script as below:
start|instantiate)
#sleep 7
shift
start $*
sleep 3
exit 1
RETVAL=$?
3. Stop controller.
4. Kill demo. Demo will move into instantiation failed state.
5. Start controller and subscribe for all notifications (ntfsubscribe >
/tmp/notification) on controller.
6. Now, SU2 will get Act assignment.
In the notification, two extra notifications "state change" for Standby came
for SU2, which is wrong because SU2 assignment didn't change:
=== Feb 17 11:04:22 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=AmfDemo1,safApp=AmfDemo1 assigned to
SU safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=AmfDemo1,safApp=AmfDemo1"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_STANDBY
=== Feb 17 11:04:22 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=AmfDemo,safApp=AmfDemo1 assigned to
SU safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1 changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=AmfDemo,safApp=AmfDemo1"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_STANDBY
TC #47: Related to Alarms and Notification: Notification and alarms,
configuration and logs(TC 47) attached in the ticket.
1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3 and
SU2(Stb) on PL-4 as below:
immcfg -f /opt/amf_demo/AppConfig-2N.xml_2
amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
2. Keep gdb in csi set of Act component and Lock SU (amf-adm lock
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1).
3. Stop controller and then respond from gdb.
4. Start controller and subscribe for all notifications(ntfsubscribe >
/tmp/notification_after_reboot).
5. The notification should be in continuation of the previous notification, but
it looks SI transitions from UNASSIGNED to PARTIALLY_ASSIGNED. Ideally it
should be from FULLY_ASSIGNED to PARTIALLY_ASSIGNED:
=== Feb 17 12:04:15 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=AmfDemo1,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.111 (0x6f)
additionalText = "The Assignment state of SI safSi=AmfDemo1,safApp=AmfDemo1
changed"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_ASSIGNMENT_STATE
Old State: SA_AMF_ASSIGNMENT_UNASSIGNED
New State: SA_AMF_ASSIGNMENT_PARTIALLY_ASSIGNED
=== Feb 17 12:04:15 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSi=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.111 (0x6f)
additionalText = "The Assignment state of SI safSi=AmfDemo,safApp=AmfDemo1
changed"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_ASSIGNMENT_STATE
Old State: SA_AMF_ASSIGNMENT_UNASSIGNED
New State: SA_AMF_ASSIGNMENT_PARTIALLY_ASSIGNED
I have attached notification_normal_scenario_without_reboot when I locked SU
and then collected notifications. Ideally, notifications should be like that
even the node is rebooted.
TC #48: Related to Alarms and Notification: Notification and alarms,
configuration and logs(TC 48) attached in the ticket.
1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3 and
SU2(Stb) on PL-4 as below:
immcfg -f /opt/amf_demo/AppConfig-2N.xml_2
amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
2. Keep gdb in csi set of Act component and Lock SI (amf-adm lock
safSi=AmfDemo,safApp=AmfDemo1).
3. Stop controller and then respond from gdb.
4. Start controller and subscribe for all notifications(ntfsubscribe >
/tmp/notification_after_reboot).
5. Apart from some problems reported above, additionally, SI unassignment alarm
is missing for safSi=AmfDemo,safApp=AmfDemo1 (notification_after_reboot
attached). The following alarm is missing, which comes under normal scenario if
the controller is there(You can find it in
notification_normal_scenario_without_reboot attached):
=== Feb 17 17:14:10 - Alarm ===
eventType = SA_NTF_ALARM_PROCESSING
notificationObject = "safSi=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.5 (0x5)
additionalText = "SI designated by safSi=AmfDemo,safApp=AmfDemo1 has no current
active assignments to any SU"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_MAJOR
TC #49: Related to Alarms and Notification: Notification and alarms,
configuration and logs(TC 49) attached in the ticket.
1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3:
immcfg -f /opt/amf_demo/AppConfig-2N.xml_2
amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
2. Keep gdb in csi set of Act component and shutdown SU1 (amf-adm shutdown
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1).
3. Stop controller and then respond from gdb.
4. Start controller and subscribe for all notifications(ntfsubscribe >
/tmp/notification_after_reboot).
5. The state change notification for SA_AMF_HA_QUIESCED is missing(when
controller is up, we get SA_AMF_HA_QUIESCED only), we are getting instead state
change notification of SA_AMF_HA_QUIESCING:
=== Feb 17 19:28:09 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=AmfDemo1,safApp=AmfDemo1 assigned to
SU safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=AmfDemo1,safApp=AmfDemo1"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCING
=== Feb 17 19:28:09 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=AmfDemo,safApp=AmfDemo1 assigned to
SU safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=AmfDemo,safApp=AmfDemo1"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCING
TC #50: Related to Alarms and Notification: Notification and alarms,
configuration and logs(TC 50) attached in the ticket.
1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3 as below:
immcfg -f /opt/amf_demo/AppConfig-2N.xml_2
amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
2. Keep gdb in csi set of Act component and shutdown SI (amf-adm shutdown
safSi=AmfDemo,safApp=AmfDemo1).
3. Stop controller and then respond from gdb.
4. Start controller and subscribe for all notifications(ntfsubscribe
> /tmp/notification_after_reboot).
5. The following notification is missing(missing in
notification_after_reboot, but you can find it in
notification_normal_scenario_without_reboot):
=== Feb 17 19:38:49 - State Change ===
eventType = SA_NTF_OBJECT_STATE_CHANGE
notificationObject = "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.110 (0x6e)
additionalText = "The HA state of SI safSi=AmfDemo,safApp=AmfDemo1 assigned to
SU safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 changed"
- additionalInfo: 0 -
infoId = 2
infoType = 10
infoValue = "safSi=AmfDemo,safApp=AmfDemo1"
sourceIndicator = SA_NTF_OBJECT_OPERATION
State ID = SA_AMF_HA_STATE
Old State:
New State: SA_AMF_HA_QUIESCED
Thanks
-Nagu
> -----Original Message-----
> From: Nagendra Kumar
> Sent: 16 February 2016 21:21
> To: minh chau; hans.nordeb...@ericsson.com; gary....@dektech.com.au;
> Praveen Malviya
> Cc: opensaf-devel@lists.sourceforge.net
> Subject: Re: [devel] FW: [PATCH 0 of 5] Review Request for amf: Add support
> for cloud resilience [#1620] V2
>
> TC #43: Related to Alarms and Notification: Notification and alarms (TC 43)
> attached in the ticket.
> Start single controller and a payload. Stop controller. Start controller and
> subscribe for all notifications (ntfsubscribe > /tmp/notification) on
> controller.
> The following notifications/alarms looks inappropriate:
> 1. State change notification of safSu=PL-
> 3,safSg=NoRed,safApp=OpenSAF from Disable to Enable. Since PL-3 is
> already running, the oper state shouldn't change.
> 2. Pres state notification of safSu=PL-3,safSg=NoRed,safApp=OpenSAF
> from UNINSTANTIATED to INSTANTIATED. [PL-3 is up].
> 3. The Assignment state of safSi=NoRed2,safApp=OpenSAF change.
> 4. HA state of SI safSi=NoRed2,safApp=OpenSAF.
> 5. The following shouldn't come because PL-3 is up. Also since SC-2 and
> PL-4 are down, so these shouldn't come because these don't come when SC-
> 1 comes first and no other node is up and running, so why these come when
> one payload is up:
> a. SI designated by safSi=NoRed1,safApp=OpenSAF has no current
> active assignments to any SU
> b. SI designated by safSi=NoRed3,safApp=OpenSAF has no current
> active assignments to any SU
> c. SI designated by safSi=NoRed4,safApp=OpenSAF has no current
> active assignments to any SU
> d. SI designated by safSi=SC-2N,safApp=OpenSAF has no current
> active assignments to any SU
> 6. The following shouldn't come as controller never sent alarm for it.
> This doesn't come when controller is coming up and no other node is up, so
> different when one payload is up:
> Previous raised alarm of safSi=NoRed1,safApp=OpenSAF is now
> cleared
> Previous raised alarm of safSi=SC-2N,safApp=OpenSAF is now
> cleared
> 7. Why oper state of PL-3 should change?
> Oper state safAmfNode=PL-3,safAmfCluster=myAmfCluster changed
> deom Dis to Enabled.
>
> TC #44: The same problem for applications SUs and SIs that are assigned
> on
> PL-3.
> TC #45: Related to Alarms and Notification: Notification and alarms,
> configuration and logs(TC 45) attached in the ticket.
> 1. Start single controller and a payload. 2N Appl, SU1(Act) on PL-3 as below:
> immcfg -f /opt/amf_demo/AppConfig-2N.xml_2 amf-adm unlock-in
> safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
> amf-adm unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
>
> 2. Keep sleep and exit 1 in instantiation script as below:
> start|instantiate)
> #sleep 7
> shift
> start $*
> sleep 3
> exit 1
> RETVAL=$?
> 3. Stop controller.
> 4. Kill demo. Demo will move into instantiation failed state.
> 5. Start controller and subscribe for all notifications (ntfsubscribe >
> /tmp/notification) on controller.
>
> In the notification, there is no "oper state change"(pasted below)
> notification for safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1. This
> notification comes when controller is up and you kill demo forcing it to go
> into inst failed state:
> === Feb 16 20:33:18 - State Change === eventType =
> SA_NTF_OBJECT_STATE_CHANGE notificationObject =
> "safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1"
> notifyingObject = "safApp=safAmfService"
> notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.108 (0x6c)
> additionalText = "Oper state safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
> changed"
> sourceIndicator = SA_NTF_OBJECT_OPERATION State ID =
> SA_AMF_OP_STATE Old State: SA_AMF_OPERATIONAL_ENABLED New State:
> SA_AMF_OPERATIONAL_DISABLED
>
> Thanks
> -Nagu
------------------------------------------------------------------------------
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=272487151&iu=/4140
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
