All alarm events are stored in the BSAAlarmData table if an appropriate profile is present. This table contains the common set of normalized alarm fields and the entire contents of the alarm in binary form.
Table 3-2 BSAAlarmData Table
|
Name |
Type |
P |
M |
F |
Description |
|---|---|---|---|---|---|
|
AlarmKey |
$ID$ |
Y |
Y |
N |
Unique random number generated when the alarm record was stored to the database. |
|
BandID |
$ID$ |
N |
Y |
Y |
Foreign key reference to the BSATimeBand table. |
|
SeriesID |
$ID$ |
N |
Y |
Y |
Foreign key to the BSASeries table. |
|
AlarmID |
NUMBER |
N |
Y |
N |
Nonpersistent Alarm ID generated by the network management system. |
|
Element |
NUMBER |
N |
Y |
N |
The ID of the affected element. This ID is not unique and might be reassigned by the Operations Center server after a server restart. |
|
UpdateType |
NUMBER |
N |
Y |
N |
Alarm update type. Supported types include:
|
|
RecordedDate |
$TIMEPOINT$ |
N |
Y |
N |
Date and time that the BSAAlarmData record was created (represented in milliseconds). |
|
RecordedDateTime |
$DATETIME$ |
N |
Y |
N |
Date and time that the BSAAlarmData record was created (represented as a native date/time object). |
|
SequenceID |
LONG |
N |
Y |
N |
Maintains data order when the data occurs within the same millisecond. |
|
TimePoint |
$TIMEPOINT$ |
N |
Y |
N |
The time point of the alarm record. This field is set to the date and time when the Operations Center server received the alarm (represented in milliseconds). |
|
TimePointDateTime |
$DATETIME$ |
N |
Y |
N |
The time point of the alarm record. This field is set to the date and time when the Operations Center server received the alarm (represented in milliseconds). |
|
TimeCreated |
$TIMEPOINT$ |
N |
Y |
N |
The date and time the alarm was created. This field is the same as NativeLastUpdateTime for alarm create records. However, if this is an alarm delete entry, the TimeCreated field is set to Long.MAX_VALUE; that is, 9223372036854775807. |
|
TimeDeleted |
$TIMEPOINT$ |
N |
Y |
N |
The date and time the alarm was closed or deleted. This field is the same date as NativeLastUpdateTime for alarm delete records. However, if this is an alarm create entry, this field is set to Long.MAX_VALUE; that is, 9223372036854775807. |
|
LastUpdateTime |
$TIMEPOINT$ |
N |
Y |
N |
The date and time of the most recent update of the current alarm. This is a skewed date/time, meaning the time is adjusted for differences between the network management system and the Operations Center server. This value is represented in milliseconds. |
|
LastUpdateDateTime |
$DATETIME$ |
N |
Y |
N |
The date and time of the most recent update of the current alarm. This is a skewed date/time; the time is adjusted for differences between the network management system and the Operations Center server. This value is represented as a native date/time object. |
|
NativeLastUpdateTime |
$TIMEPOINT$ |
N |
Y |
N |
The most recent update time of the current alarm. This is the nonskewed date/time, meaning no adjustments have been made between the network management system and Operations Center server time. |
|
Condition |
NUMBER |
N |
Y |
N |
Element condition for current alarm. Current values include:
|
|
PersistentID |
$IDX_STRING$ |
N |
Y |
N |
A unique persistent ID associated with the current alarm. This ID is persistent across Operations Center server restarts, and is unique to each adapter. |
|
ElementKe |
$ID$ |
N |
Y |
Y |
Foreign key to the BSAElements table. |
|
AdapterKe |
$ID$ |
N |
Y |
Y |
Foreign key reference to the Adapters table. |
|
Status |
$VARCHAR$(32) |
N |
N |
N |
Normalized status of the alarm. Current values include:
|
|
AlarmBlob |
LONG RAW |
N |
N |
N |
Alarm data stored as a serialized object. Cannot be viewed by external reporting tools. |