OAM Operation and Maintenance¶
OAM Operation and Maintenance Overview¶
The O-RAN SC OAM project provides administrative and operator functions for O-RAN components, such as Near-Realtime-RAN-Intelligent-Controller, O-RAN Centralized Unit, O-RAN Distributed Unit and O-RAN Radio Unit.
The project follows the specifications for the O1 interface as provided by O-RAN Working Group 1 (new 10).
The O-RAN-SC OAM project adds features and functions to the OpenDaylight-based ONAP controller ‘CCSDK/SDNC’. It is built on the Common Controller Framework to control and to manage O-RAN ManagedElements and O-RAN ManagedFunctions.
SDN-R in ONAP¶
Project Resources¶
The project uses the following Linux Foundation resources:
- The source code is maintained in this Gerrit:
- The build (CI) jobs are in this Jenkins:
- Issues are tracked in this Jira:
- Project information is available in this Wiki:
https://wiki.o-ran-sc.org/display/OAM/Operations+and+Maintenance
Scope¶
According to the O-RAN-OAM-Architecture document all ManagedElements (ME) (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) implement the O1-interface.
The O-RAN-OAM-interface specification defines
a NetConf-Server for Configuration Management (CM) and
a http-client for Fault Management (FM), Performance Management (PM) and other events on each Management-Service-Provider (MnS-Provider) running on the ManagedElement.
THe O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM documents. In addition it provides a lightweight MnS-Consumer for development and module test purposes. The assumption is that the projects for the ManagedElements can concentrate on the more important user-plane.
Each project requires its own OAM repository to address the specific needs of the ManagedFunction.
The following O-RAN specifications are considered during implementations:
Workgroup |
Specification |
Version |
|---|---|---|
WG1 - Use Cases and Overall Architecture |
O-RAN Architecture Description |
3.0 - November 2020 |
O-RAN Operations and Maintenance Architecture |
4.0 - November 2020 |
|
O-RAN Operations and Maintenance Interface |
4.0 - November 2020 |
|
O-RAN Information Model and Data Models Specification |
November 2020 |
|
WG4 - The Open Fronthaul Interfaces |
O-RAN Open Fronthaul Conformance Test Specification |
2.00 - November 2020 |
O-RAN Management Plane Specification |
5.0 - November 2020 |
|
O-RAN Management Plane Specification - YANG Models |
5.0 - November 2020 |
|
TIFG - Test & Integration Focus Group |
O-RAN End-to-End System Testing Framework Specification |
1.0 - July 2020 |
OAM Controller Configuration and Deployment¶
This documents the configuration and deployment of the O-RAN SC O1 Controller as part of the SMO implementations by the ONAP project.
The SMO deployment is described in the O-RAN-SC wiki
The procedure provides: * ONAP-DCAE * ONAP-DMaaP * ONAP-SDNC (single node, SMO functionality)
but also automatic deployment of cloud native network functions and Automated tests of the deployment.
OAM Developer Guide¶
This document provides a quickstart for developers of the O-RAN SC OAM components.
All information of development are documented in corresponding O-RAN-SC wiki: https://wiki.o-ran-sc.org/display/OAM/Operations+and+Maintenance
OAM User Guide¶
This document provides a quickstart for users of the O-RAN SC OAM web application.
General functionality¶
The following functionality is common to all applications.
Table data export¶
Every table can export its data via the ‘︙’ button. The data, which gets exported is the currently viewed data in the table. As the default pagination is set to 10, only the first 10 rows or filtered rows will be exported. To increase the number of exported rows, change the pagination.
The behavior of the export can vary based on the browser:
Some browsers allow you to save the file with the predefined name export.csv. In case your browser does not offer this function please use the ‘Save as…’ option and define the filename with extension csv.
Some browsers save the file automatically with the alphanumeric name but without an extension. In such a case navigate to the downloaded file location and rename the file. The extension (csv) must be appended to the name. The result should look like ‘export_file.csv’.
Table filters¶
The following filters are supported by all tables based on the data type of the column.
Data type |
Possible Filter |
Example |
|---|---|---|
Text |
Any characters or numbers, matches exactly unless a * is used. The * acts as a wildcard and can be used for contains, ends with and begins with queries. |
Test, Tes*, *t |
Numeric |
< or <= or > or >= or exact number |
>5000, 20, <=82 |
Boolean |
None (no filter set), true or false |
true, false |
UX Applications¶
This page shortly describes the different web applications integrated into the ODLUX framework.
Connect¶
The ‘Connect’ application on OpenDaylight provides up-to-date connectivity information about the wireless devices in the network. It automatically displays new Network Elements and their connection status. Usually, the Network Elements mount themselves. If necessary, they can be mounted manually by right-clicking on the element and selecting the ‘mount’ action. For better understanding of alarms and status, a connection status log lists all the connection status changes of OpenDaylight mount points.
Views¶
The graphical user interface is divided into two sections.
Network Elements¶
Network Elements are physical network functions (PNFs). A table view shows all configured and connected NetConf Servers of the SDN-R cluster. This view also allows to manually configure/mount a device via the ‘+’ button. The SDN controller will start connecting to the NetConf server.
Network Elements can be marked as ‘required’. If an element is required, it will stay available even if disconnected. If an element is not required, it will be deleted once disconnected.
By right-clicking on an element, an action menu opens. The menu allows to mount, unmount, view the details, edit and remove the element. Additionally, it links to several applications like Fault and Configure, which will be filtered to display information relevant to the selected element.
Connection Status Log¶
The log lists the connection status changes between SDN Controller and NetConf servers (devices).
Fault Management¶
To operate a network, it is important to get an overview about the currently raised alarms. The application offers basic fault management of devices supporting ONF-TR-532. The alarms are classified according to the severity level (warning, minor, major, critical).
Views¶
The graphical user interface is separated into three views.
Current Problem List¶
Lists all current active faults in the network. In addition, it also lists alarms sent by the SDN controller itself, which detects connection losses to the NetConf server (connectionLossOAM) or to a device via a mediator to a device (connectionLossNeOAM).
Alarm Notifications¶
As long as the view is open, all alarm notifications received by the SDN Controller are listed. Please note that refreshing the view will start the collection again. Previous alarm notification can be viewed in the alarm log.
Implementation¶
The application has two parts. While the server is listening for NetConf notifications to store them in the database, the client retrieves the information from the database and displays them in a table.
The server synchronizes with the current alarm lists of the devices. Based on raised and cleared notifications, the current alarm status of the network is calculated. The current alarms are stored in a database. In addition, all Problem Notifications received by the SDN controller are stored. There is no logic implemented on the client side.
An alarm status bar in the header of the web application informs the operator about the health status of the network.
The ODLUX web application uses web sockets to update the graphical user interface of the Alarm Notifications (devices) and Connection Status Notifications in real-time.
Contents
Maintenance¶
The ‘Maintenance’ application on OpenDaylight provides information about planned maintenances of Network Elements, currently or in the future. Users can manage devices to set the maintenance mode so that no unnecessary alarms are created. When the device is in maintenance mode, alarms are not forwarded to DCAE. As soon as the maintenance is finished, the alarms will start flowing again.
The ‘active’ field in the table shows if the Network Element is currently in maintenance mode or not. If it is ‘active’ it means the Network Element is currently undergoing maintenance, if ‘not active’ it means maintenance might have been set for a future date or is already completed.
Users can disable the maintenance mode or change its start and end dates by using the available options in the actions column.
Contents
Configuration¶
The application shows the actual values of all attributes of the ONF-TR-532 for a selected physical network function (PNF). Each view of a functional element is divided into capabilities, configuration, status, current problem, current performance and history performance information according to TR-532.
A separate window is available for modifying the configuration. All changes made are sent to the device in a single NetConf bulk request. The operator is notified about successfully configuring the device.
Implementation¶
The application is implemented as ODLUX web application using the RestConf northbound interface of the SDN controller. The key frameworks are: Typescript, React and material-ui.
Connection status information is updated automatically using a web socket for notifications from OpenDaylight to the browser.
Contents
Performance¶
Performance Monitoring values measured by the devices are necessary to analyze and optimize the network. Therefore the application automatically retrieves all historical performance values from the devices and stores them in a database. The client retrieves the values from the database and displays them in a graphical user interface.
Performance history values¶
After selecting a connected PNF supporting ONF-TR-532 and a physical interface, the application collects the received and centralized stored performance values for this interface.
The values are visualized using two views: a line chart and a table, with the chart always shown first. To switch between them, toggle buttons can be used. The chart view offers a filter to quickly limit the shown values. To keep both views in sync, the filters of the chart and the table are connected. If one view is filtered, the other one gets updated in the background.
Contents
Inventory¶
The application offers basic inventory management of devices supporting ONF-TR-512 and ietf-hardware.
The view displays the inventory data of the network element – for example, serial-numbers and part-numbers according to the containment of the equipment.
Inventory Export:¶
The ‘︙’ button in the upper right corner of the table allows exporting the inventory data as a CSV file.
Only the currently viewed table data is exported. As the default pagination is set to 10, only the first 10 rows or filtered rows would be exported. To increase the number of exported rows change the pagination.
The behavior of the export can vary based on different browsers:
Some browsers allow you to save the file with the predefined name export.csv. In case your browser does not offer this function please use the ‘Save as…’ option and define the filename with extension csv.
Some browsers save the file automatically with the alphanumeric name but without an extension. In such a case navigate to the downloaded file location and rename the file. The extension (csv) must be appended to the name. The result should look like export_file.csv.
Contents
Mediator¶
A ‘Mediator’ provides an external - to the physical network function - OAM interface.
Some physical network function manufactures use the generic mediator framework. Such mediators offer a management API to control mediator function.
New mediator servers can be added via the ‘+’ button. Afterward, a server can be selected to view all available mediator instances.
A mediator instance can be started, stopped and deleted using the available actions. Additionally, its details can be viewed. The ‘+’ button allows the user to add a new instance. During the creation, at least one ‘ODL auto connect’ configuration must be added.
Deployment¶
OAM Components are deployed in different context and for different use cases. Please see the Kubernetes deployment within the it/deb repository and its description in O-RAN-SC wiki.
The main OAM Components are:
OAM-Controller from ONAP SDN-R using OpenDaylight for O1-NETCONF and OpenFronthaul-Management-NETCONF support.
VES-Collector from ONAP DCAE for processing O1-VES messages.
Message-router from ONAP DMaaP using Kafka
Identity service from Keycloak for AAA support.
This page focus on a lightweight deployment using docker-compose on an Ubuntu system for experience with SMO OAM Components and/or development.
Prerequisites¶
The following command are used to verify your system and it installed software package. In general new version then display here should be fine.:
$ cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Ubuntu 20.04.2 LTS"
$ docker --version
Docker version 20.10.7, build 20.10.7-0ubuntu1~20.04.2
$ docker-compose version
docker-compose version 1.29.1, build c34c88b2
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019
$ git --version
git version 2.25.1
The communication between the components bases on domain-names. For a lightweight deployment on a single laptop or virtual-machine the /etc/hosts file should be modified as a simple DNS.
Please modify the /etc/hosts of your system.
<your-system>: is the hostname of the system, where the browser is started
<deployment-system-ipv4>: is the IP address of the system where the solution will be deployed
For development purposes <your-system> and <deployment-system> may reference the same system.:
$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 <your-system>
<deployment-system-ipv4> sdnc-web <your-system>
<deployment-system-ipv4> identity <your-system>
Docker Enable IPv6¶
The O-RAN Alliance specifications target the support of IPv6. To support IPv6 by docker the docker configuration must be modified.
Please see: https://docs.docker.com/config/daemon/ipv6/
Edit /etc/docker/daemon.json, set the ipv6 key to true and the fixed-cidr-v6 key to your IPv6 subnet. In this example we are setting it to 2001:db8:1::/64.
{
"dns": ["1.1.1.1"],
"registry-mirrors": [
"https://nexus3.o-ran-sc.org:10002",
"https://nexus3.onap.org:10001"
],
"log-driver": "json-file",
"log-opts": {
"max-size": "10m",
"max-file": "3"
},
"ipv6": true,
"fixed-cidr-v6": "2001:db8:1::/64"
}
Reload the Docker configuration file.
$ systemctl reload docker
It is beneficial (but not mandatory) adding the following line add the end of your ~/.bashrc file. I will suppress warnings when python script do not verify self signed certificates for HTTPS communication.:
export PYTHONWARNINGS="ignore:Unverified HTTPS request"
Please ensure that you download and copy the required 3GPP OpenAPIs for VES-stndDefined message validation into the folder ‘./solution/operation-and-maintenance/smo/oam/ves-collector/externalRepo’.
Please follow the instructions in ./solution/operation-and-maintenance/smo/oam/ves-collector/externalRepo/3gpp/rep/sa5/MnS/blob/Rel16/OpenAPI/README.md.
The following tree shows the successfully tested folder structure. It combines different versions of the schemas (‘Rel16’ and ‘SA88-Rel16’) using 3GPP branch names.:
$ tree solution/operation-and-maintenance/smo/oam/ves-collector/externalRepo/
solution/operation-and-maintenance/smo/oam/ves-collector/externalRepo/
├── 3gpp
│ └── rep
│ └── sa5
│ └── MnS
│ └── blob
│ ├── Rel16
│ │ └── OpenAPI
│ │ ├── README.md
│ │ ├── TS28532_FaultMnS.yaml
│ │ ├── TS28532_FileDataReportingMnS.yaml
│ │ ├── TS28532_HeartbeatNtf.yaml
│ │ ├── TS28532_PerfMnS.yaml
│ │ ├── TS28532_ProvMnS.yaml
│ │ ├── TS28532_StreamingDataMnS.yaml
│ │ ├── TS28536_CoslaNrm.yaml
│ │ ├── TS28541_5GcNrm.yaml
│ │ ├── TS28541_NrNrm.yaml
│ │ ├── TS28541_SliceNrm.yaml
│ │ ├── TS28550_PerfMeasJobCtrlMnS.yaml
│ │ ├── TS28623_ComDefs.yaml
│ │ ├── TS28623_GenericNrm.yaml
│ │ ├── TS29512_Npcf_SMPolicyControl.yaml
│ │ ├── TS29514_Npcf_PolicyAuthorization.yaml
│ │ └── TS29571_CommonData.yaml
│ └── SA88-Rel16
│ └── OpenAPI
│ ├── 5gcNrm.yaml
│ ├── PerDataFileReportMnS.yaml
│ ├── PerMeasJobCtlMnS.yaml
│ ├── PerThresMonMnS.yaml
│ ├── PerfDataStreamingMnS.yaml
│ ├── README.md
│ ├── comDefs.yaml
│ ├── coslaNrm.yaml
│ ├── faultMnS.yaml
│ ├── genericNrm.yaml
│ ├── heartbeatNtf.yaml
│ ├── nrNrm.yaml
│ ├── provMnS.yaml
│ ├── sliceNrm.yaml
│ └── streamingDataMnS.yaml
Expected Folder Structure¶
The following figure show the expected folder structure for the different docker-compose file and its configurations.:
├── network
│ ├── .env
│ ├── config.py
│ ├── docker-compose.yaml
│ │
│ ├── ntsim-ng-o-du
│ └── ntsim-ng-o-ru
└── smo
├── common
│ ├── .env
│ ├── docker-compose.yaml
│ │
│ ├── dmaap
│ ├── docker
│ ├── identity
│ ├── kafka
│ └── zookeeper
└── oam
├── .env
├── docker-compose.yaml
│
├── web
├── controller
└── ves-collector
Usage¶
Bring Up Solution¶
Please check and adjust, if required the environment variables:
nano smo/common/.env
nano smo/oam/.env
nano network/.env
The tested configuration uses the following external https ports:
8443 for the ves-collector
8453 for web access to ODLUX (SDNC_WEB_PORT)
8463 for the keyclock web administrator user interface.
Please note that it is necessary to configure first the identity service, before starting further docker images.
The several docker-compose yaml files must be started in the right order as listed below:
First the SMO common services must be started:
docker-compose -f smo/common/docker-compose.yaml up -d
python smo/common/identity/config.py
The python script configure the users within the identity service (keycloak). A system user (%USER) is also created with administration rights. The initial password (Default4SDN!). The identity service implemented by Keycloak is configured in a way that the user must change its initial password after the first successful login.
In a second step the OAM specific service can be started:
docker-compose -f smo/oam/docker-compose.yaml up -d
Looking into the ONAP SDN-R logs will give you the startup procedure.:
docker logs -f sdnr
The startup was successful when you see the following line:
Everything OK in Certificate Installation
If you see the login page (https://sdnc-web:8453) you are good to go and can start the (simulated) network.:
docker-compose -f network/docker-compose.yaml up -d
Usually the first ves:event gets lost. Please restart the O-DU docker container(s) to send a second ves:pnfRegistration.:
docker-compose -f network/docker-compose.yaml restart ntsim-ng-o-du-1122
python network/config.py
The python script configures the simulated O-DU and O-RU according to O-RAN hybrid architecture.
O-DU - NETCONF Call HOME and NETCONF notifications O-RU - ves:pnfRegistration and ves:fault, ves:heartbeat
‘True’ indicated that the settings through SDN-R to the NETCONF server were successful.
SDN-R reads the fault events from DMaaP and processes them. Finally the fault events are visible in ODLUX.
Log files and karaf console¶
OpenDaylight/Apache Karaf logs:
docker exec -it sdnr tail -f /opt/opendaylight/data/log/karaf.log
VES-collector logs:
docker logs -f ves-collector
Verification of Solution¶
On the web user interface https://sdnc-web:8453 you can login with the system user ($USER) and the default password mentioned above. You should see 4 network function connected via IPv6 and also alarm notification via NETCONF and VES.
Terminate solution¶
To stop all container please respect the following order:
docker-compose -f network/docker-compose.yaml down
docker-compose -f smo/oam/docker-compose.yaml down
docker-compose -f smo/common/docker-compose.yaml down
Cleanup¶
Please be very careful with the following command, if other stopped containers are on the same system:
docker system prune -a -f
Contents
Frequently asked questions¶
Which browser should I use to operate OpenDaylight SDN-R User interface?¶
An actual version of Google Chromium or Google Chrome is recommended.
How to enable detailed logs in karaf for SDN-R applications¶
If you like to see more details in karaf logs for the NetConf communication between ODL and NetConf servers (mediators/devices) please invoke the following commands in the karaf console.
# Logging settings (on)
log:set DEBUG org.onap.ccsdk.features.sdnr
log:set TRACE org.opendaylight.netconf
log:set TRACE com.highstreet.technologies.odl.app
Please note, setting the debug level to ‘TRACE’ may impact the performance on the controller. In production environment make sure to set back the debug level to ‘INFO’ as soon possible.
# Logging settings (off)
log:set INFO org.onap.ccsdk.features.sdnr
log:set INFO org.opendaylight.netconf
log:set INFO com.highstreet.technologies.odl.app
Which commands should be used to analyze karaf logs?¶
cd $ODL_KARAF_HOME/data/log
rm *.txt
grep -anr --include=*.log* "| ERROR |" . | grep 2018 >> 01-error.txt
grep -anr --include=*.log* "RemoteDevice{" . | grep 2018 >> 02-devices.txt
grep -anr --include=*.log* "RemoteDevice{" . | grep "Unable to build schema context, unsatisfied imports" | grep 2018 >> 03-schema-issue.txt
grep -anr --include=*.log* "Matched request:" . | grep 2018 >> 04-matched-request.txt
grep -anr --include=*.log* "network-element" . | grep 2018 >> 05-network-element.txt
grep -anr --include=*.log* "urn:onf:params:xml:ns:yang:core-model" . | grep 2018 >> 06-core-module.txt
grep -anr --include=*.log* "PerformanceManagerTask" . | grep 2018 >> 07-pm-tick.txt
grep -anr --include=*.log* "Unable to read NE data for mountpoint" . | grep 2018 >> 08-unable-to-read.txt
grep -anr --include=*.log* "LKCYFL79Q01M01MSS801" . | grep 2018 >> 09-LKCYFL79Q01M01MSS801.txt
How to report an odlux issue¶
If you would like to report an odlux issue which you have noticed in the Graphical User Interface, please provide the following information:
Description: In which application you have noticed the issue?
Environment:
Which browser is used and the version of the browser. eg: Google chrome - version 71.0.3578.80 / Mozilla Firefox.
Which Operating system and version. eg: Linux/ Windows 10 - version 1803.
In which language you are using the application.
The application URL which is available on the browser address bar. eg: http://hostname/odlux/index.html#/connectApp
Expected Result: What is the expected result you are looking for?
Actual Result: What is the actual result you got?
Steps to reproduce: Describe the steps to reproduce the scenario. If possible, please provide the screenshots
The above information helps us to analyze the problem quicker.
Contents
Abbreviations¶
Abbreviation |
Description |
|---|---|
AAF |
|
A&AI |
|
AAA |
|
AID |
Architecture Integration Document |
APPC |
|
BPEL |
Business Process Execution Language |
BPMN |
Business Process Model and Notation or Business Process Management Notation |
BRMS |
Business Rules Management System |
BSS |
Business Support System |
CCSDK |
Common Controller SDK project |
CDAP |
|
CDS |
Controller Design Studio |
CI/CD |
Continuous Integration / Continuous Delivery |
CL |
Control Loop |
CLAMP |
Closed Loop Automation Management Platform (project) |
CLI |
|
CMA |
Change Management Application (within ONAP) |
CNF |
Cloud Native network Function. |
COE |
Container Orchestration Engine |
CPE |
Customer Premise Equipment |
CSAR |
|
DAO |
|
DCAE |
|
DDoS |
Distributed Denial-of-Service attack |
DG |
Directed Graph |
DG Builder |
Directed Graph Builder |
DMaaP |
|
DME |
|
DNS |
Domain Name System |
DPDK |
Data Plane Development Kit |
EELF |
|
EMS |
|
ESR |
|
ETSI |
|
EUAG |
|
FCAPS |
Fault Configuration Accounting Performance Security |
GBP |
|
GNFC |
|
GUI |
|
HAS |
|
HDFS |
Hadoop Distributed File System |
HPA |
Hardware Platform Awareness |
HTTP |
HyperText Transfer Protocol |
HV VES |
|
IAM/IDAM |
Identity and Access Management |
ICE |
Incubation and Certification Environment |
IDS |
|
IETF |
|
IKE |
|
IPS |
|
IPSEC |
|
JAR |
|
JSC |
|
JSON |
JavaScript Object Notation |
LCM |
Life Cycle Management |
LFN CVC |
Linux Foundation Networking Compliance/Verification Committee |
LFN CVP |
|
LRM |
Local Resource Monitor |
M0 |
Release Kick-off milestone. See also Release Lifecycle |
M1 |
Release Planning milestone. See also Release Lifecycle |
M2 |
Release Functionality Freeze milestone. See also Release Lifecycle |
M3 |
Release API Freeze milestone. See also Release Lifecycle |
M4 |
Release Code Freeze milestone. See also Release Lifecycle |
MACD |
(Vendor specific) Move Add Change Delete/Disconnect |
MANO |
MANagement and Organization of NFV |
MD-SAL |
Model Driven Service Abstraction Layer |
MR |
Message Router (a Common Service of ONAP) |
MOP |
Method of Procedure |
MOTS |
Mechanized Operations Tracking System |
MSB |
Microservice Bus |
MVP |
|
MVP |
Minimum Viable Plan (O-RAN Alliance |
NAI |
Network Artificial Intelligence |
NANCSP |
Network Cloud Service Provider |
NBI |
North Bound Interface |
NEP |
Network Equipment Provider |
NETCONF |
|
NFV |
|
NFVI |
Network Functions Virtualization Infrastructure |
NOD |
Network On Demand |
NS |
Network Services |
NS |
(Vendor Specific) New Start |
O-CU |
O-RAN Centralized Unit |
O-DU |
O-RAN Distributed Unit |
O-RAN |
O-RAN Alliance, Operator Defined Next Generation Radio Access Networks Alliance |
O-RAN-SC |
|
O-RU |
O-RAN Radio Unit |
OAM |
Operation and Maintenance |
OA&M |
Operations, Administration and Management |
OMF |
Operational Management Framework (of ONAP) |
OMSA |
ONAP Microservice Architecture |
ONAP |
|
OOF |
ONAP Optimization Framework |
ODL |
|
OOM |
|
OPNFV |
|
OSAM |
|
OSC |
O-RAN Software Community or Optical Supervisory Channel |
OSS |
Operations Support System |
PAP |
Policy Administration Point (ONAP) |
PCE |
Path Computation and Element (ONAP) |
PCI |
Physical Cell ID |
pCPE |
physical Customer Premise Equipment |
PDP-x |
Policy Decision Point - XACML (ONAP) |
PDP-d |
Policy Decision Point - Drools (ONAP) |
PO |
Platform Orchestrator |
PoC |
Proof of Concept |
POMBA |
|
PNDA |
|
PNF |
Physical Network Function |
RCA |
Root Cause Analysis |
RCT |
Reference Connection Tool |
REST |
|
RESTCONF |
A protocol based on HTTP for configuring data defined in YANG |
RO |
Resource Orchestrator |
RPC |
Remote Procedure Call |
S3P |
|
SDC |
Service Design and Creation (component of ONAP for visual modeling and design) |
SCTP |
Stream Control Transmission Protocol (RFC 4960 <https://datatracker.ietf.org/doc/html/rfc4960>) |
SDN |
|
SDNC |
|
SDN-R |
SDN-Radio <https://wiki.onap.org/display/DW/SDN-R> __ |
SDN-GP |
Software Defined Network - Global Platform |
SEBA |
SDN-Enabled Broadband Access, see also |
SLA |
Service Level Agreement |
SLI |
Service Logic Interpreter |
SME |
Subject Matter Expert |
SMO |
Service Management and Orchestration |
SMTP |
Simple Mail Transfer Protocol |
SNMP |
Simple Network Management Protocol |
SO |
|
SOT |
Source Of Truth |
SR-IOV |
|
SSL |
|
SUPP |
(Vendor Specific) short for supplement, changing a connection before activation |
Swagger |
legacy name for the OpenAPI Specification |
TCP |
Transmission Control Protocol |
TEM |
Telecom Electronics Manufacturer |
TLS |
|
TOSCA |
Topology and Orchestration Specification for Cloud Applications |
TPS |
Transactions Per Second |
TSC |
Technical Steering Committee |
U-UI |
|
UI |
|
UX |
|
vCE |
virtual CE (Customer Edge) router (an example VNF) |
vCPE |
Virtual Customer Premise Equipment |
vDNS |
Virtual Domain Name Server (an example VNF) |
VDU |
|
VES |
Virtual function Event Stream |
vF |
Virtual Firewall (an example VNF) |
VF |
Virtual Function |
VFC |
|
VFC |
Virtual Function Component (Resource Onboarding) |
vfModule |
Virtual Function Module |
VID |
Virtual Instantiation Deployment |
VID |
|
VIM |
Virtualized Infrastructure Manager |
VLAN |
Virtual Local Area Network |
VM |
Virtual Machine |
VNF |
|
VNFC |
Virtual Network Function Component |
VNFD |
|
VNFM |
VNF Manager |
VNO |
Virtual Network Operator |
vPE |
virtual PE (Provider Edge) router (an example of a VNF) |
VPP |
|
VSP |
Vendor Software Product (from SDC Demo Guide) |
VTP |
|
VVP |
|
WAR |
|
xNF |
The combination of PNF and VNF; Network Function |
YANG |
Yet Another Next Generation - a Data Modeling Language for the Network Configuration Protocol (NETCONF) |
Operation and Maintenance Release Notes¶
This document provides the release notes for O-RAN-SC D-Release of the Operation and Maintenance (OAM) project.
Version 6.0.0, 2022-06-28¶
Issue |
Summary |
|---|---|
Deployment: sdnc-web is not coming up |
|
O-DUs must not be affected by a disaster for June 2022 |
|
Correct E2 protocol |
|
create topologies for 2022-06 OTIC PoCfest |
|
Create additional information model for topology |
|
Deployment: jenkins pod not coming up, missing pv |
|
Deployment: Minor corrections in README.md |
|
Create more VES stndDefined Examples |
|
Define Wireshark configuration |
|
Update README to document new Wireshark function |
|
Add Wireshark to docker-compose |
|
Add Wireshark to the solution |
|
Ues json file names as expected by o-ran-sc-topology service |
|
Use inline css styles for SVG |
|
ADD N1, N2 N3 interfacing to topology generation |
|
Add nodes, function and protocols for N1, N2 and N3 interfacing |
|
Create topology-parser tool |
|
remove dependency to unused tile-server |
|
Update nexus port to 10001 for VES Collector images as it is now released. |
|
Align docker-compose with SIM topology-service |
|
Add LayerProtocolQualifier |
|
Create a script to generate a Topology |
|
Create O-RAN-SC extension to TAPI Topology v2.1.3 |
|
Remove highstreet from simulated Network Functions names |
|
Modify docker-compose configuration |
|
Correct pm-streaming model |
|
Add known issue section to release notes |
|
Network slicing event support by OAM (Simulator) |
|
Update to Java 11 |
|
Update Deployment |
|
1852,Provide ONAP Guilin based nonrtric-o1-controller image |
|
ONAP Guilin SDN-R based nonrtric-o1-controller |
|
SPV is failing if Admin state and another parameter present in single request |
|
Adding Copyright license for missing files |
|
Support of heartbeat and Software management Code delivery |
|
Yang model files should be part of scp/oam/modeling |
|
License.txt should update with latest 3rd party software list |
|
Remove unused directories |
|
User plane Topology View |
|
Control Plane Topology View |
|
O1 Topology View |
|
A1/E2 Topology View |
Please see related release notes in ONAP SDNC and OpenDaylight .
Version 5.1.0, 2022-01-31¶
Issue |
Summary |
|---|---|
Bug fixes in o-ran-sc-du-hello-world yang |
|
Bug fixes in o-ran-sc-du-hello-world yang |
|
Late updates on integration deployment |
|
OAM - VES sender script improvement |
Known issues¶
Issue |
Summary |
|---|---|
Support of namespace for referred yang-identity values. |
Version 5.0.0, 2021-11-29¶
Issue |
Summary |
|---|---|
Wrong value format in measurement ves example |
|
OAM Deployment enhancements |
|
update from stating to released |
|
Create yang model for CM according to the requirements by O-DU and the use case |
|
Create VES stndDefined extension for PM-streaming |
|
Update O-RAN-SC-Du Hello-world yang for CM |
|
Update header of o-ran-sc-du-hello-world |
|
Consider CM in o-ran-sc-du-hello-world.yang |
|
Add slice management to o-ran-sc-du-hello-world.yang |
|
Add performance measurement job management to o-ran-sc-du-hello-world.yang |
|
Add subscription management to o-ran-sc-du-hello-world.yang |
|
Create VES stndDefined PM streaming OpenAPI |
|
Create a Yang notification syntax |
|
Bug fixes in o-ran-sc-du-hello-world yang |
|
Update O-RAN-SC wiki release page |
Version 4.0.4, 2021-05-22¶
Issue |
Summary |
|---|---|
Update Documentation for docker supporting IPv6 |
|
Provide OpenAPI |
|
O-RU on-boarding |
|
O-DU on-boarding |
|
Test environment |
|
O-RU closed loop recovery |
|
Documentation |
|
Add section referencing O-RAN specifications |
|
Update Deployment docs |
Version 4.0.3, 2021-04-23¶
Issue |
Summary |
|---|---|
Provide settings.xml |
|
Update docs OAM architecture diagram |
|
Creation of use case docker-compose |
|
Remove unused folders |
|
Update docker-compose to onap-sdnc:2.1.3 |
|
Create dev example for additional ves domains |
|
Create VES client example for domain ‘notification’ |
|
Create VES client example for domain ‘stateChange’ |
|
Create VES client example for domain ‘stndDefined’ |
|
Update Jenkins Jobs |
|
Remove builder jobs of project oam |
Version 4.0.3, 2021-04-23¶
Issue |
Summary |
|---|---|
Provide settings.xml |
|
Update docs OAM architecture diagram |
|
Creation of use case docker-compose |
|
Remove unused folders |
|
Update docker-compose to onap-sdnc:2.1.3 |
|
Create dev example for additional ves domains |
|
Create VES client example for domain ‘notification’ |
|
Create VES client example for domain ‘stateChange’ |
|
Create VES client example for domain ‘stndefined’ |
|
Update Jenkins Jobs |
|
Remove builder jobs of project oam |
Version 4.0.3, 2021-04-23¶
Issue |
Summary |
|---|---|
Provide settings.xml |
|
Update docs OAM architecture diagram |
|
Creation of use case docker-compose |
|
Remove unused folders |
|
Update docker-compose to onap-sdnc:2.1.3 |
|
Create dev example for additional ves domains |
|
Create VES client example for domain ‘notification’ |
|
Create VES client example for domain ‘stateChange’ |
|
Create VES client example for domain ‘stndDefined’ |
|
Update Jenkins Jobs |
|
Remove builder jobs of project oam |
Version 4.0.2, 2021-04-02¶
Issue |
Summary |
|---|---|
Wrong time format in VES client scripts |
|
Support of IPv6 by docker-compose |
|
Update docker-compose and its configurations |
|
Update VES Client scripts supporting VES 7.2 |
|
Update VES client scripts supporting https |
|
Delete folder ‘model’ from OAM repo’ |
|
Use case driven yang for O-DU |
|
Update namespace definitions in prototype yangs of O-RAN-SC |
|
Add WG4 november train yangs modules |
|
O-RAN (FrontHaul) deviceManager: support of GuiCutThrough |
|
O-RAN (FrontHaul) deviceManager: o-ran-fm.yang/alarm-notif to VES:fault |
|
CallHome to VES:pnfRegistration |
|
Logging al RESTCONF requests and responses 1 |
|
Read whole leaf-list using get/get-config RPC 1 |
|
Support NETCONF get/get-config with multiple selected subtrees 1 |
Version 4.0.1, 2021-03-12¶
Issue |
Summary |
|---|---|
Add WG4 July 2020 yang modules |
|
Rename yang filename to <module>@<revision> format |
|
Modeling Repo: SIM directory not longer required |
|
Remove yang models from Repo |
|
OAM tr069: Changing .gitignore for IntelliJ related files |
|
Request to modify SMO deployment SOP |
|
Release dashboard image at version 2.0.3 |
Version 2.0.4, 2020-06-13¶
Documentation updated
Develop reusable OAM API such that the first consumer being a VTH can query, subscribe or publish on a DMaaP topic Story
Create helm deployment for SMO
Feature split for starting devicemanagers
Seed coder for an YANG linter
Please see also Release Notes of ONAP SDNC, DCAE, DMaaP, OOM
Version 2.0.3, 2020-04-08¶
What is an SMO?
Provide xRAN data-models
Provide curl bash scripts for Software Management
Add jenkins jobs for oam
Add parents to model artifacts
Add top level pom file to distribution
Wrong image tag in non-rt-ric-o1-controller distribution pom
Use ONAP release parents directly
Adjust artifact group name to ORAN naming rule
Use ORAN parents
Add push registry to distribution pom
Version 2.0.2, 2020-03-16¶
Controller DeviceManager for O-RAN-SC
Provide O1 yang modules
Version 2.0.1, 2020-02-26¶
Develop VTH for A1 interface
Version 1.0.0, 2019-11-14¶
Documentation added
Version 0.1.1, 2019-09-18¶
Development environment added
Version 0.1.0, 2019-09-08¶
Initial version