Steps to build the RAN-Sim Controller setup: 

  1. Clone and Checkout Ran-Sim Controller 

    git clone "https://gerrit.onap.org/r/integration/simulators/ran-simulator"

  2. Copy ‘settings.xml’ from ‘<YOURFOLDER>/ran-simulator/ransim/ransimctrlr/packages/base/src/files/m2/settings.xml’ to <HOME>/.m2/ folder as settings.xml file after updating environment specific configurations. 

             If the file already exists in <HOME>/.m2/ folder, then merge this file content into the existing file appropriately. 

             Note: settings.xml entries are mandatory to include dependencies.

      3. Open the terminal and navigate to the '<YOURFOLDER>/ran-simulator/ransim'

      4. Run the following command in the terminal

mvn clean install -P docker

      5. After successful build navigate to '<YOURFOLDER>/ran-simulator/ransim/docker' directory

      6. The SDNR details can be updated in the file '<YOURFOLDER>/ran-simulator/ransim/docker/docker-compose.yml'.

                    environment: 

                           - SDNR_IP={SDNR IP address} 

                          - SDNR_PORT={SDNR port number} 

                           - SDNR_USER={SDNR user ID} 

                           - SDNR_PASSWORD={SDNR user password} 

      7. Run the 'docker-compose up -d' command in the terminal( Note: Use docker compose version 1.6.0 or above)

      8. Once the ransim and mariadb containers are started, you can see logs in the ransim container under the folder /opt/app/policy/servers/ransim/logs

 

Steps to check the RAN-Sim Controller logs 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Navigate to '/opt/app/policy/servers/ransim/logs' using the cd command.

       4. Execute the following command to check the logs:

                   'tail -f ransim-rest.log' 

 

Steps to access the tables in mysql and check table contents 

  1. Enter the following commands in console to accessmysql:

                  'mysql -uroot -psecret' 

             'use ransim_db' 

      2. Type 'show tables;' to check the and access the tables.

 

Steps to start/stop RAN network slice simulation 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Run the following command tostart the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StartRanSliceSimulation' 


       4. Run the following command tostop the RAN network slice simulation: 

curl -k -X DELETE --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StopRanSliceSimulation'

 

Steps to start/stop generating Intelligent slicing PM data 

  1. Open the console and enter the following command:

                  'docker ps' 

       2. Once the container details is displayed enter the following command:

                  'docker exec -it ransim bash'

       3. Run the following command to start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/GenerateIntelligentSlicingPmData -i  

       4. Run the following commandto Start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i 

       5. You can see the generated slicing pm data files in the ransim container under the folder /tmp/ransim-install.


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

<measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec"> 

    <fileHeader dnPrefix="Prefix" fileFormatVersion="32.435 V10.0" vendorName="Acme Ltd"> 

        <fileSender localDn="cucpserver1"/> 

        <measCollec beginTime="2020-12-02T05:01:37.863"/> 

    </fileHeader> 

    <measData> 

        <managedElement localDn="cucpserver1" swVersion="r0.1"/> 

        <measInfo measInfoId="measInfoIsVal"> 

            <job jobId="9327"/> 

            <granPeriod duration="PT900S" endTime="2020-12-02T05:01:37.863"/> 

            <repPeriod duration="PT900S"/> 

            <measType p="1">SM.PDUSessionSetupReq.0011-0010</measType> 

            <measType p="2">SM.PDUSessionSetupSucc.0011-0010</measType> 

            <measType p="3">SM.PDUSessionSetupFail.0</measType> 

            <measType p="4">SM.PDUSessionSetupReq.0010-1110</measType> 

            <measType p="5">SM.PDUSessionSetupSucc.0010-1110</measType> 

            <measValue measObjLdn="13999"> 

                <r p="1">2676.0</r> 

                <r p="2">1749.0</r> 

                <r p="4">3158.0</r> 

                <r p="5">1921.0</r> 

                <r p="3">1958.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="14000"> 

                <r p="1">2392.0</r> 

                <r p="2">1522.0</r> 

                <r p="4">3571.0</r> 

                <r p="5">2575.0</r> 

                <r p="3">1696.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15155"> 

                <r p="1">5279.0</r> 

                <r p="2">3300.0</r> 

                <r p="4">7237.0</r> 

                <r p="5">5187.0</r> 

                <r p="3">3655.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15174"> 

                <r p="1">5545.0</r> 

                <r p="2">3397.0</r> 

                <r p="4">7649.0</r> 

                <r p="5">5493.0</r> 

                <r p="3">3994.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15175"> 

                <r p="1">5229.0</r> 

                <r p="2">3349.0</r> 

                <r p="4">8120.0</r> 

                <r p="5">5590.0</r> 

                <r p="3">4016.0</r> 

                <suspect>false</suspect> 

            </measValue> 

        </measInfo> 


    </measData> 

    <fileFooter> 

        <measCollec endTime="2020-12-02T05:01:37.863"/> 

    </fileFooter> 

