EMPIRE: View SNMP OID List / Download MIB

The name of the system that the agent is running on as given by the login prompt.

The CPU type of the system that the agent is running on (e.g. sun4c, sun4m).

The amount of memory in 1024 byte units contained in the system.

The 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.

The 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.

The operating system release of the system that the agent resides (e.g. 4.1.3).

This table describes all mounted file systems on the system that the agent resides.

An entry in the device table.

This 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.

The 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).

The mount point or path name in the local file system where the device is mounted (e.g. /home).

The 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.

The total number of blocks contained in the mounted device.

The total number of free or unallocated blocks in the mounted device.

Each 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.

The number of free or unallocated files that can be created on this device.

The maximum file name length that this mounted device supports. If no fixed limit exists, 0 is returned.

The type of the mounted device. If this underlying device does not support feature, 0 is returned.

The (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.

Some 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'.

Writing 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. Enumeration: 'valid': 2, 'delete': 1.

The percentage of the device's total capacity in use.

The 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.

The agent's description and software version number (e.g 'Concord . . . Ver 4.1').

Maximum 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.

The 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.

The 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.

The number of CPUs contained within this host.

The 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.

The 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.

The amount of virtual memory in 1024 byte units (KBytes).

Maximum 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.

Maximum 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.

The 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.

Maximum 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.

Total 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.

Maximum 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.

Boolean 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. Enumeration: 'false': 2, 'true': 1.

The 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.

This 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.

This 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.

The Device and partition (e.g. sd0a) that the root filesystem is mounted from.

The root filesystem type (e.g. 4.2).

The total number of blocks contained in the root filesystem. The value 0 is returned if unknown.

The 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.

The dump filesystem type (e.g. spec). Dump is generally not a 'normal' file system like UFS, 4.2, etc.

The total number of blocks contained in the dump filesystem.

The device and partition (e.g. sd0b) that serves as swap space for the running kernel.

The swap filesystem type (e.g. spec). Swap space is not generally a typical file system like UFS, 4.2, etc.

The total number of blocks contained in the kernel's swap area.

The 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.

Maximum 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.

Number of Streams multiplexor links.

Current 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.

The largest number of open 'streams' recorded by the system. This value represents a 'high-water' mark.

The 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.

Number 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.

The largest number of open 'streams' recorded by the system. This value represents the 'high-water' mark.

The number of Streams queue allocation failures. Monitoring the queueUse, queueMax, and queueFail variables can help determine if the Streams subsystem is properly configured.

The 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.

The largest number of Streams message blocks in use at any one time. This value represents a 'high-water' mark.

The number of Streams message block allocation failures. Monitoring the mblockUse, mblockMax, and mblockFail variables can help determine if the Streams subsystem is properly configured.

The 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.

The largest number of Streams data blocks in use at any one time. This value represents a 'high-water' mark.

The number of Streams data block allocation failures. Monitoring the dblockUse, dblockMax, and dblockFail variables can help determine if the Streams subsystem is properly configured.

The underlying system (hardware/OS) type Enumeration: 'irix63Mips': 13, 'nt351Alpha': 9, 'nt52Intel': 26, 'digitalUNIX': 19, 'irix65Mips': 18, 'solarisPPC': 4, 'hpux11Parisc': 21, 'nt40Intel': 10, 'linuxIntel': 20, 'nt351Intel': 8, 'unknown': 1, 'aix41RS6000': 15, 'nt50Intel': 22, 'hpux10Parisc': 7, 'nt40Alpha': 11, 'sunosSparc': 5, 'hpux9Parisc': 6, 'solarisSparc': 2, 'nt51Intel': 24, 'hpux11IA64': 28, 'aix5RS6000': 25, 'aix42RS6000': 16, 'aix43RS6000': 17, 'solarisIntel': 3, 'irix64Mips': 14, 'nt50Alpha': 23, 'linuxIA64': 27, 'irix62Mips': 12.

The 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.

This object is used in conjunction Concord's auto-licensing and remote licensing facility starting in SystemEDGE 4.0.

This object is used in conjunction Concord's auto-licensing and remote licensing facility starting in SystemEDGE 4.0.

This 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) Enumeration: 'restrictedMode': 2, 'fullMode': 1.

The 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.

The 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).

The 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).

A 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.

The 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.

A 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.

Table 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.

An entry in the table describing defined users.

The instance of the userEntry object, derived from its index number in the password file.

The user's login ID which is normally given to the system's login prompt (e.g. root).

The user's encrypted password. Users without passwords have an '*' in this field.

The user's User-ID or UID (e.g. 0).

The user's Group-ID or GID (e.g. 1).

The user's real life name (e.g. John Doe).

The user's home directory when that user logs in (e.g. /home/john).

The user's preferred shell (e.g. /bin/csh).

Table 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.

Entry in table describing valid groups.

The instance of the groupEntry object, derived from its index in the groups file.

The name of the group (e.g. wheel).

The encrypted password for the group. Groups without passwords have an '*' in this field.

The group-ID or GID (e.g. 1).

Table describing currently running processes on the node which the SNMP agent resides.

Each 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.

The unique process ID (e.g. 0). The value of this object also serves as the instance of the processEntry object.

The name of the running process (e.g. swapper).

The 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.

The '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.

The process flags; flags are operating system dependent and are generally documented in system header files.

The process owner's user ID (e.g. 0 for root).

The process owner's group ID (e.g. 0 for wheel).

This 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.

The percentage (0-100) of real memory used by this process.

The 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.

Real memory (resident set) size of the process in kilobytes. This value indicates how many bytes are held by a process.

This process' accumulated CPU time in seconds.

This process' parent process ID (PID).

The 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.

The number of blocks of data input by the process.

The number of blocks of data output by the process.

The number of messages sent by the process.

The number of messages received by the process.

The number of system calls invoked by this process.

The number of minor page faults incurred by this process. Minor faults do not require I/O to retrieve the page.

The number of major page faults incurred by this process. Major faults require I/O to retrieve the page.

The number of times this process has been swapped.

The 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.)

The 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.

The parameters supplied to this process when it was initially started.

The 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\n

The 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.)

The process state, as above, represented by integer for easier polling and trending. Enumeration: 'procStateActive': 3, 'procStateRunnable': 2, 'procStateOther': 9, 'procStateStarting': 1, 'procStateStop': 8, 'procStateSwapped': 6, 'procStateZombie': 10, 'procStateSleeping': 5, 'procStateSleep': 7, 'procStateWait': 4.

This table represents users who are currently logged into the node which the agent resides.

An entry in the who table.

The instance of the whoEntry object.

The user name of a user logged into the node which the agent resides (e.g. root).

The device the user is using to log into the node which the agent resides (e.g. console or ttyp1).

This 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.

The time, in SNMP TimeTicks, when the user first logged in.

The location the user logged in from if applicable. (e.g. :0.0 if local or host name if logged in from a remote system).

The 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.

The 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.

The 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.

This 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.

The 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.

The 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.

The 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.

The 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.

The 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).

The 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.

The 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.

The 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.

The system-wide total number of open files.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.50

The 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.50

The 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.50

Total 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.

The 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.

The 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.

The 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.

Total number of pages examined by pageout daemon. Excessive rates of scans (change in this counter) can indicate a machine with insufficient memory.

Current 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.

This 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.

An entry in the error table.

