Instance.
Sources for this description
Reviewed vendor MIB copies in Fujitsu ServerViewMIBdepot
MIBdepot
Parsed from MEGARAID.MIB.txt · timeplex · RAID-Adapter-MIB
Source file: Download MEGARAID.MIB.txt
OID reference
1.3.6.1.4.1.16.1.1.3.1.1
The Adapter Number for this Instance of Adapter/Physical-Drive Instance.
Identification
{1 3 6 1 4 1 16 1 1 3 1 1}
Definitions may combine these properties differently.
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 RAID-Adapter-MIB, the row index consists of these components in order:
physAdapterNumber (INTEGER): one numeric subidentifier for the non-negative value.physChannel (INTEGER): one numeric subidentifier for the non-negative value.targetID (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.16.1.1.3.1.1.<physAdapterNumber>.<physChannel>.<targetID>. Use values present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.16.1.1.3.1.1
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.
Available source records contain 2 distinct definitions; some records may not include a definition.
physAdapterNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Adapter Number for this Instance of Adapter/Physical-Drive
Instance."
::= { physicaldriveEntry 1 }physAdapterNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Adapter Number for this Instance of Adapter/Physical-Drive
Instance."
::= { physicaldriveEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Reviewed vendor MIB copies in Fujitsu ServerViewMIBdepot
Parsed from MEGARAID.MIB.txt · timeplex · RAID-Adapter-MIB
Source file: Download MEGARAID.MIB.txt
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: physAdapterNumber
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"physAdapterNumber",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The Adapter Number for this Instance of Adapter/Physical-Drive Instance.\"",
"::=",
"{",
"physicaldriveEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The Adapter Number for this Instance of Adapter/Physical-Drive Instance."
],
null,
null,
null,
null
]
}Module: RAID-Adapter-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['enterprises', 'Counter'], 'RFC1213-MIB': ['DisplayString']}Module: RAID-Adapter-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['enterprises', 'Counter'], 'RFC1213-MIB': ['DisplayString']}Module: RAID-Adapter-MIB
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['enterprises', 'Counter'], 'RFC1213-MIB': ['DisplayString']}Source data warning: The published module reuses this name for different assignments. This complete declaration has an independently resolvable value; other references to the ambiguous name remain unresolved.
· Download hpnr.mib.txtModule: RAID-Adapter-MIB
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['enterprises', 'Counter'], 'RFC1213-MIB': ['DisplayString']}Source data warning: MIB copy distributed by Fujitsu in its ServerView package. The original vendor distribution and applicability to a particular device or firmware have not been independently confirmed; consult the named file and IANA enterprise registration.
· Download ServerView MIB copy — MEGARAID.MIB (saved edition 1)Related source files and packages:
Historical records
physAdapterNumber OBJECT-TYPE
SYNTAX INTEGER (1..4)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Adapter Number for this Instance of Adapter/Physical-Drive
Instance."
::= { physicaldriveEntry 1 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.16.1.1.3.1.2 | physChannel | 0 | 0 | Channel Number at Which this Physical Drive is Present. |
| 1.3.6.1.4.1.16.1.1.3.1.3 | targetID | 0 | 0 | SCSI Target ID at Which This Physical Drive is Present. |
| 1.3.6.1.4.1.16.1.1.3.1.4 | state | 0 | 0 | Current State of this Physical Drive. |
| 1.3.6.1.4.1.16.1.1.3.1.5 | arrayPosition | 0 | 0 | Array is a group of Physical Drives used to Configure Logical Drives. This String Variable has values of the type Ai-j. Example: … |
| 1.3.6.1.4.1.16.1.1.3.1.6 | sizeMB | 0 | 0 | Actual Size of this Physical Drive. |
| 1.3.6.1.4.1.16.1.1.3.1.7 | deviceType | 0 | 0 | Device Type of this Physical Drive. |
| 1.3.6.1.4.1.16.1.1.3.1.8 | inquiryString | 0 | 0 | SCSI Inquiry String for this Device. |
| 1.3.6.1.4.1.16.1.1.3.1.9 | scsiLevel | 0 | 0 | ANSI SCSI Level Conformance of this Device. |
| 1.3.6.1.4.1.16.1.1.3.1.10 | syncNegotiation | 0 | 0 | This indicates whether Firmware is Enabled or Disabled to perform the Synchronous Negotiation for this Device. |
| 1.3.6.1.4.1.16.1.1.3.1.11 | qtags | 0 | 0 | This indicates the Maximum Number of Concurrent Commands Firmware Issues to this Drive. |
| 1.3.6.1.4.1.16.1.1.3.1.12 | rebuildProgress | 0 | 0 | Rebuild Progress for this Physical Drive if the Physical Drive State is Rebuild. |
| 1.3.6.1.4.1.16.1.1.3.1.13 | mediumErrors | 0 | 0 | Medium Errors Occurred on this Drive Since it was Configured. |
| 1.3.6.1.4.1.16.1.1.3.1.14 | otherErrors | 0 | 0 | Other Errors Occurred on this Drive Since it was Configured. |
| 1.3.6.1.4.1.16.1.1.3.1.15 | maximumQueueDepth | 0 | 0 | The maximum queue depth of this Device. |
| 1.3.6.1.4.1.16.1.1.3.1.16 | physSlotStatus, physTermination | 0 | 0 | Indicates the status of interest on the drive slot |
| 1.3.6.1.4.1.16.1.1.3.1.17 | physSlotNumber, physSpeed | 0 | 0 | SCSI Target Slot Number at Which This Physical Drive is Present. |
| 1.3.6.1.4.1.16.1.1.3.1.18 | lunNumber | 0 | 0 | SCSI LUN ID of this Physical Device |