</measCollecFile> 


 


Steps to build the RAN-Sim Controller setup: 

  1. Clone and Checkout Ran-Sim Controller 

    git clone "https://gerrit.onap.org/r/integration/simulators/ran-simulator"

    You can download below patchset for refactored and enhanced RAN-simulator code for setup, the code is in review stage will be merged soon.

  2. Copy ‘settings.xml’ from ‘<YOURFOLDER>/ran-simulator/ransim/ransimctrlr/packages/base/src/files/m2/settings.xml’ to <HOME>/.m2/ folder as settings.xml file after updating environment specific configurations. 

             If the file already exists in <HOME>/.m2/ folder, then merge this file content into the existing file appropriately. 

             Note: settings.xml entries are mandatory to include dependencies.

      3. Open the terminal and navigate to the '<YOURFOLDER>/ran-simulator/ransim'

      4. Run the following command in the terminal

mvn clean install -P docker

      5. After successful build navigate to '<YOURFOLDER>/ran-simulator/ransim/docker' directory

      6. The SDNR details can be updated in the file '<YOURFOLDER>/ran-simulator/ransim/docker/docker-compose.yml'.

                    environment: 

                           - SDNR_IP={SDNR IP address} 

                          - SDNR_PORT={SDNR port number} 

                           - SDNR_USER={SDNR user ID} 

                           - SDNR_PASSWORD={SDNR user password} 

      7. Run the 'docker-compose up -d' command in the terminal( Note: Use docker compose version 1.6.0 or above)

      8. Once the ransim and mariadb containers are started, you can see logs in the ransim container under the folder /opt/app/policy/servers/ransim/logs

 

Steps to check the RAN-Sim Controller logs 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Navigate to '/opt/app/policy/servers/ransim/logs' using the cd command.

       4. Execute the following command to check the logs:

                   'tail -f ransim-rest.log' 

 

Steps to access the tables in mysql and check table contents 

  1. Enter the following commands in console to accessmysql:

                  'mysql -uroot -psecret' 

             'use ransim_db' 

      2. Type 'show tables;' to check the and access the tables.

 

Steps to start/stop RAN network slice simulation 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Run the following command tostart the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StartRanSliceSimulation' 


       4. Run the following command tostop the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StopRanSliceSimulation' 

 

Steps to start/stop generating Intelligent slicing PM data 

  1. Open the console and enter the following command:

                  'docker ps' 

       2. Once the container details is displayed enter the following command:

                  'docker exec -it ransim bash'

       3. Run the following command to start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/GenerateIntelligentSlicingPmData -i  

       4. Run the following commandto Start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i 

       5. You can see the generated slicing pm data files in the ransim container under the folder /tmp/ransim-install.


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

<measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec"> 

    <fileHeader dnPrefix="Prefix" fileFormatVersion="32.435 V10.0" vendorName="Acme Ltd"> 

        <fileSender localDn="cucpserver1"/> 

        <measCollec beginTime="2020-12-02T05:01:37.863"/> 

    </fileHeader> 

    <measData> 

        <managedElement localDn="cucpserver1" swVersion="r0.1"/> 

        <measInfo measInfoId="measInfoIsVal"> 

            <job jobId="9327"/> 

            <granPeriod duration="PT900S" endTime="2020-12-02T05:01:37.863"/> 

            <repPeriod duration="PT900S"/> 

            <measType p="1">SM.PDUSessionSetupReq.0011-0010</measType> 

            <measType p="2">SM.PDUSessionSetupSucc.0011-0010</measType> 

            <measType p="3">SM.PDUSessionSetupFail.0</measType> 

            <measType p="4">SM.PDUSessionSetupReq.0010-1110</measType> 

            <measType p="5">SM.PDUSessionSetupSucc.0010-1110</measType> 

            <measValue measObjLdn="13999"> 

                <r p="1">2676.0</r> 

                <r p="2">1749.0</r> 

                <r p="4">3158.0</r> 

                <r p="5">1921.0</r> 

                <r p="3">1958.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="14000"> 

                <r p="1">2392.0</r> 

                <r p="2">1522.0</r> 

                <r p="4">3571.0</r> 

                <r p="5">2575.0</r> 

                <r p="3">1696.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15155"> 

                <r p="1">5279.0</r> 

                <r p="2">3300.0</r> 

                <r p="4">7237.0</r> 

                <r p="5">5187.0</r> 

                <r p="3">3655.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15174"> 

                <r p="1">5545.0</r> 

                <r p="2">3397.0</r> 

                <r p="4">7649.0</r> 

                <r p="5">5493.0</r> 

                <r p="3">3994.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15175"> 

                <r p="1">5229.0</r> 

                <r p="2">3349.0</r> 

                <r p="4">8120.0</r> 

                <r p="5">5590.0</r> 

                <r p="3">4016.0</r> 

                <suspect>false</suspect> 

            </measValue> 

        </measInfo> 


    </measData> 

    <fileFooter> 

        <measCollec endTime="2020-12-02T05:01:37.863"/> 

    </fileFooter> 

</measCollecFile> 


 


Steps to build the RAN-Sim Controller setup: 

  1. Clone and Checkout Ran-Sim Controller 

    git clone "https://gerrit.onap.org/r/integration/simulators/ran-simulator"

  2. Copy ‘settings.xml’ from ‘<YOURFOLDER>/ran-simulator/ransim/ransimctrlr/packages/base/src/files/m2/settings.xml’ to <HOME>/.m2/ folder as settings.xml file after updating environment specific configurations. 

             If the file already exists in <HOME>/.m2/ folder, then merge this file content into the existing file appropriately. 

             Note: settings.xml entries are mandatory to include dependencies.

      3. Open the terminal and navigate to the '<YOURFOLDER>/ran-simulator/ransim'

      4. Run the following command in the terminal

mvn clean install -P docker

      5. After successful build navigate to '<YOURFOLDER>/ran-simulator/ransim/docker' directory

      6. The SDNR details can be updated in the file '<YOURFOLDER>/ran-simulator/ransim/docker/docker-compose.yml'.

                    environment: 

                           - SDNR_IP={SDNR IP address} 

                          - SDNR_PORT={SDNR port number} 

                           - SDNR_USER={SDNR user ID} 

                           - SDNR_PASSWORD={SDNR user password} 

      7. Run the 'docker-compose up -d' command in the terminal( Note: Use docker compose version 1.6.0 or above)

      8. Once the ransim and mariadb containers are started, you can see logs in the ransim container under the folder /opt/app/policy/servers/ransim/logs

 

Steps to check the RAN-Sim Controller logs 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Navigate to '/opt/app/policy/servers/ransim/logs' using the cd command.

       4. Execute the following command to check the logs:

                   'tail -f ransim-rest.log' 

 

Steps to access the tables in mysql and check table contents 

  1. Enter the following commands in console to accessmysql:

                  'mysql -uroot -psecret' 

             'use ransim_db' 

      2. Type 'show tables;' to check the and access the tables.

 

Steps to start/stop RAN network slice simulation 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Run the following command tostart the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StartRanSliceSimulation' 


       4. Run the following command tostop the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StopRanSliceSimulation' 

 

Steps to start/stop generating Intelligent slicing PM data 

  1. Open the console and enter the following command:

                  'docker ps' 

       2. Once the container details is displayed enter the following command:

                  'docker exec -it ransim bash'

       3. Run the following command to start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/GenerateIntelligentSlicingPmData -i  

       4. Run the following commandto Start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i 

       5. You can see the generated slicing pm data files in the ransim container under the folder /tmp/ransim-install.


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

<measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec"> 

    <fileHeader dnPrefix="Prefix" fileFormatVersion="32.435 V10.0" vendorName="Acme Ltd"> 

        <fileSender localDn="cucpserver1"/> 

        <measCollec beginTime="2020-12-02T05:01:37.863"/> 

    </fileHeader> 

    <measData> 

        <managedElement localDn="cucpserver1" swVersion="r0.1"/> 

        <measInfo measInfoId="measInfoIsVal"> 

            <job jobId="9327"/> 

            <granPeriod duration="PT900S" endTime="2020-12-02T05:01:37.863"/> 

            <repPeriod duration="PT900S"/> 

            <measType p="1">SM.PDUSessionSetupReq.0011-0010</measType> 

            <measType p="2">SM.PDUSessionSetupSucc.0011-0010</measType> 

            <measType p="3">SM.PDUSessionSetupFail.0</measType> 

            <measType p="4">SM.PDUSessionSetupReq.0010-1110</measType> 

            <measType p="5">SM.PDUSessionSetupSucc.0010-1110</measType> 

            <measValue measObjLdn="13999"> 

                <r p="1">2676.0</r> 

                <r p="2">1749.0</r> 

                <r p="4">3158.0</r> 

                <r p="5">1921.0</r> 

                <r p="3">1958.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="14000"> 

                <r p="1">2392.0</r> 

                <r p="2">1522.0</r> 

                <r p="4">3571.0</r> 

                <r p="5">2575.0</r> 

                <r p="3">1696.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15155"> 

                <r p="1">5279.0</r> 

                <r p="2">3300.0</r> 

                <r p="4">7237.0</r> 

                <r p="5">5187.0</r> 

                <r p="3">3655.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15174"> 

                <r p="1">5545.0</r> 

                <r p="2">3397.0</r> 

                <r p="4">7649.0</r> 

                <r p="5">5493.0</r> 

                <r p="3">3994.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15175"> 

                <r p="1">5229.0</r> 

                <r p="2">3349.0</r> 

                <r p="4">8120.0</r> 

                <r p="5">5590.0</r> 

                <r p="3">4016.0</r> 

                <suspect>false</suspect> 

            </measValue> 

        </measInfo> 


    </measData> 

    <fileFooter> 

        <measCollec endTime="2020-12-02T05:01:37.863"/> 

    </fileFooter> 

