The (conceptual) table of logical storage areas on
the client.
An entry shall be placed in the storage table for
each logical area of storage that is allocated and
has fixed resource limits. The amount of storage
represented in an entity is the amount actually
usable by the requesting entity, and excludes loss
due to formatting or file system reference
information.
These entries are associated with logical storage
areas, as might be seen by an application, rather
than physical storage entities which are typically
seen by an operating system. Storage such as
tapes and floppies without file systems on them
are typically not allocated in chunks by the
operating system to requesting applications, and
therefore shouldn't appear in this table.
Examples of valid storage for this table include
disk partitions, file systems, ram (for some
architectures this is further segmented into
regular memory, extended memory, and so on),
backing store for virtual memory ('swap space').
This table is intended to be a useful diagnostic
for 'out of memory' and 'out of buffers' types of
failures. In addition, it can be a useful
performance monitoring tool for tracking memory,
disk, or buffer usage.
Parsed from file ibmcltm.mib.txt
Company: ibm
Module: CLIENT-MIB
Vendor: IBM
Module: CLIENT-MIB (ibmcltm.mib)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
clntStorageTable OBJECT-TYPE SYNTAX SEQUENCE OF ClntStorageEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The (conceptual) table of logical storage areas on the client. An entry shall be placed in the storage table for each logical area of storage that is allocated and has fixed resource limits. The amount of storage represented in an entity is the amount actually usable by the requesting entity, and excludes loss due to formatting or file system reference information. These entries are associated with logical storage areas, as might be seen by an application, rather than physical storage entities which are typically seen by an operating system. Storage such as tapes and floppies without file systems on them are typically not allocated in chunks by the operating system to requesting applications, and therefore shouldn't appear in this table. Examples of valid storage for this table include disk partitions, file systems, ram (for some architectures this is further segmented into regular memory, extended memory, and so on), backing store for virtual memory ('swap space'). This table is intended to be a useful diagnostic for 'out of memory' and 'out of buffers' types of failures. In addition, it can be a useful performance monitoring tool for tracking memory, disk, or buffer usage. " ::= { clntHardware 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.50.2.1.1 | clntStorageEntry | 7 | 7 | A (conceptual) entry for one logical storage area on the client. The clntSystemIndex represents an entry in the clntSystemTable … |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.50.2.2 | clntDeviceTable | 1 | 7 | The (conceptual) table of devices contained by the client. |
| 1.3.6.1.4.1.2.6.50.2.3 | clntProcessorTable | 1 | 3 | The (conceptual) table of processors contained by the client. Note that this table is potentially sparse: a (conceptual) entry exi… |
| 1.3.6.1.4.1.2.6.50.2.4 | clntNetworkTable | 1 | 2 | The (conceptual) table of network devices contained by the client. Note that this table is potentially sparse: a (conceptual) entr… |
| 1.3.6.1.4.1.2.6.50.2.5 | clntPrinterTable | 1 | 3 | The (conceptual) table of printers local to the client. Note that this table is potentially sparse: a (conceptual) entry exists on… |
| 1.3.6.1.4.1.2.6.50.2.6 | clntDiskStorageTable | 1 | 5 | The (conceptual) table of long-term storage devices contained by the client. In particular, disk devices accessed remotely over … |
| 1.3.6.1.4.1.2.6.50.2.7 | clntPartitionTable | 1 | 6 | The (conceptual) table of partitions for long-term storage devices contained by the client. In particular, partitions accessed r… |
| 1.3.6.1.4.1.2.6.50.2.8 | clntFSTable | 1 | 10 | The (conceptual) table of file systems local to this client or remotely mounted from a file server. File systems that are in only… |