Project

General

Profile

Bug #3785

OML State Change Event Report contains invalid administrative state

Added by laforge 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Abis
Target version:
-
Start date:
02/07/2019
Due date:
% Done:

70%

Spec Reference:

Description

When osmo-bts connects to the BSC, it sends a ton of "State Change Event Report" messages indicating the Operational State (NULL), Availability status (power off) and [as an osmocom extension] also the Administrative State. However, the value of the administrative state is "0", which is not defined in TS 12.21 Section 9.4.4. The only permitted values are:
  • 1 (locked)
  • 2 (unlocked)
  • 3 (shutting down)
  • 255 (NULL; Administrative state nut supported)

Related issues

Related to OsmoBTS - Feature #2469: Proper OML MO (managed object) using osmo_fsmNew08/29/2017

History

#1 Updated by laforge 10 months ago

  • Description updated (diff)

#2 Updated by laforge 10 months ago

FYI: A nanoBTS has no Administrative State in the "Site Manager" object, and "Locked" for all other MOs.

#3 Updated by laforge 10 months ago

#4 Updated by laforge 10 months ago

  • Related to Feature #2469: Proper OML MO (managed object) using osmo_fsm added

#5 Updated by laforge 10 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

patch in https://gerrit.osmocom.org/#/c/osmo-bts/+/12864/

the big question is if this creates some interop problems, so we need to test this against osmo-bsc + openbsc.

#6 Updated by laforge 10 months ago

  • Status changed from In Progress to Resolved

patch merged

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)