Note:

Compared to previous O-RAN-SC OAM release the AlarmLog and its interface was developed.


Message Flow

Diagram

O-RAN Fault management (VES) Radio Access Network Service Management and Orchestration (SMO) (e.g. ONAP) O-RAN Component O-RAN Component Streaming ConsumerONAP DCAE VES Collector Streaming ConsumerONAP DCAE VES Collector Message busONAP DMaaP Message busONAP DMaaP O1-ControllerONAP SDN-R O1-ControllerONAP SDN-R O1-PersistenceONAP SDN-R O1-PersistenceONAP SDN-R [01]REST: VES:fault [02]REST: Publish eventunauthenticated.SEC_FAULT_OUTPUT loop[polling for VES pnfRegistration] [03]REST: Get topicunauthenticated.SEC_FAULT_OUTPUT [04]REST: fault [05]Processing by "DeviceManager" [06]update network alarm logLicenseApache 2.0Thanks to plantUml!2019-12-03 | o-ran-sc.org


Description

  1. in case of failures an O1 device sends a VES event of domain 'fault' to the VES Collector on SMO
  2. The VES collector forwards the fault content to the Message Bus (DMaaP)
  3. The DeviceManager component on O1-Controller polls for fault events on DMaaP and ...
  4. ... receives its content
  5. The DeviceManager within the O1-Controller processes the fault event and ...
  6. ... updates the alarm log.


Verification Command

The following command should display the content within the O1-Controller Alarm Log:


HTTP-POST 
BasicAuth admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2UAccept: application/yang-data+json
Content-Type: application/yang-data+json

/rests/operations/data-provider:read-faultlog-list

{
      "input": {
            "filter": [],
            "sortorder": [
          {
                            "property": "node-id",
            "sortorder": "ascending"
          }
    ],
    "pagination": {
       "size": 1000,
       "page": 1
     }
  }
}
  • No labels