What do the "TIME" fields mean in the alarm tables?
What do the TIME fields correspond to in the NAS_ALARMS the NAS_TRANSACTION_SUMMARY and the NAS_TRANSACTION_LOG tables?
DX UIM 20.4.* / 23.4
Guidance
NAS_ALARMS
[time_origin] corresponds to the date and time when the alarm was originated
[time_arrival] corresponds to the date and time when the alarm arrived to the nas
[nimts] corresponds to the epoch format of the [time_origin].nas_alarms
NAS_TRANSACTION_LOG
[time] This value corresponds to the date and time each instance of the alarm was originated. In the first occurrence of the alarm this field correspond to the [time_origin].nas_alarms
[nimts] corresponds to time_origin.nas_alarms
NAS_TRANSACTION_SUMMARY
[created] Normally the created field corresponds to the date and time of the first occurrence of the alarm (so it corresponds to the [time_origin].nas_alarms and [time].transaction_log of the first occurrence of the alarm)*
*If the NAS is configured to NOT "Accept automatic 'acknowledgement' of alarm, (Nas setup key: "allow_close_on_suppkey = no") the Created field might not correspond to the [time_origin].nas_alarms. When "Accept automatic 'acknowledgement' is not active, the level 0 alarms (Clear alarms) do not close the alarm. When the "Accept automatic 'acknowledgement' option is ticked (it is by Default when a clear alarm arrives it automatically acknowledges the alarm. Any new occurrence after being cleared and acknowledge will be a new alarm (new nimd).
When the "Accept automatic 'aknowledgement' option is NOT ticked, a clear alarm is treated as a normal alarm: it will have the same nimid. In this case when a clear alarm comes in it doesn't close the alarm and it resets a the [created].nas_transaction_log. In this cases the [created].nas_transaction_log does not correspond to the time_origin].nas_alarms but it would match instead the [time].transaction_log of the first occurence right after the clear alarm.
[closed] This is only filled when the alarm is acknowledged and corresponds to the time when the alarm is acknowledge.
[nimts] This is the date and time of the first occurrence of the alarm. (same as [time_origin].nas_alarms)
[time] This corresponds to the date and time of the last event change of the alarm (And it is the same value as the [time] field of the last occurrence of the transaction_log)
NOTE: The "time" field in the NAS_TRANSACTION_SUMMARY only updates when the "event" number increases. (When a new suppressed occurrence triggers an event change)
The "time" filed in NAS_TRANASACTION_LOG instead increases and changes at every occurrence (including identical re-occurrence)
Identical alarms, and with this saying, exact identical copies of the same alarm increase the suppcount only. When an identical alarm arrives, the suppcount increases, the NAS_TRANSACTION_LOG adds one row, but the NAS_TRANSACTION_SUMMARY time field is not updated.
The NAS_TRANSACTION_SUMMARY time is updated with the last occurrence of NAS_TRANSACTION_LOG only if the event increases.
The Event increases only if something changes in the alarm like, the severity, or a numeric change increases. (Numeric Changes are ignored by default configuration in the nas). If the same alarm contains different message instead, it will create brand new alarm.
IM - ALARMS DETAILS
[Time Received] Corresponds to the "time" field in the nas_transaction_summary
[Time Origin] Corresponds to the "time_origin" of the NAS_ALARMS and "created" field in the nas_transaction_summary.
[Time Arrival] Corresponds to the "time_arrival" field of the NAS_ALARMS (which is the time stamp of when the alarms was actually received by the nas)
IM - ALARM HISTORY
[Time Created] Corresponds to the [created] .nas_transaction_summary.
[Time] Corresponds to the [time] .nas_transaction_summary
Related Articles:
Where are the alarms stored in DX UIM?
What do the time related fields mean in the Alarm Tables in DX UIM?
nas Transaction Logging/Transaction Summary and compression
What is the meaning of the of nas alarm Subjects?
Why do some alarms' "count" increase immediately in the alarm console while others don't show the count increasing even when the alarms are suppressed?
Alarms are not 'in sync' between OC and Infrastructure Manager (IM) (broadcom.com)