This page describes O-DU High/Low pairwise testing procedure in Timer mode.
DO NOT EDIT
Only the Integration PTL should edit the delivery status table to track the release validation progress
|Deployment Artifacts||Docker Container||Dockerfiles are released, however, containers are not generated and tested.|
WLS interface ready
|UL IQ sample request|
|UL IQ sample response|
Cloning O-DU High code
Cloning O-DU Low code
- Install O-DU High pre-requisite libraries by following https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-l2/en/latest/installation-guide.html .
- Install O-DU Low by following https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-phy/en/latest/index.html .
O-DU low instructs to build DPDK using x86_64-native-linuxapp-icc
O-DU high uses x86_64-native-linuxapp-gcc, or library will be missing.
Hardcoded Library Location
The makefile of odu assumes the required libraries is located at /opt/intel
Modification of the makefile is needed if the libraries are located at different location.
Execution - Bringing up L1 of O-DU Low
Dynamic Library Path
May need to include the paths to the following libraries in the environment variable LD_LIBRARY_PATH
Execution - Bringing up FAPI Translator of O-DU Low
Assign virtual IP addresses as follows:
Execution - Running CU Stub
Execution - Running RIC Stub
Execution - Running O-DU High