</measCollecFile> 


 


Steps to build the RAN-Sim Controller setup: 

  1. Clone and Checkout Ran-Sim Controller 

    git clone "https://gerrit.onap.org/r/integration/simulators/ran-simulator"

    You can download below patchset for refactored and enhanced RAN-simulator code for setup, the code is in review stage will be merged soon.

  2. Copy ‘settings.xml’ from ‘<YOURFOLDER>/ran-simulator/ransim/ransimctrlr/packages/base/src/files/m2/settings.xml’ to <HOME>/.m2/ folder as settings.xml file after updating environment specific configurations. 

             If the file already exists in <HOME>/.m2/ folder, then merge this file content into the existing file appropriately. 

             Note: settings.xml entries are mandatory to include dependencies.

      3. Open the terminal and navigate to the '<YOURFOLDER>/ran-simulator/ransim'

      4. Run the following command in the terminal

mvn clean install -P docker

      5. After successful build navigate to '<YOURFOLDER>/ran-simulator/ransim/docker' directory

      6. The SDNR details can be updated in the file '<YOURFOLDER>/ran-simulator/ransim/docker/docker-compose.yml'.

                    environment: 

                           - SDNR_IP={SDNR IP address} 

                          - SDNR_PORT={SDNR port number} 

                           - SDNR_USER={SDNR user ID} 

                           - SDNR_PASSWORD={SDNR user password} 

      7. Run the 'docker-compose up -d' command in the terminal( Note: Use docker compose version 1.6.0 or above)

      8. Once the ransim and mariadb containers are started, you can see logs in the ransim container under the folder /opt/app/policy/servers/ransim/logs

 

Steps to check the RAN-Sim Controller logs 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Navigate to '/opt/app/policy/servers/ransim/logs' using the cd command.

       4. Execute the following command to check the logs:

                   'tail -f ransim-rest.log' 

 

Steps to access the tables in mysql and check table contents 

  1. Enter the following commands in console to accessmysql:

                  'mysql -uroot -psecret' 

             'use ransim_db' 

      2. Type 'show tables;' to check the and access the tables.

 

Steps to start/stop RAN network slice simulation 

  1. Open the console and enter the following command:

                   'docker ps' 

       2. Once the container details is displayed enter the following command:

                   'docker exec -it ransim bash'

       3. Run the following command tostart the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StartRanSliceSimulation' 


       4. Run the following command tostop the RAN network slice simulation: 

curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StopRanSliceSimulation' 

 

Steps to start/stop generating Intelligent slicing PM data 

  1. Open the console and enter the following command:

                  'docker ps' 

       2. Once the container details is displayed enter the following command:

                  'docker exec -it ransim bash'

       3. Run the following command to start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/GenerateIntelligentSlicingPmData -i  

       4. Run the following commandto Start generate Intelligent slicing PM data: 

curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i 

       5. You can see the generated slicing pm data files in the ransim container under the folder /tmp/ransim-install.


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

<measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec"> 

    <fileHeader dnPrefix="Prefix" fileFormatVersion="32.435 V10.0" vendorName="Acme Ltd"> 

        <fileSender localDn="cucpserver1"/> 

        <measCollec beginTime="2020-12-02T05:01:37.863"/> 

    </fileHeader> 

    <measData> 

        <managedElement localDn="cucpserver1" swVersion="r0.1"/> 

        <measInfo measInfoId="measInfoIsVal"> 

            <job jobId="9327"/> 

            <granPeriod duration="PT900S" endTime="2020-12-02T05:01:37.863"/> 

            <repPeriod duration="PT900S"/> 

            <measType p="1">SM.PDUSessionSetupReq.0011-0010</measType> 

            <measType p="2">SM.PDUSessionSetupSucc.0011-0010</measType> 

            <measType p="3">SM.PDUSessionSetupFail.0</measType> 

            <measType p="4">SM.PDUSessionSetupReq.0010-1110</measType> 

            <measType p="5">SM.PDUSessionSetupSucc.0010-1110</measType> 

            <measValue measObjLdn="13999"> 

                <r p="1">2676.0</r> 

                <r p="2">1749.0</r> 

                <r p="4">3158.0</r> 

                <r p="5">1921.0</r> 

                <r p="3">1958.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="14000"> 

                <r p="1">2392.0</r> 

                <r p="2">1522.0</r> 

                <r p="4">3571.0</r> 

                <r p="5">2575.0</r> 

                <r p="3">1696.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15155"> 

                <r p="1">5279.0</r> 

                <r p="2">3300.0</r> 

                <r p="4">7237.0</r> 

                <r p="5">5187.0</r> 

                <r p="3">3655.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15174"> 

                <r p="1">5545.0</r> 

                <r p="2">3397.0</r> 

                <r p="4">7649.0</r> 

                <r p="5">5493.0</r> 

                <r p="3">3994.0</r> 

                <suspect>false</suspect> 

            </measValue> 

            <measValue measObjLdn="15175"> 

                <r p="1">5229.0</r> 

                <r p="2">3349.0</r> 

                <r p="4">8120.0</r> 

                <r p="5">5590.0</r> 

                <r p="3">4016.0</r> 

                <suspect>false</suspect> 

            </measValue> 

        </measInfo> 


    </measData> 

    <fileFooter> 

        <measCollec endTime="2020-12-02T05:01:37.863"/> 

    </fileFooter> 

