Content:
Failed to get Blackhole Security Group
Corrective action:
Set the AWS Lambda environment variable PCLSWR_BLACKHOLE to the blackhole security group identifier. For information about configuring AWS Lambda, see "A. 2.4. 1 Configuring AWS Lambda" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
Content:
Failed to apply Blackhole Security Group
Corrective action:
No action is required. For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER PRIMECLUSTER Troubleshooting".
Content:
ELB target deletion failed
Corrective action:
Delete the source virtual server from the target group. For information about setting up target groups, see "A. 2.3. 2 Configuring Network Inheritance" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting ".
Content:
Failed to add target for the ELB target
Corrective action:
Add the virtual server to be switched to the target group. For information about setting up target groups, see "A. 2.3. 2 Configuring Network Inheritance" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
CloudWatch alarms update failed
Corrective action:
Check the CloudWatch alarm configuration for the alarm name (alarm_name) in the same region as the source server.
If the instance name (InstanceID) of the CloudWatch alarm contains the instance ID (new_instance_id) that you want to switch to, no action is required. If the source instance ID (instance_id) is registered for the CloudWatch alarm instance name (InstanceID), update CloudWatch alarms by replacing the source instance ID (instance_id) with the destination instance ID (new_instance_id).
For information about the currently configured configuring CloudWatch alarms, see "A.2.4.3 Configuring CloudWatch Alarm" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
Failed to update the switch execution management object
Corrective action:
In Amazon DynamoDB, look for an item in the table with the table name Fujitsu-Pclswr-DB-Switcher, with a value for the attribute name InstanceID that matches the instance ID (instance_id) from which you switched, and delete the item.
Then, see "A.2.4.4 Configuring Amazon DynamoDB" in "Installation and Administration Guide
4.6 Cloud Services" to create an item with the attribute name SystemID value set to system_id, the attribute name InstanceID value set to new_instance_id, and the attribute name State value set to NOT_SWITCHED.
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
Failed to destroy the virtual server
Corrective action:
Make sure that there is a virtual server that matches the instance ID (instance_id) of the virtual server to be switched. If it does not exist, no action is required. If present, terminate the virtual server instance if it is not terminated. If it is terminated, no action is required.
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
The event that occurs does not need to be switched, so it ends without switching. Check the event type and take appropriate action.
Corrective action:
Check the event type from the value of event_type.
If event_type is EC2_STATUSCHECKFAILED_INSUFFICIENT_DATA_EVENT:.
Among the CloudWatch alarms that monitor the virtual server whose instance ID is instance_id, check the state of the alarm that you set as the alarm for the switcher in "A.2.4.3 Configuring CloudWatch Alarm" in "Installation and Administration Guide
4.6 Cloud Services" . If the alarm condition is OK, no action is required. If the alarm status is insufficient data (INSUFFICIENT_DATA), check whether the alarm settings are correct, and if they are incorrect, reset them.
If the alarm is set correctly and the status of data shortage (INSUFFICIENT_DATA) continues, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting ".
If event_type is RMS_INSUFFICIENT_DATA_EVENT:.
Check the state of the CloudWatch agent process on the virtual server whose instance ID is instance_id and restart the process if necessary.
Content:
Failed to get information for ELB
Corrective action:
Remove the source virtual server whose instanceID is instance_id from the target group and add the destination virtual server.
For the instanceID of the virtual server to switch to, see the instance_id in the following notification message, which has the same event_id as the event_id in this message:.
- Switcher has completed switching. (event_id=event_id, system_id=system_id, new_instance_id=instance_id)
For information about setting up target groups, see "A.2.3.2 Configuring Network Takeover" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
Failed to get CloudWatch alarms information
Corrective action:
Check the CloudWatch alarm settings and update the CloudWatch alarm by replacing the instance ID (instance_id) of the virtual server you are switching to with the instance ID of the virtual server you are switching to in the instance name (InstanceID) of the CloudWatch alarm.
For the instance ID of the virtual server to switch to, see the instance_id in the following notification message, which has the same event_id as the event_id in this message:.
- Switcher has completed switching. (event_id=event_id, system_id=system_id, new_instance_id=instance_id)
For information about configuring CloudWatch alarms, see "A.2.4.3 Configuring CloudWatch Alarm" in "PRIMECLUSTER Installation and Administration Guide 4.6 Cloud Services".
For more information on the cause of the failure, collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
Content:
An internal error has been detected.
Corrective action:
Collect the survey information and contact our company service representative (SE). For details on how to collect survey information, see "PRIMECLUSTER Troubleshooting".
