Configuring alerts using esmpro agent for windows – NEC ExpressA1160 User Manual
Page 143
Configuring Alerts using Server Management Software
7-9
7.3.2. Configuring Alerts using ESMPRO Agent for Windows
To configure alert notifications using ESMPRO Agent for Windows
1. Navigate to the ESMPRO Agent for Windows software on a partition on which the
agent is installed.
The ESMPRO Agent Properties window appears.
2. On
the
General
tab, specify the following settings:
• Select
Enable the Manager to modify SNMP Setting
, if you want ESMPRO
Manager to be able to modify server operating parameters using SNMP.
• Select
Permit Remote Shutdown/Reboot
, if you want ESMPRO Manager to
be able to shut down or reboot the server remotely.
• Click
Report Setting
to display and configure Alert Manager. Refer to
7.3.1
Configuring Alerts using ESMPRO Alert Manager.
• Click
Storage Setting
to configure storage monitoring settings. Storage
settings include polling frequency for the service list, free space monitoring,
resetting an exchanged hard disk, and configuring a hard-disk prefailure
prediction.
• Configure other settings as necessary.
3. On
the
CPU
tab, specify the following settings:
• Select
the
Sample interval
seconds to set the CPU load monitoring cycle
interval.
• Select
the
Utilization Rate
to set the CPU load monitoring utilization rate.
• Select
the
CPU Threshold
to set total or individual CPU load.
• Select
Enable threshold
to activate CPU threshold settings.
• Select
Report
and Reset values for Fatal and Warning alerts.
Note: The
Report value identifies the threshold for generating an alert, and
the Reset
value identifies the threshold for dismissing an alert condition.
4. On
the
LAN
tab, specify the following settings:
• Select
Enable threshold
to activate LAN threshold settings.
• Select
the
Sample interval
seconds to set the LAN monitoring cycle interval.
• Select
the
Network hardware error
threshold, which is the percentage of
errors permitted for each monitoring cycle. Network hardware errors include
alignment errors (broken packets for collision), FCS errors (broken packets for
collision), and carrier sense errors (cable disconnected or defective or
transceiver defective).
Note: Be sure that all network cables are tightly connected and the power