OML ALERT messages are currently not really used much. They should be used more from the BTS side
Nowadays, the BTS seems to make good use of the OML failure reports. Example patch
and the BSC component in the NITB should not only log them somewhere
I've verified that the BSC is logging these messages.
but possibly even keep an in-memory ring buffer for each BTS/TRX so one can inspect the most recent errors for those objects via the VTY.
This is what I'm working on now.
I realized that it is not possible to send OML failure reports from the TTCN-3 testsuite, only RSL error reports. So, for manual testing during development, I've added a test VTY command to osmo-bts-virtual to send an OML failure report to the BSC. (osmo-bts branch: osmith/alert-buffer)
This works, the OML failure reports arrive at the BSC and I found the place to handle them. I've added code to save it to a ring buffer and a VTY command to read it out. While testing, I'm currently getting segfaults when accessing the llist, although it is already initialized.
WIP branch for osmo-bsc: osmith/alert-buffer