Basestation Logging

Configure the logs

Logs can be configured to run for the entire basestation , a module or a specific component

Configure the logs for LTE

  • Logs can be generated for the entire eNB with any desired level
  • Open ssh session (ssh yatebts@ -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • Apply the command (debug enb level <1-10>)
  • Logs can be generated for specific module in the eNB with any desired level
  • Open ssh session (ssh yatebts@<IP-address-of-basestation> -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • To have a list of loaded modules (module list)
  • Apply the command (debug <module> level <1-10>)
  • Logs can be generated for specific ponents" than "processesin the eNB with any desired level
  • Open ssh session (ssh yatebts@<IP-address-of-basestation> -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • To have a list of available debugs (debug enb) then press tab
  • Apply the command (debug enb.<ponents” than “processes> level <1-10>)

Configure the logs for GSM

When running in GSM mode, BTS is running two modules independently: mbts and transceiver

  • Logs can be generated for the entire BTS with any desired level
  • Open ssh session (ssh yatebts@<IP-address-of-basestation> -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • Apply the command (debug mbts level <1-10>) & the command (debug transceiver level <1-10>)

If there is no transceiver logs or debug messages are displayed but the transceiver otherwise appears to work see how to restart transceiver .

  • Logs can be generated for specific module in the BTS with any desired level
  • Open ssh session (ssh yatebts@<IP-address-of-basestation> -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • To have a list of loaded modules (module list)
  • Apply the command (debug <module> level <1-10>)
  • Logs can be generated for specific ponents" than "processes in the BTS with any desired level
  • Open ssh session (ssh yatebts@ -p 54321)
  • Open ssh session to eNB (telnet 0 5037)
  • Enable mbts debugs (debug mbts level <1-10>)
  • Apply the command (mbts config Log.Level.<ponents” than “processes> level <1-10>)

SatSite
20W basestation for GSM & LTE (eNodeB), operating in multiple GSM/LTE bands
See the product here ››

Most common processes

For LTE

  • From physical layer
  • enb.rar
  • enb.prach
  • From RLC layer
  • enb.rlc
  • From MAC layer
  • enb.mac

For GSM

  • From Control:
  • RadioResource.cpp – L3 RRC (radio resource control)
  • DCCHDispatch.cpp – L3 control messages other than RRC
  • From GSM:
  • GSML2LAPDm.cpp – layer 2 (link layer) (similar to ISDN LAPD)
  • GSMLogicalChannel.cpp – channel setup and release
  • GSML1FEC.cpp – PHY (L1) channel coding
  • From GPRS:
  • BSSG.cpp – L3 signaling
  • RLC.cpp – GPRS link layer (similar to LTE RLC)
  • RLCEngine.cpp – more GPRS link layer
  • FEC.cpp – PHY channel coding specific to GPRS
  • TBF.cpp – packet/frame scheduling
  • MAC.cpp – GPRS MAC layer

Accessing the logs

Logs can be accessed using

  • Terminal of the OS
  • Open ssh session (ssh yatebts@<IP-address-of-basestation> -p 54321)
  • Find the recent logs in /var/log/yate-sdr
  • Older logs are saved as yate-sdr.1
  • Logs older than part 1 are saved as yate-sdr.<part_number>.gz
  • LMI:
  • Open the lmi (http://<IP-address-of-basestation>:2080/lmi )
  • In the top right corner select (View logs)
  • Select the level (Warn, mild, note, call , info , all)
  • Select the number of lines
  • press submit and pop up menu will appear with the option to read or download the logs as text file
Accessing the Basestation logs using the Web management interface LMI - Local Management Interface

Logs levels

There are 11 debugging levels:

  1. DebugFail = 0
  2. DebugTest = 1
  3. DebugGoOn = 2
  4. DebugConf = 3
  5. DebugStub = 4
  6. DebugWarn = 5
  7. DebugMild = 6
  8. DebugCall = 7
  9. DebugNote = 8
  10. DebugInfo = 9
  11. DebugAll = 10.

logrotate

Logrotat is a UNIX program that eases the management of log files by automatically compressing, rotating, removing and emailing the logs as specified in the configuration. It runs as a daily cron job.

To edit the setting

  • Open ssh session (ssh yatebts@ -p 54321)
  • edit the file /etc/logrotate.d/yate-sdr