Inspecting call home data uploads

The uploaded call home data is generally used by the IBM® service and support teams for diagnosing issues and best practice violations, which can be reported at a customer site. However, a customer can opt to self-inspect a sample call home data upload to manually review the data without sending out any information to IBM.

You can inspect call home data uploads without sending out any information to the IBM by configuring the call home feature by using the following procedure:

Set up the call home feature but provide incorrect proxy settings.

For example,

[root@g5130-11 ~] mmcallhome proxy change --proxy-location wrong_proxy --proxy-port 1111
Call home proxy-location has been set to wrong_proxy
Call home proxy-port has been set to 1111

[root@g5130-11 ~]# mmcallhome proxy enable
Call home proxy-auth-enabled has been set to false
Call home proxy-enabled has been set to true

Start the uploaded data collection, such as daily uploaded data. The daily data upload overrides the standard 24-hour wait time and delivers the results immediately.

For example,
```
[root@g5130-11 ~] mmcallhome run GatherSend --task daily
One time run completed with failure: sending failed
```
As expected, the data uploads to the server fails as you provided incorrect proxy settings.

Find the DC file with the copy of the data that the call home feature collected and tried to send.

For example,

[root@g5130-11 ~] mmcallhome status list --task daily --verbose --numbers 1
=== Executed call home tasks ===

Group        Task   Start Time          Updated Time    Status  RC or Step                  Package File Name                                                                                                                     Original Filename
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
autoGroup_1  daily  20220126153252.022  20220126153310  failed  Uploading operation failed  /tmp/mmfs/callhome/rsENFailedQ/14559237835643.5_1_3_0.123456.US.ibmtest.autoGroup_1.gat_daily.g_daily.scale.20220126153252022.cl0.DC

Extract the DC file, which is a *.tar.gz file.

For example,

[root@g5130-11 ~]# mkdir wrong_proxy
[root@g5130-11 ~]# cd wrong_proxy/
[root@g5130-11 wrong_proxy]# tar xvf /tmp/mmfs/callhome/rsENFailedQ/14559237835643.5_1_3_0.123456.US.ibmtest.autoGroup_1.gat_daily.g_daily.scale.20220126153252022.cl0.DC
CH_20220126153252.022_daily/
CH_20220126153252.022_daily/HEADER
CH_20220126153252.022_daily/LC_g5130-14.tar.gz
CH_20220126153252.022_daily/LC_g5130-13.tar.gz
CH_20220126153252.022_daily/LC_g5130-12.tar.gz
CH_20220126153252.022_daily/MC_g5130-11.tar.gz
[root@g5130-11 wrong_proxy]# tar xvf CH_20220126153252.022_daily/MC_g5130-11.tar.gz
MC_g5130-11/
MC_g5130-11/cat_etcosrelease.txt
...

Inspect every detail of the DC file.
Run the mmcallhome proxy command to enable the call home feature and do one of the following actions:
- If you are using a proxy, then provide correct proxy settings for call home usage by using the following command:
```
mmcallhome proxy change --proxy-location <CORRECT_PROXY> --proxy-port <CORRECT_PORT>
```
- If you are using a proxy with authentication, then issue the following command:
```
[root@g5130-11 ~] mmcallhome proxy enable --with-proxy-auth
Call home proxy-auth-enabled has been set to true
Call home proxy-enabled has been set to true
```
- If you are not using a proxy, then disable the proxy usage for call home by using the following command:
```
[root@g5130-11 ~] mmcallhome proxy disable
Call home proxy-auth-enabled has been set to false
Call home proxy-enabled has been set to false
```