Actions
Bug #5576
openosmo-bts not moving NM state "Enabled -> DisabledDependency" when Admin state becomes Locked
Status:
New
Priority:
Normal
Assignee:
-
Category:
Abis
Target version:
-
Start date:
06/02/2022
Due date:
% Done:
0%
Spec Reference:
3GPP TS 52.021 sec 5.3.1
Description
According to 3GPP TS 52.021 sec 5.3.1, Locking an NM object in op=Enabled NM state should trigger the NM object to move to state op=Disabled avail=Dependency (on top of moving from Admin=Unlocked->Locked).
This procedure should also be applied to all subobjects depending on the locked object.
- BSC->BTS UNLOCK msg triggers change "Disabled Dependency" -> "Disable Offline" at the BTS.
- BSC->BTS Opstart msg triggers change "Disable Offline" -> "Enabled".
Updated by pespin almost 2 years ago
I just submitted this patch to account for this osmo-bts situation at the BSC:
https://gerrit.osmocom.org/c/osmo-bsc/+/28217 nm_rcarrier_fsm: Trigger S_NM_RUNNING_CHG when Admin st changes in op=Enabled
Actions