Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tsAlarmTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"TsAlarmEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with tsAlarmId equal to 1, and increments the value of tsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of tsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because tsAlarmId might have wrapped. The number of rows in the table at any given time is reflected by the value of tsAlarmsPresent.\"",
"::=",
"{",
"tsAlarm",
"2",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"TsAlarmEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with tsAlarmId equal to 1, and increments the value of tsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of tsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because tsAlarmId might have wrapped. The number of rows in the table at any given time is reflected by the value of tsAlarmsPresent."
],
null,
null,
null,
null
]
}