Event notifications
The system can use Simple Network Management Protocol (SNMP) traps, syslog messages, and Call Home emails to notify you and the support center when significant events are detected. Any combination of these notification methods can be used simultaneously. Notifications are normally sent immediately after an event is raised. However, there are some events that might occur because of active service actions. If a recommended service action is active, these events are notified only if they are still unfixed when the service action completes.
Events with notification type Error or Warning are shown as alerts in the event log. Events with notification type Information are shown as messages.
SNMP traps
Simple Network Management Protocol (SNMP) is a standard protocol for managing networks and exchanging messages. The system can send SNMP messages that notify personnel about an event. You can use an SNMP manager to view the SNMP messages that the system sends. You can use the management GUI or the command-line interface to configure and modify your SNMP settings. You can specify up to a maximum of six SNMP servers.
You can use the Management Information Base (MIB) file for SNMP to configure a network management program to receive SNMP messages that are sent by the system. This file can be used with SNMP messages from all versions of the software. More information about the MIB file for SNMP is available at this website:
Search for , then search for MIB. Go to the downloads results to find Management Information Base (MIB) file for SNMP. Click this link to find download options.
Syslog messages
The syslog protocol is a standard protocol for forwarding log messages from a sender to a receiver on an IP network. The IP network can be either IPv4 or IPv6. The system can send syslog messages that notify personnel about an event. The system can transmit syslog messages in either expanded or concise format. You can use a syslog manager to view the syslog messages that the system sends. The system uses the User Datagram Protocol (UDP) to transmit the syslog message. You can specify up to a maximum of six syslog servers.You can use the management GUI or the command-line interface to configure and modify your syslog settings.
| IBM Spectrum Virtualize notification type | Syslog level code | Description |
|---|---|---|
| ERROR | LOG_ALERT | Fault that might require hardware replacement that needs immediate attention. |
| WARNING | LOG_ERROR | Fault that needs immediate attention. Hardware replacement is not expected. |
| INFORMATIONAL | LOG_INFO | Information message used, for example, when a configuration change takes place or an operation completes. |
| TEST | LOG_DEBUG | Test message |
| IBM Spectrum Virtualize value | Syslog value | Syslog facility code | Message format |
|---|---|---|---|
| 0 | 16 | LOG_LOCAL0 | Full |
| 1 | 17 | LOG_LOCAL1 | Full |
| 2 | 18 | LOG_LOCAL2 | Full |
| 3 | 19 | LOG_LOCAL3 | Full |
| 4 | 20 | LOG_LOCAL4 | Concise |
| 5 | 21 | LOG_LOCAL5 | Concise |
| 6 | 22 | LOG_LOCAL6 | Concise |
| 7 | 23 | LOG_LOCAL7 | Concise |
Call Home email
The Call Home feature transmits operational and event-related data to you and service personnel through a Simple Mail Transfer Protocol (SMTP) server connection in the form of an event notification email. When configured, this function alerts service personnel about hardware failures and potentially serious configuration or environmental issues.
To send email, you must configure at least one SMTP server. You can specify as many as 5 additional SMTP servers for backup purposes. The SMTP server must accept the relaying of email from the management IP address. You can then use the management GUI or the command-line interface to configure the email settings, including contact information and email recipients. Set the reply address to a valid email address. Send a test email to check that all connections and infrastructure are set up correctly. You can disable the Call Home function at any time using the management GUI or the command-line interface.
Data that is sent with notifications
- Record type
- Machine type
- Machine serial number
- Error ID
- Error code
- Software version
- FRU part number
- Cluster (system) name
- Node ID
- Error sequence number
- Time stamp
- Object type
- Object ID
- Problem data
- Component ID
- Customer Number
- Country Code
- Contact names for first and second contacts
- Contact phone numbers for first and second contacts
- Alternate contact numbers for first and second contacts
- Offshift phone number
- Contact email address
- Machine location
- For systems that are located in North America, Latin America, South America or the Caribbean Islands, use callhome0@de.ibm.com
- For systems that are located anywhere else in the world, use callhome1@de.ibm.com