ODLUX (label) | VES | IETF | O-RAN-FH | ONF-AirInterface | OpenROADM | ITU (extension to IETF) | 3GPP | Comments |
|---|---|---|---|---|---|---|---|---|
| Timestamp | commonEventHeader/startEpochMicrosec | alarmalarms/time-created | active-alarms/event-time | current-problem-list/sequence-number | active-alarm-list/raiseTime | alarms/arm-time |
| |
| Node Name | commonEventHeader/sourceName | The node-id used by OpenDaylight | The node-id used by OpenDaylight | The node-id used by OpenDaylight | The node-id used by OpenDaylight | The node-id used by OpenDaylight | The node-id used by OpenDaylight | |
| Count | commonEventHeader/sequence | n/a | n/a | current-problem-list/sequence-number | active-alarm-list/id | n/a |
| Count doen't seems to be the best naming, VES can send 0 or 1, depending if alarm or clear. Proposal: change ODLUX label to "Sequence Number" and accept that such label is too long for a column header. |
| ObjectId | faultFields/alarmInterfaceA | alarms/resource | active-alarms/fault-source | /core-model:control-construct/core-model:logical-termination-point/core-model:uuid | active-alarm-list/resource |
|
| Proposal to rename ODLUX label to "Resource" |
| Alarm Type | faultFields/alarmCondition | alarms/alarm-type-id (alarms/alarm-type-qualifier) | active-alarms/fault-id together with active-alarms/fault-text | current-problem-list/problem-name | active-alarm-list/probableCause | alarms/probable-cause and alarms/probable-cause-string |
| |
| Severity | faultFields/eventSeverity | alarms/perceived-severity together for with alarms/is-cleared | active-alarms/fault-severity together with active-alarms/is-cleared | current-problem-list/problem-severity | active-alarm-list/severity | alarms/perceived-severity together with alarms/is-cleared |
|
Page History
Overview
Content Tools