IBM Support

Configuring HMC Version 8.8.3 and Later for Call Home

Troubleshooting


Problem

This document explains how to configure the HMC call-home tasks. It also shows how to test call home for both the HMC and a Managed Server.

Resolving The Problem

This document explains how to configure the HMC call-home functions. Call-home functions include sending serviceable events and their associated data to the service provider, transmitting electronic serivce agent (ESA) data and obtaining server firmware updates direct from IBM.

Preparation and Firewall Rules
Starting with HMC V8R8.3.0, the only available connectivity path is Electronic Customer Care (ECC) which uses an outbound Internet TCP connection over https and http protocols. The older connectivity options, including Internet VPN, Internet (legacy IBM servers), Modem, and Pass-through, are no longer available.

HMCs upgraded from earlier releases will have all legacy call home paths disabled. If "Internet" (legacy) was enabled prior to the upgrade, the upgrade will enable the new ECC Internet option. Any existing proxy configuration will be lost. Note: An additional fix, MH01539 or later, is required to disable "Internet VPN" if it were enabled prior to upgrade and to remove the "Pass-Through Systems" option from the GUI.

The HMC must have a functional Ethernet interface on an open network that has access to the internet. For additional information, refer to document N1011960, Configuring HMC Version 7 for Use on a Private and Open Network .

The network must allow outbound https and http (for firmware downloads) to the IBM servers. For a list of IP addresses, you should refer to the whitepaper ESA for HMC Connectivity Security for IBM POWER6, POWER7 and POWER8 Processor-Based Systems and IBM Storage Systems DS8000 available from the IBM ESA Web site http://www-01.ibm.com/support/esa/security.htm

Configuring call home
These steps show the "enhanced+" GUI logon for Version 8.8.6 and later. Enhanced GUI for earlier releases is similar with minor variations in some panels.

Step 1. Verify Customer contact information.
1a. In the navigation area, click Serviceability > Service Management.
1b. Click Administrator and System
1c. Verify that System Information is set to "Use administrator information" and Administrator Information has all required fields (marked by a red *) filled in or that all required fields for System Information are filled in.



Step 2. Configure an outbound remote support method.
2a. In the navigation area, click Serviceability > Service Management.
2b. Click Manage Outbound Connectivity.
2c On the Call-Home Server Consoles panel click Configure...
2d. On the Outbound Connectivity Settings panel, check Enable the local console as a call-home server. If prompted with an Agreement for Service Programs panel, read the license agreement and click Accept.
2e. Enable and configure the proxy if required.



Step 3. Test the connection
3a. On the Outbound Connectivity Settings panel, click the Test button.
3b. Click the Start button. Verify the test completes successfully.


3c. On the Test Internet panel, click Cancel.
If the Internet test fails, verify the external firewall is configured to allow the outbound https (TCP port 443) to the IBM servers. You should refer to the security whitepaper listed above for a list of IBM IP addresses that must be allowed.

Step 4. Save the configuration.
4a. On the Local Console Configuration panel, click OK.
Note: You must click OK, not cancel or the settings entered prior to the test will be discarded.

4b. On the Manage Outbound Connectivity panel, click OK again to exit.


Testing Server/HMC callhome registration
Create a test PMR to verify problem callhome connectivity and that the HMC and/or Server's serial number is properly registered for service.

Step 1. Test call home on the HMC itself.
1a. In the navigation area, click Serviceability > Service Management.
1b. Click Create Serviceable Event.
1c. Check "Test problem reporting".
1d. Enter some text in problem descriptio.n
1e. Click Request Service.
HMC create servicable event

1e. Click OK on the confirmation panel.

ACT00726 panel

Step 2. Test call home for the managed servers.
2a. In the navigation area, click Resources > All Systems.
2b Click the server to be tested to open the Server Partitions view.
2c Under Serviceability, click Serviceability.
Server panel

2d. Click Create Serviceable Events.

server - create service event

2e. SelectTest automatic problem reporting, Enter problem description, then click the Request Service button.

Test server callhome

2f. Click OK to the confirmation panel.

confirmation panel

Step 3: Verify a new service event was created. Wait a few minutes for the HMC to process the call home request.
3a. In the navigation area, click Serviceability > Serviceable Events Manger.
3b. Accept the default values of All on the Manage Serviceable Events panel, and click OK.
Each test will create a B3031007 serviceable event. The Failing MTMS is the machine-model-serial number used to submit the problem. If the call home was successful, the PMH # column will be filled in with an 11-digit IBM hardware support PMR number that was created.

Manage Serviceable Events

If the call home was successful, close the event.

3c. Check each B3031007 and B3031107, and then click the Menu option Selected, Close Event.
3d. Fill out the name/description and click Close Event button. Click Yes to the confirmation.
3e. Click Cancel to exit service events.

Step 4. Checking for failures in the console event log.
4a. To investigate call home status, click Serviceability > Console Events Log. Look for entries related to the problem number of the test service event. The most common failure is machine not registered. If you encounter a machine not registered, contact your business partner or IBM sales representative and request that they register Machine type-model/serial number provided in the error message.

Example of a successful transmission
 
07/13/2015 17:16:10.820  
SvcEventNotify:'2015/07/13 17:15:42 GMT-05:00';Manufacturer=IBM;ReportingMTMS=9119-MHE*069F10P;ProbNm=201;LparName=n/a;FailingEnclosureMTMS=9119-MHE*069F10P;SRC=B3031007;EventText=Problem reported by customer.;CallHome=true;MsgExplanation=Customer tested problem reporting by creating a serviceable event on the HMC user interface.;PMH=57352,122,000
07/13/2015 17:16:10.780  
[EVENT 1812]: A SCHEDULED OPERATION STARTED
[EVENT 1800]:
Unique ID: 44      TimerTask ID: 1395479341 
Schedulable Description: Service Agent Transmit Info 
Schedulable Class: com.ibm.sfp.p.sa.ESAXmitServiceInfoSchedulable
Target Name: p8hmc1
Target: com.ibm.hwmca.fw.managed.HMC
Params: com.ibm.sfp.p.sa.ServiceAgentAttr$ESAbatchEEDrequest@21002100
Created On: Mon Jul 13 17:16:10 GMT-05:00 2015      By: HMC LIC()

 
Currently Active Executing Is Deleted Is Scheduled Is Expired
false true false true false


 
Last Execution Date Next Scheduled Date
Mon Jul 13 17:16:10 GMT-05:00 2015 Mon Jul 13 17:16:10 GMT-05:00 2015


 
Original Repetitions: 1
Remaining Repetitions: 1
Scheduled Indefinitely: false


 
Scheduling Period: 1 (0 weeks,0 days,0 hours,0 minutes,0 seconds,1 milliseconds,)
Time Window: 1200000 (0 weeks,0 days,0 hours,20 minutes,0 seconds,0 milliseconds,)
07/13/2015 17:16:10.760  
The following operation started: Service Agent Transmit Info. It was scheduled by HMC LIC() from p8hmc1 on Mon Jul 13 17:16:10 GMT-05:00 2015.
07/13/2015 17:16:10.740  
[EVENT 1831]: A TIMER TASK HAS BEEN SCHEDULED ON A NAMED TIMER
Named Timer Thread: SchedOpsTimer
Timer Task ID:
1395479341 
Date: Mon Jul 13 17:16:10 GMT-05:00 2015
Delay (s):
Period (s):
07/13/2015 17:16:10.730  
[EVENT 1810]: A NEW SCHEDULED OPERATION WAS ADDED
[EVENT 1800]:
Unique ID: 44      TimerTask ID: 1395479341 
Schedulable Description: Service Agent Transmit Info 
Schedulable Class: com.ibm.sfp.p.sa.ESAXmitServiceInfoSchedulable
Target Name: p8hmc1
Target: com.ibm.hwmca.fw.managed.HMC
Params: com.ibm.sfp.p.sa.ServiceAgentAttr$ESAbatchEEDrequest@21002100
Created On: Mon Jul 13 17:16:10 GMT-05:00 2015      By: HMC LIC()

 
Currently Active Executing Is Deleted Is Scheduled Is Expired
false false false true false


 
Last Execution Date Next Scheduled Date
Mon Jul 13 17:16:10 GMT-05:00 2015


 
Original Repetitions: 1
Remaining Repetitions: 1
Scheduled Indefinitely: false


 
Scheduling Period: 1 (0 weeks,0 days,0 hours,0 minutes,0 seconds,1 milliseconds,)
Time Window: 1200000 (0 weeks,0 days,0 hours,20 minutes,0 seconds,0 milliseconds,)
07/13/2015 17:16:10.720  
[EVENT 1812]: A SCHEDULED OPERATION STARTED
[EVENT 1800]:
Unique ID: 43      TimerTask ID: 554443020 
Schedulable Description: Service Agent Transmit Info 
Schedulable Class: com.ibm.sfp.p.sa.ESAXmitServiceInfoSchedulable
Target Name: p8hmc1
Target: com.ibm.hwmca.fw.managed.HMC
Params: com.ibm.sfp.p.sa.ServiceAgentAttr$ESAbatchEEDrequest@4ade4ade
Created On: Mon Jul 13 17:16:10 GMT-05:00 2015      By: HMC LIC()

 
Currently Active Executing Is Deleted Is Scheduled Is Expired
false true false true false


 
Last Execution Date Next Scheduled Date
Mon Jul 13 17:16:10 GMT-05:00 2015 Mon Jul 13 17:16:10 GMT-05:00 2015


 
Original Repetitions: 1
Remaining Repetitions: 1
Scheduled Indefinitely: false


 
Scheduling Period: 1 (0 weeks,0 days,0 hours,0 minutes,0 seconds,1 milliseconds,)
Time Window: 1200000 (0 weeks,0 days,0 hours,20 minutes,0 seconds,0 milliseconds,)
07/13/2015 17:16:10.710  
The following operation was scheduled by HMC LIC() from p8hmc1: Service Agent Transmit Info.
07/13/2015 17:16:10.700  
The following operation started: Service Agent Transmit Info. It was scheduled by HMC LIC() from p8hmc1 on Mon Jul 13 17:16:10 GMT-05:00 2015.
07/13/2015 17:16:10.680  
[EVENT 1831]: A TIMER TASK HAS BEEN SCHEDULED ON A NAMED TIMER
Named Timer Thread: SchedOpsTimer
Timer Task ID:
554443020 
Date: Mon Jul 13 17:16:10 GMT-05:00 2015
Delay (s):
Period (s):
07/13/2015 17:16:10.660  
[EVENT 1810]: A NEW SCHEDULED OPERATION WAS ADDED
[EVENT 1800]:
Unique ID: 43      TimerTask ID: 554443020 
Schedulable Description: Service Agent Transmit Info 
Schedulable Class: com.ibm.sfp.p.sa.ESAXmitServiceInfoSchedulable
Target Name: p8hmc1
Target: com.ibm.hwmca.fw.managed.HMC
Params: com.ibm.sfp.p.sa.ServiceAgentAttr$ESAbatchEEDrequest@4ade4ade
Created On: Mon Jul 13 17:16:10 GMT-05:00 2015      By: HMC LIC()

 
Currently Active Executing Is Deleted Is Scheduled Is Expired
false false false true false


 
Last Execution Date Next Scheduled Date
Mon Jul 13 17:16:10 GMT-05:00 2015


 
Original Repetitions: 1
Remaining Repetitions: 1
Scheduled Indefinitely: false


 
Scheduling Period: 1 (0 weeks,0 days,0 hours,0 minutes,0 seconds,1 milliseconds,)
Time Window: 1200000 (0 weeks,0 days,0 hours,20 minutes,0 seconds,0 milliseconds,)
07/13/2015 17:16:10.650  
The following operation was scheduled by HMC LIC() from p8hmc1: Service Agent Transmit Info.
07/13/2015 17:16:10.570  
Remote support call generated on p8hmc1 completed successfully by server p8hmc1(9.5.69.18).
07/13/2015 17:16:03.480  
Ecc transmission statistics: 12 successful 0 unsuccessful problem report open/close.
07/13/2015 17:16:03.450  
Transmission of problem report from system p8hmc1(9.5.69.18) via ecc successful.
07/13/2015 17:15:52.390  
Starting remote support call 2015-07-13 05:15:51 PM for console p8hmc1(9.5.69.18). Type: Problem Report: 9119-MHE_069F10P Problem Number: 201.
07/13/2015 17:15:52.350  
Remote support call generated on p8hmc1 is being handled by phone server p8hmc1(9.5.69.18).
07/13/2015 17:15:52.200  
[EVENT 1831]: A TIMER TASK HAS BEEN SCHEDULED ON A NAMED TIMER
Named Timer Thread: RBF Query Task Timer
Timer Task ID:
1980134918 
Date:
Delay (s): 300
Period (s): 300
07/13/2015 17:15:47.790  
SvcEventNotify:'2015/07/13 17:15:42 GMT-05:00';Manufacturer=IBM;ReportingMTMS=9119-MHE*069F10P;ProbNm=201;LparName=n/a;FailingEnclosureMTMS=9119-MHE*069F10P;SRC=B3031007;EventText=Problem reported by customer.;CallHome=true;MsgExplanation=Customer tested problem reporting by creating a serviceable event on the HMC user interface.;PMH=n/a

[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"HMC","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
22 September 2021

UID

nas8N1020812