f. mt : wrapper functions over OS
g. phy_stub : Stub code for Physical layer
h. rlog : logging module
- i. o1 : o1 module
+ i. O1 : O1 module
B. Pre-requisite for Compilation :
4. Install PCAP:
a. On ubuntu : sudo apt-get install -y libpcap-dev
b. On CentOS : sudo yum install -y libpcap-devel
+5. Install libxml2:
+ a. On Ubuntu : sudo apt-get install -y libxml2-dev
+ b. On CentOS : sudo yum install -y libxml2
C. Pre-requisite for O1 Interface (Required only if run with O1 interface enabled)
a. Open the startup_config.xml and edit the desired IP and Port for CU, DU and RIC.
b. Open the nacm_config.xml and edit the desired user name to provide the access to that user.
c. Open the netconf_server_ipv6.xml and edit the desired netconf server configuration.
- d. Open the vesConfig.json and edit the details of VES collector.
- e. Open the netconfConfig.json and edit the details of Netopeer server.
- f. Install the yang modules and load initial configuration
+ d. Open the oamVesConfig.json and edit the details of OAM VES collector.
+ e. Open the smoVesConfig.json and edit the details of SMO VES collector.
+ f. Open the netconfConfig.json and edit the details of Netopeer server.
+
+3. Install the yang modules and load initial configuration:
$cd l2/build/scripts
$sudo ./load_yang.sh
-3. Start Netopeer2-server:
+4. Start Netopeer2-server:
+
$cd l2/build/scripts
$sudo ./netopeer-server.sh start
+5. In case standard defined VES format is to be enabled (this step is optional):
+
+ cd l2/src/o1/ves
+
+ Enable the Macro "StdDef" in file VesUtils.h
+
+ #define StdDef
+
D. How to Clean and Build:
--------------------------
./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 H to start the stack.
G. How to test with Intel L1:
-----------------------------
./odu
-H. How to execute the Health Check : get alarm-list
-----------------------------------------------------
-
- Steps:
+H. 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:
- 1. Start Netconf netopeer client
-
- 2. Connect to the server with
+ $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
+
+ 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.
- user: netconf
- pwd: netconf!
+ <id>rrm-2</id
- 3. Send a Netconf get request for alarms xpath
- Here are the steps as executed in the terminal
+I. How to execute the Health Check using netopeer-cli : get alarm-list
+-----------------------------------------------------------------------
+
+ 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">
The XML output is a list of active alarms in the O-DU High system.
-G. Troubleshooting Netconf server issues
+J. Troubleshooting Netconf server issues
----------------------------------------
In case the Netconf server and sysrepo breaks down, run the following steps:
$cd l2/build/scripts
$sudo ./troubleshoot_netconf.sh cleanup
- execute section C.2.f, C.3 again
+ execute section C.3 and C.4 again
Code Review / o-du / l2.git / blobdiff