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.
  2. Enter the following command to generate a test alert.
    [root@e1n1 etc]# ap issues --generate_test_alert

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

  3. Run the following command to identify the issue number:
    [root@e1n1 etc]# ap issues | grep 199
    | 1701 | 2020-04-01 09:18:23 | HW_SERVICE_REQUESTED | 199: Test HW alert                               | hw://enclosure1.node1                   | INFORMATION |
    [root@e1n1 etc]#
  4. Issue the command watch ap issues NNNN, for example:
    watch ap issues 1701
    In the display of issue details, you should first see this:
    Processing Status
            State                    : DELIVERED
            Log Collection Status    : COLLECTED
            SMTP Status              : NOT_APPLICABLE
            SNMP Status              : NOT_APPLICABLE
            Call Home Status         : SENT             
    
    Service Request
            SRID                     : None
            SR Status                : None
    
    Once Call Home has processed the alert, that section of issue details should look like this:
    Processing Status
            State                    : DELIVERED
            Log Collection Status    : COLLECTED
            SMTP Status              : NOT_APPLICABLE
            SNMP Status              : NOT_APPLICABLE
            Call Home Status         : COMPLETED
    
    Service Request
            SRID                     : TS008329297
            SR Status                : None
    
  5. If Call Home Status indicates FAILED, view 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. Example:
    Wed Apr 01 13:17:04 UTC 2020 INFO: Callhome Service started.
    Wed Apr 01 13:18:34 UTC 2020 INFO: {"TargetType": "node", "Group": "HW", "Severity": "INFORMATION", "Title": "Test HW alert", "AddData": {}, "BundleVersion": "1.0.4.0", "State": "DELIVERING", "SRID": null, "CloseDate": null, "LogFileChecksum": "703ee02db1664f0baa47670eb3f0b6c1", "Type": "HW_SERVICE_REQUESTED", "SNMPStatus": "NOT_APPLICABLE", "CallHomeStatus": "SENDING", "Stateful": 1, "Date": "2020-04-01 09:18:23.920687", "ReasonCode": 199, "AggregatedSubcomponents": null, "SMTPStatus": "NOT_APPLICABLE", "Target": "hw://enclosure1.node1", "SRStatus": null, "ID": 1701, "ReferencedAlertID": null, "LogCollectionTag": ["general"], "LogCollectionStatus": "COLLECTED", "LogFilePath": "/var/log/appliance/platform/management/alerts/alert_1701.tar.gz", "LogFileNode": "enclosure1.node1"}
    Wed Apr 01 13:18:35 UTC 2020 INFO: DOWNLOADED: /tmp/alert1701/alert_1701.tar.gz
    Wed Apr 01 13:29:30 UTC 2020 INFO: srid = TS003546564
    Wed Apr 01 13:29:30 UTC 2020 INFO: Sent message successfully.
    Wed Apr 01 13:29:30 UTC 2020 INFO: {"status": 0}
    
    Wed Apr 01 13:29:30 UTC 2020 INFO: The CallHome forensics and report generation has completed.
    Wed Apr 01 13:29:30 UTC 2020 INFO: done
  6. Enter --close test alert to close the alert.
    [root@e1n1 etc]# ap issues --close_test_alert