Ref: NONRTRIC-501 - Getting issue details... STATUS
- O-RU sends alarm as VES event to "unauthenticated.SEC_FAULT_OUTPUT"
- Poll DMaaP for alarms from "unauthenticated.SEC_FAULT_OUTPUT"
- Filter the alarms for "faultFields:alarmCondition" set to "30" ("CUS Link Failure"), with "faultFields:eventSeverity" anything but "NORMAL"
- Find O-RU identity in the alarm, provided in "commonEventHeader:sourceName", and then find the corresponding O-DU through hard coded mapping (for now)
- REST conf call to OAM Controller through SDNR, using endpoint:
"/rests/data/network-topology:network-topology/topology=topology-netconf/node=[O-DU-ID]/yang-ext:mount/o-ran-sc-du-hello-world:network-function/du-to-ru-connection=[O-RU-ID]",
to set the administrative state of the O-DU to UNLOCKED, providing data:
{"o-ran-sc-du-hello-world:du-to-ru-connection": [{"name": "O-RU-ID", "administrative-state": "UNLOCKED"}]} - (Poll DMaaP and trace out the alarm clear, "faultFields:eventSeverity" "NORMAL")
- DMaaP :
- https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/dev/ves-test-collector/client-scripts-ves-v7/json/templates/fault.json;hb=HEAD
- The @....@ entries will be replaced by the values from https://wiki.o-ran-sc.org/display/OAM/o-ran-fm%3Aalarm-notif+to+ves%3Afault#oranfm:alarmnotiftoves:fault-MappingtoVESfaultfields
- The topics etc are described in https://wiki.o-ran-sc.org/display/OAM/VES+Events+and+Topics+on+Message+Router
- https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=blob;f=solution/dev/ves-test-collector/client-scripts-ves-v7/json/templates/fault.json;hb=HEAD
- RestConf call:
- The latest draft of the Yang file for the O-DU is seen at: