- **status**: assigned --> accepted
- **Comment**:
Analysis:
For a NPI SU, only one SI can be assigned to the whole SU. Remaining SIs if
configured will remain unassign. Earliar creating a SU in the system was
allowed only in LOCK_IN state. So in typical steps, a used to configure a SU in
the system in LOCK_IN state and after this user perform unlock-in operation on
the SU. During this UNLOCK_IN opearation, AMF adjusts SG configuration
attributes for example for NPI application it adjusts the value of
saAmfSGMaxActiveSIsperSU and saAmfSGMaxStandbySIsperSU. So SU will not be
reproducible in this way.
Now from 4.5 release creation of SU is allowed if either node or sg is in
LOCK_IN state. In this reported issue SUs are created by keeping SG in LOCK_IN
state.
---
** [tickets:#1564] AMF : SG went to unstable , during initial bringup of 2N NPI
application**
**Status:** accepted
**Milestone:** 4.5.2
**Created:** Sat Oct 24, 2015 04:40 AM UTC by Srikanth R
**Last Updated:** Wed Oct 28, 2015 06:00 AM UTC
**Owner:** Praveen
**Attachments:**
-
[2nIssue.sh](https://sourceforge.net/p/opensaf/tickets/1564/attachment/2nIssue.sh)
(15.5 kB; application/x-shellscript)
Changeset : 6901
Application : 4 Sus with all NPI components.
With the attached configuration, SG went to unstable for unlock operation on
locked SG. Below is the saflog snippet from active controller.
2535 20:08:10 10/23/2015 NO safApp=safAmfService "Admin op
"UNLOCK_INSTANTIATION" initiated for 'safSg=TestApp_SG1,safApp=TestApp_TwoN',
invocation: 5046586572801"
2536 20:08:10 10/23/2015 NO safApp=safAmfService
"safSg=TestApp_SG1,safApp=TestApp_TwoN AdmState LOCKED_INSTANTIATION => LOCKED"
2537 20:08:10 10/23/2015 NO safApp=safAmfService "Admin op done for
invocation: 5046586572801, result 1"
2538 20:08:12 10/23/2015 NO safApp=safAmfService "Admin op "UNLOCK"
initiated for 'safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation:
5050881540098"
2539 20:08:12 10/23/2015 NO safApp=safAmfService
"safSg=TestApp_SG1,safApp=TestApp_TwoN AdmState LOCKED => UNLOCKED"
2540 20:08:12 10/23/2015 NO safApp=safAmfService
"safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN ReadinessState
OUT_OF_SERVICE => IN_SERVICE"
2541 20:08:12 10/23/2015 NO safApp=safAmfService
"safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN ReadinessState
OUT_OF_SERVICE => IN_SERVICE"
2542 20:08:12 10/23/2015 NO safApp=safAmfService
"safSu=TestApp_SU3,safSg=TestApp_SG1,safApp=TestApp_TwoN ReadinessState
OUT_OF_SERVICE => IN_SERVICE"
2543 20:08:12 10/23/2015 NO safApp=safAmfService
"safSu=TestApp_SU4,safSg=TestApp_SG1,safApp=TestApp_TwoN ReadinessState
OUT_OF_SERVICE => IN_SERVICE"
2544 20:08:12 10/23/2015 NO safApp=safAmfService
"safSi=TestApp_SI1,safApp=TestApp_TwoN assigned to
safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN HA State 'ACTIVE'"
2545 20:08:12 10/23/2015 NO safApp=safAmfService
"safSi=TestApp_SI2,safApp=TestApp_TwoN assigned to
safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN HA State 'ACTIVE'"
2546 20:08:12 10/23/2015 NO safApp=safAmfService
"safSi=TestApp_SI3,safApp=TestApp_TwoN assigned to
safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN HA State 'ACTIVE'"
2547 20:08:12 10/23/2015 NO safApp=safAmfService
"safSi=TestApp_SI4,safApp=TestApp_TwoN assigned to
safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN HA State 'ACTIVE'"
2548 20:08:13 10/23/2015 NO safApp=safAmfService "Admin op done for
invocation: 5050881540098, result 1"
2549 20:08:13 10/23/2015 NO safApp=safAmfService
"safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN PresenceState
INSTANTIATING => INSTANTIATED"
2550 20:09:51 10/23/2015 NO safApp=safAmfService "Admin op "LOCK"
initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN',
invocation: 5055176507393"
2551 20:09:51 10/23/2015 NO safApp=safAmfService "Admin op invocation:
5055176507393, err: 'SG state is not stable'"
Below is the syslog from the node hosting active SU.
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO Assigning
'safSi=TestApp_SI1,safApp=TestApp_TwoN' ACTIVE to
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State
UNINSTANTIATED => INSTANTIATING
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO Assigning
'safSi=TestApp_SI2,safApp=TestApp_TwoN' ACTIVE to
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO Assigning
'safSi=TestApp_SI3,safApp=TestApp_TwoN' ACTIVE to
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO Assigning
'safSi=TestApp_SI4,safApp=TestApp_TwoN' ACTIVE to
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State
INSTANTIATING => INSTANTIATED
Oct 23 20:08:14 SYSTEST-PLD-1 osafamfnd[3651]: NO Assigned
'safSi=TestApp_SI1,safApp=TestApp_TwoN' ACTIVE to
'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 23 20:28:15 SYSTEST-PLD-1 -- MARK --
---
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
