EZ5 MIB Catalog

CISCO-ENHANCED-MEMPOOL-MIB

2008-12-05

New MIB module for monitoring the memory pools of all physical entities on a managed system.

Download CISCO-ENHANCED-MEMPOOL-MIB.txt Open CISCO-ENHANCED-MEMPOOL-MIB.txt in a new tab

SCALARS (1) · TABLES (3) · TRAPS (1)

Scalars (1)

NameOID
cempMemBufferNotifyEnabled1.3.6.1.4.1.9.9.221.1.2.1

Tables (3)

NameOID
cempMemPoolTable1.3.6.1.4.1.9.9.221.1.1.1
cempMemBufferPoolTable1.3.6.1.4.1.9.9.221.1.1.2
cempMemBufferCachePoolTable1.3.6.1.4.1.9.9.221.1.1.3

Traps (1)

NameOID
cempMemBufferNotify1.3.6.1.4.1.9.9.221.0.1

END OF TOC

Scalar details

cempMemBufferNotifyEnabled

1.3.6.1.4.1.9.9.221.1.2.1

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This variable controls generation of the cempMemBufferNotify. When this variable is 'true', generation of cempMemBufferNotify is enabled. When this variable is 'false', generation of cempMemBufferNotify is disabled.

Table details

cempMemPoolTable

1.3.6.1.4.1.9.9.221.1.1.1

Index: entPhysicalIndex · cempMemPoolIndex

A table of memory pool monitoring entries for all physical entities on a managed system.

from ENTITY-MIB

entPhysicalIndex

PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d

The index for this entry.

cempMemPoolIndex

1.3.6.1.4.1.9.9.221.1.1.1.1.1

CempMemPoolIndexA unique value, greater than zero, for each memory pool in a particular physical entity. It is recommended that values are assigned contiguously starting from 1 such that the index will be unique within a particular physical entity. (1..2147483647) · Integer32

Within each physical entity, the unique value greater than zero, used to represent each memory pool. It is recommended that values are assigned contiguously starting from 1.

cempMemPoolType

1.3.6.1.4.1.9.9.221.1.1.1.1.2

CempMemPoolTypes1 = other2 = processorMemory3 = ioMemory4 = pciMemory5 = fastMemory6 = multibusMemory7 = interruptStackMemory8 = processStackMemory9 = localExceptionMemory10 = virtualMemory11 = reservedMemory12 = imageMemory13 = asicMemory14 = posixMemoryRepresents the different types of memory pools that may be present in a managed device. Note that only the processor pool is required to be supported by all devices. Support for other pool types is dependent on the device being managed. processorMemory - processor associated heap memory. ioMemory - shared memory for buffer data and controller descriptor blocks. pciMemory - Peripheral Component Interconnect bus memory which is visible to all devices on the PCI buses in a platform. fastMemory - memory defined by the particular platform for speed critical applications. multibusMemory - memory present on some platforms that is used as a fallback pool. interruptStackMemory - memory for allocating interrupt stacks. It is usually allocated from heap. processStackMemory - memory for allocating process stacks. It is usually allocated from heap. localExceptionMemory - memory reserved for processing a system core dump. virtualMemory - memory used to increase available RAM. reservedMemory - memory used for packet headers, particle headers and particles. imageMemory - memory which corresponds to the image file system. asicMemory - Application Specific Integrated Circuit memory. posixMemory - Heap memory associated with posix style processes in ion. · Integer32

The type of memory pool for which this entry contains information.

cempMemPoolName

1.3.6.1.4.1.9.9.221.1.1.1.1.3

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

A textual name assigned to the memory pool. This object is suitable for output to a human operator, and may also be used to distinguish among the various pool types.

cempMemPoolPlatformMemory

1.3.6.1.4.1.9.9.221.1.1.1.1.4

AutonomousTypeRepresents an independently extensible type identification value. It may, for example, indicate a particular sub-tree with further MIB definitions, or define a particular type of protocol or hardware. · OBJECT IDENTIFIER

An indication of the platform-specific memory pool type. The associated instance of cempMemPoolType is used to indicate the general type of memory pool. If no platform specific memory hardware type identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.

