O-RAN Alarm and Event Mapping

Event related (ietf-netconf-notifications.yang)

The "netconf-config-change" notification is populated as an "Event" in the "Event Log". An example "netconf-config-change" notification is as below -

^{<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> <eventTime>2023-12-12T06:44:16Z</eventTime> <netconf-config-change xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-notifications"> <changed-by> <username>root</username> <session-id>22</session-id> </changed-by> <datastore>running</datastore> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">/if:interfaces/if:interface[if:name='XYZ']</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">/if:interfaces/if:interface[if:name='XYZ']/if:name</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">/if:interfaces/if:interface[if:name='XYZ']/if:enabled</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">/if:interfaces/if:interface[if:name='XYZ']/if:type</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces">/if:interfaces/if:interface[if:name='XYZ']/if:description</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:l2-mtu</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:vlan-tagging</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service/o-ran-int:u-plane-marking</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service/o-ran-int:c-plane-marking</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service/o-ran-int:m-plane-marking</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service/o-ran-int:s-plane-marking</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:class-of-service/o-ran-int:other-marking</target> <operation>create</operation> </edit> <edit> <target xmlns:if="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns:o-ran-int="urn:o-ran:interfaces:1.0">/if:interfaces/if:interface[if:name='XYZ']/o-ran-int:port-reference</target> <operation>create</operation> </edit> </netconf-config-change> </notification>}

The notification consists of a list of edits identified by the NETCONF server for any changes that happen in the device. The above notification is generated by creating an "ietf-interface" using the "Config App". (Note: Though attributes like "Physical Address", "ifIndex" and "speed" are configured as part of the interface creation, they are however not present in the list of edits identified by the NETCONF server.)

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 -

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.