Project

General

Profile

Feature #5106

Watchdog that would try to un-BORKE BORKen timeslots

Added by keith 18 days ago. Updated 16 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
04/04/2021
Due date:
% Done:

0%

Spec Reference:

Description

In #5096 that discussed lchans ending up borken on a busy ericsson bts:

"What would probably make sense is some kind of watchdog that would try to un-BORKE BORKen timeslots after a certain time. This can be done by activating a broken sub-slot and releasing it immediately. If the BTS still refuses to activate it, then it's completely BORKen and the second attempt to un-BORKE can be postponed further."

(https://osmocom.org/issues/5096#note-12)


Related issues

Related to OsmoBSC - Bug #5096: rbs2000 ALL BORKEN ChannelsResolved03/26/202104/04/2021

History

#1 Updated by keith 18 days ago

  • Related to Bug #5096: rbs2000 ALL BORKEN Channels added

#2 Updated by neels 16 days ago

It would make most sense to introduce a timeout on an lchan entering the BORKEN state, to retry to resurrect the lchan by some standard actions: release the lchan, activate then release, things like that. This could be limited to say three times before entering the BORKEN state "forever".

Also we could consider to not enter the BORKEN state on a chan act NACK, but simply regard the lchan as not in use again. It seems that the reported case (I heard) included some invalid request in the chan act, and hence the NACK would simply mean to go back to UNUSED.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)