1. RAN-Sim Controller

Steps to build the RAN-Sim Controller setup:

1. Clone and Checkout Ran-Sim Controller(use Dublin branch)

git clone https://github.com/onap-oof-pci-poc/ran-sim.git

cd cd ran-sim/ransim/

checkout latest master branch.

2. Copy ‘m2_settings.xml’ from ‘<YOURFOLDER>/ransim/’ to <HOME>/.m2/ folder as settings.xml file after updating environment specific configurations.

...

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

3. Open the console terminal and navigate to the '<YOURFOLDER>/ransim/ransimctrlr'

4. Run the following command in the terminal

mvn clean install

5. The following capabilities can be modified in the 'ransim.properties' file based on user capabilities and configurations.

...

Maximum number of machines available(use default value present in the file).

e) GridSize: (Applicable only for HONEYCOMB representation)

The number of cells that can be accommodated along one side of the cluster for an auto-generated layout.

...

g) sdnrServerIp:

SDNR server IP address (change the value Neglect(Refer point 5 to update SDNR details).

h) sdnrServerPort:

SDNR server port number (change the value Neglect(Refer point 5 to update SDNR details).

i) sdnrServerUserid:

SDNR server user ID (change the valueNegelct (Refer point 5 to update SDNR details).

j) sdnrServerPassword:

SDNR server password (change the valueNegelct (Refer point 5 to update SDNR details).

k) maxPciValueAllowed:

maximum value of the physical cell Id. (Default is 503).

l)dumpFileName

Location of the dumpfile to load the topology.

The dump file is loaded from '<YOURFOLDER>/ransim/docker/config6. To form the cluster from dump file (random simulation) update the cell details in 'SIM_Ran_config.json'. A sample file is also included.

File directory:

<YOURFOLDER>/ransim/ransimctrlr/packages/base/src/files/install/servers/ransim/bin/SIM_Ran_config.json

7. Add an entry into /etc/hosts file for ransimsvr from wherever you are accessing the Ransim Web UI

<IP where ransim controller is running> ransimsvr

8. After successful build navigate to '<YOURFOLDER>/ransim/docker' directory.

9. Run the following three commands in the terminal:

'mvn prepare-package'

'docker build -t onap/ransim ransim-docker'

'docker-compose up'

Note: Use docker compose version 1.6.0 or above.

Once the docker and mariadb is built simillar commands as shown in the image will be displayed.

Image Removed

10. Access the GUI using the following url in the web browser:

‘http://<yourIP>:8081/ransimui/index.html’

Image Removed

11. Access the swagger ui using the following url:

‘http://<yourIP>:8081/ransim/api/swagger-ui.html’

Image Removed

12. Try the following url in Websocket client extension in the web browser to verify the connectivity:

dump file - 'sample.json' contains deatils of 1000 cells.

For the controller to access the dump file from the the above location use the path - /tmp/ransim-install/config/sample.json

5. The SDNR details can be updated in the file '<YOURFOLDER>/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}

6. Run the following command in the terminal

mvn clean install

7. After successful build navigate to '<YOURFOLDER>/ransim/docker' directory.

8. Run the following three commands in the terminal:

'mvn prepare-package'

'docker build -t onap/ransim-demo ransim-docker'

'docker-compose up'

Note: Use docker compose version 1.6.0 or above.

Once the ransim and mariadb containers are started, you can see logs similar to below image

9. Access the GUI using the following url in the web browser:

‘http://<yourIP>:8081/ransimui/index.html

10. Access the swagger ui using the following url:

‘http ‘ws://<yourIP>:8081/ransim/RansimAgent/hai’

Steps to check the RAN-Sim Controller logs

1. Open the console and enter the following command:

api/swagger-ui.html

11. Try the following url in Websocket client extension in the web browser to verify the connectivity:

‘ws://<yourIP>:8081/ransim/RansimAgent/hai’

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 <CONTAINER ID> ransim bash

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

...

'mysql --user=root --password=secret --host=127.0.0.1 --port=43306 3306 ransim_db'

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

2. RAN-Sim: Netconf-server(s) (agents) - Extended Honeycomb

This has the following steps:

...

This repository has the code we developed.

1. Clone(use Dublin branch) and checkout the latest:

git clone https://github.com/onap-oof-pci-poc/ran-sim.git https://github.com/onap-oof-pci-poc/ran-sim.git

git checkout masterDublin

cd hcsim-content/

...

git clone https://github.com/onap-oof-pci-poc/ran-sim/Netconf-Agents/hc_50000

cd Netconf-Agents/hc_50000

...

./honeycomb

Check the honeycomb.log in the below folder

<Your_Folder>/hc_50001/var/log/honeycomb/

tail -f honeycomb.log

Successful start yield below log entries,

For multiple instance,

Copy the EnodebSimSetup.py, start.sh and stop.sh from <Your_Folder>/Netconf-Agents/ folder to the folder in which hc_50000 is copied,

Run EnodebSimSetup.py with the number of instances required.
./EnodebSimSetup.py 24 (for 24 instances)
Then run start.sh, which will start all the honeycomb servers in the folder(in this case all 24 agents will be started)
Use stop.sh, to stop all the netconf servers.

Use netstat command to verify all the honeycomb servers are started.

netstat -navp | grep 500

Check the honeycomb.log in the below folder

<Your_Folder>/hc_50001/var/log/honeycomb/

tail -f honeycomb.log

Successful start yield below log entries,

2018-10-16 14:02: 2018-10-16 14:02:19.975 IST [main] INFO i.f.h.i.d.i.InitializerRegistryAdapter - Honeycomb initialized

...

This should show the complete topology dumped or simulated from Ransim Controller.

editget-config:

<rpc

(with filter):

<radio-access

xmlnssource>
<filter xmlns:ns0="urn:onfietf:otccparams:wireless:yang:radio-access"> <fapxml:ns:netconf:base:1.0" ns0:type="subtree">
<radio-access xmlns="org:onap:ccsdk:features:sdnr:northbound:oofpcipoc">
<fap-service>
<alias>Chn0001</alias>
</fap-service>
</radio-access>
<alias>60</alias>

<x-0005b9-lte>

<pnf-name>ncserver1001</pnf-name>

<phy-cell-id-in-use>40</phy-cell-id-in-use>

</x-0005b9-lte>

</fap-service>

<fap-service>

<x-0005b9-lte>

<pnf-name>ncserver1001</pnf-name>

<phy-cell-id-in-use>60</phy-cell-id-in-use>

</x-0005b9-lte>

</fap-service>

</radio-access>

</config>

<default-operation>merge</default-operation>

</edit-config>

</rpc>

]]>]]>

</target>

</commit>

</rpc>

]]>]]>

Successful execution of this command should update the pcid value to 60 and the same should be viewed from Ransim GUI.

</filter>
</get-config>
</rpc>
]]>]]>

edit-config:

<rpc

xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">

<edit-config>

</target>

<radio-access

xmlns="urn:onf:otcc:wireless:yang:radio-access">

<fap-service>

<x-0005b9-lte>

<pnf-name>ncserver1001</pnf-name>

<phy-cell-id-in-use>40</phy-cell-id-in-use>

</x-0005b9-lte>

</fap-service>

<fap-service>

<x-0005b9-lte>

<pnf-name>ncserver1001</pnf-name>

<phy-cell-id-in-use>60</phy-cell-id-in-use>

</x-0005b9-lte>

</fap-service>

</radio-access>

</config>

<default-operation>merge</default-operation>

</edit-config>

</rpc>

]]>]]>

</target>

</commit>

</rpc>

]]>]]>

Successful execution of this command should update the pcid value to 60 and the same should be viewed from Ransim GUI.

Edit or delete operation on different cells in the topology of the agent will notify the Ransim Controller which will update GUI & DB to be in Sync.

Notify Cell Modification tested with Netconf-console

Pre-Requisites:

ncclient must be present. If not, run pip install ncclient
pip install netconf-console

Command to establish session with device:

netconf-console --host netconf-agent-ip --port netconf-agent-port --raw

eg., netconf-console --host 10.143.125.163 --port 50000 --raw

Session will be established with an interactive shell. Run the following command to create subscription:

create-subscription -x honeycomb

For testing,

Select "Modify" menu by right clicking any cell in Ransim-GUI.
Change the pcid value and click modify. Modified Successfully message displayed.
Verify the notification received as below in netconf-console shell. Any issue check honeycomb log.
hc_50000/var/log/honeycomb/honeycomb.log

Image AddedEdit or delete operation on different cells in the topology of the agent will notify the Ransim Controller which will update GUI & DB to be in Sync.

Additional information

To run each instance of HoneyComb it requires ~353 MB of memory. Still we are working on optimizing the simulator configuration to run only required processes for ONAP setup.

3. PCI-Micro service

Cloning the chart repository

The kubernetes chart can be cloned from https://github.com/onap-oof-pci-poc/pcihms.git

Code Block

language	bash
title	git clone

    git clone https://github.com/onap-oof-pci-poc/pcihms.git

Building the postgres-init docker image

Naviagate to postgres-scripts folder and run the following command to build the docker image

Code Block

language	bash
title	git clone

    cd pcihms/postgres_scripts
    docker build -t postgres-init:1.0 .

Building the Microservice

Navigate to the project's source code (pcihms/pci-handler) and run the following commands

Code Block

language	bash
title	git clone

    cd pcihms/pci-handler
    mvn clean install
    docker build -t pci-handler:1.0 .

Generate apikeys from DMaaP

4 apikey/secret pair should generated from DMaaP(one for management of topics, one for PCI-Microservice, one for Policy and one for SDNR). These apikeys must be set as configuration parameter in PCI-Microservice.

Setting Configuration parameters

The environment variables for the microservice must be set in configMap file in th charts. The following parameters must be set in the configMap.yaml before deploying the microservice. The config file can be found under pcihms/charts/pci-handler/templates/configMap.yaml.

...

Note : The dns will be <service name>: <namespace>

Build the helm chart

Navigate to the cloned repository and run the following command

Code Block

language	bash
title	build hem chart

    cd pcihms/charts    
    make all

Deploying the microservice

DMaaP, Policy, OOF and SDNR must be running before starting the PCI-Microservice. To deploy the microservice, Run the following command

...

Space shortcuts

Page tree

Versions Compared

Old Version 22

New Version Current

Key

1. RAN-Sim Controller

3. PCI-Micro service

Cloning the chart repository

Building the postgres-init docker image

Building the Microservice

Generate apikeys from DMaaP

Setting Configuration parameters

Build the helm chart

Deploying the microservice

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 22

New Version Current

Key

1. RAN-Sim Controller

3. PCI-Micro service

Cloning the chart repository

Building the postgres-init docker image

Building the Microservice

Generate apikeys from DMaaP

Setting Configuration parameters

Build the helm chart

Deploying the microservice