...
A subset of the "Event Log" for the above notification is as below -
Alarm related (o-ran-fm.yang)
The notification generated by the NETCONF server is as below -
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2023-12-12T08:04:13Z</eventTime>
<alarm-notif xmlns="urn:o-ran:fm:1.0">
<fault-id>4</fault-id>
<fault-source>Slot-2-Port-B</fault-source>
<affected-objects>
<name>Slot-2-Port-B</name>
</affected-objects>
<fault-severity>MAJOR</fault-severity>
<is-cleared>false</is-cleared>
<fault-text>CPRI Port Down</fault-text>
<event-time>2023-12-12T08:04:13.4Z</event-time>
</alarm-notif>
</notification>
The above is a Major alarm and is mapped to the FaultLog object and displayed in the "Fault App". Mapping Info -
NETCONF Attribute | SDNR FaultLog Attribute |
---|---|
fault-source | ObjectId |
fault-text | Alarm Type |
fault-severity & is-cleared | Severity |
fault-id | Id |
For identifying a cleared alarm, a combination of "fault-severity" and "is-cleared" fields are used. If "is-cleared" is set to "true", then the Alarm is marked as Cleared. If "false", then the fault-severity value is used to identify the severity of the alarm.