Monitoring events through callhome

The call home feature automatically notifies IBM® Support if certain types of events occur in the system. Using this information, IBM Support can contact the system administrator in case of any issues. Configuring call home reduces the response time for IBM Support to address the issues.

The details are collected from individual nodes that are marked as call home child nodes in the cluster. The details from each child node are collected by the call home node. You need to create a call home group by grouping call home child nodes. One of the nodes in the group is configured as the call home node and it performs data collection and upload.

ESA call home is triggered for the following events only:
  • power_supply_failed
  • fan_failed
  • can_fan_failed
  • bootdrive_smart_failed
  • bootdrive_missing
  • canister_failed
  • bootdrive_mirror_failed
  • bootdrive_mirror_degraded
  • can_temp_sensor_failed
  • fan_speed_high
  • fan_speed_low
  • power_high_current
  • power_high_voltage
  • temp_bus_failed
  • temp_sensor_failed
  • voltage_bus_failed
  • voltage_sensor_failed
  • can_temp_bus_failed
  • coin_battery_low
  • coin_battery_missing
  • cpu_unit_missing
  • cpu_unit_speed_wrong
  • dimm_module_missing
  • dimm_module_size_wrong
  • dimm_module_speed_wrong
  • pair_canister_failed

The data gathering and upload can be configured individually on each group. Use the groups to reflect logical units in the cluster. For example, it is easier to manage when you create a group for all CES nodes and another group for all non-CES nodes.

Use the mmcallhome command to configure the call home feature in the system. For more information about the mmcallhome command, see the IBM Storage Scale: Command and Programming Reference.