</measCollecFile> 


 


  • No labels

46 Comments

  1. Yukihiro Kishimoto

    >Clone and Checkout Ran-Sim Controller
    Hi Deepika S
    I would love to try this use case.
    Please tell me the repository to get RAN-SimC.

    Yukihiro Kishimoto

    1. Deepika S

      Hi Yukihiro Kishimoto

      I will update the repository link in the wiki once the enhanced RAN-sim code is committed.

      Deepika

      1. Aniello Paolo Malinconico

        Hi Deepika S
        Still no link to clone the simulator?

        1. Deepika S

          Hi Aniello Paolo Malinconico Yukihiro Kishimoto

          I have updated the repo link

  2. Abhimanyu Garg

    Hi Deepika S,

    RanSim is running but the devices are not being synchronized with SDN-R.

    Could you suggest anything need to addon?

    Thanks,



    1. Ahila P

      Hi Abhimanyu Garg,

      Please make sure that the netconf servers (Honeycomb) is running, mention the SDN-R IP & Port in ransim's docker compose file, ensure that the certs are in place (ransim/docker/config/ransim)

      If the above said points re taken care, please check the ransim log at /opt/app/policy/servers/ransim/logs/ransim-rest.log and share the details.

      1. Abhimanyu Garg

        Hi Ahila P,

        Thanks for the reply.

        Q1: Is (Honeycomb)netconf server is mandatory to run? 

        Q2: Do we need to deploy (honeycomb)netconf? or is it part of  this current "repo-- https://gerrit.onap.org/r/integration/simulators/ran-simulator"?

        Q3: do you means to these certs - policy-keystore, jssecacerts ? which are already the part of project?

        Thanks,


        1. Abhimanyu Garg

          a) Log while start the "docker-compose up -d"

          b) While execute the  "RAN network slice simulation" 

          curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StartRanSliceSimulation' 


          c)Logs after run the RAN 

          ransim-rest.log

        2. Ahila P

          Hi Abhimanyu Garg,

          Honeycomb servers should be running to interact with SDN-R. We will share the Honeycomb setup details shortly.

          1. Abhimanyu Garg

            Hi Ahila P

            Sure, Thank you for your support.



  3. Abhimanyu Garg

    Hi Ahila P,

    Waiting for the Honeycomb setup details.


    Thanks


    1. Ahila P

      Hi Abhimanyu Garg,

      Honeycomb code is committed and the details are updated in Install Minimum Scope for Option 1 - section 9.

      Thanks,

      Ahila P.



      1. Abhimanyu Garg

        Hi Ahila P,


        Thank you, it worked and RANsim devices has mounted with SDNR by hitting the API.

        1. So auto synchronized with SDNR did not worked.
        2. And for multiple netconf server, only make changes in docker-compose file is not working.

        Could you tell any other configuration need to take care?


        Thanks


        1. Ahila P

          Hi Abhimanyu Garg,

          1→ follow this order

          a) bring up the ransim container ( using docker-compose)

          b) follow the steps under the section Steps to start/stop RAN network slice simulation 

          c) Bring up the honeycomb containers (once the honeycomb server are up, it sends mount requests to SDN-R periodically)

          2→ Do not make changes in the same docker-compose file. copy the docker folder as many servers you need ( 12 servers for slicing usecase).  Each docker-compose file is modified to change the port and it denotes a different netconf server.

          Thanks,

          Ahila P.

          1. Abhimanyu Garg

            Hi Ahila P

            Thank you for the support.

            1 - Yes I followed the same as you defined.

            2 - Yes, I copied the "hc" directory 12 time and renamed it.

            3 - In docker-compose.yml update the port.

            ports:
            - "2831:2831"            		ports:
            - "2832:2831"

            Only make changes in docker-compose.yml did not work. The periodic ping is not getting start. 

            4. I make the changes as well in this  ----  /hc/config/gnbsim.json

            "hcPort": 2831,"hcPort": 2832,

            The periodic ping get started 

            ||Sent ping message to Client ipPort:172.30.156.14:2832

            5. Receiving following exception while starting the Honeycomb server. 

            2021-04-26T08:34:53{GMT+0}+00:00|||http-nio-8081-exec-3||||INFO|||||org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:222)||Key:Content-Type , Value:[application/xml]
            2021-04-26T08:34:53{GMT+0}+00:00|||http-nio-8081-exec-3||||INFO|||||org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:222)||Key:Accept , Value:[application/xml]
            2021-04-26T08:34:54{GMT+0}+00:00|||http-nio-8081-exec-3||||ERROR|||||org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:241)||Exc in post {}
            org.springframework.web.client.HttpClientErrorException$Unauthorized: 401 Unauthorized: [no body]
            at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:105)
            at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:170)
            at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:112)
            at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63)
            at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:785)
            at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:743)
            at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:677)
            at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:586)
            at org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:229)

            6.  RANsim-Mariadb get updated with IP and Port, but In SDNR device is not Mounting.

            7. The device get Mount after hit the API - https://<172.xx.xx.xx>:<PORT>/restconf/config/network-topology:network-topology/topology/topology-netconf/node/ncserver4

            and core model and type is appearing unknow?



            Could you suggest something?

            Thanks




            1. Ahila P

              Hi Abhimanyu Garg,

              As it is related to authorization, copying the jssecacerts certificates from SDN-R container to ransim's docker folder: ran-simulator/ransim/docker/config/ransim may help.

              Thanks,

              Ahila P.

              1. Abhimanyu Garg

                Hi Ahila P,

                As I already downloaded the certs from browser SDNR(ODLUX GUI) and import into jssecacerts using  "keytool -importcert -file" .

                Still facing the same issue.

                Thanks



                1. Yukihiro Kishimoto

                  Hi Ahila P, Abhimanyu Garg

                  I have a same problem. Could you kindly show me which is the right jssecacerts on the sdnc-web?

                  ../opt/app/osaaf/local/org.onap.sdnc.trust.jks
                  ../opt/app/osaaf/local/org.onap.sdnc.jks
                  ../opt/app/osaaf/local/truststoreONAPall.jks

                2. Ahila P

                  Hi Abhimanyu Garg,

                  Can you verify once whether the username and password matches as mentioned here : gerrit.onap Code Review - integration/simulators/ran-simulator.git/blob - ransim/docker/docker-compose.yml

                  Thanks,

                  Ahila P.

                  1. Abhimanyu Garg

                    Hi Ahila P

                    Thank you, yes its working.


                    Thanks,


                    1. Aniello Paolo Malinconico

                      Hi Abhimanyu Garg, how you fixed the issue?
                      I am getting a similar error regarding certificates from RAN catalina.out log file:

                      2021_04_27_12_15_02_491 [http-nio-8081-exec-18] INFO  org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:208)- Key:Authorization  , Value:[Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==]
