CISCO-PROCESS-MIB

Unsigned32 (1..4294967295)

An index that uniquely represents a CPU (or group of CPUs) whose CPU load information is reported by a row in this table. This index is assigned arbitrarily by the engine and is not saved over reboots.

EntPhysicalIndexOrZeroThis textual convention is an extension of entPhysicalIndex. If non-zero, the object is an entPhysicalIndex. If zero, no appropriate entPhysicalIndex exists. Any additional semantics are object specific. (0..2147483647) · Integer32

The entPhysicalIndex of the physical entity for which the CPU statistics in this entry are maintained. The physical entity can be a CPU chip, a group of CPUs, a CPU card etc. The exact type of this entity is described by its entPhysicalVendorType value. If the CPU statistics in this entry correspond to more than one physical entity (or to no physical entity), or if the entPhysicalTable is not supported on the SNMP agent, the value of this object must be zero.

Gauge32 (1..100)

The overall CPU busy percentage in the last 5 second period. This object obsoletes the busyPer object from the OLD-CISCO-SYSTEM-MIB. This object is deprecated by cpmCPUTotal5secRev which has the changed range of value (0..100).

Gauge32 (1..100)

The overall CPU busy percentage in the last 1 minute period. This object obsoletes the avgBusy1 object from the OLD-CISCO-SYSTEM-MIB. This object is deprecated by cpmCPUTotal1minRev which has the changed range of value (0..100).

Gauge32 (1..100)

The overall CPU busy percentage in the last 5 minute period. This object deprecates the avgBusy5 object from the OLD-CISCO-SYSTEM-MIB. This object is deprecated by cpmCPUTotal5minRev which has the changed range of value (0..100).

Gauge32 (0..100) · percent

The overall CPU busy percentage in the last 5 second period. This object deprecates the object cpmCPUTotal5sec and increases the value range to (0..100). This object is deprecated by cpmCPUTotalMonIntervalValue

Gauge32 (0..100) · percent

The overall CPU busy percentage in the last 1 minute period. This object deprecates the object cpmCPUTotal1min and increases the value range to (0..100).

Gauge32 (0..100) · percent

The overall CPU busy percentage in the last 5 minute period. This object deprecates the object cpmCPUTotal5min and increases the value range to (0..100).

Unsigned32 · seconds

CPU usage monitoring interval. The value of this object in seconds indicates the how often the CPU utilization is calculated and monitored.

Gauge32 (0..100) · percent

The overall CPU busy percentage in the last cpmCPUMonInterval period. This object deprecates the object cpmCPUTotal5secRev.

Gauge32 (0..100) · percent

The overall CPU busy percentage in the interrupt context in the last cpmCPUMonInterval period.

Gauge32 · kilo-bytes

The overall CPU wide system memory which is currently under use.

Gauge32 · kilo-bytes

The overall CPU wide system memory which is currently free.

Gauge32 · kilo-bytes

The overall CPU wide system memory which is reserved for kernel usage.

Gauge32 · bytes

The lowest free memory that has been recorded since device has booted.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmCPUMemoryUsed. This object needs to be supported only when the value of cpmCPUMemoryUsed exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

The overall CPU wide system memory which is currently under use. This object is a 64-bit version of cpmCPUMemoryUsed.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmCPUMemoryFree. This object needs to be supported only when the value of cpmCPUMemoryFree exceeds 32-bit, otherwise this object value would be set to 0.

Counter64 (0..18446744073709551615) · kilo-bytes

The overall CPU wide system memory which is currently free. This object is a 64-bit version of cpmCPUMemoryFree.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmCPUMemoryKernelReserved. This object needs to be supported only when the value of cpmCPUMemoryKernelReserved exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

The overall CPU wide system memory which is reserved for kernel usage. This object is a 64-bit version of cpmCPUMemoryKernelReserved.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmCPUMemoryLowest. This object needs to be supported only when the value of cpmCPUMemoryLowest exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

The lowest free memory that has been recorded since device has booted. This object is a 64-bit version of cpmCPUMemoryLowest.

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall CPU load Average in the last 1 minute period

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall CPU load Average in the last 5 minutes period

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall CPU load Average in the last 15 minutes period

Gauge32

The overall CPU wide system memory which is currently Committed.

Gauge32

This object represents the upper 32-bit of cpmCPUMemoryCommitted. This object needs to be supported only when the value of cpmCPUMemoryCommitted exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64

