IBM Support

Utility to test the ECC (Electronic Customer Care) connections and firewall ports for setting up call home

Troubleshooting


Problem

To setup call home on IBM Storwize V7000 Unified system, the file modules require proper connections to IBM ECC (Electronic Customer Care) systems. The connections require either firewall ports to be opened or the use of a proxy server to allow the file modules to communicate with the IBM ECC systems. Without the firewall changes or a proxy server, the V7000 Unified file modules will not be able to create call homes. Please refer to the below Storwize V7000 Unified information center link: http://www.ibm.com/support/knowledgecenter/ST5Q4U_1.6.0/com.ibm.storwiz… For information on how to configure call home, please refer to the following link: http://www.ibm.com/support/docview.wss?uid=ssg1S1004748 To test if your Storwize V7000 Unified system has all the proper ECC (Electronic Customer Care) connections for sending call homes, refer to the below "Diagnosing the problem" section. NOTE: Customers are strongly recommended to be at IBM Storwize V7000 Unified V1.4.0.5 or higher before enabling call home on their system.

Diagnosing The Problem

Please follow the below steps to test if your Storwize V7000 Unified system has all the proper ECC (Electronic Customer Care) connections and firewall ports enabled for sending call homes.

1) Download the diagnostic utility (IBM_2073_2851_callhome_test) to your local machine from the below link:


2) Now upload it to your IBM Storwize V7000 Unified active file module using the scpuser
Note: Files uploaded by scpuser that are older than 3 hours are automatically deleted every hour.

