Uploading custom files using call home
The uploaded packages that contain the daily or weekly scheduled uploads as well as the non-ticket-related sent files are saved on the corresponding call home node for an inspection by the customer.
You can upload the data using the following
command:
mmcallhome run SendFile --file file [--desc DESC | --pmr {xxxxx.yyy.zzz | TSxxxxxxxxx}]
Discuss this procedure with the IBM® support before using
it.You can also use the following command to find the exact location of the uploaded
packages:
mmcallhome status list --verbose
-
Monitor the tasks.
- To view the status of the currently running and the already completed call home tasks, issue the
following command:
mmcallhome status list
This command gives an output similar to the following:
=== Executed call home tasks === Group Task Start Time Status ------------------------------------------------------ autoGroup_1 daily 20181203105943.289 success autoGroup_1 daily 20181204023601.112 success autoGroup_1 daily 20181205021401.524 success autoGroup_1 daily 20181206021401.281 success autoGroup_1 weekly 20181203110048.724 success autoGroup_1 sendfile 20181203105920.936 success autoGroup_1 sendfile 20181203110130.732 success
- To view the details of the status of the call home tasks, issue the following
command:
mmcallhome status list --verbose
This command gives an output similar to the following:
=== Executed call home tasks === Group Task Start Time Updated Time Status RC or Step Package File Name Original Filename ----------------------------------------------------------------------------------------------------------------------------------------- autoGroup_1 daily 20181203105943.289 20181203110008 success RC=0 /tmp/mmfs/callhome/rsENUploaded/ 13445038716695.5_0_3_0.123456... autoGroup_1.gat_daily.g_daily. scale.20181203105943289.cl0.DC autoGroup_1 weekly 20181209031101.186 20181209031122 success RC=0 /tmp/mmfs/callhome/rsENUploaded/ 13445038716695.5_0_3_0.123456... autoGroup_1.gat_weekly.g_weekly. scale.20181209031101186.cl0.DC autoGroup_1 sendfile 20181203105920.936 20181203105928 success RC=0 /tmp/mmfs/callhome/rsENUploaded/ /root/stanza.txt 13445038716695.5_0_3_0.123456... autoGroup_1.NoText.s_file.scale. 20181203105920936.cl0.DC autoGroup_1 sendfile 20181203110130.732 20181203110138 success RC=0 /tmp/mmfs/callhome/rsENUploaded/ /root/anaconda-ks.cfgg 13445038716695.5_0_3_0.123456... autoGroup_1.NoText.s_file.scale. 20181203110130732.cl0.DC
- To list the registered tasks for gather-send, issue the following
command:
mmcallhome schedule list
This command gives an output similar to the following:
=== List of registered schedule tasks === group scheduleType isEnabled confFile -------- -------------- ----------- ------------- global daily enabled daily.conf global weekly enabled weekly.conf
- To view the status of the currently running and the already completed call home tasks, issue the
following command:
-
Upload the collected data.
The call home functionality provides the following data upload methods to collect and upload the data:
- File upload: Any file can be specified for upload.
- Package upload: If the call home schedules are enabled, call home automatically collects predefined data regularly. The definitions for the data co collect can be found in /usr/lpp/mmfs/lib/mmsysmon/callhome/callhomeSchedules.json. After the upload, the data packages are stored in the data package directory for backup. You can find the exact path names by running the mmcallhome status list --verbose command.
If a prespecified RAS event that degrades the current state of an mmhealth component occurs on one of the nodes of a call home group, the debugging data is automatically collected and uploaded to ECuRep for analysis. This feature is called FTDC2CallHome. For more information on FTDC2CallHome, see Event-based uploads.