- Created by Alex Stancu, last modified on Dec 06, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 3 Next »
Table of Contents
Sub pages
The O1 Simulator offers support for demonstrating the O-RAN-SC E-Release Network Slicing use case proposed by Radisys.
Features
- Support for o-ran-du-hello-world.yang model developed by the OAM project, containing slicing information
- Support for VES PM stndDefined messages
- Support for VES Subscription and PM Job creation
Usage
Details about how to start a simulated O-DU and how to use the Network Slicing use case features are below. A video demonstrating these capabilities was presented in this meeting. The recording is available there.
Starting
A simulated O-DU can be started via docker-compose. The following .env and docker-compose.yaml files can be used to start such a simulator.
.env
NEXUS3_DOCKER_REPO=nexus3.o-ran-sc.org:10004/o-ran-sc/ NTS_BUILD_VERSION=1.4.3 CU_PREFIX=111 DU_PREFIX=${CU_PREFIX}1 IPv6_ENABLED=true SSH_CONNECTIONS=1 TLS_CONNECTIONS=0 #NTS_HOST_IP =10.20.11.121 NTS_HOST_IP=2001:db8:1::1 NTS_HOST_BASE_PORT=50000 NTS_HOST_NETCONF_SSH_BASE_PORT=50000 NTS_HOST_NETCONF_TLS_BASE_PORT=52000 NTS_HOST_TRANSFER_FTP_BASE_PORT=54000 NTS_HOST_TRANSFER_SFTP_BASE_PORT=56000 NTS_NF_MOUNT_POINT_ADDRESSING_METHOD=docker-mapping NTS_NF_STANDALONE_START_FEATURES="datastore-populate ves-heartbeat ves-file-ready ves-pnf-registration netconf-call-home web-cut-through" SDN_CONTROLLER_PROTOCOL=http SDN_CONTROLLER_IP=2001:db8:1:50::23 SDN_CONTROLLER_PORT=8181 SDN_CONTROLLER_CALLHOME_PORT=4335 SDN_CONTROLLER_CALLHOME_IP=2001:db8:1:50::23 SDN_CONTROLLER_USERNAME=admin SDN_CONTROLLER_PASSWORD=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U VES_COMMON_HEADER_VERSION=7.2.1 VES_ENDPOINT_PROTOCOL=https VES_ENDPOINT_IP=2001:db8:1:50::27 VES_ENDPOINT_PORT=8443 VES_ENDPOINT_AUTH_METHOD=basic-auth VES_ENDPOINT_USERNAME=sample1 VES_ENDPOINT_PASSWORD=sample1
docker-compose.yaml
version: '3.8' x-common_env: &common_env IPv6_ENABLED: ${IPv6_ENABLED} SSH_CONNECTIONS: ${SSH_CONNECTIONS} TLS_CONNECTIONS: ${TLS_CONNECTIONS} NTS_NF_MOUNT_POINT_ADDRESSING_METHOD: ${NTS_NF_MOUNT_POINT_ADDRESSING_METHOD} NTS_HOST_IP: ${NTS_HOST_IP} NTS_HOST_BASE_PORT: ${NTS_HOST_BASE_PORT} NTS_HOST_NETCONF_SSH_BASE_PORT: ${NTS_HOST_NETCONF_SSH_BASE_PORT} NTS_HOST_NETCONF_TLS_BASE_PORT: ${NTS_HOST_NETCONF_TLS_BASE_PORT} NTS_HOST_TRANSFER_FTP_BASE_PORT: ${NTS_HOST_TRANSFER_FTP_BASE_PORT} NTS_HOST_TRANSFER_SFTP_BASE_PORT: ${NTS_HOST_TRANSFER_SFTP_BASE_PORT} SDN_CONTROLLER_PROTOCOL: ${SDN_CONTROLLER_PROTOCOL} SDN_CONTROLLER_IP: ${SDN_CONTROLLER_IP} SDN_CONTROLLER_PORT: ${SDN_CONTROLLER_PORT} SDN_CONTROLLER_CALLHOME_IP: ${SDN_CONTROLLER_CALLHOME_IP} SDN_CONTROLLER_CALLHOME_PORT: ${SDN_CONTROLLER_CALLHOME_PORT} SDN_CONTROLLER_USERNAME: ${SDN_CONTROLLER_USERNAME} SDN_CONTROLLER_PASSWORD: ${SDN_CONTROLLER_PASSWORD} VES_COMMON_HEADER_VERSION: ${VES_COMMON_HEADER_VERSION} VES_ENDPOINT_PROTOCOL: ${VES_ENDPOINT_PROTOCOL} VES_ENDPOINT_IP: ${VES_ENDPOINT_IP} VES_ENDPOINT_PORT: ${VES_ENDPOINT_PORT} VES_ENDPOINT_AUTH_METHOD: ${VES_ENDPOINT_AUTH_METHOD} VES_ENDPOINT_USERNAME: ${VES_ENDPOINT_USERNAME} VES_ENDPOINT_PASSWORD: ${VES_ENDPOINT_PASSWORD} x-du_env: &du_env NTS_NF_STANDALONE_START_FEATURES: "datastore-populate ves-heartbeat ves-file-ready ves-pnf-registration web-cut-through" x-nf: &common_nf stop_grace_period: 5m cap_add: - SYS_ADMIN - SYS_PTRACE services: ntsim-ng-o-ran-du-1: <<: *common_nf image: "${NEXUS3_DOCKER_REPO}nts-ng-o-ran-du:${NTS_BUILD_VERSION}" container_name: ntsim-ng-o-ran-du-${DU_PREFIX} hostname: O-DU-${DU_PREFIX} environment: <<: *common_env <<: *du_env networks: default: external: name: oam
Please adjust the values in the docker-compose.yaml according to your needs: e.g. specify the correct VES Endpoint IP address, SDN Controller IP address, rename or remove the oam network, as applicable to your specific host.
Starting can be done via:
docker-compose up -d
This will start a docker container containing the o-ran-sc-du-hello-world YANG model. The user can then start a NETCONF session to this device (default is port 830 and the IP address can be the one of the docker container).
Configure VES details
After the simulated O-DU is up and running, the VES subscription details can be configured. These are part of the o-ran-sc-du-hello-world model. An example edit-config NETCONF operation that configures VES endpoint details:
PM Job creation
Generating VES PM stndDefined events can be done by adding PM Job entries. An example edit-config NETCONF operation that adds a new PM job:
- No labels