Project

General

Profile

Actions

Bug #3785

closed

OML State Change Event Report contains invalid administrative state

Added by laforge about 5 years ago. Updated about 5 years 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_fsmResolvedpespin08/29/2017

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)