Ref: - NONRTRIC-501Getting issue details... STATUS
- O-RU sends alarm as VES event
- Poll DMaaP for alarms (SMO integration to take care of this)
- Filter the alarms for CUS Link Failure alarms
- Find the O-DU that is affected by this. Find O-RU identity in the alarm and then find the corresponding O-DU (maybe hard coded)
- REST conf call to OAM Controller to set the administrative state of the O-DU to UNLOCKED
- (Poll DMaaP and trace out the alarm clear)
- 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:
- https://wiki.o-ran-sc.org/display/OAM/Use+case+driven+YANG+modules+for+O-DU and
- https://wiki.o-ran-sc.org/download/attachments/20878535/o-ran-sc-du-hello-world.yang?api=v2 and
- https://gerrit.o-ran-sc.org/r/gitweb?p=scp/oam/modeling.git;a=blob;f=data-model/yang/working/o-ran-sc/o-ran-du/o-ran-sc-du-hello-world.yang;hb=HEAD
- The latest draft of the Yang file for the O-DU is seen at: