1. Core NF Simulator Setup

  • We need a KUD vm with kubernetes installed, please follow below link to setup a KUD VM.

           https://wiki.onap.org/display/DW/Kubernetes+Baremetal+deployment+setup+instructions/

  • Please find below script with required data to be populated in AAI, provide the tenant id of the openstack project 

    #!/bin/bash 

    echo "Enter NFS Server: "
    read nfsServer

    echo "======== RUNNING AAI Data Populate ======="
    echo $nfsServer

    echo "===== Populating Customer"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v21/business/customers/customer/5GCustomer' \
    --header 'X-TransactionId: 42d3461d-074e-400e-93b1-c7ab5f48ce89' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "global-customer-id": "5GCustomer",
        "subscriber-name": "5GCustomer",
        "subscriber-type": "INFRA"
    }'

    echo "===== Populating owningEntity"


    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/business/owning-entities/owning-entity/67f2e84c-734d-4e90-a1e4-d2ffa2e75849' \
    --header 'X-TransactionId: 3656171c-3188-4a3d-b29a-284d2ba97ede' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "owning-entity-id": "67f2e84c-734d-4e90-a1e4-d2ffa2e75849",
        "owning-entity-name": "OE-5GCustomer"
    }'

    echo "===== Populating Platforms"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/business/platforms/platform/test' \
    --header 'X-TransactionId: 3c215f06-6ca5-4de4-8b75-bb06d002c922' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "platform-name": "test"
    }'

    echo "===== Populating Projects"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/business/projects/project/Project-5GCustomer' \
    --header 'X-TransactionId: 40c3addb-c661-4bd2-bf80-5160e4223776' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "project-name": "Project-5GCustomer"
    }'

    echo "====== Populating Line of Business"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/business/lines-of-business/line-of-business/LOB-5GCustomer' \
    --header 'X-TransactionId: ffed7201-15ab-41ab-8960-6db2cd16a264' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "line-of-business-name": "LOB-5GCustomer"
    }'

    echo "======== Populating Complex"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/cloud-infrastructure/complexes/complex/clli2' \
    --header 'X-TransactionId: 79ec2b55-0e1a-4a8a-904c-02d87a43fdc5' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "physical-location-id": "clli2",
        "physical-location-type": "office",
        "street1": "Dummy 1",
        "city": "Kraków",
        "postal-code": "30-000",
        "country": "Poland",
        "region": "Smaller Poland"
    }'


    echo "======== Populating Cloud Region"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour' \
    --header 'X-TransactionId: 34cac914-d32c-4523-ac75-008db129bcc6' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --data-raw '{
        "cloud-owner": "k8scloudowner4",
        "cloud-region-id": "k8sregionfour",
        "cloud-type": "k8s",
        "owner-defined-type": "t1",
        "cloud-region-version": "1.0",
        "complex-name": "clli2",
        "cloud-zone": "CloudZone",
        "sriov-automation": false
    }'


    echo "======== Populating Complex Cloud Region Relationship"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour/relationship-list/relationship' \
    --header 'X-TransactionId: 1d651697-0c65-4d21-bad5-299f95e4ddb6' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "related-to": "complex",
        "related-link": "/aai/v16/cloud-infrastructure/complexes/complex/clli2",
        "relationship-data": [
            {
                "relationship-key": "complex.physical-location-id",
                "relationship-value": "clli2"
            }
        ]
    }'

    echo "======== Populating Service"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/service-design-and-creation/services/service/5G' \
    --header 'X-TransactionId: db58cf73-f420-4f07-8cab-801474c9303c' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
            "service-description": "5GCore on K8s",
            "service-id": "5G"
    }'

    echo "======== Populating Service Subscription"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G' \
    --header 'X-TransactionId: c385a48c-cf4b-4fcd-976c-2d9cad40b19e' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
            "service-type": "5G"
    }'

    echo "======== Populating Tenant"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour/tenants/tenant/3d5819f1542e4ef9a4ccb0bcb278ca10' \
    --header 'X-TransactionId: c229f2aa-ea0f-4057-a9dd-0144b6e0e72a' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "tenant-id": "3d5819f1542e4ef9a4ccb0bcb278ca10",
        "tenant-name": "ONAP-tm",
        "relationship-list": {
            "relationship": [
                {
                    "related-to": "service-subscription",
                    "relationship-label": "org.onap.relationships.inventory.Uses",
                    "related-link": "/aai/v16/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G",
                    "relationship-data": [
                        {
                            "relationship-key": "customer.global-customer-id",
                            "relationship-value": "5GCustomer"
                        },
                        {
                            "relationship-key": "service-subscription.service-type",
                            "relationship-value": "5G"
                        }
                    ]
                }
            ]
        }
    }'


    echo "======== Populating availability zone name"

    curl -k --location -g --request PUT 'https://'$nfsServer':30233/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour/availability-zones/availability-zone/k8savz' \
    --header 'X-TransactionId: c229f2aa-ea0f-4057-a9dd-0144b6e0e72a' \
    --header 'X-FromAppId: jimmy-postman' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Basic QUFJOkFBSQ==' \
    --data-raw '{
        "availability-zone-name": "k8savz",
        "hypervisor-type": "k8s"
    }'


    echo "=========================== Finished Populating AAI Data ============="

  • After KUD setup and AAI data entries, update the connectivity Info: <port: msb-iag port>

          curl -k -i -F "metadata=<post.json;type=application/json" -F file=@/root/.kube/config -X POST https://{{k8s}}:32330/api/multicloud-k8s/v1/v1/connectivity-info

          Please find post.json below,

          {
           "cloud-region": "k8sregionfour",
           "cloud-owner": "k8scloudowner4"
          }

Refer Core NF Simulator setup to setup Core NF Simulator.

2. RAN Simulator Setup

2a) RANSIM Controller

Refer RAN-Sim setup to setup RAN-simulator

Refer RAN-Sim for ransim impacts done for Guilin Release

2b) Honeycomb:

Repo URL: https://github.com/onap-oof-pci-poc/ran-sim

Pre-requisite: SDNC & Ransim controller should be up and running.

Build Steps:

If there is a new yang model, build the gnbsim-api with new yang model

Step 1: copy the new yang model to ~/ran-sim/hcsim-content/gnbsim/gnbsim-api/src/main/yang
Step 2: Go to directory ~/ran-sim/hcsim-content/gnbsim/gnbsim-api/
Step 3: Issue the build command "JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64 mvn clean install -Dcheckstyle.skip"

For code changes in gnbsim-impl directory

Step 1: Do necessary code changes in gnbsim-impl
Step 2: Issue the build command "JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64 mvn clean install -Dcheckstyle.skip"

Once the mvn build is done, build the docker image

Step 1: Go to directory ~/ran-sim/hcsim-content/gnbsim
Step 2: JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ mvn clean install -Dcheckstyle.skip
Step 3: cp -r gnbsim-distribution/jssecacerts gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
Step 4: cp -r gnbsim-distribution/honeycomb gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
Step 5: cp -r gnbsim-distribution/Dockerfile gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/
Step 6: docker build -t gn gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/

Cross check the docker image
docker images | grep gnbsim

To run the Netconf Servers:

  1. Update ransim and honeycom IP address at ~/ran-sim/hcsim-content/gnbsim/hc/config/gnbsim.json

      2. Run the below command from ~/ran-sim/hcsim-content/gnbsim/hc directory.

          docker-compose up -d

          For slicing setup, 12 netconf servers are required. Copy the hc directory 11 more time and rename it.

         Change the external port in the docker-compose files for every netconf server.

         While running the docker-compose up -d command, these servers will be mounted in SDNC. 

Setup SFPT:

  1. Run the below docker command in the VM where you have setup the netconf servers:

           docker run -v /home/$USER/upload:/home/$USER/sftptest/upload -p 2222:22 -d atmoz/sftp $USER:pass:1001

      2. Give chmod 777 to upload folder which will be created automatically in the home dir.

Further References:

Issues faced during the RAN Simulator set up are documented in Setup related issues.


  • No labels

