OAI uses/supports a number of environment variables, documented in the following:
NFAPI_TRACE_LEVEL
: set the nfapi custom logging framework's log level; can be one oferror
,warn
,note
,info
,debug
NR_AWGN_RESULTS_DIR
: directory containing BLER curves for L2simulator channel modelling in SISO caseNR_MIMO2x2_AWGN_RESULTS_DIR
: directory containing BLER curves for L2simulator channel modelling in 2x2 MIMO caseNVRAM_DIR
: directory to read/write NVRAM data in (5G)nvram
tool; if not defined, will usePWD
(working directory)OAI_CONFIGMODULE
: can be used to pass the configuration file instead of-O
OAI_GDBSTACKS
: if defined when hitting an assertion (DevAssert()
,AssertFatal()
, ...), OAI will loadgdb
and provide a backtrace for every threadOAI_RNGSEED
: overwrites any seed for random number generators (RNG) in simulatorsOAI_THREADPOOLMEASUREMENTS
: path to a file to store thread pool debugging information, see the thread pool documentationOPENAIR_DIR
: should point to the root directory of OpenAirInterface; some code relies on this to get a filename, e.g., BLER curves for L2sim channel emulationUSIM_DIR
: directory to read/write USIM data in (4G)usim
tool; if not defined, will usePWD
(working directory)
Furthermore, these variables appear in code that is not maintained and maybe not even compiled anywhere:
HOST
: alternative host to connect to, for CLI, if neitherREMADDR
norSSH_CLIENT
are definedREMADDR
: host to connect to, for CLI clientSSH_CLIENT
: alternative host to connect to, for CLI, ifREMADDR
is not definedUSER
: user name in the command-line interfacerftestInputFile
: input file for thecalibration_test
tool