- 'active': indicates that the table row is available for
use by the managed device;
- 'notInService': indicates that the table row
exists in the agent, but is unavailable for use by the
managed device (see NOTE below);
- 'notReady': indicates that the table row exists
in the agent, but is missing information necessary in
order to be available for use by the managed device;
(cannot be specified in a set operation)
- 'createAndGo': supplied by a management station
wishing to create a new instance of a table row and
to have it available for use by the managed device;
(cannot be returned in a get response)
- 'createAndWait': supplied by a management station
wishing to create a new instance of a table row but
not to have it available for use by the managed device;
and,
(cannot be returned in a get response)
- 'destroy': supplied by a management station wishing
to delete all of the objects associated with an
existing table row.
(cannot be returned in a get response)
To create new row, a manager sets this object to
createAndWait. Agent creates a new row and sets row
status to notInService. After the manager creates
all the corresponding rows in dptScsiArrMemberTable
and has set all the relevant columnar objects, it
finally sets dptScsiArrEntryStatus to active which
saves all the information to the hardware and performs
an array build.
If the manager sets dptScsiArrEntryStatus to active or
notInService and the required number of drives are
not members of this array group (for example, a RAID-5
needs at least 3 drives), then 'inconsistentValue' is
returned.
To delete an array group, the manager sets this object to
destroy. When a row with a particular row index is
destroyed, all corresponding rows in dptScsiArrMemberTable
are destroyed as well.
+
| doesn't exist |
+
Array group is Array group is Array group is
not created created in the saved to hardware
agent and a build is
performed
Parsed from file Dpt.mib.txt
Company: None
Module: DPT-SCSI-MIB
- 'active': indicates that the table row is available for
use by the managed device;
- 'notInService': indicates that the table row
exists in the agent, but is unavailable for use by the
managed device (see NOTE below);
- 'notReady': indicates that the table row exists
in the agent, but is missing information necessary in
order to be available for use by the managed device;
- 'createAndGo': supplied by a management station
wishing to create a new instance of a table row and
to have it available for use by the managed device;
(cannot be returned in a get response)
- 'createAndWait': supplied by a management station
wishing to create a new instance of a table row but
not to have it available for use by the managed device;
and,
(cannot be returned in a get response)
- 'destroy': supplied by a management station wishing
to delete all of the objects associated with an
existing table row.
(cannot be returned in a get response)
To create new row, a manager sets this object to
createAndWait. Agent creates a new row and sets row
status to notInService. After the manager creates
all the corresponding rows in dptScsiArrMemberTable
and has set all the relevant columnar objects, it
finally sets dptScsiArrEntryStatus to active which
saves all the information to the hardware and performs
an array build.
If the manager sets dptScsiArrEntryStatus to active or
notInService and the required number of drives are
not members of this array group (for example, a RAID-5
needs at least 3 drives), then 'inconsistentValue' is
returned.
To delete an array group, the manager sets this object to
destroy. When a row with a particular row index is
destroyed, all corresponding rows in dptScsiArrMemberTable
are destroyed as well.
+
| doesn't exist |
+
Array group is Array group is Array group is
not created created in the saved to hardware
agent and a build is
performed
Parsed from file DPT-SCSI-MIB.mib
Module: DPT-SCSI-MIB
Vendor: Distributed Processing Technology
Module: DPT-SCSI-MIB
[Automatically extracted from oidview.com]
dptScsiArrEntryStatus OBJECT-TYPE SYNTAX RowStatus ACCESS read-only STATUS mandatory DESCRIPTION "- 'active': indicates that the table row is available for use by the managed device; - 'notInService': indicates that the table row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - 'notReady': indicates that the table row exists in the agent, but is missing information necessary in order to be available for use by the managed device; (cannot be specified in a set operation) - 'createAndGo': supplied by a management station wishing to create a new instance of a table row and to have it available for use by the managed device; (cannot be returned in a get response) - 'createAndWait': supplied by a management station wishing to create a new instance of a table row but not to have it available for use by the managed device; and, (cannot be returned in a get response) - 'destroy': supplied by a management station wishing to delete all of the objects associated with an existing table row. (cannot be returned in a get response) To create new row, a manager sets this object to createAndWait. Agent creates a new row and sets row status to notInService. After the manager creates all the corresponding rows in dptScsiArrMemberTable and has set all the relevant columnar objects, it finally sets dptScsiArrEntryStatus to active which saves all the information to the hardware and performs an array build. If the manager sets dptScsiArrEntryStatus to active or notInService and the required number of drives are not members of this array group (for example, a RAID-5 needs at least 3 drives), then 'inconsistentValue' is returned. To delete an array group, the manager sets this object to destroy. When a row with a particular row index is destroyed, all corresponding rows in dptScsiArrMemberTable are destroyed as well. + | doesn't exist | + Array group is Array group is Array group is not created created in the saved to hardware agent and a build is performed" ::= { dptScsiArrEntry 5 }
dptScsiArrEntryStatus OBJECT-TYPE SYNTAX RowStatus ACCESS read-only STATUS mandatory DESCRIPTION "- 'active': indicates that the table row is available for use by the managed device; - 'notInService': indicates that the table row exists in the agent, but is unavailable for use by the managed device (see NOTE below); - 'notReady': indicates that the table row exists in the agent, but is missing information necessary in order to be available for use by the managed device; - 'createAndGo': supplied by a management station wishing to create a new instance of a table row and to have it available for use by the managed device; (cannot be returned in a get response) - 'createAndWait': supplied by a management station wishing to create a new instance of a table row but not to have it available for use by the managed device; and, (cannot be returned in a get response) - 'destroy': supplied by a management station wishing to delete all of the objects associated with an existing table row. (cannot be returned in a get response) To create new row, a manager sets this object to createAndWait. Agent creates a new row and sets row status to notInService. After the manager creates all the corresponding rows in dptScsiArrMemberTable and has set all the relevant columnar objects, it finally sets dptScsiArrEntryStatus to active which saves all the information to the hardware and performs an array build. If the manager sets dptScsiArrEntryStatus to active or notInService and the required number of drives are not members of this array group (for example, a RAID-5 needs at least 3 drives), then 'inconsistentValue' is returned. To delete an array group, the manager sets this object to destroy. When a row with a particular row index is destroyed, all corresponding rows in dptScsiArrMemberTable are destroyed as well. + | doesn't exist | + Array group is Array group is Array group is not created created in the saved to hardware agent and a build is performed" ::= { dptScsiArrEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1597.1.5.1.1.1 | dptScsiArrType | 0 | 0 | The RAID type for the Logical Drive. RAID Disk-fault No.of Level Tolerant Drives RAID-0 No 2 or more RAID-1 Yes … |
| 1.3.6.1.4.1.1597.1.5.1.1.2 | dptScsiArrOwner | 0 | 0 | software entity that created this logical device. |
| 1.3.6.1.4.1.1597.1.5.1.1.3 | dptScsiArrName | 0 | 0 | Name of the RAID array group. |
| 1.3.6.1.4.1.1597.1.5.1.1.4 | dptScsiArrBackgroundProgress | 0 | 0 | Percentage of completion of an outstanding background operation, e.g., array Build, Rebuild or Verify. If there is no current bac… |