O-DU High Tests with Stubs
Delivery Status
DO NOT EDIT
Only the Integration PTL should edit the delivery status table to track the release validation progress
OTF | OAM | NONRTRIC | RICP | RICAPP | O-DU | O-CU | Test Result | Notes | ||
|---|---|---|---|---|---|---|---|---|---|---|
Deployment Artifacts | Docker Container | O-DU-RIC-STUB is not available in OSC Nexus | ||||||||
Helm Charts | ||||||||||
Deployment scripts | ||||||||||
E2E Flows | E2 UE Attach Procedure | The CU stub and RIC stub is also used in the O-DU-high and O-DU-low integrated flow |
This page describes running O-DU High using test stubs, namely CU Stub and RIC Stub. O-DU High also uses Phy Stub in the absence of O-DU Low. However, Phy Stub is built as a part of the O-DU High image itself.
Execution of below steps yields successful UE Attach procedure and message exchanges required for Traffic Steering use-case on the E2 interface. These can be verified on wireshark by capturing SCTP packets.
Prepare environment
sudo apt-get install libpcap-dev libsctp-devCloning code
mkdir odu_high cd odu_high git clone "https://gerrit.o-ran-sc.org/r/o-du/l2"Compilation of O-DU
cd odu_high/l2/build/odu make clean_odu odu MACHINE=BIT64 MODE=FDDCompilation of CU Stub
cd odu_high/l2/build/odu make clean_cu cu_stub NODE=TEST_STUB MACHINE=BIT64 MODE=FDDCompilation of RIC Stub
cd odu_high/l2/build/odu make clean_ric ric_stub NODE=TEST_STUB MACHINE=BIT64 MODE=FDDExecution - Assign IP addresses
ifconfig <interface name>:ODU “192.168.130.81” ifconfig <interface name>:CU_STUB “192.168.130.82” ifconfig <interface name>:RIC_STUB “192.168.130.80”Running CU Stub
cd odu_high/l2/bin/cu_stub sudo ./cu_stubRunning RIC Stub
cd odu_high/l2/bin/ric_stub sudo ./ric_stubRunning O-DU
cd odu_high/l2/bin/odu sudo ./oduNote:
Each of the above binaries must be run in separate terminals
CU Stub and RIC Stub images must be run before O-DU image.