2021_04_27_12_15_02_491 [http-nio-8081-exec-18] INFO  org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:208)- Key:Content-Type  , Value:[application/xml]
2021_04_27_12_15_02_491 [http-nio-8081-exec-18] INFO  org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:208)- Key:Accept  , Value:[application/xml]
2021_04_27_12_15_02_505 [http-nio-8081-exec-18] ERROR org.onap.ransim.rest.client.RestClient.sendMountRequestToSdnr(RestClient.java:225)- Exc in post {}
org.springframework.web.client.ResourceAccessException: I/O error on PUT request for "https://4.9.1700.64:30267/restconf/config/network-topology:network-topology/topology/topology-netconf/node/6": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:751)
        at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:677)

                      1. Abhimanyu Garg

                        Hi Aniello Paolo Malinconico

                        1.Download the SDNR cacerts from browser.

                        2.Import the cacerts into RANsim 

                         keytool -import -noprompt -trustcacerts -alias SNDC -file <certsfile> -keystore /ransim/docker/config/ransim/jssecacerts -storepass changeit


                        Thanks


                        1. Aniello Paolo Malinconico

                          Hi Abhimanyu Garg, where exactly can I download these certs from SDNR (ODLUX) at https://xx.xx.xx.xx:30205/odlux/index.html#/login
                          I havent found any section in order to download these certs.

                          Thanks,
                          Aniello

                          1. Abhimanyu Garg

                            Hi Aniello Paolo Malinconico

                            1. Login to firefox browser 
                            2. Click on the lock icon in address url
                            3. Click on more information
                            4. Click on Security then view certificate
                            5. PEM (cert) PEM(chain) from both SDNC and intermediateCA_9

                            Thanks


                            1. Aniello Paolo Malinconico

                              Thank u so much. 

            2. murali partha

              Hi Abhimanyu Garg 

              I'm following the build procedure as mentioned by you.

              do we also need to change "netconf-ssh-binding-port": 2831" under hcsim-content/gnbsim/hc1/config/netconf.json for each HoneyComb build

              1. Abhimanyu Garg

                Hi, 

                No need to change the binding port, as this port number will be used by simulated device.

                And only once the HoneyComb need to build.

                Thanks

          2. murali partha

            Hi Ahila P ,


            when we run the Stop RAN network Slice Simulation. It throws below error,
            curl -k -X POST --header 'Content-Type: application/json' --header 'Accept: */*' 'http://localhost:8081/ransim/api/StopRanSliceSimulation'


            Is it Deprecated now, POST for Stopping.

            1. Abhimanyu Garg

              Hi, 

              Use delete method.


              Thanks

              1. murali partha

                Thanks Abhimanyu Garg 

              2. murali partha

                Hi Abhimanyu Garg 


                1) Where do we find the procedure to generate PM data in ran sim controller.

                2) How do we convert xml to a URN while performing ietf-netconf edit-config operation.

                if you could direct us to some resource, it would be helpful.


                Thanks

                1. Abhimanyu Garg

                  Hi,

                  You can check at following link

                  Core & RAN Simulators

                  Thanks


  4. Rajeev chaudhary

    Hi Abhimanyu Garg

    Ransim is running fine with  mvn clean install -P docker command  but when i try to up the docker compose ,the ransim exited with code2

    could you suggest something to try to run ransim container ?

    Thanks

    1. Abhimanyu Garg

      Hi Rajeev chaudhary,

      Make sure your RANsim mvn clean install executed successfully. 

      if yes then could you share more info or check the docker-compose logs


      Thanks

      1. Rajeev chaudhary

        ransim_docker-compose_logs

        Thanks 

        Abhi.

  5. Vishal Varvate

    Hi Ahila P,


    Can you please confirm on whether the current RANSimulator implementation comply with 3GPP TS 28.541 or not ?

    1. Swaminathan Seetharaman

      This is a very generic and ambiguous question. TS 28.541 has several aspects in it w.r.to the RAN. Which specific aspects are you interested in (e.g., Network Slicing alone)? Also, which release/version of TS 28.541 are you looking at?

      1. Vishal Varvate

        Hi,
        The release is 3GPP TS 28.541 V17.1.0 (2020-12) and aspects we are looking for is Network Slicing alone.

  6. Swaminathan Seetharaman

    1 basic question: When asking about RAN-Sim's compliance to TS 28.541 for Slicing, can you pl. clarify which specific aspects are you looking at? I am asking this because, many of the slice-related attributes specified in TS 28.541 cannot be directly sent as-is (or) are not relevant for RAN-Sim.

    ONAP implementation of Network Slicing

    In general, we are referring to Rel. 16 of 3GPP specs only at present for Network Slicing implementation in ONAP. Even in Rel.16 there are some aspects which aren't yet considered/implemented in ONAP.

    When Rel. 17 is stable, we will consider it for possible alignment. So this also applies to TS 28.541. 

    FYI, there are quite some changes in TS 28.541 Rel. 17 w.r.to Slicing info models (e.g., Transport EP, Slice Profile, etc.), and there are still many open points in the specs which require to be addressed first.

  7. Abhimanyu Garg

    Hi Swaminathan Seetharaman

    Can we validate the communication(fronthual, midhaul, backhual),  configuration, UE integration aspect between RU-DU and CU?

    Thanks


  8. Abhimanyu Garg

    Hi Ahila P,


    Can you guide on the following error ?


    [WebSocketSimpleContainer@1449426109-22] ERROR com.wipro.www.ConfigurationHandler - Exception occurred while parsing Unrecognized field "serverId" (class com.wipro.www.websocket.models.NearRTRIC), not marked as ignorable (7 known properties: "locationName", "nearRTRICgNBId", "managedBy", "idNearRTRIC", "GNBCUUPFunction", "GNBDUFunction", "attributes"])


    Thanks

  9. Goutam Roy

    Hi All,

    How can I integrate RAN-SIM with ONAP VES-Collector(DCAE)?


    With Regards

    Goutam Roy.


  10. Niranjana Y

    Hi Goutam Roy,

    Did you mean netconf server? RAN-Sim doesn't directly connect with VES. Please do send the error logs

  11. Kamlesh Kumar

    Hi Niranjana Y ,@all

    I have integrated RAN-Sim master with SDNR and DCAE  

    RAN-SIM to DCAE looks fine and I am getting CM/PM notification in DCAE.

    But I am getting Exception in SDNR and Honeycomb logs after it is mounted on SDNR 


    Note: We are using enodeB  and I have used below URL  for ran-sim controller and Honeycomb

    Installation & setup of the RAN-Simulator and PCI-Handler micro-service


    Honeycomb Logs

    =============


    2021-09-07 12:09:43.218 UTC [netconf-netty-1] WARN  o.o.n.i.u.DeserializerExceptionHandler - An exception occurred during message handling
