The desired maximum possible number of resources in
the system. In many cases, ACCESS to this object
for a particular resType is read-only. Typically
corresponds directly to a value labeled 'Max' in the
SERVER ALTERNATE STATUS display for desired,
administrative values. When the desired change
takes effect is implementation specific, ranging
from immediately to the next system
initialization.
Parsed from file xyplex-system-mib.txt
Company: None
Module: XYPLEX-SYSTEM-MIB
The desired maximum possible number of resources in
the system. In many cases, ACCESS to this object
for a particular resType is read-only. Typically
corresponds directly to a value labeled 'Max' in the
SERVER ALTERNATE STATUS display for desired,
administrative values. When the desired change
takes effect is implementation specific, ranging
from immediately to the next system initialization.
Parsed from file MRVINREACH.mib
Module: MRVINREACH
resAdminMaximum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The desired maximum possible number of resources in the system. In many cases, ACCESS to this object for a particular resType is read-only. Typically corresponds directly to a value labeled 'Max' in the SERVER ALTERNATE STATUS display for desired, administrative values. When the desired change takes effect is implementation specific, ranging from immediately to the next system initialization." ::= { resEntry 4 }
Vendor: MRV Communications, In-Reach Product Division
Module: ITOUCH-SYSTEM-MIB
[Automatically extracted from oidview.com]
resAdminMaximum OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The desired maximum possible number of resources in the system. In many cases, ACCESS to this object for a particular resType is read-only. Typically corresponds directly to a value labeled 'Max' in the SERVER ALTERNATE STATUS display for desired, administrative values. When the desired change takes effect is implementation specific, ranging from immediately to the next system initialization." ::= { resEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.33.1.32.1.1 | resType | 0 | 0 | Identification of a resource type. Typically corresponds directly to a label such as 'Processes:' in the SERVER ALTERNATE STATUS… |
| 1.3.6.1.4.1.33.1.32.1.2 | resCurrent | 0 | 0 | The number of resources currently in use on the system. Typically corresponds directly to a value labeled 'Cur' in the SERVER AL… |
| 1.3.6.1.4.1.33.1.32.1.3 | resWorst | 0 | 0 | The highest or lowest value of resCurrent since system initialization. Typically corresponds directly to a value labeled 'High' … |
| 1.3.6.1.4.1.33.1.32.1.5 | resLacks | 0 | 0 | The number of times since system initialization that the system could not obtain the resource because none were available. Typic… |
| 1.3.6.1.4.1.33.1.32.1.6 | resLackTime | 0 | 0 | The local system date and time when resLack last increased. Typically corresponds directly to a value labeled 'Last Occurred' in… |
| 1.3.6.1.4.1.33.1.32.1.7 | resOperMaximum | 0 | 0 | The current maximum possible number of resources in the system. Typically corresponds directly to a value labeled 'Max' in the S… |