The overall CPU wide system memory which is currently committed. This object is a 64-bit version of cpmCPUMemoryCommitted

Gauge32 (1..100)

The overall CPU busy percentage in the last 15 minute period. This object deprecates the avgBusy5 object from the OLD-CISCO-SYSTEM-MIB. This object is deprecated by cpmCPUTotal15minRev which has the changed range of value (0..100).

Gauge32 (0..100) · percent

The overall CPU busy percentage in the last 15 minute period. This object deprecates the object cpmCPUTotal15min and increases the value range to (0..100).

Unsigned32 (1..4294967295)

An index that uniquely represents a Core (or group of Cores) whose Core load information is reported by a row in this table. This index is assigned arbitrarily by the engine and is not saved over reboots.

EntPhysicalIndexOrZeroThis textual convention is an extension of entPhysicalIndex. If non-zero, the object is an entPhysicalIndex. If zero, no appropriate entPhysicalIndex exists. Any additional semantics are object specific. (0..2147483647) · Integer32

The entCorePhysicalIndex of the physical entity for which the Core statistics in this entry are maintained. The physical entity can be a CPU chip, a group of CPUs, a CPU card etc. The exact type of this entity is described by its entPhysicalVendorType value. If the Core statistics in this entry correspond to more than one physical entity (or to no physical entity), or if the entPhysicalTable is not supported on the SNMP agent, the value of this object must be zero.

Gauge32 (0..100)

The overall Core busy percentage in the last 5 second period.

Gauge32 (0..100)

The overall Core busy percentage in the last 1 minute period.

Gauge32 (0..100)

The overall Core busy percentage in the last 5 minute period.

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall Core load Average in the last 1 minute period

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall Core load Average in the last 5 minutes period

CPULoadAverageThe average number of processes in the queue waiting for CPU time over the last N minutes, where the N is defined by the object using this TC. This is similar to UNIX/Linux system load average. The calculation may vary by different OS kernels, so refer to the specific system document of your interest. The object value, which uses this TC, reflects the average number of runnable processes with units of hundredths of processes, i.e. a value of 183 indicates the average number of runnable processes over the N minutes is 1.83. · Unsigned32 · hint d · hundredths of processes

The overall Core load Average in the last 15 minutes period

Unsigned32

This object contains the process ID. cpmTimeCreated should be checked against the last time it was polled, and if it has changed the PID has been reused and the entire entry should be polled again.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (1..32) · OCTET STRING · hint 255a