The unique sequence number of the error entry. The value of this object also represents the instance of the errorEntry object.

The software module identifier reporting the error.

The secondary identifier of the module reporting the error.

The time at which the error was reported and the error entry created.

A unique number which identifies the type of error that occurred.

The type of error.

The cause of the error.

The severity of the error.

The level of software reporting the error.

The module name that reported the error.

The sub-system message of the error entry.

Setting 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. Enumeration: 'valid': 2, 'delete': 1.

This table contains an entry for each system SysV message queue currently in use.

An entry in the message queue table.

The unique queue ID. The value of this object also represents the instance for the queEntry object.

The message queue key. Each message queue has a key value chosen by the creating user. Its value is only significant to the creating process.

The 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.

The login name (e.g. root) of the owner of the message queue.

The group name (e.g. wheel) of the owner of the message queue.

The number of bytes currently in the message queue.

The number of messages currently in the message queue.

Setting 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. Enumeration: 'valid': 2, 'delete': 1.

This table contains an entry for each system SysV shared memory segment currently in use.

An entry in the shared memory table.

The unique shared memory segment ID. The value of this object also represents the instance of the shmemEntry object.

The 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.

The 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.

The user login name (e.g. root) of the owner of the shared memory segment.

The group name (e.g. wheel) of the owner of the shared memory segment.

The size in bytes of the shared memory segment

The number of times the shared memory segment has been locked.

Setting 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. Enumeration: 'valid': 2, 'delete': 1.

This table contains an entry for each system SysV semaphore currently in use.

An entry in the semaphore table.

The unique semaphore ID. The value of this object represents the instance for the semEntry object.

The semaphore's key. Each semaphore is assigned a key value by the creating user. Its value is only significant to the creating process.

The 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.

The user login name (e.g. root) of the owner of the semaphore.

The group name (e.g. wheel) of the owner of the semaphore.

The number of individual semaphores within this semaphore group.

Setting 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. Enumeration: 'valid': 2, 'delete': 1.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

This 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.

An entry in the mbuf Allocation table.

The 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.

A 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.

The number of mbufs allocated and declared of to be of this type.

This table contains an entry for each Streams buffer bucket sizes.

An entry in the Streams buffer allocation table.

The table index of this entry.

The 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.

The 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.

The 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.

The total number of allocations of Streams buffers of this bucket size. A high allocation rate can help one diagnose an overloaded system.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

The 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.

Number 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.

Percentage of buffer cache lookups that result in a 'hit'. This value is derived from numBreadHits / numBreadRequests.

Total number of DNLC cache hits.

Total number of DNLC cache misses.

Total number of DNLC enters done.

Total number enters tried when already cached.

Total number of long names tried to enter.

Total number of long name lookup attempts.

Total number of least-recently used list empty.

Total number of purges to the DNLC cache.

Percentage 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.

The maximum number of possible entries in the DNLC cache. If there is no set upper bound, 0 is returned.

A Monitor event has occurred. Recall a monitor event occurs when a Monitor Table row expression evaluates to true. The expression is: 'monCurrVal monOperator monValue'.

A kernel error event has occurred; on V.4 derived operating systems, the kernel relays errors and events via the system error device. See the Empire errorTable objects.

This trap is sent when a Monitor Table entry's monRowStatus is set to 'notReady(3)'. One reason this may occur is that the object-instance identifier being monitored by its corresponding Monitor Table entry is no longer in existence. For example, when a process is being monitored (via the Empire processTable), and that process should exit, its corresponding entry in the Empire processTable would no longer exist. Consequently, the object-instance identifier (for that process) being monitored would no longer exist and the agent would send a monitorEntryNotReady trap to all properly configured managers.

This trap is sent when the log monitoring subsystem detects a match in a log file it is currently monitoring. Periodically, the agent stats each log file for changes; if any changes have occurred, the agent scans only those changes for a pattern match. Pattern matches result in logMonMatch events. Changes to log files occur when new entries are added by syslogd(1M) or other logging daemons.

This trap is sent when the status of a log monitoring entry becomes 'notReady(3)'. An entry becomes 'notReady(3)' if an error occurs during log file scaning, if the regular expression is syntactically incorrect, or if the log file does not exist. An entry that is 'notReady(3)' will undergo no further evaluation until its status becomes 'active(1)'.

This trap is sent when the event log monitoring subsystem detects a match in a log it is currently monitoring. Periodically, the agent checks each event log for changes; if any changes have occurred, the agent scans only those changes for a pattern match. Pattern matches result in ntEventMonMatch events.

This trap is sent when the status of an event log monitoring entry becomes 'notReady(3)'. An entry becomes 'notReady(3)' if an error occurs during log file scaning, if the regular expression is syntactically incorrect, or if the log file does not exist. An entry that is 'notReady(3)' will undergo no further evaluation until its status becomes 'active(1)'.

This Trap is sent when a Monitor Table entry transitions from True to False and has specified the monitor clearTrap flag. This Trap represents an indication that the condition that previously had existed no longer does. This Trap provides management software the ability to determine that an alarm can be canceled or marked as corrected. This event only occurs when a monitor table entry evaluates to True and then evaluates to False. This Trap is sent each time the entry transitions from True to false.

This Trap is sent when using a Process Monitor Table entry to monitor the state of a process. When the processing being monitored dies or transitions into a Zombie (or not runnable state), this Trap is sent. This Trap is sent if the value of pmonFlags does not preclude sending Traps.

This Trap is sent when using a Process Monitor Table entry to monitor the state of a process. When a process is re-started, and subsequently re-acquired by the SystemEDGE agent, this Trap is sent. This Trap is sent if the value of pmonFlags specifies that processStart Traps should be pay.

This Trap is sent when using a Process Monitor Table entry to monitor some attribute (e.g. memory usage, process size) of a process for some threshold. When a Process Monitor table expression evaluates to True, this Trap is sent. The expression is: 'pmonCurrVal pmonOperator pmonValue'. This Trap is sent if the value of pmonFlags does not preclude the sending of Traps.

This Trap is sent when using a Process Monitor Table entry to monitor some attribute (e.g. memory usage, process size) of a process for some threshold. When the threshold is crossed, a processThreshold Trap is sent. When the attribute threshold expression first transitions from True to False, this Trap is sent.

This Trap is sent when SystemEDGE or associated modules failed to find a valid license. It can be used in conjunction with auto-licensing or remote-licensing starting with SystemEDGE 4.0. This Trap contains a single MIB object denoting which product or module failed to find a valid license and a string containing the license information for that product or module.

This Trap is sent when SystemEDGE when it detects that its underlying IP address has changed perhaps due to DHCP or other administrative means. It includes up to the last 5 IP addresses that it this system was configured with. The addresses are ordered with most recently used addresses occuring first in the address list. This Trap may be useless on multi-homed systems.

Membership in a process group has changed (e.g. members have joined, left, or changed).

The kernel/system version including the release, build, and service-pack numbers.

The kernel build number (e.g. 1057)

The system service-pack number. If no service-packs have been applied, then 0 is returned.

The type of NT system -- NT Server or NT Workstation Enumeration: 'unknown': 3, 'workstation': 2, 'server': 1.

This object reflects whether the underlying NT system has enabled or disabled the creation of short names to correspond with long filenames. For example, if enabled, then NT will create a short filename to correspond to a file created with a long filename. This feature is often enabled if backward compatibility with DOS based applications is desired. Enumeration: 'false': 2, 'true': 1.

