This software receives and decodes an SNMP Trap that is sent from a device, and handles a device status change as an event for managing device errors.
The event is created based on the contents of SNMP traps and user settings.
The processing described below is performed for generated events.
As for the following event, this software only displays event logs, and other processing are not performed.
Trap events common to devices (the trap common to devices in "Events in Notifications Sent from Monitored Devices" in the ETERNUS SF Event Guide)
Start of performance data re-collection/Success of performance data re-collection event (Success of performance data re-collection, Success of performance data re-collection in "Performance Management Traps" in "Events in Notifications Sent from Monitored Devices" in the ETERNUS SF Event Guide)
Event that indicates when the state changes into error(red) in the device polling function ("When the state changes into error(red)"in the device polling function "Device Polling Event" in the ETERNUS SF Event Guide)
See
Refer to "Appendix A Customization" for detailed information on how to customize SNMP Trap processing.
Generated events are displayed in the event log of the Web Console. Events are displayed shown as below.
Displayed items | details |
|---|---|
type | Displays the level of a displayed event. |
date | Displays time and date event occurred in Month DD, YYYY HH:MM:SS AM (or PM). |
device | Displays the name of a device on which the event occurred. |
message | Indicates the event ID and its details. This ID is defined in the manager that is monitoring the event. |
Note
If multiple SNMP Traps comprised of the same information are received from a device at the same time and date, only the first received SNMP Trap will be displayed on the event log.
Also, generated events are reported to Systemwalker Centric Manager. Refer to "10.1 Linkage with Systemwalker Centric Manager" for information on settings required in advance. The importance levels of the events are also reported.
Note
Events of the server node agent is not reported to Systemwalker Centric Manager. (Shell/Bat linkage is operated.) Execute fault monitoring by message monitoring function of Systemwalker Centric Manager.
A generated event is specified in the call argument of the Shell file, such shown as below.
Platform of Manager | File name (full path) |
|---|---|
Windows | $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\trapop.bat arg1 arg2 arg3 arg4 arg5 arg6 |
Solaris OS, | /etc/opt/FJSVssmgr/current/trapop.sh arg1 arg2 arg3 arg4 arg5 arg6 |
The "arg1" is the fault detail for the target device.
The "arg2" is the IP address for the target device.
The "arg3" is the server node name (FQDN) for the target device (if the full domain name cannot be confirmed, the IP address is set).
The "arg4" is the number of milliseconds that have elapsed from 00:00:00 GMT 01 Jan 1970 ("zero") to the current time.
The "arg5" is the fault level ("INFO", "WARNING"," ERROR").
The "arg6" is the name for the target device.
Rewriting the content of these shell/bat files enables the e-mail linkage of fault information or other Management Software linkage (such as issuing commands to Management Software and writing information to a log file managed by Management Software).
Sample Shell/Bat files are installed in the directories shown below. Copy this sample and create Shell/Bat files for linkage.
Platform of Manager | File location |
|---|---|
Windows | $ENV_DIR\ESC\Manager\opt\FJSVssmgr\lib\sample\trapop.bat |
Solaris OS, | /opt/FJSVssmgr/lib/sample/trapop.sh |
If the Shell/Bat linkage function is not used, there is no need to create these Shell/Bat files.
The following are examples of scripts output in the system log or event log if an event occurs:
@echo off EVENTCREATE /L SYSTEM /ID 999 /SO StorageCruiser /T ERROR /D "%4 %5 %3 %2 %~1"
#!/bin/sh logger -- "$4 StorageCruiser $5 $3 $2 $1"
Note
The IP address of a target device is included in the event message output in the system log or event log.
Perform event output into in the system log or event log in a Manager environment that does not coexist with a server node agent. In the Manager and server node agent coexisting environment, a message may repeatedly be output.
Any external script other than trapop.sh/trapop.bat of Shell/Bat linkage can be executed. Up to two scripts can be defined in each SNMP Trap XML definition file. Arguments for calling such scripts are common to those for Shell/Bat linkage.
Refer to "A.6 SNMP Trap XML Definition File" for information about the methods for defining.
Note
External script linkages must be defined in the SNMP Trap XML definition file. Therefore, they are not available on devices where XML definition files are not provided.
For shell scripts or batch files in Shell/Bat linkages or external script linkages, do not output processing results and processing progress on the screen (for example, do not perform such a process as displaying a message with the echo command). Be sure to describe "@echo off" at the head under Windows.
A created event is notified by e-mail in the following format:
Subject: ETERNUS SF Event Mail From: $1 To: $2 Severity: $3 Date: $4 Device IP: $5 Device Name: $6 Message: $7 |
$1: Indicate e-mail address from where the notification is sent (You need to set it in advance.).
$2: Indicates e-mail address where the notification is sent (You need to set it in advance.).
$3: Indicates the fault level (Information, Warning, Error)
$4: Indicates time and date when the event occurred.
$5: Indicates IP address for the target device
$6: Indicates a name of the target device
$7: Indicates the fault detail
All Warning and Error events will be notified. For Information events, transition of the Thin Provisioning Pool using rate and reduction of Thin Provisioning Pool's capacity are notified. If you want to be notified other Information events, refer to "A.6 SNMP Trap XML Definition File".
Users can customize the displaying of events and descriptions of linkage for individual SNMP Traps. Refer to "A.6 SNMP Trap XML Definition File" for details.
Point
To perform Systemwalker Centric Manager linkage, Shell linkage, or external script linkage, either register the IP address and host name information for each device in the DNS server that is referenced by the Management Server, or define them in the /etc/hosts file on the Management Server so that the names of the devices registered in this software can be resolved.
