Migrated from http://devel.opensaf.org/ticket/2879.
changeset : 3796, 4.2.2
model : NpluM
Initial Configuration:-
=====
SI equal distribution
saAmfSGNumPrefInserviceSUs=5 -a saAmfSGMaxActiveSIsperSU=2 -a saAmfSGMaxStandbySIsperSU=3 -a saAmfSGNumPrefActiveSUs=3 -a saAmfSGNumPrefStandbySUs=2
saAmfSGAutoAdjust=1
6 SIs in locked state.
saAmfSIPrefActiveAssignments=1 -a saAmfSIPrefStandbyAssignments=1
5SUs with same SURank set to 5.Each SUs admin state was locked-instantiation state.
SU1, SU4, SU5 spawned on SC-1
SU2 on SC-2
SU3 on PL-4
Steps:-
1. Brought up the NplusM model with above configuration.
2. Performed unlock-instantiation operation on each SUs (SU1 to SU5)
3. Performed unlock operation on each SUs (SU1 to SU5).
4. Performed unlock of each SIs (SI1 to SI6)
Here observed that SUSI assignments were equally distributed.
Here observed that controller switchover successfully completed
but the admin lock on SU1 failed with SA_AIS_ERR_TIMEOUT.
Again tried to lock the SU1, but this time it got failed with SA_AIS_ERR_NO_OP. It was failing with the same error SA_AIS_ERR_NO_OP after reties. amf-state su states was showing the admin state of SU1 as UNLOCKED. Hence admin state of SU1 was not getting changed.
Observed that all the SUSI assignments from SU1 got removed but the
/var/log/messages was printing the below messages:-
Oct 23 13:01:53 SLOT2 osafimmnd[7176]: Timeout on syncronous admin operation 1
Oct 23 13:03:47 SLOT2 osafamfd[7225]: Admin operation (2) has no effect on current state (2)
Oct 23 13:06:15 SLOT2 osafamfd[7225]: Admin operation (2) has no effect on current state (2)
safSu=d_NplusM_1Norm_1,safSg=SG_d_npm,safApp=NpMApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=d_NplusM_1Norm_2,safSg=SG_d_npm,safApp=NpMApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=d_NplusM_1Norm_3,safSg=SG_d_npm,safApp=NpMApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=d_NplusM_1Norm_4,safSg=SG_d_npm,safApp=NpMApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=d_NplusM_1Norm_5,safSg=SG_d_npm,safApp=NpMApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSISU=safSu=SC-1\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SC-2\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-3\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?4,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-4\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?3,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_4\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_6,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_2\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_3,safApp=NpMApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=d_NplusM_1Norm_2\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_1,safApp=NpMApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=d_NplusM_1Norm_2\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_2,safApp=NpMApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=d_NplusM_1Norm_5\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_1,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_3\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_2,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_5\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_4,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_4\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_3,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=d_NplusM_1Norm_3\,safSg=SG_d_npm\,safApp=NpMApp,safSi=d_NplusM_1Norm_5,safApp=NpMApp
saAmfSISUHAState=ACTIVE(1)
Changed 7 months ago by shareef
Same issue also observed with Nway model.
Nway model configuration:-
====================
saAmfSGAutoAdjust=1 -a saAmfSGNumPrefInserviceSUs=8 -a saAmfSGNumPrefAssignedSUs=7 -a saAmfSGMaxActiveSIsperSU=3 -a saAmfSGMaxStandbySIsperSU=4 -a saAmfSGNumPrefActiveSUs=3 -a saAmfSGNumPrefStandbySUs=3
6SIs, saAmfSIPrefStandbyAssignments=2 -a saAmfSIAdminState=2
5SUs in lock-in state.
SU1, SU4, SU5 spawned on SC-1
SU2 on SC-2
SU3 on PL-4
Changed 7 months ago by shareef
■summary changed from In NplusM model, SU admin state not updated after doing controller switchover and admin lock of SU. to SU admin state not updated after doing controller switchover and admin lock of SU.
Changed 7 months ago by shareef
This issue is also observed with nway_active redandancy model.
Diff:
As part of ticket cleanup, evaluated and found that this issue needs to be fixed as defect. It looks it got fixed now, but will close it after validating.