This object reflects whether the FAT will allow creation, enumeration, opening, or querying of long file names, and whether extended time stamp information is stored and reported. Setting to true(1) reverts the system back to Win3x semantics. Enumeration: 'false': 2, 'true': 1.

The deadlock time-out for critical sections.

NT system global hexadecimal flag that controls various internal operations.

Specifies the limit of the number of bytes that can be locked for I/O operations. When 0, the default (512k) is used.

A nonzero value indicates that the system favors the system-cache working set rather than the processes working set.

Size of paged pool in bytes. When 0, system uses default size (32 MB).

Size of nonpaged pool in bytes. When 0, system uses default size (based on physical memory).

List of paging files and their sizes used by the system for paging. For each paging file the description includes the file pathname, current size in MB and maximum size in MB.

This object defines the number of system page table entries reserved for I/O buffers and other information.

This object lists those subsystems that are only loaded when the user starts a depending application.

This object lists the command-line that runs when an MS-DOS application is launched under NT.

This object defines how many seconds after the LPT port has been used that Windows NT waits before grabbing the port, closing it, and flushing the output. This value is only needed for MS-DOS based applications that use BIOS and do not close the port.

Size in MBytes of memory to be given to each individual MS-DOS virtual DOS machine (VDM).

This object defines the command line that runs when a 16-bit Windows-based application is started. The switches instruct NT to start either an MS-DOS VDM or a WOW VDM.

For RISC based computers, this object defines the amount of memory provided in a VDM when a WOW session is started. Value is in MBytes.

This object indicates whether full-screen or windowed mode is used for the console by default. Valid on x86 machines only. Enumeration: 'fullscreen': 1, 'windowed': 0.

This object indicates the number of commands stored in the history buffer by default.

This object indicates the number of history buffers associated with the console by default.

This object indicates if Quick-Edit mode is enabled by default. Enumeration: 'disabled': 0, 'enabled': 1.

Width and height of the default console screen buffer.

Default width and height of the console window.

Lists the DLLs that will be attached to all Windows-based applications.

Indicates how much time the system waits for a devices to be switched on.

Indicates whether printer output is be sent through Print Manager. Enumeration: 'false': 2, 'true': 1.

Indicates the name of disk drive and directory to which Windows for MS-DOS in standard-mode swaps non-Windows-based applications.

Transmission retry timeout in seconds used by Print Manager.

Drive and directory where the NT system resides.

System build type (uniprocessor or multiprocessor). Enumeration: 'unknown': 3, 'uniprocessor': 1, 'multiprocessor': 2.

System start options.

System BIOS date.

System BIOS version.

System video resolution.

This object indicates whether debugging information is to be written to a log file in the event of a system crash. Enumeration: 'disabled': 0, 'unknown': 2, 'enabled': 1.

This object indicates whether NTAS logging is enabled or disabled. If disabled, NT workstation logging is used. Enumeration: 'disabled': 0, 'unknown': 2, 'enabled': 1.

Indicates whether an existing log file is to be overwritten by the new one. Enabled for NTAS, disabled for NT workstation. Enumeration: 'disabled': 0, 'unknown': 2, 'enabled': 1.

Indicates whether an administrative alert is sent; enabled for NTAS, disabled for NT workstation. Enumeration: 'disabled': 0, 'unknown': 2, 'enabled': 1.

Indicates whether this system is installed and/or running in a windows cluster Enumeration: 'false': 2, 'true': 1.

The cluster name that this system is a member of. If the system is not a member of any cluster, then a zero-length string is returned. The cluster name can then be used with DNS or NetBIOS to determine the virtual address of the logical cluster.

A comma-separated list of nodes that are members of the cluster in which this system is a member. Using this information, management software can determine the members of a logical cluster and act accordingly to deal with the logical cluster and the individual nodes.

Indicates whether this system is the primary or active node in the NT cluster. It does not necessarily say if the cluster service(s) are active and up and running per se. Enumeration: 'false': 2, 'true': 1.

Indicates which of cluster members is active or primary node. Active node owns the Cluster Name resource object.

Table of NT system threads.

An entry in the NT system thread table.

The unique process ID with which this thread is contained and executing within.

The thread number within a given process. Thread numbers are not unique across all threads in the system.

The total elapsed time (in centiseconds) that this thread has executed in Privileged Mode.

The total elapsed time (in centiseconds) that this thread has used the processor to execute instructions.

Total elapsed time (in centiseconds) that this thread has executed in User Mode.

Number of thread context switches.

The total elapsed time (in seconds) this thread has been running.

The current base priority of this thread. The system may alter the thread's dynamic priority above, below the base priority.

The current dynamic priority of this thread.

Reason thread is waiting; valid only if ntThreadState is currently wait(5), otherwise undefined. Enumeration: 'waitForEventPairHigh': 14, 'waitForPageIn': 2, 'waitForExecutive1': 7, 'waitForPoolAlloc1': 10, 'suspended1': 12, 'waitForExecutive': 0, 'waitForLPCReply': 17, 'executionDelay': 4, 'waitForLPCRecv': 16, 'waitForFreePage1': 8, 'waitForFreePage': 1, 'waitForPageOut': 19, 'suspended': 5, 'executionDelay1': 11, 'waitForPoolAlloc': 3, 'waitForUserRequest': 6, 'waitForPageIn1': 9, 'waitForUserRequest1': 13, 'waitForVmem': 18, 'waitForEventPairLow': 15.

The starting virtual address of this thread.

The current state of this thread. Enumeration: 'terminated': 4, 'standby': 3, 'unknown': 7, 'transition': 6, 'running': 2, 'ready': 1, 'initialized': 0, 'wait': 5.

The system-wide unique identifier associated with this thread.

The current size of the registry in MBytes.

The size limit of the registry in MBytes.

Table of NT system services

An entry in the NT system service table.

The index of this system service.

The system service name.

The system service path.

The manner in which the service is started; automatic(1) implies that the system starts the service at boot time while manual(2) implies that the service must be started by hand by an administrator. Disabled(3) indicates that the service cannot be started. Enumeration: 'disabled': 3, 'manual': 2, 'other': 4, 'automatic': 1.

The parameters passed to this service when it is invoked.

The current state of the system service. Enumeration: 'paused': 3, 'running': 1, 'other': 4, 'notRunning': 2.

The object name for this service. This indicates the user name the service is currently running as.

Running counter of centiseconds spent by the system processor(s) in Privileged mode.

Running counter of centiseconds spent by the system processor(s) running Idle threads. Note that this is actually the inverse of the total processor time.

Running counter of centiseconds spent by the system processor(s) running User mode.

The number of alignment faults fixed by the system.

The total number of context switches that have occurred since the kernel was last initialized. A context switch occurs each time a thread 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. This counter is equivalent (for NT systems) to the UNIX counter numSwitches(kernelperf.14)

The total number of exceptions dispacted by the system since it was initialized.

An aggregate of KBytes transferred for all file system operations that are neither reads or writes (e.g. file system control requests or device control requests).

Aggregate counter of all file system operations that are neither reads nor writes.

Total number of read and write operations to file system devices issued by the system since system initialization.

Aggregate number of KBytes transferred for all the file system read operations on this system since system initialization.