cempMemPoolAlternate

1.3.6.1.4.1.9.9.221.1.1.1.1.5

CempMemPoolIndexOrNoneThis textual convention is an extension of the CempMemPoolIndex. The latter defines a value greater than zero to identify a memory pool in a particular physical entity. This extension permits the additional value of zero. The value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where memory pool was unknown, or when none or all memory pools need to be referenced. (0..2147483647) · Integer32

Indicates whether or not this memory pool has an alternate pool configured. Alternate pools are used for fallback when the current pool runs out of memory. If an instance of this object has a value of zero, then this pool does not have an alternate. Otherwise the value of this object is the same as the value of cempMemPoolType of the alternate pool.

cempMemPoolValid

1.3.6.1.4.1.9.9.221.1.1.1.1.6

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicates whether or not cempMemPoolUsed, cempMemPoolFree, cempMemPoolLargestFree and cempMemPoolLowestFree in this entry contain accurate data. If an instance of this object has the value false (which in and of itself indicates an internal error condition), the values of these objects in the conceptual row may contain inaccurate information (specifically, the reported values may be less than the actual values).

cempMemPoolUsed

1.3.6.1.4.1.9.9.221.1.1.1.1.7

Gauge32 · bytes

Indicates the number of bytes from the memory pool that are currently in use by applications on the physical entity.

cempMemPoolFree

1.3.6.1.4.1.9.9.221.1.1.1.1.8

Gauge32 · bytes

Indicates the number of bytes from the memory pool that are currently unused on the physical entity. Note that the sum of cempMemPoolUsed and cempMemPoolFree is the total amount of memory in the pool

cempMemPoolLargestFree

1.3.6.1.4.1.9.9.221.1.1.1.1.9

Gauge32 · bytes

Indicates the largest number of contiguous bytes from the memory pool that are currently unused on the physical entity.

cempMemPoolLowestFree

1.3.6.1.4.1.9.9.221.1.1.1.1.10

Gauge32 · bytes

The lowest amount of available memory in the memory pool recorded at any time during the operation of the system.

cempMemPoolUsedLowWaterMark

1.3.6.1.4.1.9.9.221.1.1.1.1.11

Gauge32

Indicates the lowest number of bytes from the memory pool that have been used by applications on the physical entity since sysUpTime.Similarly,the Used High Watermark indicates the largest number of bytes from the memory pool that have been used by applications on the physical entity since sysUpTime.This can be derived as follows: Used High Watermark = cempMemPoolUsed + cempMemPoolFree - cempMemPoolLowestFree.

cempMemPoolAllocHit

1.3.6.1.4.1.9.9.221.1.1.1.1.12

Counter32

Indicates the number of successful allocations from the memory pool

cempMemPoolAllocMiss

1.3.6.1.4.1.9.9.221.1.1.1.1.13

Counter32

Indicates the number of unsuccessful allocations from the memory pool

cempMemPoolFreeHit

1.3.6.1.4.1.9.9.221.1.1.1.1.14

Counter32

Indicates the number of successful frees/ deallocations from the memory pool

cempMemPoolFreeMiss

1.3.6.1.4.1.9.9.221.1.1.1.1.15

Counter32

Indicates the number of unsuccessful attempts to free/deallocate memory from the memory pool. For example, this could be due to ownership errors where the application that did not assign the memory is trying to free it.

cempMemPoolShared

1.3.6.1.4.1.9.9.221.1.1.1.1.16

Gauge32 · bytes

Indicates the number of bytes from the memory pool that are currently shared on the physical entity.

cempMemPoolUsedOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.17

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolUsed. This object needs to be supported only if the used bytes in the memory pool exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCUsed

1.3.6.1.4.1.9.9.221.1.1.1.1.18

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

Indicates the number of bytes from the memory pool that are currently in use by applications on the physical entity. This object is a 64-bit version of cempMemPoolUsed.

cempMemPoolFreeOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.19

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolFree. This object needs to be supported only if the unused bytes in the memory pool exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCFree

1.3.6.1.4.1.9.9.221.1.1.1.1.20

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

