Project

General

Profile

Actions

Bug #5576

open

osmo-bts not moving NM state "Enabled -> DisabledDependency" when Admin state becomes Locked

Added by pespin about 1 month ago. Updated about 1 month ago.

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.

To my understanding, that also means once unlocked again, the BSC should follow a similar path as in the bootstrap procedure:
  • BSC->BTS UNLOCK msg triggers change "Disabled Dependency" -> "Disable Offline" at the BTS.
  • BSC->BTS Opstart msg triggers change "Disable Offline" -> "Enabled".
Actions #1

Updated by pespin about 1 month 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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)