Aggregate of all the file system read operations on this system since system initialization.

Aggregate number of KBytes transferred for all the file system write operations on this system since system initialization.

Aggregate number of all the file system write operations on this system since system initialization.

Number of floating emulations performed by the system.

Instantaneous processor queue length in threads and is equivalent to runQLen(kernelperf.4)

The number of calls to system service routines. This object is equivalent to numSyscalls(kernelperf.16)

The number of hardware interrupts that have occurred. This object is equivalent to numInterrupts(kernelperf.17)

Number of async reads from Cache pages involving a memory copy of the data from the Cache to the application's buffer.

Number of async data maps of file pages into the Cache.

Number of direct-to-Cache async read operations.

Number of async memory descriptor list (MDL) reads from the Cache. The MDL contains the physical address of each page in the transfer thus permitting DMA of the pages.

Number of async reads from the Cache in preparation to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read.

Number of Cache Copy Read requests that hit the cache and did not require a disk read.

The number of reads from Cache pages that involved a memory copy of data from the Cache to the application's buffer.

Number of pages of the Cache flushed to disk as a result of a flush request or to satisfy a write-through request.

Number of Cache data flush operations.

Numberof data maps in the Cache that could be resolved without retrieval from disk.

Number of data maps in the Cache that resulted in pinning a page in main memory.

Number of times a file system such as NTFS or HPFS has mapped a page of a file into the Cache to read the page.

Number of times an API function call to bypass the file system to get at Cache data could not be honored without invoking the file system after all.

Number of Cache misses necessitated by the lack of available resources to satisfy the request.

Number of reads from Cache pages that bypass installed file systems and read from the Cache directly.

The number of times the Cache's Lazy Write thread has written to disk.

Number of pages the Cache's Lazy Write thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory so the application making the change to the file does not have to wait for the disk write to complete before proceeding.

Number of Cache Memory Descriptor List (MDL) read requests that hit the Cache.

Number of MDL Cache reads.

Number Cache Pin Read requests that hit the Cache.

Number of pages read from the Cache that have been pinned in memory.

Number of reads from Cache pages that wait for the copy operation to complete before proceeding.

Number of times that a file system such as NTFS or HPFS maps a page of a file into the Cache to read the page.

Number of sync reads from Cache pages that bypass the installed file system and retrieve the data directly from the Cache.

Number of reads from Cache pages that use a Memory Descriptor List (MDL) to access the pages.

Number of page reads that have resulted in the page being pinned in memory.

Number of KBytes of virtual memory currently on the Zeroed, Free, and Standby lists. Zeroed and free memory is ready for use. Standby memory is memory removed from a process's working set but still available.

Number of KBytes currently in use by the system Cache.

Maximum number of KBytes used by the system Cache.

Number of Cache faults whereby memory had to be located elsewhere.

Size in KBytes of virtual memory that can be committed without having to expand the paging file(s).

Number of KBytes of virtual memory that have been committed.

Number of page faults for pages that must be filled with zeros before fault is satisifed.

Number of Page Table entries not currently in use by the system.

Number of page faults in the processor and is equivalent to numPageFaults(kernelperf.25)

Number of times the disk was read to retrieve pages of virtual memory.

Number of times pages have been written to disk.

Number of pages read from disk to resolve memory references and is equivalent to numPageIns (kernelperf.22)

Number of pages written to disk because the pages were modified and is equivalent to numPageOuts (kernelperf.23).

Number of pages read or written from/to disk and is a sum of PagesInput(12) and PagesOutput(13).

Number of calls to allocate space in the system Nonpaged pool.

Number of KBytes in the Nonpaged pool which is a system memory area where space is acquired by operating systems facilities as they accomplish their tasks. These pages cannot be paged out to disk.

Number of calls to allocate space in the system Paged Pool. Paged Pool is a system memory area where space is acquired by operating systems facilities as they accomplish their tasks. Paged Pool bytes may be paged out to disk when not accessed by the system for sustained periods of time.

Number of KBytes in the Paged Pool.

Size of paged Pool resident in core memory in KBytes.

Number of KBytes currently resident in the global disk cache.

Number of KBytes of System Code Total Bytes currently resident in core memory. This is the code working set of the pagable executive.

Total number of KBytes of pageable pages in ntoskrnl.exe, hal.dll, and the boot drivers and file systems loaded by ntldr/osloader.

Number of KBytes of System Driver Total KBytes currently resident in core memory. The number is the code working set of the pagable drivers.

Number of KBytes of pageable pages in all other loaded device drivers.

Number of page faults resolved by recovering pages that were in transition to disk at time of page fault.

Number of page faults that have been satisfied by making a copy of a page when an attempt to write the page was made while it was shared.

The percentage of the page file(s) used.

The peak usage of the page file(s).

The number of events in the Application event log.

The number of events in the Security event log.

The number of events in the System event log.

Table containing NT Event Log monitor entries; each entry specifies an Event Log and regular expression. The agent periodically stats the event logs to see if they have been updated. If updated, the agent scans the new entries for the regular expressions. When an entry is found that matches the regular expressions, a trap PDU is sent to appropriate managers.

An entry in the ntEventMonTable.

An index that uniquely identifies an entry in the ntEventMonTable.

The number identifying the NT event log to scan for pattern matches. Possible values are Application(1), Security(2), and System(3). On Win2k and higher, dnsServer(4), dirService(5), and fileRepService(6) are also possibly valid. Not all win2k+ systems have these event logs. Enumeration: 'dnsServer': 4, 'system': 3, 'application': 1, 'dirService': 5, 'security': 2, 'fileRepService': 6.

The time (based on sysUpTime) at which the event occurred.

The number of traps sent by the agent on behalf of this entry. One trap PDU message is sent for each match the agent detects in the corresponding event log. This MIB object used to be called ntEventMonMatches but has been renamed to better reflect its true semantics.

The number identifying the event type of the last event that matched the search criteria. Types 1 through 5 are defined by Windows NT. Type noMatch(6) indicates that there has not yet been a matching event for this monitoring entry. Enumeration: 'information': 3, 'success': 4, 'noMatch': 6, 'failure': 5, 'warning': 2, 'error': 1.

The number identifying the event type to match. Types 1 through 5 are defined by Windows NT. Type all(6) indicates that all event types will match. Enumeration: 'information': 3, 'all': 6, 'success': 4, 'failure': 5, 'warning': 2, 'error': 1.

The source name of the last event log entry that matched this monitor entry. Each time a match occurs, this variable is updated.

The display string representation of the regular expression to match the source name in the event log. Valid regular expressions are those as defined in ed(1).

The text description message from the last event log entry that matched this monitor entry. Each time a match occurs, this variable is updated.

The display string representation of the regular expression to match the description in the event log. Valid regular expressions are those as defined in ed(1).

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(2) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular ntEventMon Table entry, its Status column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

A string specifying the command to be executed upon finding a match.

The flags field dictates the behavior of each ntEventMonEntry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical or'ing together of different bits allows one to combine different options. Hex Function Default (if not enabled) 0x01 Do not execute actions Execute actions 0x02 Do not send Traps Send Traps 0x04 Do not re-initialize Re-initialize 0x08 Do not log events Log events 0x10 Send cont Stop Traps Send single Stop Trap 0x100 Prepend event-id to descr Do not pre-pend 0x200 Logical-not the entry No operator applied