3) From CLI run the diagnostic utility (IBM_2073_2851_callhome_test) as below.
Note: Running the utility on CLI will require admin access

    $ applysoftware <path where the utility is copied>/IBM_2073_2851_callhome_test

    3(a) If your Storwize V7000 Unified system has all the proper ECC (Electronic Customer Care) connections and firewall ports enabled for sending call homes, the utility will output OK against all the required IP addresses as shown in the below example.
    Example:

    $ applysoftware /var/applysoftware/IBM_2073_2851_callhome_test
    Proceeding with Callhome Test.
    Directing Callhome Test logs to /var/log/cnlog for log capture.
    Testing direct connection
    Testing prefix Status_Report:
    Status_Report_1: 207.25.252.197 OK
    Status_Report_2: 129.42.160.51 OK

    Testing prefix Problem_Report:
    Problem_Report_1: 129.42.26.224 OK
    Problem_Report_2: 129.42.34.224 OK
    Problem_Report_3: 129.42.42.224 OK
    Problem_Report_4: 129.42.26.224 OK
    Problem_Report_5: 129.42.34.224 OK

    Testing prefix Fix_Repository:
    Fix_Repository_1: 170.225.15.28 OK
    Fix_Repository_10: 170.225.15.76 OK
    Fix_Repository_11: 129.35.224.114 OK
    Fix_Repository_12: 170.225.15.103 OK
    Fix_Repository_13: 129.35.224.103 OK
    Fix_Repository_14: 129.35.224.113 OK
    Fix_Repository_15: 170.225.15.113 OK
    Fix_Repository_16: 170.225.15.124 OK
    Fix_Repository_17: 129.35.224.124 OK
    Fix_Repository_18: 170.225.15.108 OK
    Fix_Repository_19: 129.35.224.108 OK
    Fix_Repository_2: 170.225.15.107 OK
    Fix_Repository_20: 129.35.224.109 OK
    Fix_Repository_21: 170.225.15.109 OK
    Fix_Repository_22: 129.35.224.110 OK
    Fix_Repository_23: 170.225.15.110 OK
    Fix_Repository_3: 129.35.224.107 OK
    Fix_Repository_4: 170.225.15.104 OK
    Fix_Repository_5: 129.35.224.104 OK
    Fix_Repository_6: 129.35.224.115 OK
    Fix_Repository_7: 170.225.15.115 OK
    Fix_Repository_8: 129.35.224.105 OK
    Fix_Repository_9: 170.225.15.105 OK

    Testing prefix Bulk_Data:
    Bulk_Data_1: 170.225.15.41 OK
    Bulk_Data_2: 192.109.81.20 OK
    Restoring Callhome Test log location.
    EFSSG1000I The command completed successfully.


    3(b) If your Storwize V7000 Unified system does not have all the proper ECC (Electronic Customer Care) connections and firewall ports enabled for sending call homes, the utility will output NOT OK against the IP addresses and firewall ports having issue in connecting as shown in the below example. Please refer to "Resolving the problem" section.
    Example:

    $ applysoftware /var/applysoftware/IBM_2073_2851_callhome_test
    Proceeding with Callhome Test.
    Directing Callhome Test logs to /var/log/cnlog for log capture.
    Testing direct connection
    Testing prefix Status_Report:
    Status_Report_1: 207.25.252.197 NOT OK - Port 443
    Status_Report_2: 129.42.160.51 NOT OK - Port 443

    Testing prefix Problem_Report:
    Problem_Report_1: 129.42.26.224 NOT OK - Port 443
    Problem_Report_2: 129.42.34.224 NOT OK - Port 443
    Problem_Report_3: 129.42.42.224 NOT OK - Port 443
    Problem_Report_4: 129.42.26.224 NOT OK - Port 443
    Problem_Report_5: 129.42.34.224 NOT OK - Port 443

    Testing prefix Fix_Repository:
    Fix_Repository_1: 170.225.15.28 NOT OK - Port 80
    Fix_Repository_10: 170.225.15.76 NOT OK - Port 80
    Fix_Repository_11: 129.35.224.114 NOT OK - Port 80
    Fix_Repository_12: 170.225.15.103 NOT OK - Port 80
    Fix_Repository_13: 129.35.224.103 NOT OK - Port 80
    Fix_Repository_14: 129.35.224.113 NOT OK - Port 80
    Fix_Repository_15: 170.225.15.113 NOT OK - Port 80
    Fix_Repository_16: 170.225.15.124 NOT OK - Port 80
    Fix_Repository_17: 129.35.224.124 NOT OK - Port 80
    Fix_Repository_18: 170.225.15.108 NOT OK - Port 80
    Fix_Repository_19: 129.35.224.108 NOT OK - Port 80
    Fix_Repository_2: 170.225.15.107 NOT OK - Port 80
    Fix_Repository_20: 129.35.224.109 NOT OK - Port 80
    Fix_Repository_21: 170.225.15.109 NOT OK - Port 80
    Fix_Repository_22: 129.35.224.110 NOT OK - Port 80
    Fix_Repository_23: 170.225.15.110 NOT OK - Port 80
    Fix_Repository_3: 129.35.224.107 NOT OK - Port 80
    Fix_Repository_4: 170.225.15.104 NOT OK - Port 80
    Fix_Repository_5: 129.35.224.104 NOT OK - Port 80
    Fix_Repository_6: 129.35.224.115 NOT OK - Port 80
    Fix_Repository_7: 170.225.15.115 NOT OK - Port 80
    Fix_Repository_8: 129.35.224.105 NOT OK - Port 80
    Fix_Repository_9: 170.225.15.105 NOT OK - Port 80

    Testing prefix Bulk_Data:
    Bulk_Data_1: 170.225.15.41 NOT OK - Port 443
    Bulk_Data_2: 192.109.81.20 NOT OK - Port 443

    Failures occurred during the ECC connection test.
    Please ensure the customer's network firewalls are configured to allow access to the following IP addresses and ports:
    207.25.252.197:443 129.42.160.51:443 129.42.26.224:443 129.42.34.224:443 129.42.42.224:443 129.42.26.224:443 129.42.34.224:443 170.225.15.28:80 170.225.15.76:80 129.35.224.114:80 170.225.15.103:80 129.35.224.103:80 129.35.224.113:80 170.225.15.113:80 170.225.15.124:80 129.35.224.124:80 170.225.15.108:80 129.35.224.108:80 170.225.15.107:80 129.35.224.109:80 170.225.15.109:80 129.35.224.110:80 170.225.15.110:80 129.35.224.107:80 170.225.15.104:80 129.35.224.104:80 129.35.224.115:80 170.225.15.115:80 129.35.224.105:80 170.225.15.105:80 170.225.15.41:443 192.109.81.20:443
    Restoring Callhome Test log location.
    EFSSG1000I The command completed successfully.

Resolving The Problem

    If the diagnostic utility output shows NOT OK against one or more IP addresses and ports, as shown in Example 3(b) above, please refer to the below Storwize V7000 Unified information center link and work with your network team to either enable the firewall ports and/or configure a proxy for the IP addresses showing NOT OK in the utility output. Once the needed firewalls ports and IP addresses are fixed re-run the utility (IBM_2073_2851_callhome_test) to verify the connections.

[{"Product":{"code":"ST5Q4U","label":"IBM Storwize V7000 Unified (2073-700)"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"1.6","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.4;1.5;1.6","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2018

UID

ssg1S1004554

Page Feedback