User Guide
***********
-This is the user guide for D release of O-DU/l2.
+This is the user guide for G release of O-DU/l2.
Follow installation-guide to get all the dependencies ready.
.. contents::
- ./odu
-PS: CU stub and RIC stub must be run (in no particular sequence) before ODU.
+PS: CU stub and RIC stub must be run (in no particular sequence) before ODU.
+ In case O1 is enabled and SMO is not available run section D to start the stack.
II. Execution - Using Docker Images
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The call flow between O-DU High and CU Stub can be achieved by executing docker containers.
- Pull the last built docker images:
- - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:3.0.1
- - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:3.0.1
+ - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:7.0.2
+ - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:7.0.2
- Run CU Stub docker:
- docker run -it --privileged --net=host --entrypoint bash
- nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:3.0.1
+ nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:7.0.2
- ./cu_stub
- Run ODU docker:
- docker run -it --privileged --net=host --entrypoint bash
- nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:3.0.1
+ nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:7.0.2
- ./odu
.. figure:: O-DU_High_Low_Flow.PNG
:width: 600
- :alt: Figure 7 O-DU High - O-DU Low Message Flow Diagram
+ :alt: Figure 15 O-DU High - O-DU Low Message Flow Diagram
- Figure 7 - O-DU High - O-DU Low Message Flow Diagram
+ Figure 15 - O-DU High - O-DU Low Message Flow Diagram
Note: UL IQ-Sample request and response are needed by Intel O-DU Low in timer mode(testing mode) only. Code changes for
these are guarded under INTEL_TIMER_MODE flag which can be enabled using compilation option "PHY_MODE=TIMER", as
mentioned in section B.I.1.d .
+D. Push cell and slice configuration over O1 using netopeer-cli
+---------------------------------------------------------------
+ When O-DU High is run with O1 enabled it waits for initial cell configuration to be pushed by SMO before starting the stack. In case the SMO is not available then these configurations can be pushed via netopeer-cli as follows:
-D. Health Check execution: get alarm-list
--------------------------------------------
+ | $cd l2/build/config
+ | $netopeer2-cli
+ | > connect --login netconf
+ | Interactive SSH Authentication
+ | Type your password:
+ | Password: netconf!
+ | > edit-config --target candidate --config=cellConfig.xml
+ | > OK
+ | > commit
+ | > OK
+ | > edit-config --target candidate --config=rrmPolicy.xml
+ | > OK
+ | > commit
+ | > OK
-To execute the get alarm-list flow, following steps are required to be executed:
+ For pushing these configurations in subsequent runs please edit cellConfig.xml and rrmPolicy.xml and increment number in the <id> tag to a new value e.g.
- 1. Start Netconf netopeer client
-
- 2. Connect to the server with
-
- | user: netconf
- | pwd: netconf!
+ <id>rrm-2</id
- 3. Send a Netconf get request for alarms xpath
+E. How to execute the Health Check using netopeer-cli : get alarm-list
+-----------------------------------------------------------------------
-Here are the steps as executed in the terminal
+ In case the SMO is not available the alarm list can be checked using netopeer-cli as follows:
| netopeer2-cli
| > connect --login netconf
| Interactive SSH Authentication
| Type your password:
- | Password:
+ | Password: netconf!
| > get --filter-xpath /o-ran-sc-odu-alarm-v1\:odu/alarms
| DATA
| <odu xmlns=\"urn\:o-ran\:odu\:alarm\:1.0\">
| </odu>
The XML output is a list of active alarms in the O-DU High system.
+
Code Review / o-du / l2.git / blobdiff