The number of nt-event matches detected by SystemEDGE. This value is incremented regardless of whether Traps are sent for this entry or not. Polling this variable allows you to determine the rate or number of matches over time.

The maximum size (in Bytes) of the Application event log.

The retention flag for the Application event log. This flag indicates the settings for the Event Log Wrapping settings.

The maximum size (in Bytes) of the Security event log.

The retention flag for the Security event log. This flag indicates the settings for the Event Log Wrapping settings.

The maximum size (in Bytes) of the System event log.

The retention flag for the System event log. This flag indicates the settings for the Event Log Wrapping settings.

An SNMP Get of this MIB object returns an un-used NT event monitor Table index number. It can be used for NT event monitor table row creation optimization.

This MIB object, when used in conjunction with ntEventMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the NT event monitor table and place the index value of the last entry whose description matches, in the ntEventMatchIndex MIB object.

See description for ntEventMatchDescr.

The name of the dump file specified by the registry.

The total number of threads currently running in the system. This is obtained from the performance library.

Table describing the monitoring activities of the agent. Adding rows to this table causes the agent to monitor new objects; deleting rows from the table causes the agent to cease monitoring the associated object. Row creation follows the V2 SMI RowStatus textual convention (See RFC 1443).

Each entry in the Monitor Table represents a single variable or function that the agent is monitoring. Variables are those objects in the MIB for which the agent is tracking. Likewise, functions that the agent are calling periodically as part of its internal implementation are available for manipulation via this table.

A unique value for entry in the monitorTable. The index values in the monitorTable may not necessarily be contiguous, but are unique.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

The interval, in seconds, between successive samples by the agent. It must be a multiple of 30 seconds. For example, if a manager wanted to sample the value of a particular variable every 30 seconds, then setting monInterval to 30 would instruct the agent to sample once very 30 seconds. The sampling period is not exact but represents a best-effort by the agent.

The type of sampling performed on the object represented by this entry. For example, for sampling and monitoring objects of type Counter, setting the appropriate monSampleType to deltaValue(2) causes the agent to measure/sample the rate of change in the variable rather than the absolute value. For gauge and gauge-like variables, absoluteValue(1) makes more sense. The agent does not perform sanity checks on this variable against the type of object being monitoring because there may exist some case where a manage may actually wish to monitor the absolute value of a counter or the delta value of a gauge. Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

The object identifier (including properly formed instance) of the variable being monitoring by this monitorTable entry. For example, if a manager wanted to monitor the number of packets received on a particular network interface, that manager would write the object identifier corresponding to the appropriate counter (e.g. ifTable.ifEntry.ifInUCastPkts.1 for the first interface). During row creation, the agent ensures that the object identifier is valid. If invalid, the agent returns BadValue. This variable can represent both scalar and tabular objects as well. If, at any point during the row's lifetime, the variable no longer exists in the agent's MIB, the row's status is set to notInService(2).

This variable represents the current value of the object being monitored as last sampled by the agent. If the monSampleType is deltaValue(2), then this value represents the difference between two successive samples. If monSampleType is absoluteValue(1), then this value represents the actual sampled value.

The boolean operator performed in the expression: monCurrVal monOperator monValue. For example, to monitor a value such that an alarm is generated when its value rises about 100, the expression: currValue gt 100 could be used. Likewise, currValue ge 101 could also be used. The value of nop(1) causes the agent to perform no boolean comparison; it is useful when a manager wishes that an agent track the value of some object but not perform any evaluation of its value. Enumeration: 'le': 5, 'nop': 1, 'ge': 4, 'ne': 7, 'lt': 3, 'gt': 2, 'eq': 6.

The value against which the agent compares the current value. This value represents a threshold. Its semantics are not interpreted by the agent; therefore, the manager is responsible for determining if this value 'makes sense'.

The time (based on sysUpTime) at which the agent last called or sampled the object being monitored. If the object has not yet been sampled, 0 is returned.

The number of traps sent for this particular monitor entry. This value indicates how many times the agent has evaluated this entry's expression as true. Recall, the expression takes the form of: 'monCurrVal monOperator monValue'. Because this value depends on the semantics of the variable, the entry's sampling interval (monInterval), and the interval at which the monitoring table is evaluated, it represents a lower bound on the number of times the threshold has actually been crossed.

The time (based on sysUpTime) at which the agent last sent a trap for this Monitor Table entry. If no traps have been sent, the value is 0.

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(2) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular Monitor Table entry, its monRowStatus column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

The minimum sampled value or 0 upon initialization

The maximum sampled value or 0 upon initialization

A string specifying the command to be executed upon finding a match.

The flags field dictates the behavior of each Monitor Entry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical or'ing together of different bits allows one to combine different options. Hex Function Default (if not enabled) 0x01 Do not execute actions Execute actions 0x02 Do not send Traps Send Traps 0x04 Do not re-initialize Re-initialize 0x08 Do not log events Log events 0x10 Send cont notReady Traps Send single notReady Trap 0x100 Send Clear Traps Do not send Clear Traps 0x200 Threshold after X events Threshold after 1st 0x400 X consec Thresh Traps No limit 0xfff00000 Flags value specification Default is 0

An SNMP Get of this MIB object returns an un-used monitor index number. It can be used for monitor table row creation optimization.

This MIB object, when used in conjunction with monMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the monitor table and place the index value of the last entry whose description matches, in the monMatchIndex MIB object.

See description for monMatchDescr.

The total number of RPC calls sent by the RPC client protocol software.

The total number of RPC calls rejected by the RPC client protocol software.

The total number of times an RPC call had to be retransmitted due to a timeout while waiting for an RPC server reply.

The total number of times a server RPC reply was received for which no outstanding call exists.

The total number times an RPC call timed out while waiting for a reply from the RPC server.

The total number of times an RPC call has to wait because no client handle was available.

The total number of times authentication information had to be refreshed.

The total number of times the calculated time-out value was greater than or equal to the minimum specified time-out value for an RPC call.

The total number of RPC calls received by the RPC server protocol software.

The total number of calls rejected by the RPC server protocol softeware; it is equivalent to the sum of the MIB objects serverRPCBadlen and serverRPCxdrcall.

The number of RPC requests not available when it was thought to be received.

The number of RPC requests whose lengths were shorter than the minimum size RPC message.

The number of RPC requests whose header could not be XDR decoded.

The total number of NFS calls sent by the NFS client protocol software.

The total number of times an NFS call was rejected by the underlying client RPC protocol software.

The total number of times a client NFS handle was received by the NFS client protocol software.

The total number of times a client NFS call had to sleep while waiting for a client NFS handle.

The total number of NFS 'NULL' procedure calls sent by the client NFS protocol software. The 'NULL' procedure is often used to allow server response testing and timing.

The total number of NFS 'GetAttr' procedure calls sent by the client NFS protocol software. This function is used to obtain attributes for a given file.

The total number of NFS 'SetAttr' procedure calls sent by the client NFS protocol software. This function is used to set a file's attributes.

The total number of NFS 'Root' procedure calls sent by the client NFS protocol software. This function has been declared obsolete.

The total number of NFS 'Lookup' procedure calls sent by the client NFS protocol software. This function is used to retrieve a file's attributes and handle.

The total number of NFS 'Read link' procedure calls sent by the client NFS protocol software. This function is used to read from a symbolic link.

