How to test the O1 interface

Hi

I get error " Access to the data model "o-ran-sc-ric-xapp-desc-v1" is denied because "netconf" NACM authorization failed." while doing an edit-config for

'o-ran:ric:xapp-desc' from netconf client.  Can someone help me out please.

Below is request and response

request:

<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"

xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">

<target>

<running/>

</target>

<config>

<ric xmlns="urn:o-ran:ric:xapp-desc:1.0">

<xapps>

<xapp xc:operation="create">

<name>hwxapp</name>

<release-name>hwxapp</release-name>

<version>0.0.4</version>

<namespace>ricxapp</namespace>

</xapp>

</xapps>

</ric>

</config>

</edit-config>

response:

<?xml version="1.0" encoding="utf-8"?>

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="54">

<rpc-error>

<error-type>protocol</error-type>

<error-tag>access-denied</error-tag>

<error-severity>error</error-severity>

<error-path>/o-ran-sc-ric-xapp-desc-v1:ric/xapps/xapp</error-path>

<error-message xml:lang="en">Access to the data model "o-ran-sc-ric-xapp-desc-v1" is denied because "netconf" NACM authorization failed.</error-message>

</rpc-error>

</rpc-reply>

Thanks for your response.
I have now moved to dawn release and all my previous working netconf commands have been throwing below error.
Missing mandatory prefix for XML metadata "type".
Can you please help?

I m sending this to Near-Rt-RIC.

Below is the requests.. which was fine in cherry but having issue in dawn.

<get>
<filter type="subtree">
<ric xmlns="urn:o-ran:ric:xapp-desc:1.0"/>
</filter>
</get>

<get>
<filter type="subtree">
<ric xmlns="urn:o-ran:ric:gnb-status:1.0"/>
</filter>
</get>

thanks for your response

When I verify the config changes I get:
{"errors":{"error":[{"error-tag":"data-missing","error-type":"protocol","error-message":"Mount point does not exist."}]}}

In fact, if I just try to do a GET a 409 is returned:
curl -sw '%{http_code}' -u admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U -X GET "http://127.0.1.1:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=du_sim/netconf-node-topology:available-capabilities?content=nonconfig" -H "accept: application/xml"
<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-tag>data-missing</error-tag><error-type>protocol</error-type><error-message>Request could not be completed because the relevant data model content does not exist</error-message></error></errors>409

But, I do see the RU and DU as "Connecting" in the ODLUX ONAP Connect page.  Any thoughts?

Hi David Harton,

It appears that even thought RU and DU were connecting, that they were not connected. The SMO has to be able to "mount" the device before any requests succeed. That is where I would focus.

I do not know which RU/DU you are using. If you are using the SIM version, your best bet for any questions is withAlex Stancu or Martin Skorupski. If you are using your own, then you will have to debug the NETCONF session establishment, which is what enables the SMO to mount the device.

Hi,

   I am getting a error "RU failed to Connect" when I run ./run_tests.sh.Can someone help out resolving this error.

Below is output I am getting when I run.

[+] Running 3/3
⠿ Container sdnrdb Removed 0.8s
⠿ Container sdnr Removed 11.2s
⠿ Network smo_integration Removed 0.2s
[+] Running 3/3
⠿ Network smo_integration Created 0.1s
⠿ Container sdnrdb Started 1.3s
⠿ Container sdnr Started 1.4s
000
000
000
000
000
000
000
000
000
000
000
200
SDNR is up and running

RU failed to connect.

Thanks in advance...

Adding bhanu chandra to the thread.

While we wait for bhanu chandra to respond, here are a few things I would check.

If you look at the README in the root folder, were you able to bring up the two servers, DU and RU up? Were you able to "mount" them onto ODL using the GUI? Those two steps are needed before you can run any tests.

Hello sir,

          I have checked the README in the root folder.The Host ip which i was giving was wrong i have corrected that mistake now.Its showing now RU is connected. 

Below is the snapshot of GUI which I got.

Now I am getting this issue .Please help me out.

