 |
» |
|
|
|
Some tunable parameters represent kernel resources
whose usage can be monitored. For these tunables, you can set alarms
to notify you when the usage of the corresponding kernel resource
crosses a threshold you specify. The alarms page allows you to: Activate and deactivate
alarms Find alarms that have
been triggered
You can view the alarms pane by selecting the Alarms tab on the HP SMH Kernel Configuration page, as shown in Figure 10-8. Getting Information about Alarms | |
To get more detailed information about a particular
alarm, do the following: Scroll
to the alarm in the list. Click
the radio button to select it.
The alarm details are displayed under the list,
as shown in Figure 10-9. Interpreting Alarm Information | |
The alarm details block and the alarms list contain
the information shown in Table 10-8. Table 10-8 Kernel Configuration Alarm Fields | Field Name | Description |
|---|
| Tunable | The name of the tunable. | Description of Tunable | The description of the tunable. | | Current Usage Value | The percentage of resource being consumed at the
previous polling. | | Event Type | The event notification to be used. | | Alarm Status | The status of the alarm, one of the following: - on
The alarm is active. - ringing
The alarm has been triggered. - off
The alarm is deactivated.
| | Polling Interval | The time interval between polling. | | Threshold | The percentage at which the alarm should activate. | | Notification Type | The notification method used when the alarm is triggered.
The notification types are: console, email, opcmsg, snmp, syslog, textlog, tcp, and udp. See Table 10-10 for
details. | | Notification Data | Supplementary information used by the notification
method. | | Comment | The comment field; some comment data is added automatically
when alarms are deactivated. | | Tuning Capability | One of static, dynamic, or auto. |
Changing Alarm Settings | |
To change the settings for an alarm, execute the
following steps: Select
the alarm. Click Modify Alarm in the right-hand column of the window. The Modify Kernel Alarm page
is displayed, as shown in Figure 10-10. The Modify Kernel Alarm page
displays the fields shown in Table 10-9. Table 10-9 Modify Alarm Fields Field Name | Description |
|---|
| Tunable | The name of the tunable. | Description of Tunable | The description of the tunable. | | Current Usage Value | The percentage of resource being consumed at the
previous polling. | | Event Type | When notifications are to be sent: initial, repeat, return. See Table 10-10 for details. | | Alarm Status | The status of the alarm, one of the following: - on
The alarm is active. - ringing
The alarm has been triggered. - off
The alarm is deactivated.
| | Polling Interval | The interval, in minutes, between polling of resource
usage. | | Notification Type | The notification method: console, opcmsg, syslog, textlog, email, snmp, tcp, udp. | | Notification Data | Supplementary information used by the notification
method. | | Comment | The comment field; some comment data is added automatically
when alarms are deactivated. | | Tuning Capability | One of static, dynamic, or auto. |
The Modify Kernel Alarm page also displays the areas that
you can change, as shown in Table 10-10. The areas displayed depend on the capabilities of the alarm. Enter
your changes. Table 10-10 Modify Alarm Change Options Field Name | Description |
|---|
| Threshold | Enter the percentage at which the alarm should activate. | | Event Type | Check the boxes that determine when notifications are to be
sent: - initial
First polling at which resource usage exceeds threshold.
Also sent when the alarm is first added, activated, deactivated, or
the system reboots. - repeat
Each polling at which resource usage exceeds the threshold.
This can lead to a large number of messages if the polling interval
is small. - return
First polling at which resource usage falls below
threshold.
If no box is checked, the default event type,
as set by kcalarm, is used. Note: Selecting
both initial and return will
generate a notification whenever the usage crosses above or below
the threshold. | | Polling Interval | Enter the time interval (in minutes) between polling. | | Notification Type | Select the notification method to be used when the
alarm is triggered. The choices are: - console
Send a message to the system console. - email
Send an e-mail to the specified address. Fill in the Email Address field. - opcmsg
Send messages to ITO and OpenView applications
via the opcmsg daemon. Select a value
for Notification Data, one of normal, warning, minor, major, critical. - snmp
Send messages to applications, such as Network
Node Manager, that use SNMP traps. Select a value for Notification Data, one of normal, warning, minor, major, critical. - syslog
Log the alarm in the system log file. - textlog
Log the alarm in a text file. The file is
stored in the directory /var/opt/resmon/log. Fill in a file name in the File Name field. - tcp
Send TCP encoded events to the specified target
host name and port. Fill in the Host Name and Port Number fields. - udp
Send UDP encoded events to the specified target host
name and port. Fill in the Host Name and Port Number fields.
| | Comment | Enter an optional comment. |
(Optional)
To see the command that will execute the changes, click the Preview button. After
you have entered your changes, click the Modify button to execute them. Or click the Cancel button to discard your changes.
Add an Alarm | |
To create a new alarm, execute the following steps: Click Add Alarm in the right-hand column of the Kernel
Configuration Alarms window. The Add Alarm page is displayed, as shown in Figure 10-11. In
the dropdown list of the Tunable field, select
the tunable you want to monitor. Note that only certain tunables are
included in the list. If you select any, an alarm
will be set on all the tunables in the list. You can set more than one alarm on any selectable tunable. Enter
values for the Threshold, Event Type, Polling Interval, Notification Type, and Comment fields, as described in Table 10-10. (Optional)
To see the command that will create the alarm, click the Preview button. After
you have entered your values, click the Add button to create the alarm. Or click the Cancel button to discard it.
Activate, Deactivate, or Remove an Alarm | |
To activate, deactivate, or remove an alarm, execute
the following steps: Select
the alarm. The alarm details are displayed
under the list, as shown in Figure 10-9. At
the bottom of the window, click one of the following buttons: Activate to activate the alarm. The Alarm Status changes
to on. Deactivate to deactivate the alarm. The Alarm Status changes
to off. Remove to delete the alarm. The alarm is removed from the list.
Resource Usage Commands | |
The kcalarm command is used
to add, delete, or list selected kernel tunable alarms, as well as
turn kernel tunable monitoring on and off. kcalarm is used to manage selected
kernel tunable alarms and monitors; alarms and monitors are implemented
in the kcmond daemon. Users can create, modify,
delete, and list selected kernel tunable alarms. Alarms send a notification
though various notification targets when a kernel tunable crosses
a specified percentage threshold of its current setting. Usage monitoring is the process of collecting
historical tunable data. When this feature is turned on, historical
data is collected on the usage of supported tunables. These data are
used by the kcusage command to generate usage tables
(including top consumers) for supported kernel tunables. These data
also enable usage graphs in the HP SMH tool. Monitoring is turned
on by default. For more information, see the kcalarm(1M), kcmond(1M), and kcusage(1M) manpages. To start or stop usage monitoring, you can click Start Usage Monitoring or Stop Usage Monitoring in the right-hand column of any tab on the Kernel Configuration page |
Printable version