Indicates the number of bytes from the memory pool that are currently unused on the physical entity. This object is a 64-bit version of cempMemPoolFree.

cempMemPoolLargestFreeOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.21

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolLargestFree. This object needs to be supported only if the value of cempMemPoolLargestFree exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCLargestFree

1.3.6.1.4.1.9.9.221.1.1.1.1.22

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

Indicates the largest number of contiguous bytes from the memory pool that are currently unused on the physical entity. This object is a 64-bit version of cempMemPoolLargestFree.

cempMemPoolLowestFreeOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.23

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolLowestFree. This object needs to be supported only if the value of cempMemPoolLowestFree exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCLowestFree

1.3.6.1.4.1.9.9.221.1.1.1.1.24

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 lowest amount of available memory in the memory pool recorded at any time during the operation of the system. This object is a 64-bit version of cempMemPoolLowestFree.

cempMemPoolUsedLowWaterMarkOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.25

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolUsedLowWaterMark. This object needs to be supported only if the value of cempMemPoolUsedLowWaterMark exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCUsedLowWaterMark

1.3.6.1.4.1.9.9.221.1.1.1.1.26

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

Indicates the lowest number of bytes from the memory pool that have been used by applications on the physical entity since sysUpTime. This object is a 64-bit version of cempMemPoolUsedLowWaterMark.

cempMemPoolSharedOvrflw

1.3.6.1.4.1.9.9.221.1.1.1.1.27

Gauge32 · bytes

This object represents the upper 32-bits of cempMemPoolShared. This object needs to be supported only if the value of cempMemPoolShared exceeds 32-bits, otherwise this object value would be set to 0.

cempMemPoolHCShared

1.3.6.1.4.1.9.9.221.1.1.1.1.28

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

Indicates the number of bytes from the memory pool that are currently shared on the physical entity. This object is a 64-bit version of cempMemPoolShared.

cempMemBufferPoolTable

1.3.6.1.4.1.9.9.221.1.1.2

Index: entPhysicalIndex · cempMemBufferPoolIndex

Entries in this table define entities (buffer pools in this case) which are contained in an entity (memory pool) defined by an entry from cempMemPoolTable. -- Basic Pool Architecture -- 1)Pools are classified as being either Static or Dynamic. Static pools make no attempt to increase the number of buffers contained within them if the number of free buffers (cempMemBufferFree) are less than the number of minimum buffers (cempMemBufferMin). With Dynamic pools, the pool attempts to meet the demands of its users. 2)Buffers in a pool are classified as being either Permanent or Temporary. Permanent buffers, as their name suggests, are always in the pool and are never destroyed unless the number of permanent buffers (cempMemBufferPermanent) is changed. Temporary buffers are transient buffers that are created in dynamic pools whenever the free count (cempMemBufferFree) of buffers in the pool drops below the minimum (cempMemBufferMin). 3)Buffers pools are classified as either Public or Private. Public pools are available for all users to allocate buffers from. Private pools are primarily used by interface drivers.

from ENTITY-MIB

entPhysicalIndex

PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d

The index for this entry.

cempMemBufferPoolIndex

1.3.6.1.4.1.9.9.221.1.1.2.1.1

CempMemBufferPoolIndexA unique value, greater than zero, for each buffer pool in the memory pool on a physical entity. It is recommended that values are assigned contiguously starting from 1 such that the index will be unique within a physical entity. Note that the index does not overlap among different memory pools. (1..4294967295) · Unsigned32

Within a physical entity, a unique value used to represent each buffer pool.

cempMemBufferMemPoolIndex

1.3.6.1.4.1.9.9.221.1.1.2.1.2

CempMemPoolIndexA unique value, greater than zero, for each memory pool in a particular physical entity. It is recommended that values are assigned contiguously starting from 1 such that the index will be unique within a particular physical entity. (1..2147483647) · Integer32

This index corresponds to the memory pool (with cemMemPoolIndex as index in cempMemPoolTable) from which buffers are allocated.

cempMemBufferName

1.3.6.1.4.1.9.9.221.1.1.2.1.3

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

A textual name assigned to the buffer pool. This object is suitable for output to a human operator, and may also be used to distinguish among the various buffer types. For example: 'Small', 'Big', 'Serial0/1' etc.

cempMemBufferDynamic

1.3.6.1.4.1.9.9.221.1.1.2.1.4

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Boolean poolDynamic; if TRUE, the number of buffers in the pool is adjusted (adding more packet buffers or deleting excesses) dynamically by the background process. If FALSE, the number of buffers in the pool is never adjusted, even if it falls below the minimum, or to zero.

cempMemBufferSize

1.3.6.1.4.1.9.9.221.1.1.2.1.5

Unsigned32 · bytes

Indicates the size of buffer element in number of bytes on the physical entity.

cempMemBufferMin

1.3.6.1.4.1.9.9.221.1.1.2.1.6

Unsigned32

Indicates the minimum number of free buffers allowed in the buffer pool or low-water mark (lwm). For example of its usage : If cempMemBufferFree < cempMemBufferMin & pool is dynamic, then signal for growth of particular buffer pool.

cempMemBufferMax

1.3.6.1.4.1.9.9.221.1.1.2.1.7

Unsigned32

Indicates the maximum number of free buffers allowed in the buffer pool or high-water mark (hwm). For example of its usage : If cempMemBufferFree > cempMemBufferMax & pool is dynamic, then signal for trim of particular buffer pool.

cempMemBufferPermanent

1.3.6.1.4.1.9.9.221.1.1.2.1.8

Unsigned32

Indicates the total number of permanent buffers in the pool on the physical entity.

cempMemBufferTransient

1.3.6.1.4.1.9.9.221.1.1.2.1.9

Unsigned32

Indicates the initial number of temporary buffers in the pool on the physical entity. This object instructs the system to create this many number of temporary extra buffers, just after a system restart. A change in this object will be effective only after a system restart.

cempMemBufferTotal

1.3.6.1.4.1.9.9.221.1.1.2.1.10

Gauge32

Indicates the total number of buffers (include allocated and free buffers) in the buffer pool on the physical entity.

cempMemBufferFree

1.3.6.1.4.1.9.9.221.1.1.2.1.11

Gauge32

Indicates the current number of free buffers in the buffer pool on the physical entity. Note that the cempMemBufferFree is less than or equal to cempMemBufferTotal.

cempMemBufferHit

1.3.6.1.4.1.9.9.221.1.1.2.1.12

Counter32

Indicates the number of buffers successfully allocated from the buffer pool.

cempMemBufferMiss

1.3.6.1.4.1.9.9.221.1.1.2.1.13

Counter32

Indicates the number of times a buffer has been requested, but no buffers were available in the buffer pool, or when there were fewer than min buffers(cempMemBufferMin) in the buffer pool. Note : For interface pools, a miss is actually a fall back to its corresponding public buffer pool.

cempMemBufferFreeHit

1.3.6.1.4.1.9.9.221.1.1.2.1.14

Counter32

Indicates the number of successful frees/deallocations from the buffer pool.

cempMemBufferFreeMiss

1.3.6.1.4.1.9.9.221.1.1.2.1.15

Counter32

Indicates the number of unsuccessful attempts to free/deallocate a buffer from the buffer pool. For example, this could be due to ownership errors where the application that did not assign the buffer is trying to free it.

cempMemBufferPermChange

1.3.6.1.4.1.9.9.221.1.1.2.1.16

Integer32

This value is the difference of the desired number of permanent buffer & total number of permanent buffers present in the pool. A positive value of this object tells the number of buffers needed & a negative value of the object tells the extra number of buffers in the pool.

cempMemBufferPeak

1.3.6.1.4.1.9.9.221.1.1.2.1.17

Counter32

Indicates the peak number of buffers in pool on the physical entity.

cempMemBufferPeakTime

1.3.6.1.4.1.9.9.221.1.1.2.1.18

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

Indicates the time of most recent change in the peak number of buffers (cempMemBufferPeak object) in the pool.

cempMemBufferTrim

1.3.6.1.4.1.9.9.221.1.1.2.1.19

Counter32

