Base Station administration issues

RF Region update fails

SYMPTOM: RF Region update could fail with a gateway for a specific radio configuration. A cause could be an incorrect md5 hash, which doesn't match the radio configuration tarball.

SOLUTION:

Check the md5 and the tarball configuration file's hash

1. Start a bash on the node1 lrc container:

   docker exec -it $(docker ps -q -f "name=actility_lrc1") bash
   cd /var/ftp/
   md5sum cfglrr-EU868_16channels.2-CONF_s1_a1_b1_v2.tar.gz

   cat cfglrr-EU868_16channels.2-CONF_s1_a1_b1_v2.md5

NOTE: Replace cfglrr-EU868_16channels.2-CONF_s1_a1_b1_v2 with the RF Region you tried to apply to your Base Station.

In case where they don't match, please execute the following procedure on node1, and node2 for a TPE OCP HA.

2. Start a bash on the lrc container:

   docker exec -it $(docker ps -q -f "name=actility_lrc1") bash

   NOTE: Use actility_lrc1 for node1 and actility_lrc2 for node2

3. Regenere RF_Region tarball for all RF Regions (takes 1 or 2 minutes):

    for file in $(find /home/actility/FDB_lora/RFRegion/ ! -name '*DEFAULT-RFREGION-TEMPLATE' -type f |  xargs -n 1 basename);do /home/actility/rfregtool/shells/dnrfregionid.sh -d /var/ftp/ -g $file; done