CESCLUSTER events

The following table lists the events that are created for the CESCLUSTER component.

Table 1. Events for the CESCLUSTER component
Event Event
Type		 Severity Call home Details
ces_ips__warn INFO WARNING no Message: The IBM Storage Scale CES IP assignment monitor cannot be executed, which can be a timeout issue.
Description: Check the CES IP assignment state that returned an unknown result. This might be a temporary issue, such as a timeout during the check procedure.
Cause: The CES IP assignment state cannot be determined due to a problem.
User Action: Find potential issues for this kind of failure in the /var/adm/ras/mmsysmonitor.log file.
ces_ips_all_unassigned STATE_CHANGE ERROR no Message: All {0} declared CES IPs are unassigned.
Description: All of the declared CES IPs are unassigned.
Cause: All declared CES IP addresses are unassigned.
User Action: Check the configuration of network interfaces. For more information, run the mmces address list command.
ces_ips_assigned STATE_CHANGE INFO no Message: All {0} expected CES IPs are assigned.
Description: All declared CES IPs are assigned.
Cause: N/A
User Action: N/A
Start of changeces_ips_unassignedEnd of change Start of changeSTATE_CHANGEEnd of change Start of changeWARNINGEnd of change Start of changenoEnd of change Start of changeMessage: {0} of {1} declared CES IPs are unassigned.End of change
Description: Not all of the declared CES IPs are assigned.
Cause: There are unassigned CES IP addresses.
User Action: Check the configuration of network interfaces. For more information, run the mmces address list command.
Start of changes3_config_backup_disableEnd of change Start of changeSTATE_CHANGEEnd of change Start of changeINFOEnd of change Start of changenoEnd of change Start of changeMessage: The S3 service is disabled.End of change
Description: The S3 service is disabled on the node by issuing the mmces service disable s3 command. Disabling a service also removes all configuration files, which is different from stopping a service.
Cause: N/A
User Action: N/A
Start of changes3_config_backup_notokEnd of change Start of changeSTATE_CHANGEEnd of change Start of changeWARNINGEnd of change Start of changenoEnd of change Start of changeMessage: The S3 configuration file is not backed up, the latest version of the configuration file in the CCR is {0}.End of change
Description: The S3 configuration file is not backed up in the CCR. The CCR backup is expected to be updated every 10 minutes.
Cause: The backed-up S3 configuration file in the CCR is too old or does not exist, which is displayed in the output of the mmccr flist command.
User Action: Check the mmcess3backup cronjob whether the backup job is running or not.
Start of changes3_config_backup_okEnd of change Start of changeSTATE_CHANGEEnd of change Start of changeINFOEnd of change Start of changenoEnd of change Start of changeMessage: The S3 configuration is backed up, the latest version of the backed-up configuration file in the CCR is {0}.End of change
Description: The S3 configuration backup is OK.
Cause: N/A
User Action: N/A