https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-10-06T14:31:25ZOpen Source Mobile CommunicationsOsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=55962017-10-06T14:31:25Zlaforge
<ul><li><strong>Assignee</strong> set to <i>msuraev</i></li></ul> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56082017-10-06T14:49:26Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>It's implemented to some degree in the latest master of OsmoBSC:<br /><pre>
OsmoBSC> sh bts 0
BTS 0 is of sysmobts type in band DCS1800, has CI 20909 LAC 200, BSIC 0 (NCC=0, BCC=0) and 1 TRX
...
Early Classmark Sending: forbidden
Unit ID: 6969/0/0, OML Stream ID 0xff
NM State: Oper 'Enabled', Admin 'Unlocked', Avail 'OK'
...
OML Link state: connected 0 days 0 hours 0 min. 3 sec.
...
</pre></p>
I can expose this over CTRL interface but there're few things to clarify first:
<ul>
<li>is current representation ok or it's better to reformat, show differently etc?</li>
<li>current implementation does not take into account leap year (after >= 1 year of uptime it might be 1 day inaccurate) - shall I try fixing it?</li>
<li>right now we show OML as either connected or disconnected. When shall we show "degraded" status?</li>
<li>shall we consider anything else in addition to OML?</li>
</ul> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56172017-10-06T15:10:16Zlaforge
<ul></ul><p>Hi Max,</p>
<p>thanks for the status update.</p>
<p>On Fri, Oct 06, 2017 at 02:49:26PM +0000, msuraev [REDMINE] wrote:</p>
<blockquote>
I can expose this over CTRL interface but there're few things to clarify first:
<ul>
<li>is current representation ok or it's better to reformat, show differently etc?</li>
</ul>
</blockquote>
<p>I think the plain integer number of seconds would be best for a programmatic interface like CTRL</p>
<blockquote>
<ul>
<li>current implementation does not take into account leap year (after >= 1 year of uptime it might be 1 day inaccurate) - shall I try fixing it?</li>
</ul>
</blockquote>
<p>I think it doesn't matter, we can ignore this.</p>
<blockquote>
<ul>
<li>right now we show OML as either connected or disconnected. When shall we show "degraded" status?</li>
</ul>
</blockquote>
<p>If OML is connected but somehow not all MO's in the right state. Should<br />probably be a per-bts-model specific function that determines this. Can<br />be very simplistic at first, but then expanded later on.</p>
<p>Loss of RSL while OML is connected would also be degraded.</p>
<blockquote>
<ul>
<li>shall we consider anything else in addition to OML?</li>
</ul>
</blockquote>
<p>see above, I think for RSL it's should simply lead to "degraded"</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56202017-10-06T15:54:52Zmsuraev
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Thanks for clarification.</p>
<p>laforge wrote:</p>
<blockquote>
<p>If OML is connected but somehow not all MO's in the right state. Should<br />probably be a per-bts-model specific function that determines this. Can<br />be very simplistic at first, but then expanded later on.</p>
</blockquote>
<p>Is there some sort of MO list for some BTS model which I can use as an example for such check?</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56242017-10-06T23:10:16Zlaforge
<ul></ul><p>On Fri, Oct 06, 2017 at 03:54:52PM +0000, msuraev [REDMINE] wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-high2 closed" title="Bug: show BTS up/down status + BTS uptime in BSC VTY + CTRL (Closed)" href="https://projects.osmocom.org/issues/2486">#2486</a> has been updated by msuraev.</p>
<p>Status changed from New to In Progress</p>
<p>Thanks for clarification.</p>
<p>laforge wrote:</p>
<blockquote>
<p>If OML is connected but somehow not all MO's in the right state. Should<br />probably be a per-bts-model specific function that determines this. Can<br />be very simplistic at first, but then expanded later on.</p>
</blockquote>
<p>Is there some sort of MO list for some BTS model which I can use as an example for such check?</p>
</blockquote>
<p>start simpleat first, extend later: Start with sysmoBTS :)</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56442017-10-09T15:53:51Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li></ul><p>Check for OML link state which takes into consideration RSL link is available in gerrit 4169.<br />Note: this information is already available via CTRL in "oml-connection-state" RO command.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=56632017-10-10T13:25:31Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>60</i></li></ul><p>Gerrit 4169 has been merged. Ctrl command to get uptime (in seconds) is available in gerrit 4197.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=57702017-10-11T14:14:25Zmsuraev
<ul></ul><p>Gerrit 4169 has been merged.</p>
<p>Not sure what else can be checked for "degraded" state in case of sysmobts. In case of osmo-bts-trx we can also check for osmo-trx connectivity for example.</p>
<p>Also, documentation for ctrl commands (maybe vty too) needs update - I'll work on that first.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=57742017-10-11T16:10:12Zlaforge
<ul></ul><p>On Wed, Oct 11, 2017 at 02:14:25PM +0000, msuraev [REDMINE] wrote:</p>
<blockquote>
<p>Not sure what else can be checked for "degraded" state in case of sysmobts.</p>
</blockquote>
<p>I would presume the state of all the various OML MOs (managed objects). Unless they're<br />all in their expected state, state is degraded.</p>
<blockquote>
<p>In case of osmo-bts-trx we can also check for osmo-trx connectivity for example.</p>
</blockquote>
<p>If we miss a clock indication from osmo-trx for 1.8 seconds, we kill osmo-bts, so I think<br />there's no point in indicating a different status in the short time period in between.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=60342017-11-02T14:03:06Zmsuraev
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li><li><strong>% Done</strong> changed from <i>60</i> to <i>70</i></li></ul><p>Gerrit 4197 has been merged. Example use:<br /><code>./bsc_control.py -d localhost -p 4249 -g bts.0.oml-connection-state</code></p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=60352017-11-02T14:12:54Zmsuraev
<ul></ul><p>Gerrit 4648 sent for review with documentation update.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=60362017-11-02T14:56:27Zmsuraev
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>I would presume the state of all the various OML MOs (managed objects). Unless they're<br />all in their expected state, state is degraded.</p>
</blockquote>
<p>If state is 'locked' for some MO - shall it be considered as "degraded"?</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=60372017-11-02T16:20:12Zlaforge
<ul></ul><p>On Thu, Nov 02, 2017 at 02:56:27PM +0000, msuraev [REDMINE] wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-high2 closed" title="Bug: show BTS up/down status + BTS uptime in BSC VTY + CTRL (Closed)" href="https://projects.osmocom.org/issues/2486">#2486</a> has been updated by msuraev.</p>
<p>laforge wrote:</p>
<blockquote>
<p>I would presume the state of all the various OML MOs (managed objects). Unless they're<br />all in their expected state, state is degraded.</p>
</blockquote>
<p>If state is 'locked' for some MO - shall it be considered as "degraded"?</p>
</blockquote>
<p>I would argue yes.</p>
<p>In my dreams, at some point in the future the individual MOs would then<br />have osmo_fsm and one could inquire their detailed state via CTRL. But the overall<br />state is degraded in the situation you describe.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=61252017-11-07T20:29:23Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=61392017-11-07T21:33:17Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=64272017-11-29T10:48:14Zmsuraev
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>In Progress</i></li></ul><p>For the tests, NM State can be changed to "locked" via vty:<br /><pre>
OsmoBSC# bts 0 oml class bts instance 0 0 0
OsmoBSC(oml)# change-adm-state locked
</pre></p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=64332017-11-29T13:03:38Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>70</i> to <i>80</i></li></ul><p>Gerrit 5081 has been merged, gerrit 5085 is under review. This will take into account generic BTS and TRX MO.</p>
If we exclude MO objects specific to certain BTS (BS11, RBS2k) than we have following MO available:
<ul>
<li>TS-related</li>
<li>GPRS-related</li>
<li>BTS site-manager</li>
</ul>
<p>I think TS MO can be ignored because locking single TS should not degrade entire BTS, GPRS-related MO should be taken into account only if GPRS is enabled (will send follow-up patch). Not sure what to do with site-manager.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=64392017-11-29T13:48:11Zmsuraev
<ul></ul><p>Gerrit 5084, 5085, 5092 were sent for review.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=67282017-12-11T10:47:37Zmsuraev
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>All pending patches were merged, we now take MO states into account, available both via vty and ctrl interfaces. The manual is updated as well.</p> OsmoBSC - Bug #2486: show BTS up/down status + BTS uptime in BSC VTY + CTRLhttps://projects.osmocom.org/issues/2486?journal_id=74922018-02-06T08:26:43Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>