The total number of NFS 'Read' procedure calls sent by the client NFS protocol software. This function is used to read data (in units of bytes) from a give file.

The total number of NFS 'Write Cache' procedure calls sent by the client NFS protocol software. This function is to be used in future versions of the NFS protocol.

The total number of NFS 'Write' procedure calls sent by the client NFS protocol software. This function is used to write data (in units of bytes) to a given file.

The total number of NFS 'Create' procedure calls sent by the client NFS protocol software. This function is used to create a file in a given directory.

The total number of NFS 'Remove' procedure calls sent by the client NFS protocol software. This function is used to remove a file from a given directory.

The total number of NFS 'Rename' procedure calls sent by the client NFS protocol software. This function is used to rename a given file.

The total number of NFS 'Create Link' procedure calls sent by the client NFS protocol software. This function is used to create a link to a given file.

The total number of NFS 'Create Symbolic Link' procedure calls sent by the client NFS protocol software. This function is used to create a symbolic link to a given file.

The total number of NFS 'mkdir' procedure calls sent by the client NFS protocol software. This function is used to create a directory within a given directory.

The total number of NFS 'rmdir' procedure calls sent by the client NFS protocol software. This function is used to remove a given directory.

The total number of NFS 'readdir' procedure calls sent by the client NFS protocol software. This function is used to read a variable number of directory entries from the given directory.

The total number of NFS 'stat' procedure calls sent by the client NFS protocol software. This function is used to retrieve file system statistics.

The total number of NFS calls received by the NFS server protocol software.

The total number of times an NFS call was rejected by the underlying server RPC protocol software.

The total number of NFS 'NULL' procedure calls received by the server NFS protocol software. The 'NULL' procedure is often used to allow server response testing and timing.

The total number of NFS 'GetAttr' procedure calls received by the server NFS protocol software. This function is used to obtain attributes for a given file.

The total number of NFS 'SetAttr' procedure calls received by the server NFS protocol software. This function is used to set a file's attributes.

The total number of NFS 'Root' procedure calls received by the server NFS protocol software. This function has been declared obsolete.

The total number of NFS 'Lookup' procedure calls received by the server NFS protocol software. This function is used to retrieve a file's attributes and handle.

The total number of NFS 'Read link' procedure calls received by the server NFS protocol software. This function is used to read from a symbolic link.

The total number of NFS 'Read' procedure calls received by the server NFS protocol software. This function is used to read data (in units of bytes) from a give file.

The total number of NFS 'Write Cache' procedure calls received by the server NFS protocol software. This function is to be used in future versions of the NFS protocol.

The total number of NFS 'Write' procedure calls received by the server NFS protocol software. This function is used to write data (in units of bytes) to a given file.

The total number of NFS 'Create' procedure calls received by the server NFS protocol software. This function is used to create a file in a given directory.

The total number of NFS 'Remove' procedure calls received by the server NFS protocol software. This function is used to remove a file from a given directory.

The total number of NFS 'Rename' procedure calls received by the server NFS protocol software. This function is used to rename a given file.

The total number of NFS 'Create Link' procedure calls received by the server NFS protocol software. This function is used to create a link to a given file.

The total number of NFS 'Create Symbolic Link' procedure calls received by the server NFS protocol software. This function is used to create a symbolic link to a given file.

The total number of NFS 'mkdir' procedure calls received by the server NFS protocol software. This function is used to create a directory within a given directory.

The total number of NFS 'rmdir' procedure calls received by the server NFS protocol software. This function is used to remove a given directory.

The total number of NFS 'readdir' procedure calls received by the server NFS protocol software. This function is used to read a variable number of directory entries from the given directory.

The total number of NFS 'stat' procedure calls received by the server NFS protocol software. This function is used to retrieve file system statistics.

Table describing/controlling the object history collection. Adding rows to this table causes the agent to track the history of additional objects; deleting rows from the table causes the agent to cease tracking the value of an object. Row creation follows the V2 SMI RowStatus textual convention (See RFC 1443). Further, the table is similar to the RMON HistoryControlTable in purpose (See RFC 1271).

A list of parameters that set up a periodic sampling of a single object value contained within the agent's internal MIB.

An index that uniquely identifies an entry in the empireHistoryCtrlTable. Each such entry defines a periodic sampling/history that the agent performs. The sample values can be obtained from the empireHistoryTable.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

The interval in seconds between successive samples. The sample interval must be a multiple of 30 seconds.

The object identifier of the particular object to be sampled. This object identifier must refer to a valid object and be of base type INTEGER. For example, objects of type Counter, INTEGER, and Gauge can be sampled, but objects of type DisplayString cannot.

The ASN1/SNMP tag value of the object being sampled. For example, an SNMP Gauge would be 0x42 or 66 decimal.

The requested number of discrete samples of data to be saved in the empireHistoryTable. When this object is created or modified, the agent sets the empireHistoryCtrlBucketsGrant as close as possible.

The number of number of discrete samples of data which shall be saved in the empireHistoryCtrlTable.

The value of sysUpTime when this entry was last evaluated by the agent.

The value of sysUpTime when this entry was created by the agent.

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(6) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular table entry, its Status column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

Table containing the history samples corresponding to history control entries contained in the empireHistoryCtrlTable. For each entry in the control table, a set of history samples will exist in this table. Managers can index a particular sample by combining the corresponding index from the control table with a sample number.

A historical sample of an object in the agent's MIB. Each sample is associated with an entry in the empireHistoryCtrlTable which set up the parameters for a regular collection of these samples.

The history of which this entry is a part. This value identifies a row in the empireHistoryCtrlTable of which this sample is a part.

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same history control entry. This index starts at 1 and increases by one as each new sample is taken.

The value of sysUpTime at which the first sample was taken.

The value of sysUpTime at which this particular sample was taken.

The value of this sample.

An SNMP Get of this MIB object returns an un-used history control index number. It can be used for history control table row creation optimization.

This MIB object, when used in conjunction with histCtrlMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the history control table and place the index value of the last entry whose description matches, in the histCtrlMatchIndex MIB object.

See description for histCtrlMatchDescr.

Table containing log monitor entries; each entry specifies a log file and regular expression. The agent periodically stats the log files to see if they have been updated. If updated, the agent scans the new entries for the regular expression. When that regular expression is found (or matched) in the new entries, a trap PDU is sent to appropriate managers.

An entry in the logMonitorTable.

An index that uniquely identifies an entry in the logMonitorTable.

The name of the log file to scan for pattern matches. This variable must name a valid log filename.

The display string representation of the regular expression to match in the corresponding log file. Valid regular expressions are those as defined in ed(1).

The number of traps sent by the agent on behalf of this entry. One trap PDU message is sent for each match the agent detects in the corresponding log file (if Traps have not been disabled for this entry).

The time (based on sysUpTime) at which the agent last sent a trap for this entry. Alternatively, it is the time at which the last pattern match occurred.

The last log file entry that matched the logMonitorRegularExpression. Each time a match occurs, this variable is updated.

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(2) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular logMonitor Table entry, its Status column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

The size in bytes of the log file at time of last sample. By querying this value, one can tell if the log file is growing.

The time (based on sysUpTime) that the log file was last modifed by the system or application(s) writing to this file. Monitoring this value can indicate if the system or application(s) that log to this file are active.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

