Call Home events
The following table lists the events that are created for the call home component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| callhome_customer_info_disabled | TIP | INFO | no | Message: The required customer information for call home is not checked. |
| Description: The required customer information for call home is not checked. | ||||
| Cause: Call Home capability is disabled. | ||||
| User Action: N/A | ||||
| callhome_customer_info_filled | TIP | INFO | no | Message: All required customer information for call home was provided. |
| Description: All required customer information for call home was provided. | ||||
| Cause: All required customer information for call home was provided by using the mmcallhome info change command. | ||||
| User Action: N/A | ||||
| callhome_customer_info_missing | TIP | TIP | no | Message: The required customer information is not provided: {0}. |
| Description: Some of the required customer information was not provided, but is required. For more information, see the Configuring call home to enable manual and automated data upload section in the IBM Storage Scale: Administration Guide. | ||||
| Cause: Some of the required customer information was not provided by using the mmcallhome info change command. | ||||
| User Action: Run the mmcallhome info change command to collect the required information about the customer for call home capability. | ||||
| callhome_hcalerts_ccr_failed | STATE_CHANGE | ERROR | no | Message: The data for the last health check monitoring cannot be updated in the CCR. |
| Description: The data for the last health check monitoring cannot be updated in the CCR. | ||||
| Cause: The data for the last health check monitoring cannot be updated in the Cluster Configuration Repository (CCR). | ||||
| User Action: Ensure that your cluster has a quorum. If the cluster has a quorum, then repair the CCR by following the steps mentioned in the Repair of cluster configuration information when no CCR backup is available section in the IBM Storage Scale: Problem Determination Guide. | ||||
| callhome_hcalerts_disabled | STATE_CHANGE | INFO | no | Message: The health check monitoring feature is disabled. |
| Description: The health check monitoring feature is disabled. | ||||
| Cause: Call Home capability is disabled. | ||||
| User Action: To enable health check monitoring, you must enable call home by using the mmcallhome capability enable command and set 'monitors_enabled = true' in the mmsysmonitor.conf file. | ||||
| callhome_hcalerts_failed | STATE_CHANGE | ERROR | no | Message: The last health check monitoring was not successfully processed. |
| Description: The last health check monitoring was not successfully processed. | ||||
| Cause: The last health check monitoring was not successfully processed. | ||||
| User Action: Check connectivity to the IBM ECuRep server, which includes cabling, firewall, and proxy. For more information, check the output of the mmcallhome status list --task sendfile --verbose command. | ||||
| callhome_hcalerts_noop | STATE_CHANGE | INFO | no | Message: No health check monitoring operation is performed on this node. |
Description: No health check monitoring operation is performed on this node. The health check monitoring is performed exclusively on the first call
home master node. |
||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_hcalerts_ok | STATE_CHANGE | INFO | no | Message: Call Home health check monitoring was successfully performed. |
| Description: The last health check monitoring was successfully performed. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_heartbeat_collection_failed | STATE_CHANGE | ERROR | no | Message: The data for the last call home heartbeat cannot be collected. |
| Description: The data for the last call home heartbeat cannot be collected. | ||||
| Cause: The data for the last call home heartbeat cannot be collected. | ||||
| User Action: Check whether you have enough free space in the dataStructureDump. | ||||
| callhome_heartbeat_disabled | STATE_CHANGE | INFO | no | Message: The heartbeat feature is disabled. |
| Description: The heartbeat feature is disabled. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_heartbeat_failed | STATE_CHANGE | ERROR | no | Message: The last call home heartbeat was not successfully sent. |
| Description: The last call home heartbeat was not successfully sent. | ||||
| Cause: The last call home heartbeat was not successfully sent. | ||||
| User Action: Check connectivity to the IBM ECuRep server, which includes cabling, firewall, and proxy. For more information, check the output of the mmcallhome status list --task sendfile --verbose command. | ||||
| callhome_heartbeat_ok | STATE_CHANGE | INFO | no | Message: Call Home heartbeats are successfully sent. |
| Description: The last call home heartbeat was successfully sent. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_ptfupdates_ccr_failed | STATE_CHANGE | ERROR | no | Message: The data for the last ptf update check cannot be updated in the CCR. |
| Description: The data for the last ptf update check cannot be updated in the CCR. | ||||
| Cause: The data for the last ptf update check cannot be updated in the CCR. | ||||
| User Action: Ensure that your cluster has a quorum. If the cluster has a quorum, then repair the CCR by following the steps mentioned in the Repair of cluster configuration information when no CCR backup is available section of the IBM Storage Scale: Problem Determination Guide . | ||||
| callhome_ptfupdates_disabled | STATE_CHANGE | INFO | no | Message: The ptf update check feature is disabled. To
enable it, use the 'mmcallhome capability enable' command. |
| Description: The ptf update check feature is disabled. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_ptfupdates_failed | STATE_CHANGE | ERROR | no | Message: The last ptf update check was not successfully processed. |
| Description: The last ptf update check was not successfully processed. | ||||
| Cause: The last ptf update check was not successfully processed. | ||||
| User Action: Check connectivity to the IBM ECuRep server, which includes cabling, firewall, and proxy. For more information, check the output of the mmcallhome status list --task sendfile --verbose command. | ||||
| callhome_ptfupdates_noop | STATE_CHANGE | INFO | no | Message: No Call Home ptf update check operation on this node. Because the call home ptf update check is performed exclusively on the first call
home master node considering that it is not running in the cloud native storage
architecture. |
| Description: No Call Home ptf update check operation is performed on this node. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_ptfupdates_ok | STATE_CHANGE | INFO | no | Message: Call Home ptf update check was successfully performed. |
| Description: The last ptf update check was successfully performed. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_sudouser_defined | STATE_CHANGE | INFO | no | Message: The sudo user variable is properly set up. |
| Description: The sudo user variable is properly set up. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_sudouser_not_exists | STATE_CHANGE | ERROR | no | Message: The sudo user '{0}' does not exist on this node. |
| Description: The sudo user does not exist on this node. | ||||
| Cause: The sudo user, specified in the mmsdrquery sdrq_cluster_info sudoUser command, does not exist on this node. | ||||
| User Action: Create the sudo user on this node or specify a new sudo user by using the mmchcluster --sudo-user <userName> command. | ||||
| callhome_sudouser_not_needed | STATE_CHANGE | INFO | no | Message: Not monitoring sudo user configuration variable, since sudo wrappers are not being used. |
| Description: Not monitoring sudo user configuration variable, since sudo wrappers are not being used. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_sudouser_perm_missing | STATE_CHANGE | ERROR | no | Message: The sudo user is missing a recursive execute permission for the dataStructureDump: {0}. |
| Description: The sudo user is missing a recursive execute permission for the dataStructureDump. | ||||
| Cause: The sudo user, specified in the IBM Storage Scale configuration, cannot read or write call home directories in dataStructureDump. | ||||
| User Action: Ensure that the sudo user, specified in the IBM Storage Scalesettings, has the recursive execute permission for the dataStructureDump. | ||||
| callhome_sudouser_perm_not_needed | STATE_CHANGE | INFO | no | Message: Not monitoring sudo user permissions, since sudo wrappers are not being used. |
| Description: Not monitoring sudo user permissions, since sudo wrappers are not being used. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_sudouser_perm_ok | STATE_CHANGE | INFO | no | Message: The sudo user has correct permissions for the dataStructureDump: {0}. |
| Description: The sudo user has correct permissions for the dataStructureDump. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| callhome_sudouser_undefined | STATE_CHANGE | ERROR | no | Message: The sudo user variable is not set up in the IBM Storage Scale configuration. |
| Description: The sudo user variable is not set up in the IBM Storage Scale configuration. | ||||
| Cause: The mmsdrquery sdrq_cluster_info sudoUser command reports 'root' or a sudo user is not set up. | ||||
| User Action: Specify a valid non-root sudo user by using the mmchcluster --sudo-user <userName> command. |