Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpiIdrAreaRowStatus",
"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 three defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device. - `createAndWait(5)', 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 an Area to the specified Inventory Data Repository. The row is created (and changes state to 'active' when the hpiAreaType has been correctly set) to a new instance of the conceptual row. The dis-allowed hpiAreaType value is undefined(0) and unspecified(256) - `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 an Inventory Data Area, including the Area header and all fields contained with the area, from a particular Inventory Data Repository. In some implementations, certain Areas are intrinsically read-only. The hpiAreaIsReadOnly flag, indicates if the Area is read-only. If the Inventory Data Area is not read-only, but contains a Field that is read-only, the Area cannot be deleted. An attempt to delete an Area that contains a read-only Field will return an error.\"",
"::=",
"{",
"hpiIdrAreaEntry",
"5",
"}"
],
"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 three defined values: - `active(1)', which indicates that the conceptual row is available for use by the managed device; - `notInService(2)', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device. - `createAndWait(5)', 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 an Area to the specified Inventory Data Repository. The row is created (and changes state to 'active' when the hpiAreaType has been correctly set) to a new instance of the conceptual row. The dis-allowed hpiAreaType value is undefined(0) and unspecified(256) - `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 an Inventory Data Area, including the Area header and all fields contained with the area, from a particular Inventory Data Repository. In some implementations, certain Areas are intrinsically read-only. The hpiAreaIsReadOnly flag, indicates if the Area is read-only. If the Inventory Data Area is not read-only, but contains a Field that is read-only, the Area cannot be deleted. An attempt to delete an Area that contains a read-only Field will return an error."
],
null,
null,
null,
null
]
}