In the simplest case, an HMC has a direct Internet connection. To configure the HMC as a call-home server, you only need to set the following 3 attributes:

   is_hmc_callhome_server
      0 - disable this HMC as a call-home server
      1 - enable this HMC as a call-home server
   use_internet_conn
      0 - do not use an existing Internet connection
      1 - use an existing Internet connection
   use_ssl_proxy
      0 - use direct Internet connection
      1 - use an SSL proxy

The command to activate the HMC as a call home server then looks like this:

$ hmc chcallhome hmc01 is_hmc_callhome_server=1 \
 use_internet_conn=1 use_ssl_proxy=0
Shared connection to virt-hmc01 closed.
$

The current configuration and current status can be displayed with the “hmc lscallhome” command:

$ hmc lscallhome
            CALLHOME       INTERNET  SSL    
HMC      STATE     SERVER  CONN      PROXY  PROTOCOL  SERVER_NAMES
hmc01    Enabled   1       1         0      ipv4      hmc01
hmc02    Disabled  0       0         0      ipv4      -
$

To check whether an HMC is correctly configured as a call home server and whether Call Home works, the command “hmc testcallhome” can be used:

$ hmc testcallhome hmc01
Test beginning
Edge_Gateway_1:129.42.56.189:443(esupport.ibm.com)::Connected
Edge_Gateway_2:129.42.54.189:443(esupport.ibm.com)::Connected
Edge_Gateway_3:129.42.60.189:443(esupport.ibm.com)::Connected
Testing Completed
Shared connection to hmc01 closed.
$

In this case, the test was successful and the IBM support servers could be reached via call home.