Description 1
Sources for this description
MIBdepot
Parsed from ASYNCOS-MAIL-MIB.txt · ironport · ASYNCOS-MAIL-MIB
Source file: Download ASYNCOS-MAIL-MIB.txt
OID reference
1.3.6.1.4.1.15497.1.1.1.18.1.2
Status reported by RAID controller.
Identification
{1 3 6 1 4 1 15497 1 1 1 18 1 2}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it.
| Value | Name | Source variants |
|---|---|---|
| 1 | driveHealthy | 1, 2 |
| 2 | driveFailure | 1, 2 |
| 3 | driveRebuild | 1, 2 |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In ASYNCOS-MAIL-MIB, the row index raidIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.15497.1.1.1.18.1.2.<raidIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.15497.1.1.1.18.1.2
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
raidStatus OBJECT-TYPE
SYNTAX INTEGER {
driveHealthy(1),
driveFailure(2),
driveRebuild(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the status of a a drive attached to a RAID
controller in the appliance.
driveHealthy -
The corresponding drive is connected to the RAID
controller and functioning as a healthy member in
the RAID volume.
driveFailure -
The drive is either disconnected from the RAID
controller, or has failed to operate within
thresholds defined in vendor specifications for the
drive and the controller.
driveRebuild -
The corresponding drive is connected to the RAID
controller. It is being rebuilt according to the
RAID controller specific rebuild algorithm for the
current operating mode of the RAID volume.
"
::= { raidEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Parsed from ASYNCOS-MAIL-MIB.txt · ironport · ASYNCOS-MAIL-MIB
Source file: Download ASYNCOS-MAIL-MIB.txt
Description 2
Represents the status of a a drive attached to a RAID controller in the appliance. driveHealthy - The corresponding drive is connected to the RAID controller and functioning as a healthy member in the RAID volume. driveFailure - The drive is either disconnected from the RAID controller, or has failed to operate within thresholds defined in vendor specifications for the drive and the controller. driveRebuild - The corresponding drive is connected to the RAID controller. It is being rebuilt according to the RAID controller specific rebuild algorithm for the current operating mode of the RAID volume.
Cisco MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: raidStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"raidStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"driveHealthy",
"(",
"1",
")",
",",
"driveFailure",
"(",
"2",
")",
",",
"driveRebuild",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Represents the status of a a drive attached to a RAID controller in the appliance. driveHealthy - The corresponding drive is connected to the RAID controller and functioning as a healthy member in the RAID volume. driveFailure - The drive is either disconnected from the RAID controller, or has failed to operate within thresholds defined in vendor specifications for the drive and the controller. driveRebuild - The corresponding drive is connected to the RAID controller. It is being rebuilt according to the RAID controller specific rebuild algorithm for the current operating mode of the RAID volume. \"",
"::=",
"{",
"raidEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"driveHealthy",
1
],
[
"driveFailure",
2
],
[
"driveRebuild",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Represents the status of a a drive attached to a RAID controller in the appliance. driveHealthy - The corresponding drive is connected to the RAID controller and functioning as a healthy member in the RAID volume. driveFailure - The drive is either disconnected from the RAID controller, or has failed to operate within thresholds defined in vendor specifications for the drive and the controller. driveRebuild - The corresponding drive is connected to the RAID controller. It is being rebuilt according to the RAID controller specific rebuild algorithm for the current operating mode of the RAID volume."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive. Cisco support.
Module: ASYNCOS-MAIL-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'Gauge32', 'Integer32'], 'IRONPORT-SMI': ['asyncOSMail']}Related source files and packages:
Same file in Observium Community.
Historical records
raidStatus OBJECT-TYPE
SYNTAX INTEGER {
driveHealthy(1),
driveFailure(2),
driveRebuild(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Status reported by RAID controller."
::= { raidEntry 2 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.15497.1.1.1.18.1.1 | raidIndex | 0 | 0 | Index into raidTable. |
| 1.3.6.1.4.1.15497.1.1.1.18.1.3 | raidID | 0 | 0 | Name of RAID component. E.g.: RAID 1, DISK 2. |
| 1.3.6.1.4.1.15497.1.1.1.18.1.4 | raidLastError | 0 | 0 | Last RAID Error Message. |