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, like 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 FAILED	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 HEALTHY	INFO	no	Message: All {0} expected CES IPs are assigned.
				Description: All declared CES IPs are assigned.
				Cause: N/A
				User Action: N/A
ces_ips_unassigned	STATE_CHANGE DEGRADED	WARNING	no	Message: {0} of {1} declared CES IPs are unassigned.
				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.
s3_config_backup_disable	STATE_CHANGE HEALTHY	INFO	no	Message: The CES S3 service is disabled.
				Description: The S3 service is disabled by mmces service disable s3 command on this node. Disabling a service also removes all configuration files, which are different from stopping a service.
				Cause: N/A
				User Action: N/A
s3_config_backup_notok	STATE_CHANGE DEGRADED	WARNING	no	Message: S3 config backup failed, last backup CCR version is {0}.
				Description: There is a problem in backing up of S3 config file in CCR. We expect the CCR backup to be updated every 10 minutes.
				Cause: The S3 backup file in CCR is too old or does not exist, as can be seen in the output of the mmccr flist command.
				User Action: Check the mmcess3backup cronjob whether backup job is running or not.
s3_config_backup_ok	STATE_CHANGE HEALTHY	INFO	no	Message: S3 config backup done, current backed up version is {0}.
				Description: The config backup is OK.
				Cause: N/A
				User Action: N/A