The name associated with this process. If the name is longer than 32 characters, it will be truncated to the first 31 characters, and a `*' will be appended as the last character to imply this is a truncated process name.

INTEGER0 = down1 = running2 = started3 = waiting4 = disabled5 = userdisabled6 = locked7 = other · Integer32

This object indicates the current state of a process. Running state means that the process is actively consuming CPU. All the other states are just waiting states. The valid states are: other - Any other state apart from the ones listed. down - The process is not operational. running - Actively running on a core. started - The process is just forked. waiting - The ProcessMgr config for this process specifies a delay before the process moves to running. disabled - The process is not enabled in the ProcessMgr configuration. userdisabled - The process is put to disabled state by admin. locked - Implies that if the process exits, it will not be restarted until the lock is released.

Unsigned32 · microseconds

Average elapsed CPU time in microseconds when the process was active. This object is deprecated by cpmProcessAverageUSecs.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time when the process was created. The process ID and the time when the process was created, uniquely identifies a process.

Unsigned32 · microseconds

Average elapsed CPU time in microseconds when the process was active. This object deprecates the object cpmProcessuSecs.

Gauge32 · bytes

The sum of all the dynamically allocated memory that this process has received from the system. This includes memory that may have been returned. The sum of freed memory is provided by cpmProcExtMemFreed. This object is deprecated by cpmProcExtMemAllocatedRev.

Gauge32 · bytes

The sum of all memory that this process has returned to the system. This object is deprecated by cpmProcExtMemFreedRev.

Counter32

The number of times since cpmTimeCreated that the process has been invoked. This object is deprecated by cpmProcExtInvokedRev.

Counter32 · microseconds

The amount of CPU time the process has used, in microseconds. This object is deprecated by cpmProcExtRuntimeRev.

Gauge32 (1..100)

This object provides a general idea of how busy a process caused the processor to be over a 5 second period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object is deprecated by cpmProcExtUtil5SecRev which has the changed range of value (0..100).

Gauge32 (1..100)

This object provides a general idea of how busy a process caused the processor to be over a 1 minute period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object is deprecated by cpmProcExtUtil1MinRev which has the changed range of value (0..100).

Gauge32 (1..100)

This object provides a general idea of how busy a process caused the processor to be over a 5 minute period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object is deprecated by cpmProcExtUtil5MinRev which has the changed range of value (0..100).

INTEGER1 = critical2 = high3 = normal4 = low5 = notAssigned · Integer32

The priority level at which the process is running. This object is deprecated by cpmProcExtPriorityRev.

Gauge32 · bytes

The sum of all the dynamically allocated memory that this process has received from the system. This includes memory that may have been returned. The sum of freed memory is provided by cpmProcExtMemFreedRev. This object deprecates cpmProcExtMemAllocated.

Gauge32 · bytes

The sum of all memory that this process has returned to the system. This object deprecates cpmProcExtMemFreed.

Counter32

The number of times since cpmTimeCreated that the process has been invoked. This object deprecates cpmProcExtInvoked.

Counter32 · microseconds

The amount of CPU time the process has used, in microseconds. This object deprecates cpmProcExtRuntime.

Gauge32 (0..100) · percent

This object provides a general idea of how busy a process caused the processor to be over a 5 second period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object deprecates cpmProcExtUtil5Sec and increases the value range to (0..100).

Gauge32 (0..100) · percent

This object provides a general idea of how busy a process caused the processor to be over a 1 minute period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object deprecates cpmProcExtUtil1Min and increases the value range to (0..100).

Gauge32 (0..100) · percent

This object provides a general idea of how busy a process caused the processor to be over a 5 minute period. It is determined as a weighted decaying average of the current idle time over the longest idle time. Note that this information should be used as an estimate only. This object deprecates cpmProcExtUtil5Min and increases the value range to (0..100).

INTEGER1 = critical2 = high3 = normal4 = low5 = notAssigned · Integer32

The priority level at which the process is running. This object deprecates cpmProcExtPriority.

INTEGER1 = other2 = posix3 = ios · Integer32

This indicates the kind of process in context.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This indicates whether respawn of a process is enabled or not. If enabled the process in context repawns after it has crashed/stopped.

Counter32

This indicates the number of times the process has respawned/restarted.

Counter32

This indicates the number of times a process has restarted after the last patch is applied. This is to determine the stability of the last patch.

INTEGER1 = other2 = mainmem3 = mainmemSharedmem4 = mainmemText5 = mainmemTextSharedmem6 = sharedmem7 = sparse8 = off · Integer32

This indicates the part of process memory to be dumped when a process crashes. The process memory is used for debugging purposes to trace the root cause of the crash. sparse - Some operating systems support minimal dump of process core like register info, partial stack, partial memory pages especially for critical process to facilitate faster process restart.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This indicate the user that has last restarted the process or has taken running coredump of the process.

Unsigned32 · kilo-bytes

This indicates the text memory of a process and all its shared objects.

Gauge32 · kilo-bytes

This indicates the data segment of a process and all its shared objects.

Gauge32 · kilo-bytes

This indicates the amount of stack memory used by the process.

Gauge32 · kilo-bytes

This indicates the amount of dynamic memory being used by the process.

Gauge32 · bytes

This object represents the upper 32-bit of cpmProcExtMemAllocatedRev. This object needs to be supported only when the value of cpmProcExtMemAllocatedRev exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · bytes

The sum of all the dynamically allocated memory that this process has received from the system. This includes memory that may have been returned. This object is a 64-bit version of cpmProcExtMemAllocatedRev.

Gauge32 · bytes

This object represents the upper 32-bit of cpmProcExtMemFreedRev. This object needs to be supported only when the value of cpmProcExtMemFreedRev exceeds 32-bit,otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · bytes

The sum of all memory that this process has returned to the system. This object is a 64-bit version of cpmProcExtMemFreedRev.

Unsigned32 · kilo-bytes

This object represents the upper 32-bit of cpmProcessTextSegmentSize. This object needs to be supported only when the value of cpmProcessTextSegmentSize exceeds 32-bit, otherwise this object value would be set to 0.

Unsigned64An unsigned 64 bit integer. We use SYNTAX Counter64 for the encoding rules. (0..18446744073709551615) · Counter64 · kilo-bytes

This indicates the text memory of a process and all its shared objects. This object is a 64-bit version of cpmProcessTextSegmentSize.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmProcessDataSegmentSize. This object needs to be supported only when the value of cpmProcessDataSegmentSize exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

This indicates the data segment of a process and all its shared objects.. This object is a 64-bit version of cpmProcessDataSegmentSize.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmProcessStackSize. This object needs to be supported only when the value of cpmProcessStackSize exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

This indicates the amount of stack memory used by the process. This object is a 64-bit version of cpmProcessStackSize.

Gauge32 · kilo-bytes

This object represents the upper 32-bit of cpmProcessDynamicMemorySize. This object needs to be supported only when the value of cpmProcessDynamicMemorySize exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · kilo-bytes

This indicates the amount of dynamic memory being used by the process. This object is a 64-bit version of cpmProcessDynamicMemorySize.

INTEGER1 = total2 = interrupt3 = process · Integer32

Value of this object indicates the type of utilization, which is monitored. The total(1) indicates the total CPU utilization, interrupt(2) indicates the the CPU utilization in interrupt context and process(3) indicates the CPU utilization in the process level execution context.

Unsigned32 (1..100)

The percentage rising threshold value configured by the user. The value indicates, if the percentage CPU utilization is equal to or above this value for cpmCPURisingThresholdPeriod duration then send a cpmCPURisingThreshold notification to the NMS.

Unsigned32 (5..4294967295) · seconds

This is an observation interval. The value of this object indicates that the CPU utilization should be above cpmCPURisingThresholdValue for this duration to send a cpmCPURisingThreshold notification to the NMS.

Unsigned32 (1..100)

The percentage falling threshold value configured by the user. The value indicates, if the percentage CPU utilization is equal to or below this value for cpmCPUFallingThresholdPeriod duration then send a cpmCPUFallingThreshold notification to the NMS.

Unsigned32 (5..4294967295) · seconds

This is an observation interval. The value of this object indicates that CPU utilization should be below cpmCPUFallingThresholdValue for this duration to send a cpmCPURisingThreshold notification to the NMS.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this table entry.

Unsigned32

All the entries which are created at the same time will have same value for this object. When the configured threshold for being a part of History table is reached then the qualified processes become the part of history table. The entries which became the part of history table at one instant will have the same value for this object. When this object reaches the max index value then it will wrap around.

Unsigned32

The number of process entries in a report. This object gives information about how many processes became a part of history table at one instant.

Gauge32 (0..100) · percent

Total percentage of CPU utilization at cpmCPUHistoryCreated.

Gauge32 (0..100) · percent

Percentage of CPU utilization in the interrupt context at cpmCPUHistoryCreated.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Time stamp with respect to sysUpTime indicating the time at which this report is created.

Unsigned32 (1..4294967295)

An index that uniquely identifies an entry in the cmpCPUProcessHistory table among those in the same report. This index is between 1 to N, where N is the cpmCPUHistoryReportSize.

Unsigned32 (1..2147483647)

The process Id associated with this entry.

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

The process name associated with this entry.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time when the process was created. The process ID and the time when the process was created, uniquely identifies a process.

Gauge32 (0..100) · percent

The percentage CPU utilization of a process at cpmCPUHistoryCreatedTime.

Unsigned32

This object contains the thread ID. ThreadID is Unique per process.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object represents the name of the thread. Thread names need not be unique. Hence statistics should be analyzed against thread ID.

Unsigned32 (0..63)

This object indicates the priority of a POSIX thread. The higher the number, the higher the priority of the thread over other threads.

INTEGER1 = other2 = dead3 = running4 = ready5 = stopped6 = send7 = receive8 = reply9 = stack10 = waitpage11 = sigsuspend12 = sigwaitinfo13 = nanosleep14 = mutex15 = condvar16 = join17 = intr18 = sem · Integer32

This object indicates the current state of a thread. Running state means that the thread is actively consumig CPU. All the other states are just waiting states. The valid states are: other - Any other state apart from the listed ones. dead - Kernel is waiting to release the thread's resources. running - Actively running on a CPU. ready - Not running on a CPU, but is ready to run (one or more higher or equal priority threads are running). stopped - Suspended (SIGSTOP signal). send - Waiting for a server to receive a message. receive - Waiting for a client to send a message. reply - Waiting for a server to reply to a message. stack - Waiting for more stack to be allocated. waitpage - Waiting for process manager to resolve a fault on a page. sigsuspend - Suspended for a signal. sigwaitinfo - Waiting for a signal. nanosleep - Sleeping for a period of time. mutex - Waiting to acquire a mutex condvar - Waiting for a condition variable to be signalled. join - Waiting for the completion of another thread. intr - Waiting for an interrupt. sem - Waiting to acquire a semaphore.

RowPointerRepresents a pointer to a conceptual row. The value is the name of the instance of the first accessible columnar object in the conceptual row. For example, ifIndex.3 would point to the 3rd row in the ifTable (note that if ifIndex were not-accessible, then ifDescr.3 would be used instead). · OBJECT IDENTIFIER

This object identifies the process on which the current thread is blocked on. This points to the cpmProcessTable of the process on which the thread in context is blocked. This is valid only to threads which are either in send/reply states. For the rest of the threads it is returned as 0.0

Gauge32 · milliseconds

This object provides a general idea on how busy the thread in context caused the processor to be.

Gauge32 · bytes

This object indicates the stack size allocated to the thread in context.

Gauge32 · bytes

This object represents the upper 32-bit of cpmThreadStackSize. This object needs to be supported only when the value of cpmThreadStackSize exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · bytes

This object indicates the stack size allocated to the thread in context. This object is a 64-bit version of cpmThreadStackSize.

Unsigned32

This object indicates the process ID of a virtual process. PID is unique only inside one address space. Virtual process PID should be considered along with Parent process cpmProcessPID.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..32) · OCTET STRING · hint 255t

This object indicates the name of a virtual process. If the name is longer than 32 characters, it will be truncated to the first 31 characters, and a `*' will be appended as the last character to imply this is a truncated process name.

