trap is not notified, verify the network environment, SNMP manager settings,
and SNMP agent settings.
Table 2-126 Web console operation
Item Operation
Testing SNMP trap
notification
Administration
tab > SNMP > Action button > Send
SNMP trap
Table 2-127 CLI console command
Item Command
Testing SNMP trap notification test snmp trap
Releasing for production
Release the SNMP for production purpose. When a failure is detected in the
system unit, collect the dump log as necessary. For details about dump log,
see Dump log on page 2-264.
Notification by E-mail
This section describes e-mail notification provided by management modules.
Overview
This subsection describes notification triggers.
Notification of failure (triggered by failure occurrence)
When a failure occurs in the system unit, the log information required for the
failure analysis is collected, and then the failure is notified by E-mail with
attached failure log file.
The history of the notified failure is maintained in the management module
by maximum 32 notifications. When the number exceed 32 notification, the
oldest notification is deleted as FIFO basis.
Notification of log dump (triggered by log dump occurrence)
When a log is dumped from the server blade, the log file is attached to the E-
mail. This notification by E-mail is supplemental for the failure notification.
Notification of current status (triggered by manual operation)
After collecting current status of the system unit, you can send the
information by E-mail as an attached file.
2-238
Functional detail
Hitachi Compute Blade 500 Series Management Module Setup Guide
To Next Page
Loading...