25 Comments

  1. Hi Ahila P,


    This directory path is not present in git repo  "/ransim_rannetwork/ransim/gnbsim/" 


    Thanks

      1. Hi Ahila P,

         1st query, my devices get mounted into sdnr, but the devices are not getting configured as per the ran-network yang.

        2nd query i spawned all 12 netconf server how can I verify this use case.

        here I am using guilin release.

        Thanks

        1. Hi Abhimanyu Garg,

          You can verify the mounted devices and its configurations in the ODL page. https://<ip>:<port>/apidoc/explorer/index.html

          1. hi Ahila P,

            The devices get mounted in odl with applied Ran-network yang, but the configuration is not present while using the get api


            Thanks


  2. Hi Ahila P

    We have an issue demonstrating the flow of Closed Loop Use-Case in E2E network slicing use case in Honolulu (commit 2021-04-22 https://gerrit.onap.org/r/gitweb?p=oom.git;a=commit;h=06eacdc8e156fcb2ff94d50a40ce03338045a823 - Installation Documentation @ https://wiki.onap.org/display/DW/Install+Minimum+Scope+for+Option+1?src=contextnavpagetreemode)

    Honeycomb NetConf Servers (part of RAN-SIM, following this documentation Core & RAN Simulators - Developer Wiki - Confluence (onap.org)), while sending FileReady Event to VES interface, are receiving a “400” Bad Parameter, because the json body is not compliant with VES 7.2.1 Schema. In details, “reportingEntityName” property is missing. Moreover “location”, “compression”, “fileFormatType” and “fileFormatVersion” attributes are present in the FileReady event but not defined in the V 7.2.1 schema.

    If you manually fix the original FileReady against correct Schema, then VES is able to receive and forward via DMAAP the event to DFC. But finally, when DFC parses the JSON, it shows an error because it is unable to connect to the given FTPES server. We found that the FTPES endpoint is hardcoded in the RANSIM-GNBSIM codebase as you can see from the LOC #161 in SlicePmDataHandler.java -> ran-sim/SlicePmDataHandler.java at 539208f300315ad50f00a84966b0eb2cfc0645fc · onap-oof-pci-poc/ran-sim · GitHub.

    In particular it links a “random” local ip (192.168.x.x – maybe developer’s machine one?). On the other hand it seems that no FTPES port binding is present on Netconf Honeycomb servers so we can not imagine how it could work within the given configuration.

    Are the RAN SIM implementations, contained in ONAP-OOF-PCI-POC repo , really intended for closed loop use case (master branch @  https://github.com/onap-oof-pci-poc/ran-sim/commit/a6483c41863a6197c38a0f19143d4aded17a77e8)?

    Are we supposed to launch an additional FTPES server inside the ONAP cluster in order to get the use case work?


    Thank you 

  3. Hi Raffaele Passannanti, I have updated the documentation. You can use the latest commit from github.

  4. Hi,

    Is there any significant of the following Exception:  

    Found in RANsim


    2021-06-25T14:24:20{GMT+0}+00:00|||localhost-startStop-1||||ERROR|||||org.onap.ransim.rest.config.RansimRestConfig.init(RansimRestConfig.java:59)||Exception Occured while loading properties file : {}
    java.io.FileNotFoundException: rs.properties (No such file or directory)
    at java.io.FileInputStream.open0(Native Method)
    at java.io.FileInputStream.open(FileInputStream.java:195)
    at java.io.FileInputStream.<init>(FileInputStream.java:138)
    at java.io.FileInputStream.<init>(FileInputStream.java:93)
    at org.onap.ransim.rest.config.RansimRestConfig.init(RansimRestConfig.java:55)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:389)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:333)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:157)


    Thanks

    1. Hi Abhimanyu Garg,

      just to know how did you fix this RANsim problem:

      "RansimRestConfig.init(RansimRestConfig.java:59)||Exception Occured while loading properties file : {} java.io.FileNotFoundException: rs.properties (No such file or directory)",

      I've exactly the same error in ransim logs when I launch ran simulator.

      Thanks.

      1. Hi Bruno Lainé ,

        There is not such significance of this exception. This will not give any impact on using RANsim.

        Thanks.

  5. Hi Niranjana Y,


    These following from SlicePmDataHandler.java

    As we are using gnbsim git repo which code of line need to use to get the sftphost ip? As HcIp method is commented?  

    //private static String SFTPHOST = (Configuration.getInstance().getHcIp()).trim();



    Is this enodebsimIp variable reading from following path?

    #\ran-sim\hcsim-content\gnbsim\hcsim-content\enodebsim\enodebsim-distribution\src\main\docker\toCopy\config\ransim.properties

    private static String SFTPHOST = (System.getenv("enodebsimIp")).trim();;


    RANsim controller logs:

    2021-07-05 13:54:49.639 UTC [WebSocketSimpleContainer@1158002702-69] INFO c.wipro.www.ves.SlicePmDataHandler - Compressing file
    2021-07-05 13:54:49.640 UTC [WebSocketSimpleContainer@1158002702-69] INFO c.wipro.www.ves.SlicePmDataHandler - Initiate SFTP transfer for PM data file
    2021-07-05 13:54:49.640 UTC [WebSocketSimpleContainer@1158002702-69] INFO c.wipro.www.ves.SlicePmDataHandler - preparing the host information for sftp.
    2021-07-05 13:54:49.655 UTC [WebSocketSimpleContainer@1158002702-69] INFO c.wipro.www.ves.SlicePmDataHandler - Exception found while tranfer the response. com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused (Connection refused)



    Thanks



    1. You can update the SFTPHOST with the IP address of the VM in which you have setup SFTP.

  6. Hi Niranjana Y,

    If we make the following as hardcode it works.

    private static String SFTPHOST = "172.16.XX.XX"

    but we this as uncomment -  private static String SFTPHOST = (Configuration.getInstance().getHcIp()).trim();

    getting following exception:

    Caused by: java.lang.NullPointerException: null
    at com.wipro.www.ves.SlicePmDataHandler.<clinit>(SlicePmDataHandler.java:64) ~[gnbsim-impl-1.19.08-SNAPSHOT.jar:na]
     ===================================================
    =================

    Now we are facing the below issue as above one has been resolved by doing the hardcode.

    We have the ves url with http  Slice Pm url: http://172.xx.xx.xx:31974/eventListener/v7

    so due to that ves event is not sending to ves collector from HC

    2021-07-09 13:03:36.613 UTC [WebSocketSimpleContainer@1310276436-34] ERROR c.w.w.ves.restclient.HttpRequester - Exc in post java.lang.ClassCastException: sun.net.www.protocol.http.HttpURLConnection cannot be cast to javax.net.ssl.HttpsURLConnection
    2021-07-09 13:03:36.613 UTC [WebSocketSimpleContainer@1310276436-34] INFO c.wipro.www.ves.SlicePmDataHandler - SlicePmDataHandler Response: Post failed


    Is this issue of http and https? as HC is supporting only https for ves event.

    Thanks



    1. Hi Abhimanyu Garg, I am testing this use case too...
      For VES issue, I think you need to update the URL from http to https ... In rel. H, VES service is exposed only in https.

      Let me know your progress,

      Aniello

      1. Hi Ahila P,

        I am facing below error :

        2021-08-17 10:13:21.961 UTC [WebSocketSimpleContainer@1867778905-31] INFO c.wipro.www.ves.SlicePmDataHandler - Slice Pm url: https://172.xx.xx.xx:30919/eventListener/v7
        2021-08-17 10:13:21.982 UTC [WebSocketSimpleContainer@1867778905-31] ERROR c.w.w.ves.restclient.HttpRequester - Exc in post javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        2021-08-17 10:13:21.982 UTC [WebSocketSimpleContainer@1867778905-31] INFO c.wipro.www.ves.SlicePmDataHandler - SlicePmDataHandler Response: Post failed


        I tried to import the certs into honeycomb-keystore at path /opt/app/honeycomb/cert:

        getting below error

        root@honeycomb:/opt/app/honeycomb/cert# keytool -import -noprompt -trustcacerts -alias VEScacerts -file cacert.pem -keystore /opt/app/honeycomb/cert/honeycomb-keystore -storepass changeit
        keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
        root@honeycomb:/opt/app/honeycomb/cert#


        Please guide me resolve this issue

        Thanks



        1. Hi Abhimanyu Garg,

          You need to add the VES certificate and rename the file as jssecacerts.

          I have added a sample here https://github.com/onap-oof-pci-poc/ran-sim/commit/8ec26f9a800eb4ad686bc983fcdde3a50c120787

          Copy jssecacerts, honeycomb to gnbsim-distribution-1.19.08-SNAPSHOT/ directory and build the docker image.

          cp -r gnbsim-distribution/jssecacerts gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/

           cp -r gnbsim-distribution/honeycomb gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT/

  7. Hi ,

    I am facing below error for Guilin SDN-R. This is happening while performing configuration of RANsim(honeycomb base) devices from "Configuration" TAB of ODLUX. The applied capabilities are not appearing at "Configuration" TAB of ODLUX.

    Could you tell me how to fix this issue?


    GET https://172.xx.xx.xx:30205/yang-schema/notifications/2008-07-14 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-netconf-monitoring-extension/2013-12-10 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-inet-types/2013-07-15 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/yang-ext/2013-07-09 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/iana-if-type/2014-05-08 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ran-network/2020-08-06 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-netconf/2011-06-01 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-yang-library/2016-06-21 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/nc-notifications/2008-07-14 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-interfaces/2014-05-08 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-netconf-monitoring/2010-10-04 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-yang-types/2013-07-15 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/network-topology/2013-10-21 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-netconf-notifications/2012-02-06 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/ietf-restconf-monitoring/2017-01-26 404 (Not Found)
    GET https://172.xx.xx.xx:30205/yang-schema/odl-general-entity/2015-09-30 404 (Not Found)

    Thanks

    Abhimanyu


    1. Hi Abhimanyu Garg 

      Just in case you did not find the root cause of the above issue -   

      The above error in Config App is due to a gap in the functionality in Config App. Config App reads schema files only from the /opt/opendaylight/cache/schema directory, however the devices mounted by Ransim have the schema directory explicitly configured with the mountpoint name. As a result, the Config App is not able to find the required yang schema files. Request generated by NetConf servers for mounting the device into SDNR is as below -

      <node xmlns="urn:TBD:params:xml:ns:yang:network-topology">    <node-id> ncserver1 </node-id>    <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>    <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>    <host xmlns="urn:opendaylight:netconf-node-topology">10.20.11.161</host>    <schema-cache-directory xmlns="urn:opendaylight:netconf-node-topology">ncserver1</schema-cache-directory>    <port xmlns="urn:opendaylight:netconf-node-topology">2831</port>    <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>    <schemaless xmlns="urn:opendaylight:netconf-node-topology">false</schemaless>    <max-connection-attempts xmlns="urn:opendaylight:netconf-node-topology">0</max-connection-attempts>    <connection-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">20000</connection-timeout-millis>    <default-request-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">60000</default-request-timeout-millis>    <sleep-factor xmlns="urn:opendaylight:netconf-node-topology">1.1</sleep-factor>    <between-attempts-timeout-millis xmlns="urn:opendaylight:netconf-node-topology">2000</between-attempts-timeout-millis>    <reconnect-on-changed-schema xmlns="urn:opendaylight:netconf-node-topology">false</reconnect-on-changed-schema>    <keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">60</keepalive-delay>    <concurrent-rpc-limit xmlns="urn:opendaylight:netconf-node-topology">0</concurrent-rpc-limit>    <actor-response-wait-time xmlns="urn:opendaylight:netconf-node-topology">60</actor-response-wait-time></node>


      Regards,

      Ravi

  8. Hi All,

    I have done the setup for ransim and gnodebsim with all 12 cu du nearrtic, and it is mounted to SDNR as well, and i can see the configuration also all of them.

    But my question is when we use oofpcipoc model we have cells displayed in ransim UI.

    But now we are using ran-network yang model, I am not able to see anything in ransim UI, it is bank no cells and nothing over there.

    So is it correct only or do i have to load any specific file for simulation?

    Plz help

    1. Hi amol jadhav ,

      We are working on the O-RAN Compliance for SON use case. With the current setup, RANSIM UI cannot reflect the ran-network.

      Thanks & Regards,

      Ahila P.

      1. Hi Ahila P 

        That means. currently we are not supporting the ran-network model on RanSim UI. Only oofpcipoc model for son use case have a support over Ransim UI.

        Am i right?

        Thanks,

        Amol Jadhav

        1. Yes. You are correct.

          1. ok Ahila P , Thank you for quick support.

  9. Hi Ahila P 


    I tried Generating PM Slice Intelligent data from RANSim and i could see events are Collected in the VESCollector end.
    Now i wanna simulate Fault Generation for the HC devices, how do we do that?

    pls guide.


    Thanks

    1. Hi murali partha ,

      FM message simulation is not in place for E2E network slicing.

      Regards,

      Ahila P.