Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpiUserEventRowStatus",
"OBJECT-TYPE",
"SYNTAX",
"RowStatus",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This columnar node contains the status of the row and also perform add and delete operations. The status column uses four defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device). This function is used to add a User Alarm to this User Event Table and also to the to the Domain Alarm Table; When creating this row, the value of hpiEventSeverity indice must not be one of these minor(3), major(2), and critical(3). The effect of creating a new row will also be reflected in the DAT - with a new row there. - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. This function allows the HPI MIB User to delete a single User Alarm from the User Event Table and Domain Alarm Table. Only User Alarms added to the DAT and User Event Table can be deleted. To delete a single, specific alarm, set the hpiDomainAlarmId parameter to a value representing an actual User Alarm in the User Event Table.\"",
"::=",
"{",
"hpiUserEventEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"RowStatus"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This columnar node contains the status of the row and also perform add and delete operations. The status column uses four defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `createAndGo(4)', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device). This function is used to add a User Alarm to this User Event Table and also to the to the Domain Alarm Table; When creating this row, the value of hpiEventSeverity indice must not be one of these minor(3), major(2), and critical(3). The effect of creating a new row will also be reflected in the DAT - with a new row there. - `destroy(6)', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. This function allows the HPI MIB User to delete a single User Alarm from the User Event Table and Domain Alarm Table. Only User Alarms added to the DAT and User Event Table can be deleted. To delete a single, specific alarm, set the hpiDomainAlarmId parameter to a value representing an actual User Alarm in the User Event Table."
],
null,
null,
null,
null
]
}