Project

General

Profile

Feature #1605

logging / ring buffer for ALERT messages from A-bis OML from the BTS side

Added by laforge over 2 years ago. Updated about 2 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
02/23/2016
Due date:
% Done:

0%

Spec Reference:

Description

OML ALERT messages are currently not really used much. They should be used more from the BTS side, and the BSC component in the NITB should not only log them somewhere but possibly even keep an in-memory rng buffer for each BTS/TRX so one can inspect the most recent errors for those objects via the VTY.


Related issues

Related to OsmoBSC - Feature #1857: aggregate and report OML ALERT messages received from BTSsNew2016-11-18

History

#1 Updated by laforge almost 2 years ago

  • Related to Feature #1857: aggregate and report OML ALERT messages received from BTSs added

#2 Updated by laforge 11 months ago

  • Project changed from OpenBSC to OsmoBSC
  • Category deleted (libbsc)

#3 Updated by laforge about 2 months ago

  • Assignee set to osmith

#4 Updated by laforge about 2 months ago

This is actually slightly similar to the "show last unsuccessful BTS connection attempts". In both cases we want to keep a ring-buffer of most recent events. However, the difference is that for ALERT, we want one FIFO ring buffer per BTS, while for the BTS connection attempts, we want one global ring buffer, and entries should be overwritten in case the same BTS attempts again...

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)