[+] Running 1/0
⠿ tests Warning: No resource found to remove 0.0s
[+] Running 3/3
⠿ Network tests_default Created 0.1s
⠿ Container tests-ntsim-ng-o-ru-1 Started 1.4s
⠿ Container tests-ntsim-ng-o-du-1 Started 1.3s
[+] Running 3/3
⠿ Container sdnr Removed 11.3s
⠿ Container sdnrdb Removed 0.9s
⠿ Network smo_integration Removed 0.2s
[+] Running 3/3
⠿ Network smo_integration Created 0.1s
⠿ Container sdnr Started 1.4s
⠿ Container sdnrdb Started 1.4s
000
000
000
000
000
000
000
000
000
000
000
200
SDNR is up and running

RU is up.

DU is up.

Adding DU simulator
Successfully added device DU

Checking DU simulator

DU simulator is not responding.

How can we manually send the software upgrade RPC in this SMO?

Hi, while trying to execute a RESTCONF 'POST' request to the point http://localhost:8181/rests/operations/network-topology:network-topology/topology=topology-netconf/node=ru_sim/yang-ext:mount/ietf-netconf:get-config, using POSTMAN, I am getting an internal server error as follows:

<html>

<head>
    <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
    <title>Error 500 Request failed.</title>
</head>

<body>
    <h2>HTTP ERROR 500 Request failed.</h2>
    <table>
        <tr>
            <th>URI:</th>
            <td>/rests/operations/network-topology:network-topology/topology=topology-netconf/node=ru_sim/yang-ext:mount/ietf-netconf:get-config
            </td>
        </tr>
        <tr>
            <th>STATUS:</th>
            <td>500</td>
        </tr>
        <tr>
            <th>MESSAGE:</th>
            <td>Request failed.</td>
        </tr>
        <tr>
            <th>SERVLET:</th>
            <td>org.glassfish.jersey.servlet.ServletContainer</td>
        </tr>
    </table>

</body>

</html>

Could anyone please help.

Were you successful in “mounting” the device?

Yes. both du and ru are mounted and visible on the ODL GUI. All the basic netconf messages except get, get-config, cancel-commit and kill session are working with 200 OK response from the server.

Syama Nair Above issue is related to the bug on opendaylight https://jira.opendaylight.org/browse/NETCONF-806

bhanu chandraThank you for the response. 

Mahesh Jethanandani What is the role of NTS_manager in these tests? I mean, how can we connect the NTS manager to sdnr? 

Hi.  When pnfReg goes to SMO, I assert username "root".  When netconf client at SMO talks to my netconf-server, it attempts to use a password.  I have no idea what it is using, however.  When I look in ODLUX UI I see "connecting" status.  If I change the password there to something I know, it works.  The question is that field has a pre-populated perhaps 4-character password in place.  I'd like to make that my password to make the auto-discovery hands free.  Can anyone tell me what default password smo-netconf could be trying to use?  Should I avoid this altogether and use an existing known published username/password credential for netconf ssh?

Hi, is there any way to force password authentication instead of key-based for netconf-ssh in the SDNC?We are trying to connect to a node over O1 interface and it seems SDNC prefers key based authentication only, whereas the node accepts only password-based authentication, resulting in a connection failure.

Hi, 

I can see that the F-release version of the DU, part of SIM project has PM support. The following can be seen as part of the config:

"supported-measurements": [
                {
                    "performance-measurement-type": "o-ran-sc-du-hello-world:user-equipment-average-throughput-downlink",
                    "supported-snssai-subcounter-instances": [
                        {
                            "slice-differentiator": 2,
                            "slice-service-type": 2
                        },
                        {
                            "slice-differentiator": 1,
                            "slice-service-type": 2
                        },
                        {
                            "slice-differentiator": 2,

Is there anyway to store this as historical performance measurement data, to be visible in ODLUX, as well as be sent to the ves collector?

Hi,

Alexandru Stancu santanu de bhanu chandra  There seems to be an option in ODLUX to generate file-ready notifications-but the server is constantly sending back an error notification . Is there any specific format to be followed to successfully execute this message? Thanks in advance for your help.