Project

General

Profile

Actions

Bug #2317

closed

multibts setup produce unnecessary OML warning

Added by msuraev over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/06/2017
Due date:
% Done:

100%

Spec Reference:

Description

The setup described in https://projects.osmocom.org/projects/openbsc/wiki/Multi-BTS_with_handover currently gives misleading warnings:

BSC:
BTS 1: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Process stopped, Additional Text=Formatted O&M with BTS 1 out of range (0:0xFF).

BTS:
<0001> oml.c:75 Reporting FAILURE to BSC: Formatted O&M with BTS 1 out of range (0:0xFF)
<0001> oml.c:372 Sending FOM NACK with cause BTS no. unknown.

Logs are produced when osmo-bts-trx (configured as bts 1 in openbsc) is trying to connect to BSC. Using the same configuration with bts 0 and bts 1 reversed gives no such warning.

The setup seems to be functional but this error message should be removed nevertheless - there's no 1:1 mapping between bts numbers in openbsc and osmobts configs.

For the reference, command-line arguments used while testing:
./openbsc/src/osmo-nitb/osmo-nitb -c ~/.config/osmocom/open-bsc.cfg-oml -l ~/.config/osmocom/hlr.sqlite3 -P
./src/osmo-bts-trx/osmo-bts-trx -c ~/.config/osmocom/osmo-bts.cfg-oml -t 2 -i 127.0.0.8


Files

open-bsc.cfg-oml open-bsc.cfg-oml 4.8 KB msuraev, 06/06/2017 12:47 PM
osmo-bts.cfg-oml osmo-bts.cfg-oml 923 Bytes msuraev, 06/06/2017 12:47 PM
open-bsc.cfg-oml-rev open-bsc.cfg-oml-rev 4.8 KB msuraev, 06/06/2017 01:02 PM

Related issues

Related to OsmoBSC - Bug #1614: better identification of BTS model / capabilities to BSCStalled02/23/2016

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)