Gauge32 (0..100) · percent

This indicates an estimated CPU utilization by a virtual process over the last 5 seconds.

Gauge32 (0..100) · percent

This indicates an estimated CPU utilization by a virtual process over the last one minute.

Gauge32 (0..100) · percent

This indicates an estimated CPU utilization by a virtual process over the last 5 minutes.

Gauge32 · bytes

This object indicates the memory allocated by the virtual process inside the address space of a process running on Native OS.

Gauge32 · bytes

This object indicates the memory freed by the virtual process inside the address space of a process running on Native OS.

Counter32

The number of times a virtual process is invoked.

Counter32 · microseconds

The amount of CPU time a virtual process has used in microseconds.

Gauge32 · bytes

This object represents the upper 32-bit of cpmVirtualProcessMemAllocated. This object needs to be supported only when the value of cpmVirtualProcessMemAllocated exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · bytes

This object indicates the memory allocated by the virtual process inside the address space of a process running on Native OS. This object is a 64-bit version of cpmVirtualProcessMemAllocated.

Gauge32 · bytes

This object represents the upper 32-bit of cpmVirtualProcessMemFreed. This object needs to be supported only when the value of cpmVirtualProcessMemFreed exceeds 32-bit, otherwise this object value would be set to 0.

CounterBasedGauge64The CounterBasedGauge64 type represents a non-negative integer, which may increase or decrease, but shall never exceed a maximum value, nor fall below a minimum value. The maximum value can not be greater than 2^64-1 (18446744073709551615 decimal), and the minimum value can not be smaller than 0. The value of a CounterBasedGauge64 has its maximum value whenever the information being modeled is greater than or equal to its maximum value, and has its minimum value whenever the information being modeled is smaller than or equal to its minimum value. If the information being modeled subsequently decreases below (increases above) the maximum (minimum) value, the CounterBasedGauge64 also decreases (increases). Note that this TC is not strictly supported in SMIv2, because the 'always increasing' and 'counter wrap' semantics associated with the Counter64 base type are not preserved. It is possible that management applications which rely solely upon the (Counter64) ASN.1 tag to determine object semantics will mistakenly operate upon objects of this type as they would for Counter64 objects. This textual convention represents a limited and short-term solution, and may be deprecated as a long term solution is defined and deployed to replace it. (0..18446744073709551615) · Counter64 · bytes

This object indicates the memory freed by the virtual process inside the address space of a process running on Native OS.This object is a 64-bit version of cpmVirtualProcessMemAllocated.