io.netty.handler.codec.DecoderException: java.lang.NullPointerException
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.finishPeerRead0(LocalChannel.java:446) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.access$300(LocalChannel.java:50) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel$5.run(LocalChannel.java:400) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]
Caused by: java.lang.NullPointerException: null
    at org.openexi.sax.ReaderSupport.doAttribute(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.doElement(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.opendaylight.netconf.nettyutil.handler.NetconfEXIToMessageDecoder.decode(NetconfEXIToMessageDecoder.java:96) ~[netconf-netty-util-1.4.2.jar:na]
    at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    ... 21 common frames omitted
2021-09-07 12:09:48.622 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore
2021-09-07 12:09:58.623 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore




    SDNR Logs:

    ======================

    2021-09-07 12:09:43.218 UTC [netconf-netty-1] WARN  o.o.n.i.u.DeserializerExceptionHandler - An exception occurred during message handling
io.netty.handler.codec.DecoderException: java.lang.NullPointerException
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.local.LocalChannel.finishPeerRead0(LocalChannel.java:446) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.local.LocalChannel.access$300(LocalChannel.java:50) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.local.LocalChannel$5.run(LocalChannel.java:400) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-common-4.1.22.Final.jar:4.1.22.Final]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]
Caused by: java.lang.NullPointerException: null
	at org.openexi.sax.ReaderSupport.doAttribute(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
	at org.openexi.sax.EXIReader.doElement(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
	at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
	at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
	at org.opendaylight.netconf.nettyutil.handler.NetconfEXIToMessageDecoder.decode(NetconfEXIToMessageDecoder.java:96) ~[netconf-netty-util-1.4.2.jar:na]
	at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
	... 21 common frames omitted
2021-09-07 12:09:48.622 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore
2021-09-07 12:09:58.623 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore



2021-09-07 12:09:43.218 UTC [netconf-netty-1] WARN  o.o.n.i.u.DeserializerExceptionHandler - An exception occurred during message handling
io.netty.handler.codec.DecoderException: java.lang.NullPointerException
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.finishPeerRead0(LocalChannel.java:446) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.access$300(LocalChannel.java:50) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel$5.run(LocalChannel.java:400) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]
Caused by: java.lang.NullPointerException: null
    at org.openexi.sax.ReaderSupport.doAttribute(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.doElement(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.opendaylight.netconf.nettyutil.handler.NetconfEXIToMessageDecoder.decode(NetconfEXIToMessageDecoder.java:96) ~[netconf-netty-util-1.4.2.jar:na]
    at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    ... 21 common frames omitted
2021-09-07 12:09:48.622 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore
2021-09-07 12:09:58.623 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore

2021-09-07 12:09:43.218 UTC [netconf-netty-1] WARN  o.o.n.i.u.DeserializerExceptionHandler - An exception occurred during message handling
io.netty.handler.codec.DecoderException: java.lang.NullPointerException
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:459) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:265) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1414) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:945) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.finishPeerRead0(LocalChannel.java:446) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel.access$300(LocalChannel.java:50) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.local.LocalChannel$5.run(LocalChannel.java:400) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463) [netty-transport-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:886) [netty-common-4.1.22.Final.jar:4.1.22.Final]
    at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]
Caused by: java.lang.NullPointerException: null
    at org.openexi.sax.ReaderSupport.doAttribute(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.doElement(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.openexi.sax.EXIReader.parse(Unknown Source) ~[nagasena-0000.0002.0062.0.jar:na]
    at org.opendaylight.netconf.nettyutil.handler.NetconfEXIToMessageDecoder.decode(NetconfEXIToMessageDecoder.java:96) ~[netconf-netty-util-1.4.2.jar:na]
    at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:489) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:428) [netty-codec-4.1.22.Final.jar:4.1.22.Final]
    ... 21 common frames omitted
2021-09-07 12:09:48.622 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore
2021-09-07 12:09:58.623 UTC [WebSocketSimpleContainer@815992954-4536] DEBUG o.o.r.w.c.RansimClientWebSocket - Periodic ping message.... ignore


    Please find SDNR karaf logs 



  12. amol jadhav

    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

  13. avinash sarraff

    After executing command mvn clean install -P docker, the build is getting stuck at below line. Any idea or help ?


    [INFO] DOCKER> Executing: /tmp/apt-key-gpghome.kierdlwEK1/gpg.1.sh --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8