Table of Contents
Advertisement
CONFIGURATION
_________________________________________________________________________________________________________
(Show Symbolic link):
root@BS5000:/root# cd BS5000/
root@BS5000:/root/BS5000# ls -l bs_config.xml
l rwxrwxrwx 1 root root 16 Jan
2 05:43 bs_config.xml -> bs_config.xml_1M
(Remove symbolic link and create new symbolic link):
root@BS5000:/root/BS5000# rm bs_config.xml
root@BS5000:/root/BS5000# ln -s bs_config.xml_1M_asym bs_config.xml
root@BS5000:/root/BS5000# ls -l bs_config.xml
(Show new Symbolic link):
root@BS5000:/root/BS5000# ls -l bs_config.xml
lrwxrwxrwx 1 root root 21 Jan 2 05:50 bs_config.xml ->
bs_config.xml_1M_asym
5.4
Coordinated Configuration File Changes
The recommended process is to first make changes in the base station, but to delay rebooting
the radio until the equivalent changes have been made in the remote radio(s). The configuration
file is only read at boot time, so any changes will not take effect until the radio reboots.
However, be aware that a base station will go through a sanity reboot every 300 seconds if no
remote is connected, although this interval may be configured to a different value or disabled
entirely. Similarly, a disconnected remote radio will go through a sanity reboot if it fails to
connect to a base station within a defined time, typically configured as 300 seconds.
Once configuration changes have been made in the base station and remote radios, reboot the
radio to which you do NOT have local access. This is usually the remote radio(s) since typically
backhaul exists to the base stations at the tower site(s). However, if experiments are being
conducted from remote sites in the field, then the base station would be rebooted first.
COM-00-21-04
Version No.: A.1
5-14
OCTOBER 2021
Advertisement
Table of Contents
