in use.
Sources for this description
MIBdepot
Source file: Download empire2.asn1.mib.txt
Source file: Download empire1.asn1.mib.txt
Source file: Download empire.mib.txt
Source file: Download empire.mib.txt
OID reference
1.3.6.1.4.1.546.1.1.1.7.1.14
The percentage of the device's total capacity in use.
Identification
{1 3 6 1 4 1 546 1 1 1 7 1 14}
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 EMPIRE, the row index devIndex 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.546.1.1.1.7.1.14.<devIndex>. 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.546.1.1.1.7.1.14
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.
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Source file: Download empire2.asn1.mib.txt
Source file: Download empire1.asn1.mib.txt
Source file: Download empire.mib.txt
Source file: Download empire.mib.txt
Historical records
devCapacity OBJECT-TYPE
SYNTAX INTEGER (0..100)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The percentage of the device's total capacity
in use."
::= { devTableEntry 14 }
devCapacity OBJECT-TYPE
SYNTAX INTEGER (0..100)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The percentage of the device's total capacity
in use."
::= { devTableEntry 14 }
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.546.1.1.1.7.1.1 | devIndex | 0 | 0 | This object does not describe the mounted device. Its sole purpose is to indicate the row instance. The instance is derived fro… |
| 1.3.6.1.4.1.546.1.1.1.7.1.2 | devDevice | 0 | 0 | The device name (e.g. /dev/sd0a) corresponding to the mounted file system. For example, the '/' file system is commonly mounted fr… |
| 1.3.6.1.4.1.546.1.1.1.7.1.3 | devMntPt | 0 | 0 | The mount point or path name in the local file system where the device is mounted (e.g. /home). |
| 1.3.6.1.4.1.546.1.1.1.7.1.4 | devBsize | 0 | 0 | The block size of the mounted device in bytes. File systems and disk devices generally allocate data in fixed size 'blocks' gener… |
| 1.3.6.1.4.1.546.1.1.1.7.1.5 | devTblks | 0 | 0 | The total number of blocks contained in the mounted device. |
| 1.3.6.1.4.1.546.1.1.1.7.1.6 | devFblks | 0 | 0 | The total number of free or unallocated blocks in the mounted device. |
| 1.3.6.1.4.1.546.1.1.1.7.1.7 | devTfiles | 0 | 0 | Each disk device and file system allocates a fixed, maximum number of files that can be written to the device. The value of thi… |
| 1.3.6.1.4.1.546.1.1.1.7.1.8 | devFfiles | 0 | 0 | The number of free or unallocated files that can be created on this device. |
| 1.3.6.1.4.1.546.1.1.1.7.1.9 | devMaxNameLen | 0 | 0 | The maximum file name length that this mounted device supports. If no fixed limit exists, 0 is returned. |
| 1.3.6.1.4.1.546.1.1.1.7.1.10 | devType | 0 | 0 | The type of the mounted device. If this underlying device does not support feature, 0 is returned. |
| 1.3.6.1.4.1.546.1.1.1.7.1.11 | devFsid | 0 | 0 | The (possibly unique) file system ID of the mounted device. V.4 systems support its uniqueness while SunOS does not. For device… |
| 1.3.6.1.4.1.546.1.1.1.7.1.12 | devFstr | 0 | 0 | Some devices support a description string. If supported by the underlying device and operating system, that device specific descri… |
| 1.3.6.1.4.1.546.1.1.1.7.1.13 | devUnmount | 0 | 0 | Writing a delete(1) to this object causes the agent to unmount this device and remove its entry from the mounted file system tabl… |
| 1.3.6.1.4.1.546.1.1.1.7.1.15 | devInodeCapacity | 0 | 0 | The percentage of the device's total file capacity (inodes) in use. File systems often place an upper bound on the number of fil… |