Project

General

Profile

Actions

Bug #3789

closed

BTS permits OPSTART of MO without attributes

Added by laforge about 5 years ago. Updated 12 months ago.

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

100%

Spec Reference:

Description

After writing some OML testcases, I discovered that it's currently possible to OPSTART a Managed Object which doesn't yet have all of its attributes set. This is a likely cause of OML initialization failures, and should be NACKed.

As per TS 12.21 Figure 2, the Attribute setting happens before OPSTART. The OPSTART then attempts to put the object into the ENABLED operational state.


Files


Related issues

Related to OsmoBTS - Bug #3782: OML bringup fails for osmo-bts-oc2g on high latency linksNew02/06/2019

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

Actions
Related to OsmoBSC - Bug #5977: osmo-bsc unable to bring up osmo-bts-sysmo (BSIC/TSC)Closedpespin03/27/2023

Actions
Has duplicate OsmoBTS - Bug #5961: BTS accepts OPSTART without prior SET ATTRIBUTESResolvedpespin03/26/2023

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)