EMPIRE
Detailed view of the defined objects, syntax rules, and hierarchical paths.
281
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
281 total| Object Name |
|---|
empire OBJECT IDENTIFIER .1.3.6.1.4.1.546 |
IMPORTS Unknown .1.3.6.1.4.1.546 |
unix OBJECT IDENTIFIER .1.3.6.1.4.1.546.1 |
sysmgmt OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1 |
system OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.1 |
nodenameThe name of the system that the agent is
running on as given by the login prompt.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.1 |
cpuThe CPU type of the system that the agent is
running on (e.g. sun4c, sun4m).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.2 |
memoryThe amount of memory in 1024 byte units
contained in the system.ro INTEGER .1.3.6.1.4.1.546.1.1.1.3 |
hostidThe hostid number that resides on the mother
board of the system that the agent is running
on. The hostid is unique across all machines
manufactured by the same vendor.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.4 |
osverThe operating system version of the system
that the agent resides (e.g. 7). Each time a
new kernel is re-linked for a given kernel
configuration file, this number is incremented.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.5 |
osrelThe operating system release of the system
that the agent resides (e.g. 4.1.3).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.6 |
devTableThis table describes all mounted file systems
on the system that the agent resides. SEQUENCE OF DevTableEntry .1.3.6.1.4.1.546.1.1.1.7 |
devTableEntryAn entry in the device table. DevTableEntry .1.3.6.1.4.1.546.1.1.1.7.1 |
devIndexThis object does not describe the mounted
device. Its sole purpose is to indicate the
row instance. The instance is derived from
the index number from the mounted file systems
file.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.1 |
devDeviceThe device name (e.g. /dev/sd0a)
corresponding to the mounted file system.
For example, the '/' file system is commonly
mounted from the device '/dev/sd0a'. For
network file systems, the value corresponds
to the remote host and remote file system
name (e.g. emptech:/usr/local).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.7.1.2 |
devMntPtThe mount point or path name in the local
file system where the device is mounted (e.g.
/home).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.7.1.3 |
devBsizeThe block size of the mounted device in
bytes. File systems and disk devices
generally allocate data in fixed size
'blocks' generally referred to as the device's
block size. Common block sizes are 1024 (1K) and
2048 (2K) bytes.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.4 |
devTblksThe total number of blocks contained in the
mounted device.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.5 |
devFblksThe total number of free or unallocated
blocks in the mounted device.ro Gauge .1.3.6.1.4.1.546.1.1.1.7.1.6 |
devTfilesEach disk device and file system allocates a
fixed, maximum number of files that can be
written to the device. The value of this
object indicates the maximum number of files
that can be written to this device.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.7 |
devFfilesThe number of free or unallocated files that
can be created on this device.ro Gauge .1.3.6.1.4.1.546.1.1.1.7.1.8 |
devMaxNameLenThe maximum file name length that this mounted
device supports. If no fixed limit exists, 0
is returned.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.9 |
devTypeThe type of the mounted device. If this
underlying device does not support feature, 0
is returned.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.7.1.10 |
devFsidThe (possibly unique) file system ID of the
mounted device. V.4 systems support its
uniqueness while SunOS does not. For devices
or operating systems not supporting this
object, the object instance identifier is
returned instead.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.11 |
devFstrSome devices support a description string.
If supported by the underlying device and
operating system, that device specific
description string is returned. If not
supported, the string 'Not supported' is
returned. An example description string may
be 'User home directories'.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.7.1.12 |
devUnmountWriting a delete(1) to this object causes the agent
to unmount this device and remove its entry
from the mounted file system table. Writing any
other value to this object will cause no
action to be taken by the agent.rw DeleteButtonType SYNTAX INTEGER { delete(1), valid(2) } .1.3.6.1.4.1.546.1.1.1.7.1.13 |
devCapacityThe percentage of the device's total capacity
in use.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.14 |
devInodeCapacityThe percentage of the device's total file capacity
(inodes) in use. File systems often place an
upper bound on the number of files that can be
created on a filesystem. This value indicates the
percentage of total possible files that are in
use. Many times, NFS clients cannot determine
this value for remotely mounted filesystems; in
that case, 0 is returned.ro INTEGER .1.3.6.1.4.1.546.1.1.1.7.1.15 |
agentVersionThe agent's description and software version
number (e.g 'Concord . . . Ver 4.1').ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.8 |
kernelConfig OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.1.9 |
maxProcsMaximum number of slots in the system process
table or simply, the maximum number of
processes that may run at any one time on the
system.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.1 |
serialNumberThe system's serial number. This number is
different from the system's hostid value; it
should be unique across all platforms
manufactured by the same vendor.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.2 |
romVersionThe system's ROM version number (e.g 2.6).
Different versions of ROM often support
different commands and options. Knowing the
system's ROM version number is often helpful
in debugging operating system problems.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.9.3 |
numCPUThe number of CPUs contained within this host.ro Gauge .1.3.6.1.4.1.546.1.1.1.9.4 |
clockHZThe system's clock or 'tick' rate in HZ.
This is the rate at operating system is given
regularly, periodic interrupts in order to
handle I/O, schedule processes, etc. This
value should not be confused with the CPU
clock speed which is generally on the order
mega-hertz.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.5 |
kernelVersThe kernel version; This description string
is compiled into the kernel at kernel build
time and is generally used to convey
information about its functionality, patch
level, or administrative domain.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.9.6 |
virtualMemThe amount of virtual memory in 1024 byte
units (KBytes).ro Gauge .1.3.6.1.4.1.546.1.1.1.9.7 |
maxInodeMaximum number of in core file inodes
allocated by this host. An inode is a data
structure used by a file system to describe a
file. Part of it is cached in memory (in
core) while the other is stored on disk; the
kernel allocates a fixed amount of these
structures at kernel boot time for use with
file I/O.ro Gauge .1.3.6.1.4.1.546.1.1.1.9.8 |
maxFilesMaximum number of open files the system can
support at any one time. The kernel
pre-allocates, at kernel boot time, a table
of structures for file I/O. If the kernel does
not place any upper bound (e.g. Solaris 2.x), than
0 is returned.ro Gauge .1.3.6.1.4.1.546.1.1.1.9.9 |
maxClistThe maximum number of 'clist' structures
allocated by the kernel. Line disciplines,
like terminals, manipulate data on 'clists'
which are essentially linked-lists of data
heading to and from terminal or serial
devices. If the underlying operating system
does not utilize 'clists', then 0 is returned.ro Gauge .1.3.6.1.4.1.546.1.1.1.9.10 |
maxMemPerProcMaximum memory per process in KBytes.
Operating systems often set an upper limit on
the amount of memory a process may use. If
the underlying operating system does not set
such a limit, than 0 is returned.ro Gauge .1.3.6.1.4.1.546.1.1.1.9.11 |
totalSwapTotal system swap space in KBytes. Swap is a
region on secondary storage (primarily disks)
that is used for swapping and paging.
Swapping is a memory management policy in
which entire processes are written to
secondary storage when memory is in short
supply. When a process begins, all its pages
are in virtual memory; only those pages
actively being used are brought in from disk
or swap.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.12 |
openMaxPerProcMaximum number of open files per process.
Each process is generally given a limit on
the maximum number of files it may have open
at any one time. If the operating system
does not impose such limits, the value 0 is
returned.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.13 |
posixJobCtrlBoolean variable indicating if Posix Job
Control supported. POSIX, an IEEE standard,
defines a portable, open interface to
operating systems. Part of the specification
includes the definition of support for
advanced job control. This value indicates
whether the system supports POSIX-style job
control.ro Enumeration .1.3.6.1.4.1.546.1.1.1.9.14 |
posixVersionThe POSIX version number supported by host operating
system. As new versions of POSIX are
released, it may be important to monitor
which host supports which version of the
POSIX standard.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.15 |
pageSizeThis object returns the number of bytes in a
page; a 'page' is the fixed size unit of
measurement when dealing with both virtual
and physical memory. Page granularity is the
granularity of many of the memory statistics
and objects throughout the Concord MIB. This
page size is an operating system page size
and may not correspond to the underlying
hardware page size.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.16 |
wordSizeThis object returns the kernel word size.
For example, if Solaris is booted with a
64 bit kernel, this object would return
64. If Solaris is booted with a 32 bit
kernel, this object would return 32.
This object is available in SystemEDGE
4.1 and higher.ro INTEGER .1.3.6.1.4.1.546.1.1.1.9.17 |
bootconf OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.1.10 |
rootNameThe Device and partition (e.g. sd0a) that the root
filesystem is mounted from.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.1 |
rootFSTypeThe root filesystem type (e.g. 4.2).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.2 |
rootBlocksThe total number of blocks contained in the
root filesystem. The value 0 is returned if
unknown.ro INTEGER .1.3.6.1.4.1.546.1.1.1.10.3 |
dumpNameThe device and partition (e.g. sd0b) that the
dump filesystem is mounted from. 'Dump' is a
area of secondary storage reserved by the
operating system so that it may write
diagnostic information in the event of a
kernel crash.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.4 |
dumpFSTypeThe dump filesystem type (e.g. spec). Dump
is generally not a 'normal' file system like
UFS, 4.2, etc.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.5 |
dumpBlocksThe total number of blocks contained in the
dump filesystem.ro INTEGER .1.3.6.1.4.1.546.1.1.1.10.6 |
swapNameThe device and partition (e.g. sd0b) that
serves as swap space for the running kernel.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.7 |
swapFSTypeThe swap filesystem type (e.g. spec). Swap
space is not generally a typical file system
like UFS, 4.2, etc.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.10.8 |
swapSizeThe total number of blocks contained in the kernel's
swap area.ro INTEGER .1.3.6.1.4.1.546.1.1.1.10.9 |
streams OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.1.11 |
maxmsgSizeThe maximum Streams message size in bytes.
Streams often places a limit on the size of
an individual message. If the underlying
system does not place such a limit, 0 is
returned.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.1 |
maxNumPushMaximum number of Streams modules that may be
'pushed' onto an individual stream at any one
time. If the underlying system does not
define such a limit, 0 is returned.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.2 |
numMuxLinksNumber of Streams multiplexor links.ro Gauge .1.3.6.1.4.1.546.1.1.1.11.3 |
streamUseCurrent number of open 'streams' in the
system. Operating systems often place a
limit on the number of streams that may be in
use at any one time. Monitoring this variable
and streamMax can indicate if additional
streams should be configured.ro Gauge .1.3.6.1.4.1.546.1.1.1.11.4 |
streamMaxsThe largest number of open 'streams' recorded
by the system. This value represents a
'high-water' mark.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.5 |
streamFailsThe number of 'stream' allocation failures
that have occurred. Monitoring the streamUse,
streamMax, and streamFail variables can help
determine if the Streams subsystem is
properly configured.ro Counter .1.3.6.1.4.1.546.1.1.1.11.6 |
queueUseNumber of Streams queues currently in use by
the system. Streams are composed of queues,
one for each direction of data flow. The
value of this variable indicates the number
of queue data structures currently in use.ro Gauge .1.3.6.1.4.1.546.1.1.1.11.7 |
queueMaxsThe largest number of open 'streams' recorded by
the system. This value represents the
'high-water' mark.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.8 |
queueFailsThe number of Streams queue allocation
failures. Monitoring the queueUse, queueMax,
and queueFail variables can help determine if
the Streams subsystem is properly configured.ro Counter .1.3.6.1.4.1.546.1.1.1.11.9 |
mblockUseThe number of Streams message blocks currently in
use. Streams messages are composed of
message-blocks in a linked-list. The value
of this variable indicates how many of the
systems message blocks are in use.ro Gauge .1.3.6.1.4.1.546.1.1.1.11.10 |
mblockMaxsThe largest number of Streams message blocks in use
at any one time. This value represents a
'high-water' mark.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.11 |
mblockFailsThe number of Streams message block allocation
failures. Monitoring the mblockUse,
mblockMax, and mblockFail variables can help
determine if the Streams subsystem is
properly configured.ro Counter .1.3.6.1.4.1.546.1.1.1.11.12 |
dblockUseThe number of Streams data blocks currently
in use. Message data is stored in
data-blocks; the value of this variable
indicates how many of the data-blocks are
currently in use.ro Gauge .1.3.6.1.4.1.546.1.1.1.11.13 |
dblockMaxsThe largest number of Streams data blocks in use
at any one time. This value represents a
'high-water' mark.ro INTEGER .1.3.6.1.4.1.546.1.1.1.11.14 |
dblockFailsThe number of Streams data block allocation
failures. Monitoring the dblockUse,
dblockMax, and dblockFail variables can help
determine if the Streams subsystem is
properly configured.ro Counter .1.3.6.1.4.1.546.1.1.1.11.15 |
systemTypeThe underlying system (hardware/OS) typero Enumeration .1.3.6.1.4.1.546.1.1.1.12 |
systemEdgeUptimeThe SystemEDGE agent's uptime. Use for uptime
calculations with variables in the Concord MIB.
This is the same value as returned by the uptime
value in MIB2. However, on some platforms (e.g. NT),
that value is not returned by SystemEDGE and is
thus inconsistent with the SystemEDGE uptime.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.546.1.1.1.13 |
sysedgeLicenseStringThis object is used in conjunction Concord's
auto-licensing and remote licensing facility
starting in SystemEDGE 4.0.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.14 |
sysedgeLicenseKeyThis object is used in conjunction Concord's
auto-licensing and remote licensing facility
starting in SystemEDGE 4.0.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.16 |
sysedgeModeThis object indicates if SystemEDGE is in
full-mode or restricted-mode. Restricted-mode
is entered, when SystemEDGE 4.0 and higher,
fails to find a valid license. Once
a valid license has been allocated and
set, SystemEDGE will then transition to
fullMode(1)ro Enumeration .1.3.6.1.4.1.546.1.1.1.17 |
systemTimeZoneThe timezone this system is in obtained via
TZ environment variable (UNIX) or NT win32
call. If SystemEDGE is unable to determine the
timezone, 'unknown' is returned. This value
is operating-system depdendent in that each
OS often has slightly different names for same
timezone.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.18 |
sysedgeAddressListThe space-separated list of up to 5 past IP
addresses that this system was configured for.
This MIB object, when used with the
addrChangeTrap, is useful to pollers trying to poll
client machines whose addresses change due to DHCP or
with mobile systems or those whose configuration
changes over time. Addresses are ordered with
most-recently from most-recently used to
least-recently used (left to right).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.19 |
sysedgeFQDNThe system's fully qualified domain name (FQDN);
this MIB object is a duplicate of
mib-2.system.sysName but is repeated here for
platform consistency (e.g. NT vs. UNIX).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.20 |
sysedgeConfProfileA space-separated list of configuration profile
names currently configured in SystemEDGE.
Configuration profiles are managed by AdvantEDGE
View; AdvantEDGE View uses this MIB object to
store, with each agent, which profiles are
currently deployed to that agent. Writing to or
modifying this variable outside of AdvantEDGE View
is strongly discouraged. This MIB variable should
not contain single nor double quotations.rw DisplayString .1.3.6.1.4.1.546.1.1.1.21 |
sysedgeInstallDirThe directory where the SystemEDGE distribution is
installed (e.g. c:\sysedge or /opt/EMPsysedge).
One can use this value to help configure actions,
extensions, etc.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.22 |
sysedgePluginListA comma-separated list of plugins that are
currently loaded into SystemEDGE. Management
software can use this MIB object to determine
installation and upgrade requirements. If no
plugins are loaded, a zero-length string is
returned.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.1.23 |
userTableTable describing defined users of the node
which the agent resides on. Normally, the
list of valid users is stored in the
/etc/passwd file; on systems which run NIS or
NIS+, this table represents both users in the
/etc/passwd file and in the NIS passwd file. SEQUENCE OF UserEntry .1.3.6.1.4.1.546.1.1.2 |
userEntryAn entry in the table describing defined users. UserEntry .1.3.6.1.4.1.546.1.1.2.1 |
userIndexThe instance of the userEntry object, derived
from its index number in the password file.ro INTEGER .1.3.6.1.4.1.546.1.1.2.1.1 |
userLoginIDThe user's login ID which is normally given
to the system's login prompt (e.g. root).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.2.1.2 |
userPasswdThe user's encrypted password. Users without
passwords have an '*' in this field.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.2.1.3 |
userUIDThe user's User-ID or UID (e.g. 0).ro INTEGER .1.3.6.1.4.1.546.1.1.2.1.4 |
userGIDThe user's Group-ID or GID (e.g. 1).ro INTEGER .1.3.6.1.4.1.546.1.1.2.1.5 |
userNameThe user's real life name (e.g. John Doe).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.2.1.6 |
userHomeDirThe user's home directory when that user logs
in (e.g. /home/john).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.2.1.7 |
userShellThe user's preferred shell (e.g. /bin/csh).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.2.1.8 |
groupTableTable describing defined groups on node that
agent resides. Normally the list of valid
user groups is stored in the file /etc/group.
On systems running NIS or NIS+, this table
represents valid groups in /etc/group and in
the NIS group file. SEQUENCE OF GroupEntry .1.3.6.1.4.1.546.1.1.3 |
groupEntryEntry in table describing valid groups. GroupEntry .1.3.6.1.4.1.546.1.1.3.1 |
groupIndexThe instance of the groupEntry object,
derived from its index in the groups file.ro INTEGER .1.3.6.1.4.1.546.1.1.3.1.1 |
groupNameThe name of the group (e.g. wheel).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.3.1.2 |
groupPasswdThe encrypted password for the group. Groups
without passwords have an '*' in this field.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.3.1.3 |
groupGIDThe group-ID or GID (e.g. 1).ro INTEGER .1.3.6.1.4.1.546.1.1.3.1.4 |
processTableTable describing currently running processes
on the node which the SNMP agent resides. SEQUENCE OF ProcessEntry .1.3.6.1.4.1.546.1.1.4 |
processEntryEach entry in the process table represents a
single running process. Because the SNMP standard
does not allow tables to be indexed with the value
0, and because PID 0 is valid on many UNIX and NT
systems, SystemEDGE really indexes the
processTable with processID+1. That is, process
with PID 0 is contained at table index 1. ProcessEntry .1.3.6.1.4.1.546.1.1.4.1 |
processIDThe unique process ID (e.g. 0). The value of this
object also serves as the instance of the
processEntry object.ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.1 |
processNameThe name of the running process (e.g. swapper).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.4.1.2 |
processStateThe process state is operating system
dependent. Possible states (for SunOS 4.1.3)
include sleeping(1), waiting(2), running (3),
idle (4), zombie (5), stopped(6), unknown(7).
This MIB object should be deprecated in favor
of processStateStr which is portable and
standard across all platforms. processState
values are platform specific and thus harder
to handle in platform-independent manner.rodeprecated INTEGER .1.3.6.1.4.1.546.1.1.4.1.3 |
processNiceThe 'nice' value of the process which can be
modified to give a process greater or lesser
priority over other processes. The 'nice'
value reflects the level of priority that the
running process has; the higher the value,
the lower the priority the process has.rw INTEGER .1.3.6.1.4.1.546.1.1.4.1.4 |
processFlagsThe process flags; flags are operating system
dependent and are generally documented in
system header files.ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.5 |
processUIDThe process owner's user ID (e.g. 0 for root).ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.6 |
processGIDThe process owner's group ID (e.g. 0 for wheel).ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.7 |
processKillThis object represents a signal that can be
sent to the running process. When accessed
with GET or GetNext, a 0 is returned. When a
valid signal value is written, the agent
sends that signal to the corresponding process.
To kill or delete a process from the process
table, the value corresponding to SIGKILL(9)
should be written to this object. Signals
are defined in a system dependent manner and
are usually defined in system header files
and manual pages.rw INTEGER .1.3.6.1.4.1.546.1.1.4.1.8 |
processMEMThe percentage (0-100) of real memory used by
this process.ro Gauge .1.3.6.1.4.1.546.1.1.4.1.9 |
processSizeThe combined size of the text, data and stack segments
in KBytes. Processes are normally broken
into segments including those for text (or
program), data, and stack. This variable
indicates how large the variable size portion
of a process is. Monitoring this value can
help determine the health of a process.ro Gauge .1.3.6.1.4.1.546.1.1.4.1.10 |
processRSSReal memory (resident set) size of the process in
kilobytes. This value indicates how many
bytes are held by a process.ro Gauge .1.3.6.1.4.1.546.1.1.4.1.11 |
processTimeThis process' accumulated CPU time in seconds.ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.12 |
processParentPIDThis process' parent process ID (PID).ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.13 |
processNumThreadsThe number of threads executing within this
process. Note, on some systems, the operating
system may be un-aware of user-level threads
executing within the process. This object
reflects the number of threads executing within
the process that the operating system is aware of.ro INTEGER .1.3.6.1.4.1.546.1.1.4.1.14 |
processInBlksThe number of blocks of data input by the process.ro Counter .1.3.6.1.4.1.546.1.1.4.1.15 |
processOutBlksThe number of blocks of data output by the process.ro Counter .1.3.6.1.4.1.546.1.1.4.1.16 |
processMsgsSentThe number of messages sent by the process.ro Counter .1.3.6.1.4.1.546.1.1.4.1.17 |
processMsgsRecvThe number of messages received by the process.ro Counter .1.3.6.1.4.1.546.1.1.4.1.18 |
processSysCallsThe number of system calls invoked by this process.ro Counter .1.3.6.1.4.1.546.1.1.4.1.19 |
processMinorPgFltsThe number of minor page faults incurred by this
process. Minor faults do not require I/O to
retrieve the page.ro Counter .1.3.6.1.4.1.546.1.1.4.1.20 |
processMajorPgFltsThe number of major page faults incurred by this
process. Major faults require I/O to retrieve the
page.ro Counter .1.3.6.1.4.1.546.1.1.4.1.21 |
processNumSwapsThe number of times this process has been swapped.ro Counter .1.3.6.1.4.1.546.1.1.4.1.22 |
processVolCtxThe number of voluntary context switches incurred
by this process. Voluntary context switches occur
when the processor 'voluntary' gives up the CPU
(e.g. waiting on I/O.)ro Counter .1.3.6.1.4.1.546.1.1.4.1.23 |
processInvolCtxThe number of involuntary context switches
incurred by this process. An involuntary context
switch occurs when the process has executed for
the duration of its time quantum and is switched
out by the process scheduler.ro Counter .1.3.6.1.4.1.546.1.1.4.1.24 |
processArgsThe parameters supplied to this process when it
was initially started.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.4.1.25 |
processStartTimeThe date/time at which this process started. The
format is as follows: to local time in the form
of a 26-character string as shown below. Time
zone and daylight savings corrections are made
before string generation. The fields are
constant width:
Fri Sep 13 00:00:00 1986\nro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.4.1.26 |
processStateStrThe process state in an operating-system
independent format. A process-state matrix
is included below. Note that not all operating
systems may support a specific process-state.
State Description
starting Process under creation
runnable Process is on run queue
sleeping Process is waiting for event to complete
sleep Uninterruptible sleep (usually IO)
zombie Process terminated; parent not waiting
stop Process stopped either by job control
signal or because it is being traced
active The process is running on a processor
swapped Process is swapped out to secondary storage
wait Process is waiting for memory;
subclass of sleeping state
other Misc state
(forking, exiting, transition, etc.)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.4.1.27 |
processStateIntThe process state, as above, represented by
integer for easier polling and trending.ro Enumeration .1.3.6.1.4.1.546.1.1.4.1.28 |
whoTableThis table represents users who are currently logged
into the node which the agent resides. SEQUENCE OF WhoEntry .1.3.6.1.4.1.546.1.1.5 |
whoEntryAn entry in the who table. WhoEntry .1.3.6.1.4.1.546.1.1.5.1 |
whoIndexThe instance of the whoEntry object.ro INTEGER .1.3.6.1.4.1.546.1.1.5.1.1 |
whoNameThe user name of a user logged into the node which
the agent resides (e.g. root).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.5.1.2 |
whoDeviceThe device the user is using to log into the
node which the agent resides (e.g. console or
ttyp1).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.5.1.3 |
whoPIDThis object represents the process ID for the
user's login shell. This object is not
supported on SunOS 4.X systems; 0 is returned
instead.ro INTEGER .1.3.6.1.4.1.546.1.1.5.1.4 |
whoTimeThe time, in SNMP TimeTicks, when the user first
logged in.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.546.1.1.5.1.5 |
whoWhereThe location the user logged in from if
applicable. (e.g. :0.0 if local or host name
if logged in from a remote system).ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.5.1.6 |
remoteShell OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.6 |
shellOutputThe name of a file that will receive all
output from the execution of a UNIX command
initiated by the agent. This file is
restricted to the '/tmp' ('\temp' or '\tmp' for
NT) directory for security and safety
considerations. If the value object is set to
anything other that that residing in '/tmp' or a
relative pathname, an error will be returned.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.6.1 |
shellCmdThe command and arguments to be executed by
the agent. When this object is SET, (and
a valid shellOutput object exists), the agent
fork/execs the command with STDOUT and STDERR going
to the value of shellOutput. On NT systems, the
command is run synchronously so care should be
taken not to block the subagent indefinitely.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.6.2 |
shellExitStatThe exit code from the execution of a shell
command. The value remains unchanged until
another command is executed. Each execution
of a shell command overwrites the previous
value of this object. On some systems (HPUX-9),
the exit status is not available if the shell
command was invoked in the background in order to
avoid defunct or zombie processes waiting on that
shell command's exit value.ro INTEGER .1.3.6.1.4.1.546.1.1.6.3 |
shellOutputContentsThis object returns up to the first 512 characters
of the last shell-command output stored in the file
specified by shellOutput (remoteShell.1). No
attempt at translating the character output is
made by the agent.ro DisplayString .1.3.6.1.4.1.546.1.1.6.4 |
performance OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.7 |
kernelperf OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.7.8 |
runQLenThe length of the scheduler's run queue
sampled over a fixed period of time. The
sampling interval is system dependent. In
SunOS, the kernel updates this parameter once
every 5 seconds. The system's load average
is computed from the value of runQLen; the
load average is defined as the average
runQLen value over some interval.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.4 |
diskWaitNumThe number of jobs that are waiting on disk
I/O sampled over a fixed period of time. The
sampling interval is system dependent. In
SunOS, the kernel updates this parameter once
every 5 seconds. A large value may indicate
an overloaded system although larger values
may be observed on file server systems.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.5 |
pageWaitNumThe number of jobs that are waiting on page
I/O sampled over a fixed period of time. The
sampling interval is system dependent. In
SunOS, the kernel updates this parameter once
every 5 seconds. A large value may indicate
the system does not have enough memory for
the current load.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.6 |
swapActiveThe number of jobs that are active yet
swapped out of memory, sampled over a fixed
period of time. The sampling interval is
system dependent. In SunOS, the kernel
updates this parameter once every 5 seconds.
A high value for this object may indicate
that system memory is not sufficient for the
current load.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.7 |
sleepActiveThe number of jobs that are active yet
sleeping in core, sampled over a fixed
period of time. The sampling interval is
system dependent. In SunOS, the kernel
updates this parameter once every 5 seconds.
A process is active yet sleeping in core
when it is not running and not swapped out
to secondary storage (swap).ro Gauge .1.3.6.1.4.1.546.1.1.7.8.8 |
memInUseThe total real KBytes of memory in use
sampled over a fixed period of time. The
sampling interval is system dependent. In
SunOS, the kernel updates this parameter
once every 5 seconds. Comparing memInUse to
memory (in the Concord 'system' group) can
help indicate if a system has sufficent
memory for its current load.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.9 |
activeMemThe total active real memory (KBytes)
sampled over a fixed period of time. The
sampling interval is system dependent. In
SunOS, the kernel updates this parameter
once every 5 seconds. Memory is active when
it is actually being used by a process
running in memory. This value should be
less than or equal to memInUse. A high
value may indicate a system with
insufficient memory.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.10 |
numProcsThe number of processes table slots currently
allocated and in use. On older BSD-based
systems, this metric is important since it
places an uppder bound on the total number of
processes that may run on the system at any one
time.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.11 |
numOpenFilesThe system-wide total number of open files.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.12 |
swapInUseThe amount of swap space (KBytes) currently in
use by the system. Swap space is used when
memory is in short supply. Typically,
entire processes are swapped out to
secondary storage. Comparing this value to
totalSwap (in Concord's kernelConfig group)
can help indicate if additional swap space
is needed.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.13 |
numSwitchesThe total number of context switches that
have occurred since the kernel was last
initialized. A context switch occurs each
time a process gives up the CPU and another
takes its place. This counter reflects the
level of system activity; a high rate of
context switching is indicative of the system load.ro Counter .1.3.6.1.4.1.546.1.1.7.8.14 |
numTrapsThe total number of traps switching a process
from user to kernel mode that have occurred since
the kernel was last initialized. Traps are
hardware exceptions that occur and are
usually caused by the currently running
process. Example traps include those for
incorrect arithmetic operations, segmentation
violations or page faults. An excessive trap
rate can indicate a faulty program, excessive
system loading, or some other abnormality.ro Counter .1.3.6.1.4.1.546.1.1.7.8.15 |
numSyscallsThe total number of system calls that
have occurred since the kernel was last
initialized. System calls occur when a
process calls a function which must execute
in kernel or privileged mode; it is a
indicator of the system load and may be
higher on servers or machines shared by many
users.ro Counter .1.3.6.1.4.1.546.1.1.7.8.16 |
numInterruptsThe total number of device interrupts that
have occurred since the kernel was last
initialized. The operating system is
interrupted by devices and peripherals when
they require the attention of the system. An
excessive rate of interrupts can indicate a
heavily loaded machine; servers and machines
shared by many users will typically have a
higher rate though.ro Counter .1.3.6.1.4.1.546.1.1.7.8.17 |
numPageSwapInsThe total number of pages that have been swapped in
since the kernel was last initialized. Page
swapping occurs when a process is swapped to
and from secondary storage. A high rate of
page swap activity can indicate an overloaded
system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.18 |
numPageSwapOutsThe total number of pages that have been swapped out
since the kernel was last initialized. Page
swapping occurs when a process is swapped to
and from secondary storage. A high rate of
page swap activity can indicate an overloaded
system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.19 |
numSwapInsThe total number of processes that have been swapped
in since the kernel was last initialized.
Processes are swapped to and from secondary
storage when memory is in short supply. A
high rate may indicate an overloaded system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.20 |
numSwapOutsThe total number of processes that have been swapped
out since the kernel was last initialized.
Processes are swapped to and from secondary
storage when memory is in short supply. A
high rate may indicate an overloaded system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.21 |
numPageInsThe total number of pages that have been paged in
since the kernel was last initialized.
Page-in is an operation performed by the
virtual memory system in which the contents
of a page are read from secondary storage. A
high rate of change may indicate an
overloaded system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.22 |
numPageOutsThe total number of pages that have been paged out
since the kernel was last initialized.
Page-out is an operation performed by the
virtual memory system in which the contents
of a page are written to secondary storage.
A high rate of change may indicate an
overloaded system.ro Counter .1.3.6.1.4.1.546.1.1.7.8.23 |
numPageReclaimsThe total pages that have been reclaimed from the
freelist since the kernel was last
initialized. Memory pages are stored on a
free-list when not in use. If a page has
been acquired from the free-list, it has been
reclaimed. A high rate of changed indicates
an active system which is not generally
considered to be overloaded.ro Counter .1.3.6.1.4.1.546.1.1.7.8.24 |
numPageFaultsThe total number of page faults that have
occurred since the kernel was last
initialized. A page fault occurs when a
running process attempts to access a virtual
memory page that is not currently in physical
memory resulting in a hardware page fault. A
high rage of page faults may indicate an
overloaded system or one with insufficient
memory.ro Counter .1.3.6.1.4.1.546.1.1.7.8.25 |
loadAverage1MinThe load average over the last 1 minute. The
load average represents the average number of
jobs in the run queue over the specified time
range. The value reported is the load
average multiplied by 100. For example, if
the value 50 represents a load average of 0.50ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.26 |
loadAverage5MinThe load average over the last 5 minutes. The
load average represents the average number of
jobs in the run queue over the specified time
range. The value reported is the load
average multiplied by 100. For example, if
the value 50 represents a load average of 0.50ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.27 |
loadAverage15MinThe load average over the last 15 minutes. The
load average represents the average number of
jobs in the run queue over the specified time
range. The value reported is the load
average multiplied by 100. For example, if
the value 50 represents a load average of 0.50ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.28 |
totalSwapSpaceTotal system swap space in KBytes. This object
is identical to the kernelConfig.totalSwap(12)
object and is repeated here for the convenience
of management stations which cannot simultaneously
poll groups of objects in different branches of
the MIB.ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.29 |
swapCapacityThe percentage of the system's total swap in use.
The value of this object can be computed by
dividing swapInUse(13) by totalSwapSpace(29)
and multiplying by 100. It is included here
for convenient polling, monitoring, and history
sampling. This object is an aggregate value over
all the swap partitions and areas.ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.30 |
memCapacityThe percentage of the system's active memory in use.
The value of this object can be approximated by
dividing activeMem(10) by memory(system.3) and
converting to a percentage. Because virutal
memory allows systems to operate with a higher
memCapacity value, this value alone should not
be used to judge how loaded a system is. Managers
should also monitor swapCapacity.ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.31 |
memInUseCapacityThe percentage of the system's memory in use.
The value of this object can be approximated by
dividing memInUse(9) by memory(system.3) and
converting to a percentage. Because virutal
memory allows systems to operate with a higher
memCapacity value, this value alone should not
be used to judge how loaded a system is. Managers
should also monitor swapCapacity.ro INTEGER .1.3.6.1.4.1.546.1.1.7.8.32 |
pageScansTotal number of pages examined by pageout daemon.
Excessive rates of scans (change in this counter)
can indicate a machine with insufficient memory.ro Counter .1.3.6.1.4.1.546.1.1.7.8.33 |
numZombieProcsCurrent number of zombie processes found on the
system. This MIB object is found by adding up
all processes with a processStateStr of zombie.
The lower the number the better. Supported in
SystemEDGE 4.1 and higher.ro Gauge .1.3.6.1.4.1.546.1.1.7.8.34 |
errorTableThis table contains errors reported to the
system console. On System V.4 platforms, it
also contains errors passed up via the system
error device. Note, errors in this table
are also sent out as TRAPS. V.4 derived
systems support a flexible, consistent
interface for hardware and system errors.
This table represents error feedback from
this interface. It is not supported on SunOS
4.X systems.deprecated SEQUENCE OF ErrorEntry .1.3.6.1.4.1.546.1.1.8 |
errorEntryAn entry in the error table.deprecated ErrorEntry .1.3.6.1.4.1.546.1.1.8.1 |
seqNumThe unique sequence number of the error
entry. The value of this object also
represents the instance of the errorEntry
object.rodeprecated INTEGER .1.3.6.1.4.1.546.1.1.8.1.1 |
midThe software module identifier reporting the
error.rodeprecated INTEGER .1.3.6.1.4.1.546.1.1.8.1.2 |
sidThe secondary identifier of the module
reporting the error.rodeprecated INTEGER .1.3.6.1.4.1.546.1.1.8.1.3 |
timeThe time at which the error was reported and
the error entry created.rodeprecated TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.546.1.1.8.1.4 |
tagA unique number which identifies the type of
error that occurred.rodeprecated INTEGER .1.3.6.1.4.1.546.1.1.8.1.5 |
typeThe type of error.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.6 |
causeThe cause of the error.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.7 |
severityThe severity of the error.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.8 |
levelThe level of software reporting the error.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.9 |
moduleThe module name that reported the error.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.10 |
subSysmsgThe sub-system message of the error entry.rodeprecated DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.8.1.11 |
errDeleteSetting this object to the value 1 causes the
agent to delete this entry from the error
table. Writing any other value causes the
agent to take no action.rwdeprecated DeleteButtonType SYNTAX INTEGER { delete(1), valid(2) } .1.3.6.1.4.1.546.1.1.8.1.12 |
ipc OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.9 |
msgqueTableThis table contains an entry for each system
SysV message queue currently in use. SEQUENCE OF MsgqueEntry .1.3.6.1.4.1.546.1.1.9.1 |
msgqueEntryAn entry in the message queue table. MsgqueEntry .1.3.6.1.4.1.546.1.1.9.1.1 |
queIDThe unique queue ID. The value of this
object also represents the instance for the
queEntry object.ro INTEGER .1.3.6.1.4.1.546.1.1.9.1.1.1 |
queKeyThe message queue key. Each message queue
has a key value chosen by the creating user.
Its value is only significant to the creating
process.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.1.1.2 |
queModeThe message queue permissions mode. The mode
defines access permissions for the message
queue as well as status information. See the
man page ipcs(1) for more information.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.1.1.3 |
queOwnerThe login name (e.g. root) of the owner of
the message queue.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.1.1.4 |
queGroupThe group name (e.g. wheel) of the owner of
the message queue.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.1.1.5 |
queNBytesThe number of bytes currently in the message queue.ro Gauge .1.3.6.1.4.1.546.1.1.9.1.1.6 |
queNMesgThe number of messages currently in the
message queue.ro Gauge .1.3.6.1.4.1.546.1.1.9.1.1.7 |
queDelSetting this object to the value 1 causes
this agent to remove the message queue from
its table. The message queue identifier is
removed from the system-wide table and the
kernel message queue and associated data
structure are destroyed.rw DeleteButtonType SYNTAX INTEGER { delete(1), valid(2) } .1.3.6.1.4.1.546.1.1.9.1.1.8 |
shmemTableThis table contains an entry for each system
SysV shared memory segment currently in use. SEQUENCE OF ShmemEntry .1.3.6.1.4.1.546.1.1.9.2 |
shmemEntryAn entry in the shared memory table. ShmemEntry .1.3.6.1.4.1.546.1.1.9.2.1 |
shmemIDThe unique shared memory segment ID. The
value of this object also represents the
instance of the shmemEntry object.ro INTEGER .1.3.6.1.4.1.546.1.1.9.2.1.1 |
shmemKeyThe shared memory segment key. Each shared
memory segment is assigned a key value by the
creating user. Its value is only significant
to the creating process.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.2.1.2 |
shmemModeThe shared memory segment permissions mode. The mode
defines access permissions for the message
queue as well as status information. See the
man page ipcs(1) for more information.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.2.1.3 |
shmemOwnerThe user login name (e.g. root) of the owner of the
shared memory segment.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.2.1.4 |
shmemGroupThe group name (e.g. wheel) of the owner of
the shared memory segment.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.2.1.5 |
shmemSegSzThe size in bytes of the shared memory segmentro INTEGER .1.3.6.1.4.1.546.1.1.9.2.1.6 |
shmemNLcksThe number of times the shared memory segment
has been locked.ro INTEGER .1.3.6.1.4.1.546.1.1.9.2.1.7 |
shmemDelSetting this object to the value of 1 causes
the agent to remove this entry from the
table. The shared memory identifier is
removed from the system-wide table and the
kernel shared memory segment and associated
data structure are destroyed.rw DeleteButtonType SYNTAX INTEGER { delete(1), valid(2) } .1.3.6.1.4.1.546.1.1.9.2.1.8 |
semTableThis table contains an entry for each system
SysV semaphore currently in use. SEQUENCE OF SemEntry .1.3.6.1.4.1.546.1.1.9.3 |
semEntryAn entry in the semaphore table. SemEntry .1.3.6.1.4.1.546.1.1.9.3.1 |
semIDThe unique semaphore ID. The value of this
object represents the instance for the
semEntry object.ro INTEGER .1.3.6.1.4.1.546.1.1.9.3.1.1 |
semKeyThe semaphore's key. Each semaphore is
assigned a key value by the creating user.
Its value is only significant to the creating
process.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.3.1.2 |
semModeThe semaphore permissions mode. The mode
defines access permissions for the message
queue as well as status information. See the
man page ipcs(1) for more information.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.3.1.3 |
semOwnerThe user login name (e.g. root) of the owner of the
semaphore.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.3.1.4 |
semGroupThe group name (e.g. wheel) of the owner of
the semaphore.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.9.3.1.5 |
semNsemsThe number of individual semaphores within
this semaphore group.ro INTEGER .1.3.6.1.4.1.546.1.1.9.3.1.6 |
semDelSetting the value of 1, causes the agent to
remove this entry from its semaphore table.
The semaphore identifier is removed from the
system-wide table and the kernel semaphore
group and associated data structures are
destroyed.rw DeleteButtonType SYNTAX INTEGER { delete(1), valid(2) } .1.3.6.1.4.1.546.1.1.9.3.1.7 |
buffers OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.10 |
mbufs OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.10.1 |
numMbufsThe total number of mbufs contained in the mbuf
pool. The BSD networking subsystem utilizes
a buffer abstraction called 'mbufs'. This
object indicates the number of mbuf buffers
pre-allocated by the operating system. If
the BSD networking subsystem is not
supported, than 0 is returned.ro Gauge .1.3.6.1.4.1.546.1.1.10.1.1 |
numClustersThe total number of logical pages or clusters
obtained from the page pool. Memory pages
(or clusters) can also be attached to mbufs
if needed. The size of this pool is returned
in this object. If the BSD subsystem is not
supported, than 0 is returned.ro Gauge .1.3.6.1.4.1.546.1.1.10.1.2 |
freeClustersThe number of free clusters or memory pages
in the mbuf cluster pool. Monitoring the
number of free clusters can help determine if
the BSD protocol subsystem is properly
configured. On SunOS 4.X systems, TCP/IP is
coded in the BSD subsystem. Monitoring this
variable can help determine if TCP/IP
performance problems are due to insufficient
buffer resources.ro Gauge .1.3.6.1.4.1.546.1.1.10.1.3 |
numDropsThe number of times requests for mbufs were
denied. An excessive rate of mbuf allocation
failures may indicate an overloaded system or
one with insufficient memory resources.ro Counter .1.3.6.1.4.1.546.1.1.10.1.4 |
numWaitsThe number of times requests for mbufs were
delayed. An excessive rate of mbuf
allocation 'waits' may indicate an overloaded
system or one with insufficient memory
resources.ro Counter .1.3.6.1.4.1.546.1.1.10.1.5 |
numDrainsThe total number of calls to protocol drain
routines. When the protocol subsystem is
running low on buffers, it can call each
protocol's 'drain' function forcing that
protocol to free buffers. This object
reveals how many times this even has occurred.
An excessive rate of calls to 'drain' may
indicate an overloaded or misconfigured system.ro Counter .1.3.6.1.4.1.546.1.1.10.1.6 |
mbufAllocTableThis table contains an entry for each mbuf
type that has been allocated. In the BSD
networking subsystem, when an mbuf is
allocated, the mbuf's intended use is
categorized. This table represents the
categories and the number of mbuf's allocated
to each type. SEQUENCE OF MbufAllocEntry .1.3.6.1.4.1.546.1.1.10.1.7 |
mbufAllocEntryAn entry in the mbuf Allocation table. MbufAllocEntry .1.3.6.1.4.1.546.1.1.10.1.7.1 |
mbufTypeThe type of mbuf. Mbuf types generally range
from from 0 to 255; many mbuf types
(numbers > 30) are undefined and generally
not used. Their use and description are a
local matter and may vary from system to system.ro INTEGER .1.3.6.1.4.1.546.1.1.10.1.7.1.1 |
mbufDescA textual description of the mbuf type.
Example mbuf descriptions include 'Packet
header', 'Socket structure', etc. Undefined
or unknown mbuf type descriptions return
'Unknown mbuf type' as their description.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.1.1.10.1.7.1.2 |
mbufAllocThe number of mbufs allocated and declared of to
be of this type.ro Gauge .1.3.6.1.4.1.546.1.1.10.1.7.1.3 |
strbufs OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.10.2 |
strbufAllocTableThis table contains an entry for each Streams
buffer bucket sizes. SEQUENCE OF StrbufAllocEntry .1.3.6.1.4.1.546.1.1.10.2.1 |
strbufAllocEntryAn entry in the Streams buffer allocation table. StrbufAllocEntry .1.3.6.1.4.1.546.1.1.10.2.1.1 |
strbufAllocIndexThe table index of this entry.ro INTEGER .1.3.6.1.4.1.546.1.1.10.2.1.1.1 |
strbufAllocSizeThe size of this bucket in bytes. The size is
less than or equal to this value yet greater
than the previous entry's bucket size. For
example, if the bucket size os 1024 bytes,
all Streams buffer requests of less than or
equal to 1024 bytes will return a buffer of
size 1024.ro INTEGER .1.3.6.1.4.1.546.1.1.10.2.1.1.2 |
strbufAllocCurrentThe number of Streams buffers of this currently
allocated. Comparing the value of this
object to strbufAllocMax can help one
determine if the system is properly configured.ro Gauge .1.3.6.1.4.1.546.1.1.10.2.1.1.3 |
strbufAllocMaxsThe maximum number of Streams buffers of this
size ever allocated at any one time. This
value serves as a high-water mark for buffer
allocations of this size.ro INTEGER .1.3.6.1.4.1.546.1.1.10.2.1.1.4 |
strbufAllocTotalsThe total number of allocations of Streams buffers
of this bucket size. A high allocation rate
can help one diagnose an overloaded system.ro Counter .1.3.6.1.4.1.546.1.1.10.2.1.1.5 |
strbufAllocFailsThe total number of allocation failures for Streams
buffers of this bucket size. A high rate of
failure can indicate an overloaded system or
one that is not properly configured.ro Counter .1.3.6.1.4.1.546.1.1.10.2.1.1.6 |
ioBufferCache OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.10.3 |
numBreadRequestsThe total number of calls to the kernel's bread()
function. This function is the primary read
interface to the kernel's buffer pool used
for file system I/O. On NT systems, this value is
an aggregate of several read variables in the
ntCachePerf group.ro Counter .1.3.6.1.4.1.546.1.1.10.3.1 |
numBreadHitsThe number of kernel buffer cache 'hits'.
The kernel caches previously used I/O buffers
in an attempt to avoid excessive reading and
writing to disk. A cache 'hit' indicates
that this strategy has paid off because a
process has requested a buffer that was in
the buffer cache thereby avoiding a more
expensive disk read. A high rate of cache
hits indicates a relatively smooth running
system. On NT systems, this value is an aggregate
of several hit variables in the ntCachePerf group.ro Counter .1.3.6.1.4.1.546.1.1.10.3.2 |
numBufSleepsThe total number of times the kernel had to 'sleep'
for a buffer. The kernel 'sleeps' for a
buffer when it fails to find it in the cache
and must access the disk for it. Excessive
buffer 'sleeps' indicates that the caching
algorithm is not able to effectively predict
and cache disk I/O patterns. Adding more
memory for buffering may improve the cache
hit ratio.ro Counter .1.3.6.1.4.1.546.1.1.10.3.3 |
numAgeAllocsThe total number of times an aged buffer was
allocated. The buffer pool is stored in
one of several lists. One such list, the AGE
list, holds buffers buffers that have a lower
probability of being used. New buffer
requests are filled from this list first.
This variable contains the number of times a
buffer request was satisfied by a buffer on
the AGE list.ro Counter .1.3.6.1.4.1.546.1.1.10.3.4 |
numLRUAllocsThe total number times an LRU buffer was
allocated. The Least-recently-used list is
another list on which buffers are stored.
They are allocated in a 'least-recently-used'
manner. This variable indicates the number
of times a buffer was allocated from the LRU
list.ro Counter .1.3.6.1.4.1.546.1.1.10.3.5 |
minNumBufHdrsThe minimum number of buffer headers to
allocated. These headers are used at the
head of each buffer hash list. This value
represents an upper bound on the number of
separate hash lists the buffer cache may
use.ro Gauge .1.3.6.1.4.1.546.1.1.10.3.6 |
numAllocBufNumber of buffers that are currently
allocated. Monitoring this variable, and
others in the ioBufferCache group, can help
indicate if the system is properly configured
or has sufficient memory for buffering.ro Gauge .1.3.6.1.4.1.546.1.1.10.3.7 |
ioBufferHitRatePercentage of buffer cache lookups that result in a
'hit'. This value is derived from
numBreadHits / numBreadRequests.ro INTEGER .1.3.6.1.4.1.546.1.1.10.3.8 |
dnlc OBJECT IDENTIFIER .1.3.6.1.4.1.546.1.1.11 |
dnlcHitsTotal number of DNLC cache hits.ro Counter .1.3.6.1.4.1.546.1.1.11.1 |
dnlcMissesTotal number of DNLC cache misses.ro Counter .1.3.6.1.4.1.546.1.1.11.2 |
dnlcEntersTotal number of DNLC enters done.ro Counter .1.3.6.1.4.1.546.1.1.11.3 |
dnlcDblEntersTotal number enters tried when already cached.ro Counter .1.3.6.1.4.1.546.1.1.11.4 |
dnlcLongEntersTotal number of long names tried to enter.ro Counter .1.3.6.1.4.1.546.1.1.11.5 |
dnlcLongLooksTotal number of long name lookup attempts.ro Counter .1.3.6.1.4.1.546.1.1.11.6 |
dnlcLruEmptyTotal number of least-recently used list empty.ro Counter .1.3.6.1.4.1.546.1.1.11.7 |
dnlcPurgesTotal number of purges to the DNLC cache.ro Counter .1.3.6.1.4.1.546.1.1.11.8 |
dnlcHitRatePercentage of DNLC cache lookups that result in a
'hit'. Hit rates less than 90% are considered
poor and may require kernel tuning. This value is
derived from dnlcHits / dnlcHits + dnlcMisses.ro INTEGER .1.3.6.1.4.1.546.1.1.11.9 |
dnlcCacheSizeThe maximum number of possible entries in the DNLC
cache. If there is no set upper bound, 0 is
returned.ro INTEGER .1.3.6.1.4.1.546.1.1.11.10 |
dos OBJECT IDENTIFIER .1.3.6.1.4.1.546.2 |
os2 OBJECT IDENTIFIER .1.3.6.1.4.1.546.3 |
windows OBJECT IDENTIFIER .1.3.6.1.4.1.546.4 |
nt OBJECT IDENTIFIER .1.3.6.1.4.1.546.5 |
ntSystem OBJECT IDENTIFIER .1.3.6.1.4.1.546.5.1 |
ntSystemVersionThe kernel/system version including the release,
build, and service-pack numbers.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.546.5.1.1 |
ntBuildNumberThe kernel build number (e.g. 1057)ro INTEGER .1.3.6.1.4.1.546.5.1.2 |
ntServicePackNumberThe system service-pack number. If no
service-packs have been applied, then 0 is returned.ro INTEGER .1.3.6.1.4.1.546.5.1.3 |
monitor OBJECT IDENTIFIER .1.3.6.1.4.1.546.6 |
empireexp OBJECT IDENTIFIER .1.3.6.1.4.1.546.7 |
distribsys OBJECT IDENTIFIER .1.3.6.1.4.1.546.8 |
traps OBJECT IDENTIFIER .1.3.6.1.4.1.546.9 |
empireHistory OBJECT IDENTIFIER .1.3.6.1.4.1.546.10 |
logMonitor OBJECT IDENTIFIER .1.3.6.1.4.1.546.11 |
diskGroup OBJECT IDENTIFIER .1.3.6.1.4.1.546.12 |
cpuGroup OBJECT IDENTIFIER .1.3.6.1.4.1.546.13 |
extensionGroup OBJECT IDENTIFIER .1.3.6.1.4.1.546.14 |
processMonitor OBJECT IDENTIFIER .1.3.6.1.4.1.546.15 |
applications OBJECT IDENTIFIER .1.3.6.1.4.1.546.16 |