o1-netconf.zip


The above zip file contains SMO NETCONF client support for O1 interface. It brings up two containers, SDNR and SDNR_DB which support O1 interface. The containers acts as a NETCONF client to the O-RAN elements (O-RU, O-CU, O-DU and the Near RT-RIC). It has both a GUI as well as RESTCONF support for the configuration management of devices.

Prerequisites:

  • docker
  • docker-compose
  • Java, version 11 or newer

Instructions

Below are the steps to bring up the required services


1. Download and unzip the file

unzip o1-netconf.zip


2. Bringup the services

cd client
docker-compose up -d

3. check status

docker-compose ps


Expect an output that looks something like this:

$ docker-compose ps
Name  Command                    State Ports 
------------------------------------------------------------------------
sdnr /bin/sh -c /opt/onap/sdnc/   Up    0.0.0.0:8101->8101/tcp,:::
     ...                                8101->8101/tcp, 0.0.0.0:81
                                        81->8181/tcp,:::8181->8181
                                        /tcp 
sdnrdb /tini -- /usr/local/bin/do Up    9200/tcp, 9300/tcp

Access details

Access the GUI and RESTCONF interface using the following URLs, credentials are common for both of them.

GUI: http://<host_ip>:8181/odlux/index.html
Restconf: http://<host_ip>:8181/apidoc/explorer/index.html
username/password: admin/ Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U


  • No labels

8 Comments

  1. RAGHU KOTA

    I am facing issue connecting to this client using dawn(i mean master clone) release, with cherry release it is working fine.
    {"log":"/usr/local/bin/netopeer2-server: /usr/lib/x86_64-linux-gnu/libssh.so.4: no version information available (required by /usr/local/bin/netopeer2-server)\n","stream":"stdout","time":"2021-08-02T10:51:41.489093024Z"}
    {"log":"/usr/local/bin/netopeer2-server: /usr/lib/x86_64-linux-gnu/libssh.so.4: no version information available (required by /usr/local/lib/libnetconf2.so.2)\n","stream":"stdout","time":"2021-08-02T10:51:41.489100364Z"}
    {"log":"\n","stream":"stdout","time":"2021-08-02T10:51:41.489111845Z"}

    Its in connecting state only and i see below logs

    {"log":"free(): invalid pointer\n","stream":"stdout","time":"2021-08-02T10:51:40.289816725Z"}

    {"log":"\n","stream":"stdout","time":"2021-08-02T10:51:40.289822182Z"}

    {"log":"2021-08-02 10:51:40,478 DEBG fd 10 closed, stopped monitoring \u003cPOutputDispatcher at 139825121098720 for \u003cSubprocess at 139825121365360 with name

    netopeer2-server in state RUNNING\u003e (stdout)\u003e\n","stream":"stdout","time":"2021-08-02T10:51:40.47878272Z"}

    {"log":"2021-08-02 10:51:40,478 INFO exited: netopeer2-server (terminated by SIGABRT (core dumped); not expected)\n","stream":"stdout","time":"2021-08-02T10:51:40.

    47903554Z"}



    1. Mahesh Jethanandani

      Hi Raghu,

      It is not clear to me what you are trying to do. Could you describe your setup?

      For example, the first set of messages are all from netopeer2 server complaining it does not have access to SSH libraries. First of all, SMO is the client, not the server, and these messages are coming from the server. Secondly, it is asking for SSH libraries, which means you have not installed SSH libraries on your machine. Have you made sure you have fulfilled the requirements for netopeer2 specified here?

      1. RAGHU KOTA

        Hi Mahesh,

        I am using this client to test my NearRTRIC O1 interface. In my setup NearRTRIC acts as netopeer2 server.
        The logs message i have given above are from "deployment-ricplt-o1mediator-f7dd5fcc8-5x7vm" pod on the NearRTRIC.

        When i have used the code "git clone http://gerrit.o-ran-sc.org/r/it/dep -b cherry" it was working with this client.
        But when i have used the code from "http://gerrit.o-ran-sc.org/r/it/dep" which is latest, client is not able to connect to the server.

        Yes the issue is not with the client but with the server, so was asking is there any issue with the latest o-ran-sc O1agent code which acts as netconf server. Please let me know if u need any further details.

        1. Mahesh Jethanandani

          Hi Raghu, 

          I do not know what you mean when you say "I am using this client". What is "this client"? The SMO image or your own NETCONF client?

          Either ways, based on what you are telling me, the issue seems to be with the server code of Near RT-RIC. In that case, you need to bring this up with the Near RT-RIC, and not here on the SMO page.

          1. RAGHU KOTA

            OK thanks ...i will post in the Near  RT-RIC Page

            Just to clarify i am using the above "zip file contains SMO NETCONF client support for O1 interface", mentioned in this page to test Near RT_RIC O1 interface for NEAR-RT RIC as it mentions the same.

  2. PRIYADHARSHINI G S

    Hi

    What would be the minimum requirements for the VM to install SMO dawn release?


    Thanks

  3. Mahesh Jethanandani

    Hi PRIYADHARSHINI G S, I do not know what the minimum requirements are, but I have run the O1 and VES interface on a VM that has 2 vCPUs and 8G of memory.

    HTH.

  4. Brand Lu

    If I want to use this UDM to connect with real device,how to debug the netconf procedure between client and server?