The number of buffers that have been trimmed from the pool when the number of free buffers (cempMemBufferFree) exceeded the number of max allowed buffers(cempMemBufferMax).

cempMemBufferGrow

1.3.6.1.4.1.9.9.221.1.1.2.1.20

Counter32

The number of buffers that have been created in the pool when the number of free buffers(cempMemBufferFree) was less than minimum(cempMemBufferMix).

cempMemBufferFailures

1.3.6.1.4.1.9.9.221.1.1.2.1.21

Counter32

The number of failures to grant a buffer to a requester due to reasons other than insufficient memory. For example, in systems where there are different execution contexts, it may be too expensive to create new buffers when running in certain contexts. In those cases it may be preferable to fail the request.

cempMemBufferNoStorage

1.3.6.1.4.1.9.9.221.1.1.2.1.22

Counter32

The number of times the system tried to create new buffers, but could not due to insufficient free memory in the system.

cempMemBufferCachePoolTable

1.3.6.1.4.1.9.9.221.1.1.3

Index: entPhysicalIndex · cempMemBufferPoolIndex

A table that lists the cache buffer pools configured on a managed system. 1)To provide a noticeable performance boost, Cache Pool can be used. A Cache Pool is effectively a lookaside list of free buffers that can be accessed quickly. Cache Pool is tied to Buffer Pool. 2)Cache pools can optionally have a threshold value on the number of cache buffers used in a pool. This can provide flow control management by having a implementation specific approach such as invoking a vector when pool cache rises above the optional threshold set for it on creation.

from ENTITY-MIB

entPhysicalIndex

PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d

The index for this entry.

cempMemBufferCacheSize

1.3.6.1.4.1.9.9.221.1.1.3.1.1

Unsigned32

Indicates the number of buffers in the cache pool on the physical entity.

cempMemBufferCacheTotal

1.3.6.1.4.1.9.9.221.1.1.3.1.2

Gauge32

Indicates the maximum number of free buffers allowed in the cache pool.

cempMemBufferCacheUsed

1.3.6.1.4.1.9.9.221.1.1.3.1.3

Gauge32

Indicates the number of cache buffers from the pool that are currently used on the physical entity. Note that the cempMemBufferCacheUsed is less than or equal to cempMemBufferCacheTotal.

cempMemBufferCacheHit

1.3.6.1.4.1.9.9.221.1.1.3.1.4

Counter32

Indicates the number of buffers successfully allocated from the cache pool.

cempMemBufferCacheMiss

1.3.6.1.4.1.9.9.221.1.1.3.1.5

Counter32

Indicates the number of times a buffer has been requested, but no buffers were available in the cache pool.

cempMemBufferCacheThreshold

1.3.6.1.4.1.9.9.221.1.1.3.1.6

Gauge32

Indicates the threshold limit for number of cache buffers used(cempMemBufferCacheUsed).

cempMemBufferCacheThresholdCount

1.3.6.1.4.1.9.9.221.1.1.3.1.7

Counter32

Indicates how many times the number of cache buffers used(cempMemBufferCacheUsed) has crossed the threshold value(cempMemBufferCacheThreshold).

Trap details

cempMemBufferNotify

1.3.6.1.4.1.9.9.221.0.1

Whenever cempMemBufferPeak object is updated in the buffer pool, a cempMemBufferNotify notification is sent. The sending of these notifications can be enabled/disabled via the cempMemBufferNotifyEnabled object.

cempMemBufferName

1.3.6.1.4.1.9.9.221.1.1.2.1.3

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

A textual name assigned to the buffer pool. This object is suitable for output to a human operator, and may also be used to distinguish among the various buffer types. For example: 'Small', 'Big', 'Serial0/1' etc.

cempMemBufferPeak

1.3.6.1.4.1.9.9.221.1.1.2.1.17

Counter32

Indicates the peak number of buffers in pool on the physical entity.

cempMemBufferPeakTime

1.3.6.1.4.1.9.9.221.1.1.2.1.18

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

Indicates the time of most recent change in the peak number of buffers (cempMemBufferPeak object) in the pool.

↑ To TOC