Doc changes for F release O1 enhancements

[o-du/l2.git] / docs / README

diff --git a/docs/README b/docs/README
index bd57bec..8b5056d 100644 (file)
--- a/docs/README
+++ b/docs/README
@@ -52,13 +52,22 @@ C. Pre-requisite for O1 Interface (Required only if run with O1 interface enable
    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.
+   g. Install the yang modules and load initial configuration
 
    $cd l2/build/scripts
    $sudo ./load_yang.sh
 
+   h. To enable Standard Defined VES format:
+      
+      cd l2/src/o1/ves
+      
+      Enable the Macro "StdDef" in file VesUtils.h
+      
+      #define StdDef
+
 3. Start Netopeer2-server:
    $cd l2/build/scripts
    $sudo ./netopeer-server.sh start
@@ -278,8 +287,17 @@ H. How to execute the Health Check : get alarm-list
 
    The XML output is a list of active alarms in the O-DU High system.
 
+I. Push cell and slice configuration over O1 using netopeer-cli
+---------------------------------------------------------------
+   When O-DU High is run with O1 enabled it waits for cell configuration to be pushed by SMO. In case the SMO is not available then these configurations can be pushed via netopeer-cli as follows.
+   1. Follow step H.1 and H.2.
+   2. update cellConfig.xml and rrmPolicy.xml.
+      $cd l2/build/config
+      $edit-config --target candidate --config=cellConfig.xml
+      $edit-config --target candidate --config=rrmPolicy.xml
+
 
-G. Troubleshooting Netconf server issues
+J. Troubleshooting Netconf server issues
 ----------------------------------------
    In case the Netconf server and sysrepo breaks down, run the following steps: