https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092016-11-18T22:09:21ZOpen Source Mobile CommunicationsOsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=24912016-11-18T22:09:21Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-2 priority-default" href="/issues/1857">Feature #1857</a>: aggregate and report OML ALERT messages received from BTSs</i> added</li></ul> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=66862017-12-10T20:05:13Zlaforge
<ul><li><strong>Project</strong> changed from <i>OpenBSC</i> to <i>OsmoBSC</i></li><li><strong>Category</strong> deleted (<del><i>libbsc</i></del>)</li></ul> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=117462018-09-30T10:48:08Zlaforge
<ul><li><strong>Assignee</strong> set to <i>osmith</i></li></ul> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=117472018-09-30T10:49:47Zlaforge
<ul></ul><p>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...</p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=177612020-03-17T14:23:15Zosmith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=177992020-03-20T15:59:03Zosmith
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/17799/diff?detail_id=29544">diff</a>)</li><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><blockquote>
<p>OML ALERT messages are currently not really used much. They should be used more from the BTS side</p>
</blockquote>
<p>Nowadays, the BTS seems to make good use of the OML failure reports. <a href="https://gerrit.osmocom.org/c/osmo-bts/+/1525" class="external">Example patch</a></p>
<blockquote>
<p>and the BSC component in the NITB should not only log them somewhere</p>
</blockquote>
<p>I've verified that the BSC is logging these messages.</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>This is what I'm working on now.</p>
<p>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)</p>
<p>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.</p>
<p>WIP branch for osmo-bsc: osmith/alert-buffer</p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=178192020-03-21T11:30:14Zlaforge
<ul></ul><p>On Fri, Mar 20, 2020 at 03:59:03PM +0000, osmith [REDMINE] wrote:</p>
<blockquote>
<p>I realized that it is not possible to send OML failure reports from the TTCN-3 testsuite, only RSL error reports.</p>
</blockquote>
<p>That's only half true. Since May 2019, library/AbisOML_* contains type<br />definitions, templates and an "Emulation" part for OML. Even<br />ts_OML_FailureEvtRep() exists. It's just that none of our existing<br />tests / testsuites uses it.</p>
<p>I currently don't see a reason why they couldn't be used. Sure, as a<br />first user you might run into bugs, but I think it should at least be<br />tried.</p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=178482020-03-23T09:28:14Zosmith
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>On Fri, Mar 20, 2020 at 03:59:03PM +0000, osmith [REDMINE] wrote:</p>
<blockquote>
<p>I realized that it is not possible to send OML failure reports from the TTCN-3 testsuite, only RSL error reports.</p>
</blockquote>
<p>That's only half true. Since May 2019, library/AbisOML_* contains type<br />definitions, templates and an "Emulation" part for OML. Even<br />ts_OML_FailureEvtRep() exists. It's just that none of our existing<br />tests / testsuites uses it.</p>
</blockquote>
<p>Cool, I'll try this!</p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=178502020-03-23T10:25:29Zosmith
<ul></ul><p>osmith wrote:</p>
<blockquote>
<p>While testing, I'm currently getting segfaults when accessing the llist, although it is already initialized.</p>
</blockquote>
<p>The wrong BTS pointer is getting passed, fix here: <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/17569">https://gerrit.osmocom.org/c/osmo-bsc/+/17569</a></p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=178532020-03-23T14:52:45Zosmith
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>60</i></li></ul><blockquote>
<p>keep an in-memory ring buffer for each BTS/TRX so one can inspect the most recent errors for those objects via the VTY.</p>
</blockquote>
<p>Patch submitted: <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/17571">https://gerrit.osmocom.org/c/osmo-bsc/+/17571</a></p>
<p>Another patch submitted with what I've been using for manual testing with OsmoBTS: <a class="external" href="https://gerrit.osmocom.org/c/osmo-bts/+/17573">https://gerrit.osmocom.org/c/osmo-bts/+/17573</a></p>
<p>Automated TTCN-3 test remains.</p> OsmoBSC - Feature #1605: logging / ring buffer for ALERT messages from A-bis OML from the BTS sidehttps://projects.osmocom.org/issues/1605?journal_id=178722020-03-27T09:40:52Zosmith
<ul><li><strong>% Done</strong> changed from <i>60</i> to <i>70</i></li></ul><p>Patches merged.</p>