A textual string specifying the command to be executed upon finding a match.

The flags field dictates the behavior of each logMonitorEntry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical or'ing together of different bits allows one to combine different options. Hex Function Default (if not enabled) 0x01 Do not execute actions Execute actions 0x02 Do not send Traps Send Traps 0x04 Do not re-initialize Re-initialize 0x08 Do not log events Log events 0x10 Send cont notReady Traps Send single notReady Trap 0x100 Apply logical NOT oper No additional operator

The number of logfile entries matching the regular expression; this value is incremented regardless of whether Traps are sent for this entry or not. Polling this variable allows you to determine the rate or number of matches over time.

An SNMP Get of this MIB object returns an un-used logfile monitor index number. It can be used for logfile monitor table row creation optimization.

This MIB object, when used in conjunction with logmonMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the logfile monitor table and place the index value of the last entry whose description matches, in the logmonMatchIndex MIB object.

See description for logmonMatchDescr.

Table containing disk I/O stat entries; each entry provides the latest disk statistics for one disk. The agent periodically stats the system data structures for each disk and records the values in the table.

An entry in the diskStatsTable.

An index that uniquely identifies an entry in the diskStatsTable.

The average number of operations waiting in the disk's service queue over the last measurement period.

The average service time in milliseconds for operations served on this disk over the last measurement period. This could be expressed as: disk-busy-time / number-of-transfers.

The utilization rate (percentage utilization) for this disk over the last measurement period. This could also be expressed as: (disk-busy-time / elapsed-time) * 100.

The number of KBytes transferred to/from this disk.

The number of transfer operations to/from this disk.

The number of read operations from this disk.

The number of write operations to this disk.

The index of this disk device in the device table of the Host Resources MIB.

The time in SNMP Time Ticks of the last update of this diskStatsTable entry.

Number of KBbytes transfered to/from this disk in ascii string format so that 64-bit values can be passed w/o having to go through high/low order word calculations.

Number of transfer operations to/from this disk in ascii string format so that 64-bit values can be passed w/o having to go through high/low order word calculations.

The number of read operations from this disk in ascii string format so that 64-bit values can be passed w/o having to go through high/low order word calculations.

The number of write operations to this disk in ascii string format so that 64-bit values can be passed w/o having to go through high/low order word calculations.

High-order 32-bits of diskStatsKBytesTransferred if the underlying system supports 64-bit disk stats; zero otherwise. Recovering the 64-bit counter is as simple as: diskStatsKBytesXferHi << 32 | diskStatsKBytesTransferred

High-order 32-bits of diskStatsTransfers if the underlying system supports 64-bit disk stats; zero otherwise. Recovering the 64-bit counter is as simple as: diskStatsXferOpsHi << 32 | diskStatsTransfers

High-order 32-bits of diskStatsReads if the underlying system supports 64-bit disk stats; zero otherwise. Recovering the 64-bit counter is as simple as: diskStatsReadsHi << 32 | diskStatsReads

High-order 32-bits of diskStatsWrites if the underlying system supports 64-bit disk stats; zero otherwise. Recovering the 64-bit counter is as simple as: diskStatsWritesHi << 32 | diskStatsWrites

This table provides per-cpu statistics and counters; the agent periodically (approximately every 60 seconds) updates data contained in this table. By periodically sampling entries in this table, one can determine the percentage of time spent by each CPU in their respective modes. This percentage can be calculated by summing the total 'ticks' spent in each mode and then dividing the 'ticks' spent in each mode by the total. 'Ticks' is a system-dependent quantity whose unit is not necessary when calculating the percentage of time spent in each CPU mode.

An entry in the cpuStatsTable

An index that uniquely identifies an entry in the cpuStatsTable.

The type of CPU for which statistics are reported. On Solaris 2.x, this description also includes the CPU's clock speed.

The total number of 'ticks' spent by this CPU in Idle mode. This variable is not supported by NT. This value may wrap 32-bit counter.

The total number of 'ticks' spent by this CPU in User mode. This value may wrap 32-bit counter.

The total number of 'ticks' spent by this CPU in Kernel or system mode. This value may wrap a 32-bit counter.

The total number of 'ticks' spent by this CPU in Wait mode. Wait mode is that time spent waiting on I/O or swap. It may wrap a 32-bit counter.

The time (based on sysUpTime) that the counters for this CPU were last updated. Because these values are cached periodically by the agent, the time of last update is important for determining the interval over which CPU mode percentages are calculated.

The percentage of time (over the sample period) that the system's CPU was idle.

The percentage of time (over the sample period) that the system's CPU was executing in user mode.

The percentage of time (over the sample period) that the system's CPU was executing the kernel or operating system.

The percentage of time (over the sample period) that the system's CPU was waiting for I/O. This object may not be supported by the underlying operating system.

The total number of 'ticks' spent by all CPUs in Idle mode. This variable is not supported by NT. This value may wrap 32-bit counter.

The total number of 'ticks' spent by all CPUs in User mode. This value may wrap 32-bit counter.

The total number of 'ticks' spent by all CPUs in Kernel or system mode. This value may wrap a 32-bit counter.

The total number of 'ticks' spent by all CPUs in Wait mode. Wait mode is that time spent waiting on I/O or swap. It may wrap a 32-bit counter.

The time (based on sysUpTime) that these counters were last updated. Because these values are cached periodically by the agent, the time of last update is important for determining the interval over which CPU mode percentages are calculated.

The percentage of time (over the sample period) that the system's CPUs were idle.

The percentage of time (over the sample period) that the system's CPUs were executing in user mode.

The percentage of time (over the sample period) that the system's CPUs were executing the kernel or operating system.

The percentage of time (over the sample period) that the system's CPUs were waiting for I/O. This object may not be supported by the underlying operating system.

The Domain Name Service domain name for this host. This value is obtained by a shell script included with the agent distribution.

The NIS (YP) server currently being used by this host. This value is obtained by a shell script included with the agent distribution.

The Message Of The Day. Return the first line of the /etc/motd file on this host. This value is obtained by a shell script included with the agent distribution.

This variable allows the agent to support remote Ping operations. This functionality is useful for remote troubleshooting of routing problems. Sets to this object indicate which system to Ping while Get and GetNext operations perform the Ping operation and return its output.

The process monitor table used for monitoring single instances of processes.

A process monitor entry; one entry per process to monitor.

A unique value for entry in the processMonTable. The index values in the processMonTable may not necessarily be contiguous, but are unique.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

The interval, in seconds, between successive samples by the agent. It must be a multiple of 30 seconds. For example, if a manager wanted to sample the value of a particular variable every 30 seconds, then setting monInterval to 30 would instruct the agent to sample once very 30 seconds. The sampling period is not exact but represents a best-effort by the agent.

The type of sampling performed on the object represented by this entry. For example, for sampling and monitoring objects of type Counter, setting the appropriate monSampleType to deltaValue(2) causes the agent to measure/sample the rate of change in the variable rather than the absolute value. For gauge and gauge-like variables, absoluteValue(1) makes more sense. The agent does not perform sanity checks on this variable against the type of object being monitoring because there may exist some case where a manage may actually wish to monitor the absolute value of a counter or the delta value of a gauge. Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

