Content Comparison

Table of Contents

Scope

This page describes the mapping of several alarm / fault data models towards its representation in ODLUX.

Jira Legacy

The following data models should be considered are:

- VES 7.2
- ietf-alarms.yang (RFC 8632)
- o-ran-fm.yang (OpenFronthaul M-Plane)
- onf:air-interfaces-2.0.yang (OpenBackhaul)
- OpenROADM Alarm

ODLUX (label)	VES	IETF	O-RAN-FOFH
Timestamp	commonEventHeader/startEpochMicrosec	alarm/time-created	active-alarms/event-time
Node Name	commonEventHeader/sourceName	The node-id used by OpenDaylight	The node-id used by OpenDaylight
Count	commonEventHeader/sequence	n/a	n/a
ObjectId	faultFields/alarmInterfaceA	alarms/resource	active-alarms/fault-source
Alarm Type	faultFields/alarmCondition	alarms/alarm-type-id (alarms/alarm-type-qualifier)	active-alarms/fault-id together with active-alarms/fault-text
Severity	faultFields/eventSeverity	alarms/perceived-severity together for alarms/is-cleared	active-alarms/fault-severity together with active-alarms/is-cleared