Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Linux Foundation Analytics

Scope

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (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 (ME).


The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common 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.

Of course each project needs its own OAM repo to address the specific needs of the ManagedElement.

OAM Architecture

Messenger

You can find us on Slack: https://onapproject.slack.com/archives/C01K8CNUJA2

Mailing list and #oam

We use  discuss@lists.o-ran-sc.org with hashtag "oam" in the subject of emails.

Please make sure that you add somewhere in the subject of your email "#oam". 


Recent space activity

Recently Updated
typespage, comment, blogpost
max5
hideHeadingtrue
themesocial

Space contributors

Contributors
modelist
scopedescendants
limit5
showLastTimetrue
orderupdate

Table of Contents


Linux Foundation Analytics

Scope

According to the O-RAN-SC-OAM-Architecture document, all ManagedElements (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 Managment (FM), Performance Management (PM) and other events

on each Management-Service-Provider (MnS-Provider) running on the ManagedElement (ME).


The O-RAN-SC-OAM project provides reference implementation according to the O-RAN OAM (WG1) documents. In addition we provide a common 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.

Of course each project needs its own OAM repo to address the specific needs of the ManagedElement.

OAM Architecture

Messenger

You can find us on Slack: https://onapproject.slack.com/archives/C01K8CNUJA2

Mailing list and #oam

We use main@lists.o-ran-sc.org with hashtag "oam" in the subject of emails.

Please make sure that you add somewhere in the subject of your email "#oam". 

Example subject: "#oam Please help!"

More examples: https://lists.o-ran-sc.org/g/main/search?q=%23oam&ct=1

O-RAN-SC members who are not interested in OAM email conversations can mute the hashtag "#oam": https://lists.o-ran-sc.org/g/main/hashtags

Tip
titleWelcome to your new space!

Confluence spaces are great for sharing content and news with your team. This is your home page. Right now it shows recent space activity, but you can customize this page in any way you like.

Complete these tasks to get started

  •  Edit this home page - Click Edit in the top right of this screen to customize your Space home page
  •  Create your first page - Click the Create button in the header to get started
  •  Brand your Space - Click Configure Sidebar in the left panel to update space details and logo
  •  Set permissions - Click Space Tools in the left sidebar to update permissions and give others access

 


Recent space activity

Recently Updated
typespage, comment, blogpost
max5
hideHeadingtrue
themesocial

Space contributors

Contributors
modelist
scopedescendants
limit5
showLastTimetrue
orderupdate