26 Jan
2019
26 Jan
'19
12:29 p.m.
Hi Gullik,
On Mon, Jan 21, 2019 at 01:05:09PM +0100, Gullik Webjorn wrote:
What is the best practice to enable / disable a single
bts / trx in a multi
trx configuration?
Just stop/disconnect it?
Just stopping it, phones settle after some time, but I
get a lot of timeouts in syslog.
what kind of "timeouts in syslog" ?
So, for service / reconfig purposes, how do I disable
a single (remote ) bts
from the BSC side? ( without making a temporary config file and restarting ? )
you can make any change to the configuration at runtime and you don't need
to restart the BSC.
Option 1:
----
enable
configure terminal
network
bts 0
ip.access unit_id 55555
end
drop bts connection 0 oml
----
assuming that "55555" is not a valid unit-id, the BTS will be disconnected
and not permitted to reconnect due to unknown unit-id
this is a bit of a hack.
The better solution is:
----
enable
configure terminal
network
bts 0
trx 0
rf_locked 1
end
drop bts connection 0 oml
----
And then if you want to re-enable it, do the same with 'rf_locked 0'.
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)