Generating a Call Home event

You can test the Call Home service by triggering a test alert in Platform Manager that will cause the Call Home service to notify the IBM Support servers and your customer contacts of the event and create a test case.

Procedure

  1. Log in to the active host of the IBM system as the appliance user. 
    [apuser@node0101 ~]# ap issues | grep 199
  2. Enter --generate test alert to generate a test alert. 
    [apuser@node0101 ~]# ap issues --generate_test_alert

    The command triggers the requested event as a test. The command requires 1-2 minutes to complete. 

    [apuser@node0101 ~]# ap issues | grep 199
| 1334 | 2017-08-18 06:08:44 | HW_SERVICE_REQUESTED | 199: Test HW alert | hw://hadomain1.node1 | INFORMATION |
    If you tail the Call Home log file /opt/ibm/appliance/storage/platform/ras/callhome/log/callHome/callHome.0.log on the node, and /opt/ibm/callhome/log/callHome/callHome.0.log in the Call Home container, you see the following:
    
Wed Jun 28 18:21:52 UTC 2017 INFO: {"TargetType": "node", "Group": "HW", "Target": "hw://hadomain1.node1", "Title": "Test HW alert", "CloseDate": null, "ReasonCode": 199, "AddData": {}, "Stateful": 1, "Date": "2017-06-28 14:21:38.563148", "State": "DELIVERING", "Severity": "CRITICAL", "LogCollectionTag": ["general"], "LogCollectionStatus": "COLLECTED", "SRID": null, "SMTPStatus": "NOT_APPLICABLE", "LogFilePath": "/var/log/appliance/platform/management/alerts/alert_3660.tar.gz", "LogFileNode": "hadomain1.node1", "Type": "HW_SERVICE_REQUESTED", "ID": 3660, "CallHomeStatus": "SENDING"}
Wed Jun 28 18:21:53 UTC 2017 INFO: DOWNLOADED: /tmp/alert3660/alert_3660.tar.gz
[apuser@node0101-fab /]# Wed Jun 28 18:22:55 UTC 2017 INFO: srid = 23239933000
Wed Jun 28 18:22:56 UTC 2017 INFO: Sent message successfully.
Wed Jun 28 18:22:56 UTC 2017 INFO: {
  "status": 0
}

Wed Jun 28 18:22:56 UTC 2017 INFO: The Call Home forensics and report generation has completed.
Wed Jun 28 18:22:56 UTC 2017 INFO: done
  3. Enter --close test alert to close the alert. 
    [apuser@node0101 ~]# ap issues --close_test_alert