This section explains error messages for the shutdown facility, in the alphabetical order.
Content:
Execution of the command command failed.
Corrective action:
Check that the command command can be executed normally on the command executed node, referring to the returned value from the command. After check is complete, re-execute the command.
Content:
The command command failed on the node node.
Corrective action:
Check that the command command can be executed normally on the node node, referring to the returned value from the command. After check is complete, re-execute the command.
Content:
Timeout occurred during execution of the command command.
Corrective action:
Check that the command command can be executed normally on the command executed node, referring to the returned value from the command. After check is complete, re-execute the command.
Content:
Distribution of the index file to node node failed.
Corrective action:
Confirm that the CF services (CFSH, CFCP) have been set correctly, referring to "Setting Up CF and CIP" of "PRIMECLUSTER Installation and Administration Guide."
If the CF services have been set correctly, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Distribution of the panicinfo definition file to node node failed.
Corrective action:
Confirm that the CF services (CFSH, CFCP) have been set correctly, referring to "Setting Up CF and CIP" of "PRIMECLUSTER Installation and Administration Guide."
If the CF services have been set correctly, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Reading of the Netdump client settings on the node node failed.
Corrective action:
Confirm that Netdump is normally set up.
Content:
Changing the mode of index file on node node failed.
Corrective action:
Confirm that the chmod command can be executed normally on node node for the "/etc/opt/FJSVcllkcd/etc/SA_lkcd.idx" file, and then re-execute the command.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Updating the rcsd.cfg failed on the node node.
Corrective action:
Confirm that the "/etc/opt/SMAW/SMAWsf/rcsd.cfg" file is included in the node node, and then re-execute the command.
Content:
Changing the owner of files on the node node failed.
Corrective action:
Confirm that the chown command can be executed normally for the "/etc/opt/FJSVcllkcd/etc/SA_lkcd.idx" file and "/etc/opt/SMAW/SMAWsf/rcsd.cfg" file on the node node, and then re-execute the command.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Changing the owner group of files on the node node failed.
Corrective action:
Confirm that the chgrp command can be executed normally for the "/etc/opt/FJSVcllkcd/etc/SA_lkcd.idx" file and "/etc/opt/SMAW/SMAWsf/rcsd.cfg" file on the node node, and then re-execute the command.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Changing the mode of panicinfo configuration definition file on node node failed.
Corrective action:
Confirm that the chmod command can be executed normally on node node for the "/etc/panicinfo.conf" file, and then re-execute the command.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Changing the owner of panicinfo configuration definition file on the node node failed.
Corrective action:
Confirm that the chmod command can be executed normally on node node for the "/etc/panicinfo.conf" file, and then re-execute the command.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Changing the owner group of panicinfo configuration definition file on the node node failed.
Corrective action:
Check that chgrp command is executed normally for the "/etc/panicinfo.conf" file on the node node, and then execute the command again.
If the command cannot be executed normally, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An internal error occurred in the program.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Reading Shutdown Agent configuration failed. You might have set the Shutdown Agent incorrectly.
Corrective action:
Confirm that Shutdown Agent configuration is correct then execute the command again.
Content:
Reading Shutdown Facility configuration failed. You might have set the Shutdown Facility incorrectly.
Corrective action:
Make sure the configuration of the SF is complete and then execute the command again.
Content:
The configuration file for the Blade Shutdown Agent does not exist. The setting of the Blade Shutdown Agent may not have been complete.
Corrective action:
Make sure the configuration of the Blade Shutdown Agent is complete and then execute the command again.
Content:
The configuration file for the IPMI Shutdown Agent does not exist. The setting of the IPMI Shutdown Agent may not have been complete.
Corrective action:
Make sure the configuration of the IPMI Shutdown Agent is complete and then execute the command again.
Content:
The configuration definition file of the IPMI Shutdown Agent (SA_ipmi.cfg) differs among the nodes.
Corrective action:
Conform the contents of the "/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg" file on all the nodes.
After the contents of the "/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg" file are conformed on all the nodes, execute the command again.
Content:
The iRMC IP address of the node node is not set correctly in the configuration definition file of the IPMI Shutdown Agent. (iRMC IP address of the node node : ip-address)
Corrective action:
Correct the value of the iRMC IP address of the node node, which is set in the "/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg" file on all the nodes.
Correct the value of the iRMC IP address to be valid, and then execute the command again.
Content:
The RSB Shutdown Agent configuration file is not found. You might not have completed configuration the RSB Shutdown Agent.
Corrective action:
Confirm that RSB Shutdown Agent configuration is completed then execute the command again.
Content:
The configuration file for the SF does not exist. The setting of the SF may not have been complete.
Corrective action:
Make sure the configuration of the SF is complete and then execute the command again.
Content:
Creation of the file name file failed.
Corrective action:
Confirm that the file name file can be created then execute the command again.
