Chapter 13. RAS, monitoring, and troubleshooting 725
– The expanded format provides more details about the event. 
/SM590000Event Notifications
Consider the following points about event notifications:
–S e l e c t  Error if you want the user to receive messages about problems, such as 
hardware failures, that must be resolved immediately.
–S e l e c t  Warning if you want the user to receive messages about problems and 
unexpected conditions. Investigate the cause immediately to determine whether any 
corrective action is necessary.
–S e l e c t  Info if you want the user to receive messages about expected events. No action 
is required for these events. 
Figure 13-64   Syslog configuration
To remove a syslog server, click the Minus sign (-).
To add another syslog server, click the Plus sign (+).
The syslog messages can be sent in concise message format or expanded message format.
Example 13-4 shows a compact format syslog message.
Example 13-4   Compact syslog message example
IBM2076 #NotificationType=Error #ErrorID=077102 #ErrorCode=1091 #Description=Node
Double fan failed #ClusterName=V7000G2_1 #Timestamp=Wed Jul 02 08:00:00 2017 BST
#ObjectType=Node #ObjectName=Node1 #CopyID=0 #ErrorSequenceNumber=120
Example 13-5 shows an expanded format syslog message.
Example 13-5   Full format syslog message example
IBM2076 #NotificationType=Error #ErrorID=077102 #ErrorCode=1091 #Description=Node
Double fan failed #ClusterName=V7000G2_1 #Timestamp=Wed Jul 02 08:00:00 2017 BST
#ObjectType=Node #ObjectName=Node1 #CopyID=0 #ErrorSequenceNumber=120 #ObjectID=2
#NodeID=2 #MachineType=2076624#SerialNumber=1234567 #SoftwareVersion=8.1.0.0
Important: Browse to Recommended Actions to run the fix procedures on these 
notifications.
Important: Browse to Recommended Actions to run the fix procedures on these 
notifications.