amf: SU admin state not updated after doing controller switchover and admin...

Brought to you by: anders-w, gary_lee, hansnordeback, jonasarndt, and 3 others

#399 amf: SU admin state not updated after doing controller switchover and admin lock of SU.

Milestone: future

Status: unassigned

Owner: nobody

Labels: None

Type: defect

Component: amf

Part: -

Version: 4.2.2

Priority: major

Blocker: False

Updated: 2017-08-28

Created: 2013-05-31

Creator: Praveen

Private: No

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.

Now on SC-1, command line trigger controller switchover
and immediately on SC-2, trigger the admin lock on SU1.

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.

Discussion

Anders Bjornerstedt - 2015-07-15

Description has changed:

Diff:

--- old +++ new @@ -1,4 +1,3 @@ - Migrated from http://devel.opensaf.org/ticket/2879. changeset : 3796, 4.2.2

Type: defect --> enhancement
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nagendra Kumar - 2015-08-06

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nagendra Kumar - 2015-08-06

Type: enhancement --> defect

Milestone: future --> 4.5.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nagendra Kumar - 2015-08-12

status: unassigned --> assigned

assigned_to: Nagendra Kumar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anders Widell - 2015-11-02

Milestone: 4.5.2 --> 4.6.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mathi Naickan - 2016-05-04

Milestone: 4.6.2 --> 4.7.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anders Widell - 2016-09-20

Milestone: 4.7.2 --> 5.0.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anders Widell - 2017-04-03

Milestone: 5.0.2 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nagendra Kumar - 2017-08-28

status: assigned --> unassigned

Blocker: --> False
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nagendra Kumar - 2017-08-28

assigned_to: Nagendra Kumar --> nobody
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.