The following is a list of Events management objects (SNMP Groups)
that can be monitored or altered. This group of objects is defined in the AgentMon MIB.
This section lists the SNMP Groups and their test results
Group | Action |
|---|---|
OBJECT IDENTIFIER::={ Events20 1 } This SNMP group is used to manage Events from a network management station. It allows the Network Manager to reconfigure Events in many of the same ways that the System Administrator can with the Configure Events GUI. | |
OBJECT INDENTIFIER::={ Events20 2 } This group is also used by the Network Manager. This group is used for enabling and disabling TRAPs and for changing the severity level associated with each TRAP. | |
OBJECT INDENTIFIER::={ Events20 3 } Displays read-only values for the operating system name, local time, and time of last reboot. | |
kernel | OBJECT INDENTIFIER::={ Events20 4} Displays values for various kernel-related statistics. These values are useful for an OS kernel guru who likes to tweak the O/S for performance. |
OBJECT INDENTIFIER::={ Events20 5} Displays statistics for various network-related message buffers. | |
OBJECT INDENTIFIER::={ Events20 6} Displays statistics on the Name Cache (if present). | |
OBJECT INDENTIFIER::={ Events20 7} Displays statistics about the virtual memory system. | |
OBJECT INDENTIFIER::={ Events20 8} Displays the CPU load (average growth of a run queue) and CPU time for the following states: kernel, user, system, and idle (as a percentage; total % of four states = 100%). | |
OBJECT INDENTIFIER::={ Events20 9} Displays the number loaded, CPU time used, and the process size for a user-selected process. The process status is also available on some operating systems. | |
OBJECT INDENTIFIER::={ Events20 10 } Displays a list of local filesystems, their size, and the amount of free space available. This may also include swap space. | |
OBJECT INDENTIFIER::={ Events20 11} For each user-specified file, this reports one or more of the user-specified items: filename, size, last accessed time, last time file was modified, or last string matched if `file clamping' is selected and the user has specified one or more regular expressions. | |
OBJECT INDENTIFIER::={ Events20 12} For each user-specified directory, this reports the total number of files and number of old files in the directory. This also has a variable field (for each directory) so the user can specify what `old' is. | |
OBJECT INDENTIFIER::={ Events20 13} Displays a list of all hardware that was discovered on the system when Events was last started. | |
OBJECT INDENTIFIER::={ Events20 14} Displays a list of all software currently installed on the system, if such software was (de)installed with pkgadd. On SCO UNIX, the list also includes all software installed with custom. | |
OBJECT INDENTIFIER::={ Events20 15} Displays the printer daemon's view of the current status for each printer being monitored. | |
OBJECT INDENTIFIER::={ Events20 16 } This group is reserved for future use. | |
rpc | OBJECT INDENTIFIER::={ Events20 17} Displays RPC client and server statistics. |
OBJECT INDENTIFIER::={ Events18-23 } This group allows Events to monitor user-provided data. If you have test scripts that already collect data, you could modify the scripts to write any data to a file. Then you could use one or more of the API groups to monitor the data in the file and check for High and Low thresholds.
Like all other tests, a threshold violation could then send email or a TRAP, notify PEP, and be logged to the EMD. Logging of non-alarm data is also provided, just as it is with other tests.
See Chapter 5, “Monitoring Network Systems With Events,” in the EnlightenDSM User Guide for more details on using API tests. | |
usertraps | OBJECT INDENTIFIER::={ Events20 24 } This group shows the last TRAP PDU that was initiated through the EventsCli command line interface. The EventsCli is an “open” interface between your existing shell scripts (and other monitoring programs) and the Events alarm notification methods (PEP, TRAPs, EMD). This is best suited to users who are already monitoring site-specific data and have their own threshold logic.
When your tests detect an alarm condition, they could call the EventsCli. This then gives you easy access to our event management framework. See “EventsCli (8N)” for more details. |
This section lists the MIB II Groups and their object identifiers.
Group | Action |
|---|---|
mib-2 | OBJECT IDENTIFIER::={ mgmt 1 } Events20 also provides MIB-2 functionality in addition to UNIX MIB. MIB-2 primarily relates to statistics concerned with various network protocols. |
AgentMon can issue Enterprise-specific traps. Each trap is manageable via SNMP. A trap is issued whenever the corresponding measured value traverses an alarm threshold (if one is specified) and the particular trap is enabled. Our Internet Enterprise number is:
1.3.6.1.4.1.548.1.2.2 |
The first part “1.3.6.1.4.1.548” identifies “our” SNMP domain and the remaining numbers refer to a specific MIB of ours, in this case, our UNIX MIB: Events20.
To enable and disable traps, use the trapmanage group from your Network Management Application. Changes take effect immediately and become the new start-up values should Events be restarted later. Only Network Administrator can enable and disable Traps, via SNMP. If a new test is added to Events, and that test has an associated trap, the trap will be disabled.
For instance, the blocksFree trap refers to the amount of free space on a filesystem. There is a single trap type (trap #12), but you can enable and disable each “instance type” (i.e., enable/disable per filesystem). The Enterprise-specific traps and the reasons they are sent (alarm conditions) are defined in the following table.
Trap Name | Alarm Condition |
|---|---|
Number of message buffer clusters | |
Amount of virtual memory remaining | |
3. swapfree | Amount of free swap space |
Average lenth of the CPU run queue | |
5. cpuuser | Percentage of time CPU has spent in user mode |
6. cpukernel | Percentage of time CPU has spent in kernel mode |
7. cpuwait | Percentage of time CPU has spent in wait mode |
8. procinstance | Number of instances of a process has changed |
9. procsize | Size of a process has changed |
10. proctime | CPU usage (time) of a process |
11. procfree | Number of free process slots in kernel |
12. fsbfree | Filesystem space (number of blocks free) |
13. fsifree | Filesystem inodes (number of inodes free) |
14. filesize | Size of a file |
15. filemtime | Modification time of a file |
16. fileatime | Time of last access of a file |
Number of old files in a directory | |
Total number of files in a directory | |
19. hwchange | Change in the hardware inventory |
20. swchange | Change in the software inventory |
21. printerState | Change in the status of a printer |
22. api1trap | User-provided data |
23. api2trap | User-provided data |
24. api3trap | User-provided data |
25. api4trap | User-provided data |
26. api5trap | User-provided data |
27. api6trap | User-provided data |
28. fileclamp | Regular expression match occurred in a file |
500. utrap500 | TRAP originating from an instance of the EventsCli |
501. utrap501 | TRAP originating from an instance of the EventsCli |
502. utrap502 | TRAP originating from an instance of the EventsCli |
503. utrap503 | TRAP originating from an instance of the EventsCli |
504. utrap504 | TRAP originating from an instance of the EventsCli |
505. utrap505 | TRAP originating from an instance of the EventsCli |
506. utrap506 | TRAP originating from an instance of the EventsCli |
507. utrap507 | TRAP originating from an instance of the EventsCli |
508. utrap508 | TRAP originating from an instance of the EventsCli |
509. utrap509 | TRAP originating from an instance of the EventsCli |
510. utrap510 | TRAP originating from an instance of the EventsCli |
511. utrap511 | TRAP originating from an instance of the EventsCli |