The process attribute being monitored. These enumerated values map directly to columns in the Empire Process table. Enumeration: 'procMsgsSent': 8, 'procMajorPgFlts': 15, 'procMinorPgFlts': 14, 'procTime': 5, 'procNumSwaps': 12, 'procNumThreads': 11, 'procOutBlks': 7, 'procMemory': 2, 'procInvolCtx': 17, 'procNice': 10, 'procRSS': 4, 'procSysCalls': 13, 'procAlive': 1, 'procSize': 3, 'procVolCtx': 16, 'procMsgsRecv': 9, 'procInBlks': 6.

This variable represents the current value of the object being monitored as last sampled by the agent. If the pmonSampleType is deltaValue(2), then this value represents the difference between two successive samples. If pmonSampleType is absoluteValue(1), then this value represents the actual sampled value.

Enumeration: 'le': 5, 'nop': 1, 'ge': 4, 'ne': 7, 'lt': 3, 'gt': 2, 'eq': 6.

The value against which the agent compares the current value. This value represents a threshold. Its semantics are not interpreted by the agent; therefore, the manager is responsible for determining if this value 'makes sense'.

The time (based on sysUpTime) at which the agent last called or sampled the object being monitored. If the object has not yet been sampled, 0 is returned.

The number of traps sent for this particular monitor entry. This value indicates how many times the agent has evaluated this entry's expression as true. Recall, the expression takes the form of: 'pmonCurrVal pmonOperator pmonValue'. Because this value depends on the semantics of the variable, the entry's sampling interval (monInterval), and the interval at which the monitoring table is evaluated, it represents a lower bound on the number of times the threshold has actually been crossed.

The time (based on sysUpTime) at which the agent last sent a trap for this Monitor Table entry. If no traps have been sent, the value is 0.

The flags field dictates the behavior of each processMonEntry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical or'ing together of different bits allows one to combine different options. Hex Function Default (if not enabled) 0x01 Do not execute actions Execute actions 0x02 Do not send Traps Send Traps 0x04 Do not re-initialize Re-initialize 0x08 Do not log events Log events 0x10 Send cont Stop Traps Send single Stop Trap 0x100 Monitor parent process Monitor first found 0x200 Do not send Start Trap Send Start Trap 0x400 Send Clear Traps Send Clear Traps 0x800 Match name and args Match process name only 0x1000 Threshold after X events Threshold after 1st 0x2000 X consec Thresh Traps No limit 0x4000 Monitor for X processes Monitor for single process 0xfff00000 Flags value specification Default is 0

A string specifying the command to be executed upon finding a match.

The regular expression to use for matching processes by name or NT services by name

The minimum sampled value or 0 upon initialization

The maximum sampled value or 0 upon initialization

The PID of the process being monitored

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(2) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular processMonTable entry, its pmonRowStatus column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

The number of events for this process monitor entry. Events do not necessarily imply traps because Traps may be turned off for this row via flags setting.

An SNMP Get of this MIB object returns an un-used processMonitorTable index number. It can be used for processMonitor table row creation optimization.

This MIB object, when used in conjunction with pmonMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the process monitor table and place the index value of the last entry whose description matches, in the pmonMatchIndex MIB object.

See description for pmonMatchDescr.

The process group monitor table used for monitoring arbitrary groups of processes.

A process group monitor entry; one entry per group of processes to monitor.

A unique value for entry in the processGroupMonTable. The index values in the processGroupMonTable may not necessarily be contiguous, but are unique.

A textual description of this entry possibly identifying the purpose of this entry and who created it.

The interval, in seconds, between successive samples by the agent. It must be a multiple of 30 seconds. For example, if a manager wanted to sample the value of a particular variable every 30 seconds, then setting monInterval to 30 would instruct the agent to sample once very 30 seconds. The sampling period is not exact but represents a best-effort by the agent.

The regular expression to use for matching processes by name

The flags field dictates the behavior of each processGroupMonEntry. Each bit in the integer represents the toggling of an option. The flags field of 0x00 is enables default behavior. Logical or'ing together of different bits allows one to combine different options. SystemEDGE common-table flags apply to this table. Table-specific flags include are defined below. Hex Function Default (if not enabled) 0x100 Match name and args Match process name only

The current number of processes in the process group being tracked by this table entry. A process belongs to the process-group if its name (and possibly args) match the regular expression configured for this entry.

A list of the numeric PIDs in this process group separated by space character.

A list of the process states in this process group separated by space character. See processStateInt for explanation of the state of a process. Entries in the status list have a one-to-one correspondence with entries in the PID list.

A string specifying the command to be executed upon process group event.

The number of events for this process group table entry. Events do not necessarily imply traps because Traps may be turned off for this row via flags setting.

The number Traps sent for this process group table entry.

The time (based on sysUpTime) at which the agent last sent a trap for this entry. If no traps have been sent, the value is 0.

The status of this entry. This variable is equivalent in semantics to the V2 SMI RowStatus textual-convention (see RFC 1443). A value of active(1) indicates that the agent is currently monitoring and evaluating the current row. A Value of notInService(2) indicates that the agent has suspended evaluation of the row. Setting this object to destroy(2) causes the agent to suspend evaluation of its row and free its resources. For row creation to occur, the manager must supply active(1), createAndGo(4), createAndWait(5), or notInService(2) as the value of this object. If an error occurs at any time during the processing of a particular processGroupMonTable entry, its pgmonRowStatus column will be set to notReady(3). Enumeration: 'createAndWait': 5, 'notInService': 2, 'notReady': 3, 'createAndGo': 4, 'active': 1, 'destroy': 6.

The combined resident set size of the group of processes. (See processRSS). RSS for each process in the group is summed each interval and stored in this MIB variable. Because RSS also includes shared-memory, the total RSS for a group could actually exceed total possible physical memory for the underlying system.

The cobmined size of text/data/stack segments of the group of processes. (See processSize) Size for each process in the group is summed each interval and stored in this MIB variable. Because Size also includes shared-memory, the total Size for a group could actually exceed total virtual memory for the underlying system.

The total number of threads for the group of processes. (See processNumThreads) The number of threads running in each process in the group is summed each interval and stored in this MIB variable.

The total percentage of real memory used by the processes in this group. The percentage of memory used by each process in the group is summed each interval and stored in this MIB variable. Because memory usage includes shared memory (e.g. shared librarys and DLLs), the total percentage may exceed 100.

Number of blocks of data input by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of blocks of data output by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of messages sent by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of messages received by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of system calls invoked by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of minor page faults incurred by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of major page faults incurred by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of times processes in this gropu have been swapped. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of voluntary context switches incurred by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of involuntary context switches incurred by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

Number of seconds of CPU time used by processes in this group. SystemEDGE maintains a 'history' of group membership and tracks process stats even after an individual process has left the group.

If set to a valid username, SystemEDGE will match running processes by username in addition to any process name regular expression. Only valid on UNIX.

If set to a valid groupname, SystemEDGE will match running processes by group name in addition to any process name regular expression and username matching. Only valid on UNIX.

An SNMP Get of this MIB object returns an un-used processGroupMonitorTable index number. It can be used for processMonitor table row creation optimization.

This MIB object, when used in conjunction with pgmonMatchIndex can be used to quickly determine the index number corresponding to a particular entry description. SNMP Set'ing a description to this MIB object causes the agent to search through entries in the process group monitor table and place the index value of the last entry whose description matches, in the pgmonMatchIndex MIB object.

See description for pgmonMatchDescr.