This section explains the FJSVcluster format error messages in the order of message numbers.
If an error message is output, conduct the log analysis on the time zone the message was output from the /var/adm/messages file for Solaris or the /var/log/messages for Linux to check if other messages had output beforehand. If so, take corrective action following instructions on that error message in the first place.
Content:
The text of the message that is correspondent to the message number is not available.
Conduct confirmation as it is possible that no message catalog or symbolic link to the message catalog exists.
Corrective action:
If no message catalog exists, conduct installation again.
If no symbolic link exists, create the link using the In command.
If the message is displayed again, collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
For message catalogs, see below.
Solaris/Linux
/opt/FJSVclapi/locale/C/LC_MESSAGES/FJSVcluster
/opt/FJSVcldev/locale/C/LC_MESSAGES/FJSVcldev
/opt/FJSVclapi/locale/ja/LC_MESSAGES/FJSVcluster
/opt/FJSVcldev/locale/ja/LC_MESSAGES/FJSVcldev
For symbolic links, see below.
Solaris
/usr/lib/locale/C/LC_MESSAGES/FJSVcluster
/usr/lib/locale/C/LC_MESSAGES/FJSVcldev
/usr/lib/locale/ja/LC_MESSAGES/FJSVcluster
/usr/lib/locale/ja/LC_MESSAGES/FJSVcldev
Linux
/usr/share/locale/C/LC_MESSAGES/FJSVcluster
/usr/share/locale/C/LC_MESSAGES/FJSVcldev
/usr/share/locale/ja_JP.UTF-8/LC_MESSAGES/FJSVcluster
/usr/share/locale/ja_JP.UTF-8/LC_MESSAGES/FJSVcldev
/usr/share/locale/ja_JP/LC_MESSAGES/FJSVcluster
/usr/share/locale/ja_JP/LC_MESSAGES/FJSVcldev
/usr/share/locale/ja_JP.eucJP/LC_MESSAGES/FJSVcluster
/usr/share/locale/ja_JP.eucJP/LC_MESSAGES/FJSVcldev
Content:
A failure occurred in the server. It will be terminated.
Corrective action:
Follow the corrective action of the error message that was displayed right before this 0102 message.
Content:
An internal error occurred in the program.
function, code1, code2, code3, and code4 indicate the investigation information for error diagnosis.
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:
This message indicates that the memory resources are insufficient.
code1 and code2 indicate the information necessary for error investigation.
Corrective action:
One of the following could be the case:
The memory resources are insufficient.
The kernel parameter has incorrect settings.
Reexamine the estimation of the memory resources that are required for the entire system. For information on the amount of memory required for cluster control, see the Installation Guide for PRIMECLUSTER, which is provided with each product.
If you still have the problem, confirm that the kernel parameter settings are correct by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
Change the settings if necessary, and then reboot the system. If above actions do not help you solve the problem, contact field engineers.
If above actions do not help you solve the problem, record the message, collect the investigation information and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates that disk or system resources are insufficient. code1 and code2 indicate the information necessary for error investigation.
Corrective action:
One of the following could be the case:
The disk resources are insufficient.
The kernel parameter has incorrect settings.
Record this message and collect information for an investigation. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Confirm that there is sufficient disk space to enable the operation of PRIMECLUSTER. If necessary, delete any unnecessary files to create sufficient free space and then restart the system. For information on the amount of required disk space, see the Installation Guide for PRIMECLUSTER," which is provided with each product.
If you still have the problem, confirm that the kernel parameter settings are correct by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier. Change the settings if necessary, and then reboot the system.
If above actions do not help you solve the problem, contact field engineers.
Content:
Option designation is incorrect. option indicates an option.
Corrective action:
Specify the option correctly, and then re-execute the operation.
Content:
It is required to execute by the system administrator authority.
Corrective action:
Re-execute the process with system administrator' s authority.
Content:
Shared memory resources are insufficient for the Resource Database to operate.
Corrective action:
Review estimated allocation for shared memory resource by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier. Then, reboot the node that has the changed kernel parameter settings.
If this error cannot be corrected by the above 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."
code1 and code2 indicate the information required for error investigation.
Content:
Specify the mandatory options shown in option.
Corrective action:
Specify the option correctly, and then re-execute the operation.
Content:
Specify on of mandatory options shown in option.
Corrective action:
Specify a correct option, and execute the command again.
Content:
When an option is specified option1, an option must be specified also to option2.
Corrective action:
Specify the option correctly, and then re-execute the operation.
Content:
Two options specified with the command conflict.
Corrective action:
Re-execute the command by specifying either one of the options.
Content:
If one of the options is specified to option1, any option cannot be specified to option2.
Corrective action:
Specify the option correctly, and then re-execute the operation.
Content:
Specify options sequentially in the correct order. option indicates an option specified in the wrong order and order, correct designation sequence.
Corrective action:
Specify options in the order shown by order. Then, run the processing again.
Content:
Specify the value of the option shown in option within the range between value1 and value2.
option indicates the specified option while value1 and value2 indicate values.
Corrective action:
Specify the value of the option shown in option within the range between value1 and value2. Then, run the processing again.
Content:
This message indicates that mismatch of cluster configuration database occurred to the cluster configuration management facility.
Corrective action:
Collect the investigation information from all the nodes and then recover the system as instructed below. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
As the node to which this message is not output is the one that has mismatch of the cluster configuration database, reboot that node.
name indicates a database name in which a mismatch occurred, while node indicates an ID node name that has an old cluster configuration database. node of the node number indicates a node ID number of which cluster configuration database is normal.
If above actions do not help you solve the problem, record this message and contact field engineers.
Content:
An internal error occurred in the cluster configuration management facility.
node indicates a node where an error occurred. code indicates a code showing the details of processing executed against the error.
Corrective action:
One of the following could be the case:
The kernel parameter has incorrect settings.
The memory resources are insufficient.
The disk resources are insufficient.
Confirm that the kernel parameter settings are correct by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
If not, correct the settings and then reboot the system.
If the above does not correct the problem, review the estimated memory resources required for the entire system. As for memory resources required for controlling the cluster, refer to the Installation Guide for PRIMECLUSTER provided with each product.
If the problem still remains, confirm that there is sufficient disk space to enable the operation of PRIMECLUSTER. If necessary, delete any unnecessary files to create sufficient free space and then restart the system.
For information on the amount of required disk space, see the Installation Guide for PRIMECLUSTER, which is provided with each product.
CF and the cluster interconnect are not running.
Check if CF and the cluster interconnect are running by using the cftool and ciptool commands. If not, take a necessary action based on the displayed CF message.
If the error still cannot be solved after the above actions, record this message and collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An internal error has occurred in the event configuration management facility of the cluster control.
cod1 and code2 indicate the information necessary for error investigation.
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:
This message indicates that communication paths to other nodes are disconnected for the cluster management configuration system.
Corrective action:
Check the state of other nodes and path of a private LAN.
Content:
This message indicates that the cluster management configuration system has not been started up.
Corrective action:
Record this message and those before and after 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:
This message indicates that there is the wrong command definition information that is used by the cluster management configuration system.
target indicates a command name.
Corrective action:
Record this message and those before and after 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:
There is a node among nodes that configure the cluster domain, which has not been started up.
Corrective action:
Activate the node in the stopped state.
Content:
The user has no access authority. target indicates a command name.
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:
The specified file or cluster configuration database does not exist.
target indicates a file name or cluster configuration database name.
Corrective action:
One of the following causes is possible:
The kernel parameter has incorrect settings.
The memory resources are insufficient.
The disk resources are insufficient.
Confirm that the kernel parameter settings are correct by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
If not, correct the settings and then reboot the system.
If the above does not correct the problem, review the estimated memory resources required for the entire system. As for memory resources required for controlling the cluster, refer to the Installation Guide for PRIMECLUSTER provided with each product.
If the problem still remains, confirm that the disk space necessary for operation of PRIMECLUSTER. If not, delete unnecessary files to ensure the sufficient space and then reboot the system. For details on memory space required for PRIMECLUSTER operation, refer to the Installation Guide for PRIMECLUSTER provided with each product.
If this error cannot be corrected by the above 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:
The specified cluster configuration database is currently being used.
table indicates a cluster configuration database name.
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:
A cluster configuration database that has the same name exists.
table indicates a cluster configuration database name.
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:
The specified configuration change procedure has already been registered.
proc indicates a configuration change procedure name.
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:
The same information already exists in the cluster configuration database.
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:
The cluster configuration database reflecting processing of the cluster configuration management facility has terminated abnormally.
target indicates a cluster configuration database name.
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."
Collect the investigation information in all the nodes, then reactivate all the nodes.
Content:
This message appears when you attempt to add a node exceeding the maximum number of configuration nodes.
Corrective action:
Review the cluster system configuration so that the number of nodes becomes equal to or less than the maximum number of composing nodes.
Content:
Mismatch of cluster configuration database occurred for the cluster configuration management facility because of insufficient memory resources of other node.
name indicates a database in which a mismatch occurred and node indicates a node for which a memory shortfall occurred.
Corrective action:
Review the memory resource allocation, and reboot the node. If an error still occurs, record this message and collect the investigation information. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Review the memory resource allocation. If this error cannot be solved by operator response, contact field engineers. After collecting data for all the nodes, stop the node and start it again.
Content:
Mismatch of cluster configuration database occurred for the cluster configuration management facility because of insufficient disk or system resources of other node.
name indicates a database in which a mismatch occurred and node indicates the node in which insufficient disk resources or system resources occurred.
Corrective action:
Record this message and collect information for an investigation. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Review the disk resource and system resource (kernel parameters) allocation by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier. When the kernel parameter is changed for a given node, restart that node. If this error cannot be corrected by the above, contact field engineers.
Content:
An error occurred during distribution of a file to a stopping node.
name indicates the file name that was distributed when a failure occurred, node indicates the node in which a failure occurred, and errno indicates the error number when a failure occurred.
Corrective action:
File cannot be distributed from the erroneous node to the stopped node. Be sure to start the stopped node before the active node stops. It is unnecessary to re-execute the command.
Content:
The activating node cannot be recognized by the cluster configuration management facility.
code1 and code2 indicate the information required for error investigation.
Corrective action:
Confirm that there are no failures in Cluster Foundation (CF) or cluster interconnection. If a failure occurs in CF, take the corrective action following the CF message. If a failure occurs in cluster interconnection, check the cluster interconnection and network settings. If you still have this problem after going through the above instructions, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Communications cannot be done between nodes or processes for the cluster configuration management facility.
code1 and code2 indicate the information required for investigation.
Corrective action:
Confirm that there are no failures in cluster interconnection. If a failure occurs in cluster interconnection, check the cluster interconnection and network settings.
If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Parameter setting used by cluster management is incorrect.
code1 and code2 indicate the information required for error investigation.
Corrective action:
The kernel parameter used by the resource database is incorrect. Modify the settings by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
When the kernel parameter is modified, reboot the modified node.
If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The network to be used by the cluster configuration management facility is not available.
code1 and code2 indicate the information required for error investigation.
Corrective action:
Confirm the /etc/inet/services file is linked to the /etc/services file. If not, you need to create a symbolic link to the /etc/services file after editing to correct settings. Confirm the following network services are set up correctly in the /etc/inet/services file. If any of the followings are missing, you need to add the missing one.
dcmcom 9331/tcp# FJSVcldbm packagedcmsync 9379/tcp# FJSVcldbm packagedcmlck 9378/tcp# FJSVcldbm packagedcmfcp 9377/tcp# FJSVcldbm packagedcmmst 9375/tcp# FJSVcldbm packagedcmevm 9376/tcp# FJSVcldbm packageIf the above settings are correct, confirm that the services of the /etc/nsswitch.conf file are defined as shown below. If not, you need to define them correctly.
services: files nisplusReboot the modified node.
If the /etc/nsswitch.conf file is correctly set, confirm that the SysNode names are also correctly set to /etc/inet/hosts (for Solaris) or /etc/hosts (for Linux).
If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An error is detected to the specified command.
command, code1 and code2 indicate the information required for error investigation.
Corrective action:
Confirm that you can normally run the program specified by the "clexec" command. If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
One or more kernel parameter settings used for cluster management are missing.
code indicates a missing kernel parameter setting and the minimum value necessary for cluster management to operate.
Corrective action:
One or more kernel parameters used by the resource database are not specified. Modify the settings by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier. When the kernel parameter is modified, reboot the modified node.
If this message appears during initial setting of the resource database, review the kernel parameter settings, execute the "clinitreset" command, reboot the node, and initialize the resource database again.
If you still have this problem after going through the above instructions, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
FJSVclswu must have been installed for executing this command.
Corrective action:
Install the FJSVclswu package before executing the command. Refer to the Installation Guide for PRIMECLUSTER for further details.
Content:
This message indicates failure in resource database setting.
code1 and code2 represent the information for error investigation.
Corrective action:
Check if an error message is output to /var/adm/messages (Solaris) or /var/log/messages (Linux) by the cluster management facility. If so, take the following corrective action:
Execute "clinitreset" command at all the nodes.
Reboot all the nodes.
One of the following could be the case:
An error caused by the error message displayed before this message.
The CIP setting is invalid.
Communication used for PRIMECLUSTER by filtering the network (such as iptables) is not available.
If an error message was displayed before this message, see the corrective action of the error message.
If no error message is displayed, see "PRIMECLUSTER Installation and Administration Guide" to check that the CIP setting is correct.
If the setting is not correct, modify it.
If you still have the problem, check whether the communication used for PRIMECLUSTER by filtering the network (such as iptables) is not available.
If the setting is not correct, restart the system.
If this message appears during execution of "clsetup" command, execute the command again. If this message appears on the CRM main window, initialize the CRM again.
If you still have this problem after going through the above instructions, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates failure in creating a backup file of the resource database.
code1 and code2 indicate the information required for investigation.
Corrective action:
The disk space might be insufficient. Make sure you have 1 MB or more of free disk space, and try backing up again.
If you still have this problem after going through the above instruction, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates failure in restoring the resource database information.
code1 and code2 indicate the information required for investigation.
Corrective action:
The disk space might be insufficient. Make sure you have 1 MB or more of free disk space, and try backing up again.
If you still have this problem after going through the above instruction, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The specified resource cannot be manipulated because of lack of user authority.
Corrective action:
Re-execute the specified resource with registered user authority.
Content:
Cannot delete the specified resource.
resource indicates the resource name of the specified resource. rid indicates the resource ID of the specified resource.
Corrective action:
Specify the resource correctly, and then re-execute it.
Content:
The specified resource does not exist. code1 and code2 indicate the information required for investigation.
Corrective action:
Specify the resource correctly, and then re-execute the operation. If the message is displayed again, record the message, collect the information required for investigation, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
A non-existing file is specified.
Corrective action:
Specify the correct file, then re-execute the processing.
Content:
A non-existing resource class is specified.
Corrective action:
Specify the correct resource class, and then re-execute the processing.
A specifiable resource class is a file name itself that is under /etc/opt/FJSVcluster/classes.
Confirm that there is no error in the character strings that have been specified as the resource class.
Content:
The specified resource cannot be operated, as the service is not in the stopped state.
code1 and code2 indicate the information required for error investigation.
Corrective action:
Stop the cluster service, then re-execute the processing.
Content:
A non-existing node is specified.
Corrective action:
Specify the node correctly. Then, execute again.
Content:
Operation cannot be performed, as the resource information of the specified resource is under updating.
code1 and code2 indicate the information required for error investigation.
Corrective action:
Re-execute the processing.
Content:
The specified resource has already been registered.
code1 and code2 indicate the information required for error investigation.
Corrective action:
If this message appears when the resource is registered, it indicates that the specified resource has been already registered. It is unnecessary to register it again.
If this message appears when changing a displayed name, specify other name because the specified display name has already been registered.
Content:
An internal error occurred in the cluster configuration management facility.
code1 and code2 indicate the information required for error investigation.
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:
The cluster configuration management facility is not running.
code1 and code2 indicate the investigation information required for field engineers.
Corrective action:
Reactivate the Resource Database by restarting the node. If the message is redisplayed, record this message and collect related information for investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An error occurred to communication processing of cluster configuration management facility.
code1 and code2 indicate the investigation information required for field engineers.
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:
The specified state transition procedure file does not exist.
Corrective action:
Specify the state transition procedure file correctly, and then run the processing again.
If the problem cannot be solved with this corrective action, collect the investigation information and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
As the state transition procedure file having the same name already exists, the state transition procedure could not be saved.
Corrective action:
To overwrite the state transition procedure file, specify the "-----o" option and then run the processing again.
Content:
As a wrong resource class is specified, the state transition procedure file could not be saved.
Corrective action:
Specify the resource class correctly, and then run the processing again. The applicable resource classes are file names under /etc/opt/FJSVcluster/classes.
Confirm that the character string specified as the resource class contains no errors.
Content:
This message indicates failure in operation of the state transition procedure file.
code1 indicates the necessary investigation information while code2 indicates an error number.
Corrective action:
When retrieving the state transition procedure:
Confirm that the disk resource from which the state transition procedure is retrieved or the node resource of the file system is sufficient. Correct the insufficient resource problem or change the location from which the state transition procedure is retried, and retry. Use the command listed below for confirmation of resources:
For Solaris
df(1M)
For Linux
df(1)
When registering the state transition procedure:
Confirm that the disk resource on which the cluster system is installed or the node resource of the file system is sufficient. If insufficient, correct the insufficient resource problem, and retry. Use the command listed below for confirmation of resources:
For Solaris
df(1M)
For Linux
df(1)
If the problem cannot be solved even after the above corrective action, collect the investigation information and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The specified state transition procedure file cannot be deleted.
Corrective action:
You can delete only the state transition procedure file that was defined by a user.
For information on how to delete a state transition procedure file not defined by the user, consult the file supplier.
Content:
The specified resource does not exist in the cluster services.
resource indicates the resource name not registered to the resource database while rid, the resource ID not registered to the resource database.
Corrective action:
Solaris
A procedure resource that is registered in the userApplication is not in the resource database. This message is not output if the userApplication was registered by using the userApplication Configuration Wizard (GUI). However, if this occurs, record this message, collect the investigation information, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Linux
A procedure resource that is registered in the userApplication is not in the resource database. This message is not output if the userApplication was registered by using the hvw for selecting the procedure resource. However, if this occurs, record this message, collect the investigation information, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Confirm that the procedure resource described in the message text is not registered to the resource database by using the "clgettree" command. If it is not registered to the resource database, register the procedure resource described in the message text.As for how to register a procedure resource, make sure to register correctly according to the product of "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)," or "PRIMECLUSTER Installation and Administration Guide (Linux)." If it is registered to the resource database, record this message and collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message will not be displayed on a client system on which a browser is active. This message is displayed on the standard output when you respond to the operator intervention message with the CLI command (clreply). If a string other than yes or no is entered, this message will be displayed.
Corrective action:
Specify the option correctly, and then run the processing again.
Content:
The specified resource cannot be operated.
Corrective action:
The userApplication in which the specified resource is registered is not in the Deact state.
You need to bring the userApplication to which the specified resource is registered to the Deact state by using the ClusterAdmin or "hvutil" command.
Content:
Specify the option option with the absolute path name.
Corrective action:
Specify the option correctly, and then re-execute the operation.
Content:
The specified resource is not being monitored. code indicates the information required for investigation.
Corrective action:
If this message is output while the monitoring process is under operation, check for wrong resource ID that is specified by the "clmonproc" command by using the "clgettree" command. For details on the "clgettree" command, see the manual page.
If this message is output after completion of monitoring process, no action is required.
Content:
The specified process does not exist. pid represents the process ID of the specified process.
Corrective action:
Check the process ID using the "ps" command, specify the process ID correctly, and run the processing again.
Content:
The specified command does not exist. command represents the specified command.
Corrective action:
Specify the command correctly with full path name, and then run the processing again.
Content:
The cluster control is not active. code indicates the information required for investigation.
Corrective action:
Confirm that the resource database is running by executing the clgettree(1) command. If not, reboot the node.
If you still have this problem after going through the above instruction, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The process did not terminate within the termination wait time of the process.
code1 and code2 indicate the information required for investigation.
Corrective action:
Search for a cause. For information on the investigation, contact the creator of the process.
Content:
As a wrong directory was specified, the process cannot be executed.
Corrective action:
Specify the directory correctly, and then re-execute the operation.
Content:
As it is in the single-user mode, the command cannot be executed.
Corrective action:
Boot the node in multi-user mode and retry.
Content:
As the setting for the product shown by the product_name, the command cannot be executed.
Corrective action:
Cancel the setting of the Resource Database product_name and retry. For instructions on how to cancel the setting, refer to the appropriate manual for product_name.
Content:
A non-existing directory is specified.
Corrective action:
Specify an existing directory, and then run the processing again.
Content:
A userApplication or resource that is not registered to patrol diagnosis is specified. resource indicates the specified userApplication or resource name.
Corrective action:
Reexamine the configuration of patrol diagnosis by referring to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
The patrol diagnosis is disabled by the userApplication status. The state of userApplication is output to status.
Corrective action:
Specify the userApplication that is in the following state, and then run the processing again:
Standby, Offline, Faulted, Deact
Content:
Timeout has occurred during patrol diagnosis.
Corrective action:
Confirm that power is being supplied to the node on which patrol is enabled. Power on the node if necessary, and then re-execute.
Confirm that RMS is activated.
If RMS is not activated, start the RMS with Cluster Admin or the "hvcm(1M)" command and then re-execute operation.
Content:
An error has occurred because of a failure at the resource specified by the message.
Corrective action:
If a failure occurred to a hardware resource, repair the hardware.
If a failure occurred to an application resource, check for error cause of respective application.
If a failure occurred to a Cmdline resource that is a procedure created by the user, identify the abnormal termination cause of the process monitored by the check script, and review the program to see if the procedure normally functions.
If a failure occurred to the process monitoring resource, identify the cause of abnormal termination of the monitoring program.
If a failure occurred to the Gds or Gls resource, identify the error cause, referring to the manual of the respective product.
If a failure occurred to the Fsystem resource, check if the warning message alerting that the mount point check process (system call) fails to complete within the predetermined time because of the I/O load or other reasons. If this error occurs frequently, tune the mount point monitoring time (HV_GMOUNTMAXLOOP value) to reduce the I/O load.
Content:
A SysNode failure has occurred. SysNode indicates the SysNode where the failure occurred.
Corrective action:
Respond to the operator intervention message that is displayed after the node is started or confirm the state of userApplication running on the node in which the failure occurred, by using the RMS main window or executing the "hvdisp(1M)" command. If userApplication is Faulted, you need to clear the Fault by using the RMS main window or specifying the "-c" option of the "hvutil(1M)" command.
Content:
If a failure occurs when you execute the RMS command (hvdisp) to enable the history function for the failed resource or the operation intervention function, an error message will be displayed. Examine this error message and after taking an appropriate corrective action, execute the request again.
Corrective action:
Confirm the contents of this message and, after taking the required corrective action, re-execute the processing. For details on the necessary corrective action, refer to "PRIMECLUSTER Installation and Administration Guide."
Content:
Since the RMS command ended abnormally, the operator intervention function indicated by the message failed. command represents the RMS command that terminated abnormally. "Error message from RMS command" indicates the error message that is output to the standard error by the RMS command.
Corrective action:
Note the contents of this message and, after applying an appropriate correction, re-execute the required processing.
number indicates the operator intervention message for which processing failed. action indicates the first response to the message from the operator with either yes or no.
Content:
The specified message number does not exist.
number indicates the number of operator intervention message.
Corrective action:
This message is output in the following situations:
The operator specified a nonexistent message number when executing the "clreply" command. This problem can be solved by specifying a message number that is included in the unfinished message list.
The operator intervention function has automatically replaced the message for which a response has been entered with other message. For example, when the operator intervention function's message number 1422 is replaced by the message number 1423 and vice versa. In such a case, the operator intervention function responds to the first message, displays another message, and advises a user that the message number has been changed.
The message for which a response was entered has been canceled. This occurs when the message gets old since the application state has been changed. You do not have to take any action.
Content:
Since the node indicated by SysNode has stopped, the response to the operator intervention message failed.
SysNode indicates the SysNode name of the node that is stopped. number indicates the number of the operator intervention messages that failed to respond. action indicates the operator's response by yes or no.
Corrective action:
Reboot the node, and then confirm that RMS is running.
Content:
The "clmonproc" command failed to request start or stop monitoring of the process monitoring function.
Corrective action:
The daemon process for the process monitoring function might not be running. Check the "prmd" process by executing the "ps" command. If the "prmd" process does not exist, execute /etc/init.d/clprmd start to recover the process. If the "prmd" process exists, execute /etc/init.d/clprmd stop and then /etc/init.d/clprmd start, to recover the process.
If above actions do not help you solve the problem, contact field engineers.
Content:
A process to be monitored by specifying the "-g" option in the "clmonproc" command must satisfy the condition "process ends immediately after descendent processes are generated." However, the parent process did not end even after the specified time (default 10 seconds) elapsed after the process was started. If the system continues to monitor the process in this condition, the load on the system is getting high, so the process was removed from the processes to be monitored by the process monitoring function.
appli indicates the absolute path name of the monitored process.
Corrective action:
Take one of the following actions:
Do not monitor descendent processes. Do not specify the "-g" option in the "clmonproc" command.
If the monitored process can be changed, do not change the process group in the descendent processes, and do not specify the "-g" option in the "clmonproc" command.
If processes were generated, end the parent process immediately. Set up the process so that the first child process that is generated becomes the process leader immediately after it operates.
Content:
The command that was specified with the "-a" option of the "clmonproc" command could not be executed.
appli indicates the absolute path name of the process that has failed startup. error indicates the detailed code.
Corrective action:
Check whether the command that was specified with the "-a" option of the "clmonproc" command can be executed. Execute the command, and check whether an error occurs. If this message is output again even if the command could be executed, contact field engineers.
Since errno is output as a detail code, field engineers should investigate the cause from this message information. For example, if errno is 13 (EACCES), the most likely cause is that the command path that was specified in the "-a" option of the "clmonproc" command does not have execute permission.
Content:
The power to the disk unit may not be turned on or the disk may be disconnected. If an attempt is made to start userApplication, userApplication may not start normally.
Two messages, namely, this message and that of message number 6836 may be displayed depending on connection.
NodeID indicates the identification number of the node to which the disk unit was connected while disk indicates the shared disk that could not be detected.
Corrective action:
Confirm that the power to the shared disk device is turned on and that the shared disk device is connected correctly. If power is not being supplied to the shared disk device, stop the node, turn on the power to the shared disk device, and then boot the node. If the connection of the shared disk device is incorrect, stop the node, rectify the connection, and then boot the node.
Content:
A failure occurred during execution of the state transition procedure.
procedure indicates the state transition procedure that occurred the failure. When the state transition procedure shown by the procedure was created, correct the state transition procedure, referring to the information hereafter.
code1, code2, code3, code4, code5, or code6 indicates the state transition instruction that resulted in an error. code7 represents the necessary investigation information.
code1: the first argument (state transition instruction type)
code2: the second argument (cluster service instance type)
code3: the third argument (state transition instruction timing)
code4: the fourth argument (resource ID)
code5: the fifth argument (state transition event type)
code6: the sixth argument (state transition event detail)
error indicates the error cause. The error causes include the following:
procedure file exit error
Corrective action:
The possible causes are as follows:
The state transition procedure (procedure) is not a Bourne shell script.
The state transition processes for the individual arguments (code1 to code6) of the state transition procedure (procedure) returned an error. The control program of the procedure resource determines the success or failure of the state transition processes based on the exit code (exit function) of the state transition procedure.
Exit code 0: The control program determines that the state transition process is normal.
Exit code other than 0: The control program determines that the state transition process failed.
Take the following actions:
Obtain the state transition procedure, and check that the state transition procedure (procedure) is a Bourne shell script. If the procedure is not a Bourne shell script, specify the following in the first line of the state transition procedure, and then register the state transition procedure again:
#!/bin/sh
To obtain the state transition procedure, execute the "clgetproc(1M)" command. To register the state transition procedure, execute the "clsetproc(1M)" command. For details on each command, see the corresponding manual page.
Check the return value of the state transition process for each argument (code1 to code6). If there is no process that sets up an exit code (exit function), you need to add this exit code process. If there is no process, the execution result of the last command in the state transition procedure becomes the return value.
If the conditions are satisfied, 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:
The following causes might be considered:
The wiring of the shared disk device is incorrect.
No value is set for the volume name of vtoc.
As the main reason, it is considered that the automatic configuration was not performed when swapping the disk.
If an attempt is made to start the cluster application in the current state, the cluster application may not start up normally.
This message and Message 6807 may be displayed depending on the connection condition.
NodeID indicates the node identification number to which the shared disk device is connected while disk indicates the shared disk in which an error has been detected.
Corrective action:
Confirm that the shared disk device is connected correctly. If the connection is incorrect, stop the node, correct the connection, and then boot the node.
If the cause is "2," perform the automatic configuration.
Content:
The automatic resource registration has terminated abnormally.
reason indicates the command that was abnormally terminated or the returned value.
Corrective action:
If reason is sdxnetdiskconfig-failed, the initial setting of the device for mirroring among servers may have failed. Take the following procedure, and then execute the command again.
If an abnormal node exists in the cluster domain, restore the abnormal node.
Make sure that the description of the shared disk definition file is correct.
Check the free disk space in /etc/opt directory.
If the disk space is less than 100 MB, delete any unnecessary files.
Execute the cat command to output /etc/opt/FJSVsdx/.sdxnetmirror_ipaddr file, and check if the outputs contain the garbled characters. If the outputs are garbled, delete the file.
If the problem is still not solved after taking this procedure, collect the information for error investigation and contact field engineers. For details on how to collect the investigation information, refer to "PRIMECLUSTER Installation and Administration Guide."
If reason is other than sdxnetdiskconfig-failed, this problem may occur when the disk or system resource is not set correctly. Check the setting by referring to PRIMECLUSTER Designsheets (PRIMECLUSTER 4.4 or later) or "PRIMECLUSTER System Design Worksheets" in "PRIMECLUSTER Installation and Administration Guide" (PRIMECLUSTER 4.3 or earlier) that is prepared beforehand. If the problem is still not solved, record this message and collect the information for error investigation. For details on how to collect the investigation information, refer to "PRIMECLUSTER Installation and Administration Guide."
For details on how to create the designsheet, see PRIMECLUSTER Designsheets.
Content:
The automatic resource registration cannot be done if a stopping node exists in the cluster domain.
Corrective action:
Start all the nodes and perform automatic resource registration.
Content:
The automatic resource registration cannot be done unless the cluster configuration management facility is running.
Corrective action:
Record this message and collect the information for error investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After collection of the investigation information, the system may be restored by starting all the nodes again. Restart nodes using the "shutdown(8)" command.
Content:
Creation of a logical path was failed.
node indicates an identification name of the node where creation of the logical path was failed. dev1 indicates the logical path (mplb2048 or a like), and dev2 indicates a tangible path (clt0d0, c2t0d0, and so on) corresponding to the logical path.
Corrective action:
Contact field engineers to confirm that the current setting permit creation of a logical path for the shared disk.
If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Maintenance information (for system administrators)
The command line executed for creating the logical path is stored in the following file of the node indicated by the node identification name.
/var/opt/FJSVcluster/data/ACF/acfmk*device ("*" is an optional figure of 0 or more)
If the command line is correct, the setting of the shared disk device may not support by the logical path.
Content:
This message indicates failure in the resource registration.
reason indicates the reason of the error.
Corrective action:
Check whether the disk or system resource is set correctly.
If above actions do not help you solve the problem, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The following causes might be considered:
A user has created a logical path of multi-path disk before performing the automatic resource registration.
The automatic resource registration was not performed even though the disk was swapped. It can be determined if the setting of volume name vtoc is not set.
If this message appears during registration of an automatic resource after expansion of disks and nodes, the registration command might fail to check the instance displays when performing the automatic resource registration after expanding a disk device or a node, as access to the logical path of the multi-path disk is impossible. This case can be determined from the following conditions:
The same logical path name is created on multiple nodes,
And this logical path can be accessed from certain node, but not from others
Corrective action:
This message appears when the logical path of the multi-path disk is created by the user before registering the automatic resource.
If this message appears during registration of an automatic resource after expansion of disks and nodes, the registration command might fail to check the instance number, as access to the logical path of the multi-path disk is impossible. This happens in the following conditions:
The same logical path name is created on multiple nodes
This path can be accessed from certain nodes, but not from others
The PRIMECLUSTER automatic resource registration has a feature to provide the same environment to all applications. If the instance number (indicates 2048 of mplb2048) of the logical path in the same disk is different between nodes, this message appears, and the automatic resource registration process is aborted. You need to check the logical path of all the nodes. Recreate the logical path if necessary. The instance number should be the same. Then, register the automatic resource again.
If the cause is the failure of accessing the logical path of the multi-path disk, there might be a failure in the disk, or the disk is disconnected to the node.
Take the necessary corrective action and register the automatic resource again.
If you still have this problem after going through the above instructions, collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Maintenance information (for system administrators)
A unique volume name is set to "vtoc" of the disk unit for the automatic resource registration. It can be judged if the disk unit is identical or not by referring to this volume name. Use the "prtvtoc(1M)" command for checking the volume name of disk unit. Examples where the identical disk unit (same volume name) has different instance numbers of logical paths.
node0:
# /usr/sbin/prtvtoc /dev/FJSVmplb/rdsk/mplb2048s2 |head - 1
* /dev/FJSVmplb/rdsk/mplb2048s2 (volume "vol00001") partition map
(v0100001 shown in quotation marks represents a volume name.)
# /usr/sbin/prtvtoc /dev/FJSVmplb/rdsk/mplb2049s2 |head - 1
* /dev/FJSVmplb/rdsk/mplb2049s2 (volume "vol00002") partition map
node1:
# /usr/sbin/prtvtoc /dev/FJSVmplb/rdsk/mplb2048s2 |head - 1
* /dev/FJSVmplb/rdsk/mplb2048s2 (volume "vol00002") partition map
# /usr/sbin/prtvtoc /dev/FJSVmplb/rdsk/mplb2048s2 |head - 1
* /dev/FJSVmplb/rdsk/mplb2049s2 (volume "vol00001") partition map
Create the logical device by eliminating logical paths that have different instance numbers between nodes against /dev/rdsk/cXtXdXs2 while checking volume names using "prtvtoc(1M)" command, in a way the identical disk unit has the same instance number.
As for details on how to create the logical device, refer to "Multi-path Disk Control Guide."
If the cause is disabled access to the disk unit, the "prtvtoc(1M)" command terminates abnormally. In this case, check faulty disk unit and abnormal state of the connection path.
Content:
As disk device settings vary between nodes, the automatic resource registration cannot be done.
Corrective action:
This failure might be caused by one of the following incorrect settings:
Among the nodes connected to the same shared disk, the package of the multi-path disk control is not installed on all the nodes.
The priority mode for automatic detection of the shared disk devices is different between nodes.
The number of paths to the shared disk device is different between nodes.
Remove the failure cause and register the automatic resource again.
Content:
As disk unit configurations conflict each other, the automatic resource registration cannot be done.
Corrective action:
When the same shared disk was mistakenly connected to other cluster system or for other reasons, the volume label might have been overridden. Review the disk unit configuration.
Check the setting if it permits re-write of volume label of shared disk unit (by nodes other than those that configure the cluster system). If this message is displayed while the configuration is correct, record this message, collect the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Rebooting of the node is required for activating the cluster automatic resource registration.
node_name indicates the identifier (volume label) of the node rebooting is required.
Corrective action:
The nodes constituting the cluster system must be restarted. Restart the nodes constituting the cluster system. After that, perform the necessary resource registration again.
When two or more nodes are indicated in the node_name, those node identifiers are delimited with commas. If node_name is "All," restart all of the nodes constituting the cluster system.
Maintenance information (for system administrators)
The measure numbers of "sfdsk" drivers must match each other between nodes for enabling the automatic resource registration. As the driver measure numbers are reserved during PRIMECLUSTER installation, this message is normally not displayed. The case this message is displayed is limited only when, although a measure number is reserved after PRIMECLUSTER installation, the node is not restarted and the driver is not running by the reserved measure number.
Content:
The message indicates that all device number information must be matched among all the nodes for disabling the cluster automatic resource registration.
dev_name represents the necessary information for investigation.
Corrective action:
Record this message, and contact field engineers. The system engineer will take care of matching transaction based on the information on the disk devices.
Maintenance information (for system administrators)
Measure numbers must be matched among "sfdsk" drivers between nodes for enabling the automatic resource registration. For this reason, reservation of a measure number is attempted during PRIMECLUSTER installation, the attempt is failed, as other driver already uses that number or for other reasons. Reserve a unique measure number to each driver and restart the node for reflecting the new settings. dev_name indicates the prefix of the driver reservation again is required.
Content:
This message indicates that an error for RCI is detected.
Corrective action:
An RCI transmission failure occurs between the node where the error message is output and nodename in the error message. Improper connection of RCI or a system error might be considered as the cause of the error.
Check the following:
The RCI cable is connected.
Operations such as firm reboot or firm up is performed on the RCI.
If these are the cause, take the corrective action. Then, execute the following commands on the node where the error message appears to restart the Shutdown Facility (SF) and the RCI monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e
# /etc/opt/FJSVcluster/bin/clrcimonctl stop
# /etc/opt/FJSVcluster/bin/clrcimonctl start
# /opt/SMAW/bin/sdtool -b
If this corrective action does not work, hardware failures such as the RCI cable and System Control Facility (hereafter, SCF) might be considered as the cause of the error.
Write down the error message, collect SCF dump and required information for troubleshooting, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Field engineers restart the RCI monitoring agent (MA) and the Shutdown Facility (SF) after recovering hardware.
Content:
This message indicates that the RCI address is not correct.
Corrective action:
The following causes might be considered:
The RCI address is not configured.
The RCI address is duplicated.
The RCI address of other node is changed while the RCI monitoring agent is running.
Write down the error message, collect SCF dump and required information for troubleshooting, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
The field engineer confirms if the RCI address of nodename indicated in the message is correctly set up. To check the previous RCI address, execute the following command on an arbitrary node:
# /opt/FJSVmadm/sbin/setrci -c statAfter setting the correct RCI address, execute the following commands on the node where the error message appears to restart the RCI monitoring agent (MA) and the Shutdown Facility (SF):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrcimonctl stop# /etc/opt/FJSVcluster/bin/clrcimonctl start# /opt/SMAW/bin/sdtool -----b
Content:
There is a problem in the RCI setting.
Corrective action:
RCI has not been set or the RCI setting is incorrect.
Record this message and collect information for an investigation. If a message of System Control Facility (SCF) is output, record that message and collect SCF dumps. Then, contact field engineers. For details on how to collect information and SCF dumps, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide." For the messages output from the System Control Facility (SCF), see the "Enhanced Support Facility User's Guide."
Take the above corrective action and execute the following commands on the node where this message was output. Then, restart the Shutdown Facility (SF) and RCI monitoring agent.
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrcimonctl stop# /etc/opt/FJSVcluster/bin/clrcimonctl start# /opt/SMAW/bin/sdtool -bContent:
This message indicates that the console monitoring agent has been started.
Corrective action:
If you do not need to restart the console monitoring agent, you do not have to take any action. If you need to restart the console monitoring agent, execute the following commands on the node where this error message appeared to restart the console monitoring agent (MA) and the Shutdown Facility (SF):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrccumonctl stop# /etc/opt/FJSVcluster/bin/clrccumonctl start# /opt/SMAW/bin/sdtool -bIf this corrective action does not work, write down the error message, collect required information for troubleshooting and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates that the RCI monitoring agent has been started.
Corrective action:
If you do not need to restart the RCI monitoring agent, you do not have to take any action. If you need to restart the RCI monitoring agent, execute the following commands on the node where this error message appeared to restart the RCI monitoring agent (MA) and Shutdown Facility (SF):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrcimonctl stop# /etc/opt/FJSVcluster/bin/clrcimonctl start# /opt/SMAW/bin/sdtool -bIf this corrective action does not work, write down the error message, collect required information for troubleshooting and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Unsupported version of Hardware Control Program (HCP) is in use.
Corrective action:
The HCP version is not supported. To use XSCF, you need to update HCP to the appropriate version. For information on how to update HCP, refer to the XSCF (eXtended System Control Facility) User's Guide.
If this corrective action does not work, write down the error message, collect required information for troubleshooting and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates that XSCF currently in use is not supported.
Corrective action:
The following causes are possible:
XSCF is not implemented in the main unit
ESF (Enhanced Support Facility) is not installed
Refer to the instruction manual of the main unit and check whether XSCF is implemented. Also refer to the ESF Installation Guide to check whether ESF is installed. If XSCF is implemented and ESF is not installed, install it.
If this corrective action does not work, record the error message, collect the investigation information, and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates the CF is not running.
Corrective action:
If CF has not been configured, you need to configure it, referring to "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide." If CF has been configured, reboot the node and start CF.
As for details on how to start the CF, refer to "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
Content:
This message indicates failure in obtaining the HCP version.
Corrective action:
The HCP version is not known. ESF (Enhanced Support Facility) might have been incorrectly installed. Or referring to the ESF Installation Guide, check if ESF is installed.
If the conditions are satisfied, 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."
Corrective action:
You need to check the following points and execute the command again:
Whether the specified CF node name is correct.
Use "cftool" and check whether the specified CF node name is correct. If an incorrect CF node name was specified, specify the correct CF node name.
Whether the CF of the specified node is operating.
Use "cftool," and check whether the CF is operating. If the CF is not operating, start the CF. As for the "cftool" command, refer to the manual page of the "cftool" command. For details on how to start the CF, refer to "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
If this corrective action does not work, record the error message, collect the investigation information and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
No console information of the specified CF node name has been registered.
Corrective action:
Check the currently registered console information using the "clrccusetup -----l" command. Register the console information, if necessary, using the Shutdown Agent Wizard or the "clrccusetup" command. For the Shutdown Agent Wizard, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)." For the clrccusetup command, see the manual pages.
If this corrective action does not work, record the error message, collect the investigation information and contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
This message indicates detection of an RCI address error.
Corrective action:
Check if the RCI address is correct. Record the message, collect the SCF dump and investigation information, and field engineers. For details on how to collect the SCF dump and investigation information, refer to "PRIMECLUSTER Installation and Administration Guide."
Our field engineers confirms if the RCI address of nodename indicated in the message is correctly set up. To check the previous RCI address, execute the following command on an arbitrary node:
# /opt/FJSVmadm/sbin/setrci statIf the RCI address is incorrect, correct it. For details on the setting procedure, refer to the maintenance manual for field engineers. The node of the nodename shown in the error message is excluded from monitoring and furious stop until the shutdown facility (SF) is restarted. After setting up of the correct RCI address, execute the following command at the node to which the message was output to restart the shutdown facility (SF):
# /opt/SMAW/bin/sdtool -----e
# /opt/SMAW/bin/sdtool -----b
Content:
RCI cannot be operated in the environment.
Corrective action:
Check if Enhanced Support Facility (hereafter, SCF) is installed correctly and it operates properly. If there is a problem on ESF, take the corrective action. Then, execute the following commands on the node where the error message appeared to restart the Shutdown Facility (SF) and the RCI monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrcimonctl stop# /etc/opt/FJSVcluster/bin/clrcimonctl start# /opt/SMAW/bin/sdtool -bIf the problem has not yet been resolved, record this message and collect information for an investigation. If a message of System Control Facility (SCF) is output, record that message and collect SCF dumps. Then, contact field engineers. For details on how to collect information and SCF dumps, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide." For the messages output from the System Control Facility (SCF), see the "Enhanced Support Facility User's Guide."
Content:
SNMP information for the specified CF node name has not been registered.
Corrective action:
Execute the clsnmpsetup -l command, and check the currently registered console information.
Then, if necessary, use the shutdown configuration wizard or the clsnmpsetup command to register the console information.
For details about the shutdown configuration wizard, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)." For details about the clsnmpsetup command, see the manual page.
If this corrective action does not work, 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:
This message indicates that the connection to the console is disconnected.
Corrective action:
Check the following points:
<When RCCU is used for the console>
RCCU is powered on.
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the RCCU and HUB connectors.
The load is not placed on the network of the system or RCCU.
<When XSCF is used for the console>
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the XSCF's XSCF-LAN port and HUB connectors.
The shell port of the XSCF telnet ports is not connected from other software products outside the cluster system.
You can check by connecting to the XSCF shell via serial port (tty-a). For information on how to connect and check the connection, see the "XSCF (eXtended SystemControl Facility) User's Guide."
The load is not placed on the network of the system or XSCF.
Operations such as firm reboot or firm up is not performed, or an event such as failover has not occurred on XSCF.
<When ILOM is used for the console>
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the network management (NET MGT) port and HUB connectors.
The load is not placed on the network of the system or ILOM.
Operations such as firm reboot or firm up is not performed on ILOM.
If any one of the above turns out to be the cause of the problem, take the corrective action. Then, execute the following commands on the node where the error message appeared to restart the Shutdown Facility (SF) and the console monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrccumonctl stop# /etc/opt/FJSVcluster/bin/clrccumonctl start# /opt/SMAW/bin/sdtool -bIf the problem has not yet been resolved, users should consider failures of network and hardware such as RCCU, XSCF, ILOM, or HUB. Contact field engineers. Also, collect and submit troubleshooting information and the message to field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Connection to the console cannot be established during the console monitoring agent startup.
Corrective action:
Check the following:
<When RCCU is used for the console>
The IP address or host name of RCCU is correct.
Use the clrccusetup(1M) command to check. If the IP address or host name is incorrect, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to configure the console monitoring agent again.
RCCU is powered on.
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the RCCU and HUB connectors.
The IP address of RCCU belongs to the same segment as the Administrative LAN.
The console information of RCCU is correct.
Use the clrccusetup(1M) command to check. If it is incorrect, register console information again using the clrccusetup(1M) command.
<When XSCF is used for the console>
The IP address or host name of XSCF is correct.
Use the clrccusetup(1M) command to check. If the IP address or host name is incorrect, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to configure the console monitoring agent again.
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable connectors are connected to the XSCF's XSCF-LAN port and HUB.
The shell port of the XSCF telnet ports is not connected from other software products outside the cluster system.
You can check by connecting to the XSCF shell via serial port (tty-a). For information on how to connect and check the connection, see the "XSCF (eXtended SystemControl Facility) User's Guide."
The IP address of XSCF belongs to the same segment as the Administrative LAN.
The console information of XSCF is correct.
Use the clrccusetup(1M) command to check. If it is incorrect, register console information again using the clrccusetup(1M) command.
If SSH is used to connect to XSCF, the login user account for the Shutdown Facility is used to connect to XSCF from the cluster node via SSH connection, and also the user inquiry of the SSH connection first time such as RSA Key Generation is complete.
Operations such as firm reboot or firm up is not performed, or an event such as failover has not occurred on XSCF.
<When ILOM is used for the console>
The IP address or host name of ILOM is correct.
Use the clrccusetup(1M) command to check. If the IP address or host name is incorrect, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to configure the console monitoring agent again.
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the network management (NET MGT) port and HUB connectors.
The console information of ILOM is correct.
Use the clrccusetup(1M) command to check. If it is incorrect, register console information again using the clrccusetup(1M) command.
For ILOM 3.0, the required privilege is not given to the login user account for the Shutdown Facility. For details on the privilege, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
The login user account for the Shutdown Facility is used to connect to ILOM from the cluster node via SSH connection, and also the user inquiry of the SSH connection first time such as RSA Key Generation is complete.
Operations such as firm reboot or firm up is not performed, or an event such as failover has not occurred on ILOM.
If any one of the above turns out to be the cause of the problem, take the corrective action. Then, execute the following commands on the node where the error message appeared to restart the Shutdown Facility (SF) and the
console monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrccumonctl stop# /etc/opt/FJSVcluster/bin/clrccumonctl start# /opt/SMAW/bin/sdtool -bIf the problem has not yet been resolved, users should consider failures of network and hardware such as RCCU, XSCF, ILOM, or HUB.
If the conditions are satisfied, 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:
SSH pre-connection to the ILOM has not been completed.
Corrective action:
Connect to ILOM from the cluster node via SSH by using the login user account for the shutdown facility, and complete the user inquiry of the SSH connection first time (such as RSA Key Generation).
Afterwards, execute the following commands to restart the Shutdown Facility (SF) and the console monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clrccumonctl stop# /etc/opt/FJSVcluster/bin/clrccumonctl start# /opt/SMAW/bin/sdtool -bIf this corrective action does not work, 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:
As a result of hardware diagnosis of the LAN device, it is determined as a failure.
To the altname, the interface name of the LAN device which was determined as faulty is output. nodename, rid, and code indicate the information required for investigation.
Corrective action:
Take corrective action by referring to "Corrective Action when Patrol Diagnosis Detects a Fault" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
As a result of hardware diagnosis of the LAN device, it is determined that the network device diagnosis command terminated abnormally.
An interface name of the LAN device for which a failure is diagnosed is output with altname. nodename, rid, and code indicate investigation information.
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:
As a result of hardware diagnosis of the shared device, it is determined as a failure.
A device name for which a failure is diagnosed is output with altname. nodename, rid, and code indicate investigation information.
Corrective action:
Take corrective action by referring to "Corrective Action when Patrol Diagnosis Detects a Fault" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
As a result of hardware diagnosis of the shared device, it is determined that the disk monitoring command terminated abnormally.
A shared device name for which a failure is diagnosed is output with altname. nodename, rid, and code indicate investigation information.
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:
As a result of hardware diagnosis of the shared device, the designated device could not be opened.
The device name that could not found can be output with altname. nodename, rid, and code indicate investigation information.
Corrective action:
Specify the available hardware in which patrol diagnosis is enabled. See "Setting Up Patrol Diagnosis" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
As a result of hardware diagnosis of the LAN device, the designated LAN device could not be found.
The interface name of the LAN device that could not be found can be output with altname. nodename, rid, and code indicate investigation information.
Corrective action:
Specify the available hardware in which patrol diagnosis is enabled. See "Setting Up Patrol Diagnosis" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
As a result of hardware diagnosis on the LAN device, the flag settings of the activated LAN device was found improper.
The network device name, which is in the inadequate state, can be output with altname. nodename, rid, and code indicates investigation information.
Corrective action:
The flag used when the LAN device is activated is in the inadequate state such as not UP and not BROADCAST. After confirming the system configuration, activate the device correctly. Confirm the flag by executing the "ifconfig(1M)" command.
UP must be set.
BROADCAST must be set.
LOOPBACK must not be set.
POINTOPOINT must not be set.
NOARP must not be set.
Content:
SCF cannot be accessed because it is in the busy state. type indicates information for research.
Corrective action:
Leave the operation undone for several minutes, and then re-execute accessing.
Content:
SCF open failed. errno indicates an error number.
Corrective action:
Contact field engineers to check whether the SCF is operating normally.
Content:
SCF access failed. errno indicates an error number.
Corrective action:
Contact field engineers to check whether the SCF is operating normally.
Content:
A line switching unit whose subclass cannot be identified is connected.
addr: Indicates the RCI address of the line switching unit.
no: Indicates the subclass of the line switching unit.
0x01: Indicates a 4-line switching unit.
0x02: Indicates a 16-line switching unit.
Corrective action:
Confirm if the line switching unit is a supported product.
Content:
No line switching unit that is specified with the RCI address exists. addr indicates an RCI address.
Corrective action:
Confirm with field engineers whether the RCI address of the specified line switching unit is correct or it is connected.
Content:
The power to the line switching unit is not on, or the RCI cable has been disconnected. addr indicates the RCI address of the line switching unit.
Corrective action:
Confirm if the power of the specified line switching unit is turned on and that the RCI cable is not disconnected.
Content:
Although no times of attempts were made to reserve the switching unit, which was specified with mask of the line switching unit that was specified with RCI address (addr), reservation failed.
addr indicates the RCI address of the line switching unit, while mask indicates a mask that represents a switching unit of the line switching unit and no indicates the retry count until an error is displayed.
Corrective action:
Check whether the line switching unit has failed, whether the RCI connection has an error, and whether the power-supply voltage is abnormal. If errors occur frequently, contact field engineers.
Content:
An error was detected in the switching control board of the line switching unit.
addr: Indicates the RCI address of the line switching unit in which an error was detected.
status: Indicates the internal status of the line switching unit by error type.
type: Indicates the error type.
1: 1: Error in the switching control system (status: status 0)
status: Indicates the value of status 0 (see below) of the line switching unit.
0x80: QANS (0: normal, 1: abnormal)
Indicates that the switching line of QSC remains in the asserted state (abnormal) although other than switchover processing is being performed.
0x40: QAST (0: normal, 1: abnormal)
Indicates that the switching line of QSC cannot be asserted during switchover processing. Once an abnormal state arises, that state remains until the power supply is turned off.
2: Power/circuit error (status: status 0)
status: Indicates the value of status 0 (see below) of the line switching unit.
0x10: QENA (0: normal, 1: abnormal)
Indicates the QSC switchover function enabled state. If this Bit is ON, it indicates that every connected QSC is abnormal.
0x08: DCNV (0: normal, 1: abnormal)
Indicates that the output voltage of the DC-DC converter, which is mounted in the QSC, is normal. If this Bit is ON, it indicates that the output voltage of the DC-DC converter is abnormal.
Remark: This bit is enabled only for a 4-line switching unit.
0x04: PW12
0 is indicated for a single power unit while 1 indicates two power units.
Remark: This bit is enabled only for a 16-line switching unit.
0x02: PRY1 (0: normal, 1: abnormal)
0x01: PRY0 (0: normal, 1: abnormal)
Indicates whether the power supply is normal/abnormal. (Normal means that power is supplied without any failure.)
Remark: This Bit is enabled only for a 16-line switching unit.
3: QSC connection error (status: status 1)
status: Indicates the value of status 1 (see below) of the line switching unit.
0x80: HSC (0: 4-line switching unit, 1: 16-line switching unit)
Indicates if a 16-line switching unit is used.
0x20: QSC1 (slot 1 mounted)
0x10: QSC0 (slot 0 mounted)
Indicates the slot in which the QSC (switching control board) is mounted. Values other than 0x10 and 0x20 indicate errors.
0x02: OBSY
Indicates that the other side of the duplicated QSC is presently executing switchover processing (canceling of reserve, switchover command 0, and switchover command 1).
Corrective action:
Check whether the line switching unit has a failure, if the RCI connection has an error, or whether the power-supply voltage is abnormal. If these errors occur frequently, contact field engineers.
Content:
An error was detected in the switching unit of the line switching unit.
addr: Indicates an RCI address of the line switching unit in to be controlled.
mask: Indicates an LSU mask which is the target of control.
status: Indicates the internal status of the line switching unit by error type (for research).
type: Indicates an error type.
1: Indicates an erroneous state.
status: Indicates the abnormal state of each LSU, which is included in the switching unit, as the value of LSU mask.
0: Indicates that the relevant LSU is normal.
1: Indicates that the relevant LSU is abnormal.
2: Indicates that a request of canceling switchover/reserve has been sent to the unconnected LSU.
status: Indicates whether each LSU that is included in the switching unit is connected using the value of the LSU mask.
0: Indicates that the LSU is unconnected.
1: Indicates that the LSU is connected.
LSU mask value
LSU15 LSU14 LSU13 LSU12 *** LSU03 LSU02 LSU01 LSU00
0x8000 0x4000 0x2000 0x1000 *** 0x0008 0x0004 0x0002 0x0001
Corrective action:
Check whether the line switching unit has a failure, if the RCI connection has an error, or if the power-supply voltage is abnormal. If these errors occur frequently, contact field engineers.
Maintenance information (for system administrators)
Check whether the specified line switching unit has an error.
Content:
The cluster event control facility is not running. code1 and code2 indicate information items for diagnosis.
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."
After that, reboot the node in which the error occurred. If you need to stop the node, execute the "shutdown(1M)" command.
Content:
Communication failed in the cluster event control facility. code1 and code2 indicate the information required for troubleshooting.
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."
After that, reboot the node in which the error occurred. If you need to stop the node, execute the "shutdown(1M)" command.
Content:
An internal error occurred in the cluster event control facility. code1 and code2 indicate the information required for troubleshooting.
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."
After that, reboot the node in which the error occurred. If you need to stop the node, execute the "shutdown(1M)" command.
Content:
The port number information is not set for resource SWLine.
rid indicates the resource ID of SWLine in the line switching unit.
Corrective action:
Set the port number attribute (port) of the line switching unit used for the resource SWLine.
Content:
The port number specified for resource SWLine is incorrect.
rid indicates the resource ID of the SWLine in the line switching unit while port indicates a port number.
Corrective action:
Set up the correct port number.
Content:
The LSU mask information has not been set for the shared resource SH_SWLine.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
Set up the mask (Isu_mask) attribute of the switching unit used for the shared resource SH_SWLine.
Content:
The parent resource of the shared resource SH_SWLine is a resource other than the shared resource SH_SWU.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
Re-create the shared resource SH_SWLine as a child resource of shared resource SH_SWU.
Content:
The RCI address information has not been set for the shared resource SH_SWU.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
Set up the RCI address attribute (addr) of the line switching unit used for the shared resource SH_SWU.
Content:
For the resource ID of the node that is connected to the specified port of the line switching unit, an incorrect resource ID of other than a node or nonexistent resource ID is specified.
no indicates a port number in the line switching unit while rid indicates the resource ID.
Corrective action:
Set up the correct resource ID of the node.
Content:
The same resource ID cannot be specified for port 0 and port 1 in the line switching unit.
rid indicates the resource ID of the specified node.
Corrective action:
Set up the correct resource ID of the node.
Content:
The specified resource ID is not present in the shared resource class.
rid indicates a resource ID while class indicates the class name of the shared resource class.
Corrective action:
Set up the correct resource ID.
Content:
The specified resource name is not present in the shared resource class.
name indicates a resource name while class indicates the class name of the shared resource class.
Corrective action:
Set up the correct resource ID.
Content:
The configuration file of the console monitoring agent filename does not exist.
Corrective action:
Download the configuration file displayed in miscellaneous information using ftp from other nodes and store this file in the original directory. Then, set up the same access permission mode of this file as other nodes. After that, restart the system. If all the nodes constituting a cluster do not have this configuration file, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Collecting troubleshooting information" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
Content:
The configuration file of the RCI monitoring agent filename does not exist.
Corrective action:
Download the configuration file displayed in miscellaneous information using ftp from other nodes and store this file in the original directory. Then, set up the same access permission mode of this file as other nodes. After that, restart the system. If all the nodes constituting a cluster do not have this configuration file, 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:
There is an incorrect format of the configuration file in the console monitoring agent.
Corrective action:
If the configuration file name displayed in miscellaneous information is SA_rccu.cfg, reconfigure the Shutdown Facility by invoking the configuration wizard. Then, confirm if the RCCU name is correct. If the above corrective action does not work, or the configuration file name is other than SA_rccu.cfg, 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:
You are not allowed to log in to the control port of the console (such as RCCU, XSCF, or ILOM).
Corrective action:
The username or password that is registered in a cluster system is different than the one that is configured for the console. Configure the console monitoring agent and Shutdown Facility again.
If the above corrective action does not work, 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:
The console's IP address is unknown.
Corrective action:
You need to check if a node name of RCCU, XSCF, or ILOM is correct using the clrccusetup command.
If the node name is correct, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to reconfigure the SF Wizard.
If this corrective action does not work, 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:
A communication error occurred due to an error in the MMB of the node on which the message was displayed.
Corrective action:
An error may occur in PSA (PRIMEQUEST Server Agent)/SVmco (ServerView Mission Critical Option) or a hardware failure may occur, or the system may be under high load. Check if the following settings are correctly set:
Check if PSA or SVmco is installed or set.
Check if a node is restarted after installing SVmco manually.
Check if PSA or SVmco is correctly set.
Make sure an incorrect IP address (such as an IP address of MMB) is not specified to the IP address of the administrative LAN.
Check if the firewall for operation of PSA or SVmco is correctly set.
Check if MMB is correctly set.
Check if the correct IP address is set.
Check if both the virtual IP address and the physical IP address are set.
Check if MMB does not have a failure.
Check if a node is not under high load.
If this corrective action does not work, 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."
After field engineers carry out the hardware recovery operation, the MMB monitoring agent/iRMC asynchronous monitoring agent recovers automatically.
Content:
The MMB monitoring agent function has already been started.
Corrective action:
If there is no need to restart the MMB monitoring agent function, no action is necessary. If the MMB monitoring agent function must be restarted, execute the following commands on the node on which the message was output and restart the MMB monitoring agent function (MA) and the shutdown facility (SF).
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clmmbmonctl stop# /etc/opt/FJSVcluster/bin/clmmbmonctl start# /opt/SMAW/bin/sdtool -bIf this corrective action does not work, 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:
MMB information for the specified CF node name has not been registered.
Corrective action:
Check the following points:
Since the clmmbsetup command is for the PRIMEQUEST 2000/1000/500/400 environment, use the correct command suitable for your environment.
Execute the clmmbsetup -l command, and check the currently registered MMB information. Then, if necessary, use the shutdown configuration wizard or the clmmbsetup command to register the MMB information.
For details about the shutdown configuration wizard, see "Setting up the Shutdown Facility" in "PRIMECLUSTER Installation and Administration Guide (Linux)." For details about the clmmbsetup(8) command, see the manual page of the "clmmbsetup(8)" command.
If this corrective action does not work, 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 error was detected in the transmission route to the MMB.
Corrective action:
Check the following points:
Whether the normal lamp of the port to which the HUB and the LAN cable are connected is on.
Whether the MMB port connector or the LAN cable from the HUB-side connector is disconnected.
Whether an incorrect IP address was specified for the MMB IP address.
Whether an incorrect IP address was specified for the management LAN IP address that uses shutdown configuration.
If one of the above items is found to be the cause, MMB monitoring agent recovers automatically after the corrective action is taken.
Automatic recovery takes up to 10 minutes.
If the connection fails even after the above items are checked, contact field engineers because there may be a network failure or a hardware failure, such as in the MMB of the HUB. If this corrective action does not work, 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."
After field engineers carry out the hardware recovery operation, the MMB monitoring agent function recovers automatically.
Content:
You cannot log in to the MMB.
Either the user name or the password for logging in to the MMB is different from the value that was set to the MMB, or the MMB may not have been set.
Corrective action:
Specify the settings for MMB monitoring agent/iRMC asynchronous monitoring agent and the shutdown facility again. For details, see "Setting up the Shutdown Facility" in "PRIMECLUSTER Installation and Administration Guide." For instructions on setting the MMB, see "PRIMEQUEST 2000 series" or "PRIMEQUEST 3000 series" of "Setting Up the Cluster High-Speed Failover Function" in "PRIMECLUSTER Installation and Administration Guide." If this corrective action does not work, 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:
The MMB IP address of the node on which this message was output or the IP address in the management LAN of the shutdown configuration was changed.
Corrective action:
Immediately after this message is output, if the Test State of the shutdown facility (SF) is Test Failed, check the following point:
Whether the change in the MMB IP address or the IP address in the management of the shutdown configuration is correct.
If the above item is found to be the cause, take corrective action. Then, execute the following commands on all the nodes, and restart the MMB monitoring agent function (MA) and the shutdown facility (SF). In addition, if you changed the MMB IP address, first, execute the following commands only on the changed nodes. Then, execute them on the rest of the nodes.
# /opt/SMAW/bin/sdtool -e# /etc/opt/FJSVcluster/bin/clmmbmonctl stop# /etc/opt/FJSVcluster/bin/clmmbmonctl start# /opt/SMAW/bin/sdtool -bIf this corrective action does not work, 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:
This command cannot be operated in the environment.
Corrective action:
Check the environment where the command is being executed and use the correct command.
Content:
This message indicates the host OS information, which the specified CF nodename belongs to, is not registered.
Corrective action:
Execute the clvmgsetup -l command to check the information on the currently registered Host OS. If necessary, register the Host OS information using the clvmgsetup command.
If this corrective action does not work, 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:
This message indicates that the guest domain name cannot be obtained.
Corrective action:
Make sure that the node running the clvmgsetup command is a guest domain.
If so, see "When Using the Virtual Machine Function" in "PRIMECLUSTER Installation and Administration Guide (Linux)" to set the guest domain.
Content:
The specified guest domain name does not exist.
Corrective action:
The specified guest domain name does not exist. Confirm the following points, and retry.
Is the specified guest domain name correct?
Confirm whether the specified guest domain name is wrong. If the guest domain name is wrong, specify the correct one.
Is the specified guest domain running?
Check whether the guest domain is running. If it is not, start it.
Has the configuration information of the logical domains been saved?
Check whether the configuration information of the logical domains has been saved with the ldm add-spconfig command in the control domain.
If not, use the ldm add-spconfig command to save the information.
Can the states of the logical domains be checked in XSCF?
Check the states of the logical domains in XSCF.
If it cannot be checked in XSCF, use the ldm add-spconfig command in the control domain to save the information.
Has the operation been performed for the cluster after Migration?
Use clsnmpsetup(1M) to check the set IP address of XSCF.
Then, check the states of the logical domains in XSCF.
If the IP address of XSCF is invalid, or the states of the logical domains cannot be checked, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to perform the operation after Migration.
Has the guest domain, which was stopped by Cold Migration, been started?
Check whether the guest domain, which was stopped by Cold Migration, has been started.
If the guest domain is still being stopped, see "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to perform the operation after Cold Migration.
If this corrective action does not work, 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:
The username or password to login to the host OS registered to a cluster system is different from ones set to the host OS.
Corrective action:
Register the host OS information by using the clvmgsetup command.
See "Changing Virtual Machine Settings" in "PRIMECLUSTER Installation and Administration Guide (Linux)."
If this corrective action does not work, 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:
Connection to the host OS is refused.
Corrective action:
Check the following points:
Is the IP address specified for the Host OS set correctly?
Is the IP address allocated to the guest OS correct?
Is a passphrase set for connection to the Host OS?
If any of the above points turns out to be the cause of the error, take the appropriate corrective action and execute the following commands on the node on which the prompt was output to restart the shutdown facility (SF):
# /opt/SMAW/bin/sdtool -e# /opt/SMAW/bin/sdtool -bIf the connection can still not be established after checking above items, the possible cause may be a hardware damage (e.g. network or hub failure).In that case, please contact field engineers.
If this corrective action does not work, 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:
SSH pre-connection to the host OS has not been completed.
Corrective action:
Connect to the host OS from the guest OS via SSH by using the account created to forcibly stop the guest OS (FJSVvmSP), and complete the user inquiry of the SSH connection first time (such as RSA Key Generation).
Content:
Connection to the host OS was disconnected.
Corrective action:
Check the state of other nodes and path of a private LAN.
Content:
The clvmgsetup command has been executed.
Corrective action:
The clvmgsetup command has already been executed. Execute it again after the command under execution has ended.
Content:
Connection to XSCF from SNMP monitoring agent.
Corrective action:
Check the following points:
Whether this message is output when the OS is shut down.
No corrective action is required. If this message is output when the OS is shut down, there is no problem with the operation.
Whether the IP address of XSCF or the node name is correct.
Check the IP address set by using the clsnmpsetup(1M) or the node name.
If either the IP address or the node name is incorrect, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to set the SF wizard again.
If the error message is displayed during OVM cold migration, refer to "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)" to reset OVM cold migration.
Whether the normal lamps of the port to which the HUB and the LAN cable are connected are on.
Whether the XSCF-LAN port connector of XSCF from HUB-side connector is disconnected.
Whether the shell port of the XSCF port is not connected from other software products outside the cluster system.
Check the connection to the XSCF shell via serial port (tty-a).
For information on how to connect and check the connection, see "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide."
Whether the IP address of XSCF belongs to the same segment as the Administrative LAN.
If SSH is used to connect to XSCF, the login user account for the Shutdown Facility is used to connect to XSCF from the cluster node via SSH connection, and also the user inquiry of the SSH connection first time such as RSA Key Generation is complete.
Operations such as firm reboot or firm up is not performed, or an event such as failover has not occurred on XSCF.
If any of the above items turn out to be the cause of the problem, execute the corrective action. Then, execute the following commands on the node where the error message was displayed.
If the error message is displayed during OVM cold migration, restart the OS of the node where the error message was displayed.
Otherwise, execute the following commands on the node where the error message appeared to restart the Shutdown Facility (SF) and the SNMP monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e # /etc/opt/FJSVcluster/bin/clsnmpmonctl stop # /etc/opt/FJSVcluster/bin/clsnmpmonctl start # /opt/SMAW/bin/sdtool -b
If the problem has not yet been resolved despite performing the above operations, users should consider failures of network and hardware such as XSCF or HUB. Contact field engineers.
If this corrective action does not work, 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:
You cannot log in to XSCF.
Either the user name or password for logging in to XSCF is different from the value that was set to XSCF.
Corrective action:
Specify the settings for SNMP monitoring agent and the shutdown facility again.
For instructions on setting XSCF, see "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide."
If this corrective action does not work, 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."
Corrective action:
Enable the SNMP agent of XSCF.
For instructions on setting XSCF, see "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide."
If this corrective action does not work, 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."
Corrective action:
This action is only required when restarting the SNMP monitoring agent.
In the case, execute the following commands on a node where this message was output, and then restart the SNMP monitoring agent and the shutdown facility
# /opt/SMAW/bin/sdtool -e
# /etc/opt/FJSVcluster/bin/clsnmpmonctl stop
# /etc/opt/FJSVcluster/bin/clsnmpmonctl start
# /opt/SMAW/bin/sdtool -b
If this corrective action does not work, 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:
The specified PPAR-ID is inexistence or incorrect.
Corrective action:
Check the following points and specify the correct PPAR-ID again.
Make sure the specified PPAR-ID is correct.
Check if the specified PPAR-ID is correct. If not, specify the correct PPAR-ID again.
Specify "0" to PPAR-ID.
Make sure the specified PPAR-ID has been defined.
Check the state of PPAR-ID by executing the following command in XSCF.
XSCF> showpparstatus -a
The PPAR-ID which "-" is displayed in [PPAR status] cannot be specified because it is not defined. Only the PPAR-ID which "Running" is displayed in [PPAR Status] can be specified.
If this corrective action does not work, 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."
Corrective action:
Connect to XSCF from the cluster node via SSH by using the login user account for the shutdown facility, and complete the user inquiry of the SSH connection first time (such as RSA Key Generation).
Afterwards, execute the following commands on the node where the message is displayed:
If the error message is displayed during OVM cold migration, restart the OS of the node where the error message was displayed.
Otherwise, execute the following commands to restart the Shutdown Facility (SF) and the SNMP monitoring agent (MA):
# /opt/SMAW/bin/sdtool -e # /etc/opt/FJSVcluster/bin/clsnmpmonctl stop # /etc/opt/FJSVcluster/bin/clsnmpmonctl start # /opt/SMAW/bin/sdtool -b
If this corrective action does not work, 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 cluster resource management.
function, code1, and code2 indicates information required for error investigation.
Corrective action:
This failure might be attributed to the following:
The memory resources are insufficient.
The disk resources are insufficient.
Record this message and collect information for an investigation. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Confirm that the kernel parameter settings are correct by referring to "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
Check that there is sufficient disk space required for PRIMECLUSTER operation. If necessary, delete any unnecessary files to create sufficient free space, and then restart the system. For information on the amount of required disk space, see the Installation Guide for PRIMECLUSTER, which is provided with each product.
If you still have this problem after going through the above instructions, contact field engineers.
Content:
The memory resources are insufficient in the cluster resource management facility.
function, code1 indicates information required for error investigation.
Corrective action:
Record this message and collect information for an investigation. Then, review the estimate of the disk resource. For the memory required for resource database, see the Installation Guide for PRIMECLUSTER, which is provided with each product. If this error cannot be corrected by this operator response, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The disk resources or system resources are insufficient in the cluster resource management facility.
function, code1 indicates information required for error investigation
Corrective action:
Record this message and collect information for an investigation. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Review the estimate of the disk resource and system resource (kernel parameter). If the kernel parameters have been changed, reboot the node for which the kernel parameters have been changed. See "Setup (initial configuration)" of PRIMECLUSTER Designsheets for PRIMECLUSTER 4.4 or later, or the description of "Kernel Parameter Worksheet" of "PRIMECLUSTER Installation and Administration Guide" for PRIMECLUSTER 4.3 or earlier.
If this error cannot be corrected by this operator response, record this message, and contact field engineers.
Content:
The event cannot be notified because of an abnormal communication.
type, rid indicates event information and code1 indicates information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide." After this event is generated, restart all the nodes within a cluster domain.
Content:
The event notification is because of an abnormal communication.
type, rid indicates event information and code1 indicates information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide." After this event is generated, restart all the nodes within a cluster domain.
Content:
The node is stopped because event cannot be notified by abnormal communication.
node indicates the node identifier of the node to be stopped, type, rid the event information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The node is forcibly stopped because event cannot be notified by abnormal communication.
node indicates the node identifier of the node to be stopped, type, rid the event information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The resource activation processing cannot be executed because of an abnormal communication.
resource indicates the resource name for which activation processing was disabled, rid the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource) belongs.
Content:
The resource activation processing is stopped because of an abnormal communication.
resource2 indicates the resource name for which activation processing was not performed, rid2 the resource ID, resource1 the resource name for which activation processing is not performed, rid1 the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource2) belongs.
Content:
The resource deactivation processing cannot be executed because of an abnormal communication.
resource indicates the resource name for which deactivation processing was not performed, rid the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource) belongs.
Content:
The resource deactivation processing is aborted because of an abnormal communication.
resource2 indicates the resource name for which deactivation processing was not performed, rid2 the resource ID, resource1 the resource name for which deactivation processing is not performed, rid1 the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource2) belongs.
Content:
An error occurred by the event processing of the resource controller.
type, rid indicates the event information, pclass, prid indicates resource controller information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node in which the message was displayed.
Content:
The event notification is stopped because an error occurred in the resource controller.
type, rid indicates the event information, pclass, prid indicates resource controller information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node in which the message was displayed.
Content:
The node is stopped because an error in the resource controller.
node indicates the node identifier of the node to be stopped, type, rid the event information, pclass, prid the resource controller information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The node is forcibly stopped because an error occurred in the resource controller.
node indicates the node identifier of the node to be forcibly stopped, type, rid the event information, pclass, prid the resource controller information, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An error occurred by the resource activation processing.
resource indicates the resource name in which an error occurred in the activation processing, rid the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource) belongs. An error occurs in the resource activation processing and activation of the resource (resource) cannot be performed.
Content:
An error occurred by the resource deactivation processing.
resource indicates the resource name in which an error occurred in the activation processing, rid the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource) belongs. An error occurs in the resource deactivation processing and deactivation of the resource (resource) cannot be performed.
Content:
The resource activation processing is stopped because an error occurred by the resource activation processing.
Resource2 indicates the resource name in which an error occurred in the activation processing, rid2 the resource ID, resource1 the resource name in which activation processing is not performed, rid1 the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource2) belongs.
Content:
The resource deactivation processing is aborted because an error occurred by the resource deactivation processing.
resource2 indicates the resource name in which deactivation processing was disabled, rid2 the resource ID, resource1 the resource name in which deactivation processing is not performed, rid1 the resource ID, and code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
After this phenomenon occurs, restart the node to which the resource (resource2) belongs.
Content:
An error occurred in exit processing for the cluster resource management facility.
node indicates the node in which an error occurred and function, code1 the information for investigation.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The specified resource does not exist or be not able to set the dependence relation.
rid indicates a resource ID of the specified resource.
Corrective action:
Specify the correct resource, then re-execute the processing.
Content:
The specified resource does not exist or be not able to set the dependence relation.
name indicates the specified resource name and rclass the class name.
Corrective action:
Specify the correct resource, then re-execute the processing.
Content:
The resource belonging to other node is specified.
Corrective action:
Specify a resource that belongs to the same node and re-execute it.
Content:
As the resource controller is not available in the resource processing, resource (resource) activation was not performed.
resource indicates the resource name for which activation processing was disabled, and rid a resource ID.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
As the resource controller is not available in the resource deactivation processing, resource deactivation was not performed.
resource indicates the resource name for which deactivation processing could not be performed, and rid the resource ID.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Corrective action:
After activation processing of the resource completes, re-execute it. Resource activation processing completion can be confirmed with 3204 message that is displayed on the console of the node to which the resource belongs.
Corrective action:
After deactivation processing of the resource completes, re-execute it. Resource deactivation processing completion can be confirmed with 3206 message that is displayed on the console of the node to which the resource belongs.
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Corrective action:
Record this message and collect information for an investigation. After that, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
As the node node to which the resource to be activated belongs is stopped, the resource activation processing cannot be performed.
Corrective action:
After starting up the node to which resource to be activated belongs, re-execute it again.
node indicates the node identifier of the node where the connection is broken.
Content:
As the node node to which the resource to be deactivated belongs is stopped, the resource deactivation processing cannot be performed.
node indicates the node identifier of the node where the connection is broken.
Corrective action:
After starting up the node to which resource to be deactivated belongs, re-execute it again.
Corrective action:
Refer to the measures in the error message displayed between activation processing start message (3203) and completion message (3204), which are displayed when this command is executed.
Corrective action:
Refer to the measures in the error message displayed between deactivation processing start message (3205) and completion message (3206), which are displayed when this command is executed.
Content:
Failed to set iRMC/MMB in order to perform iRMC asynchronous monitoring agent.
Outputs whether iRMC/MMB setting has failed to detail.
iRMC or MMB of the node where the message was displayed has a failure is possible.
Corrective action:
An error may occur in the hardware failure or the system may be under high load. Check if the following settings are correctly set:
iRMC/MMB does not have a failure.
A node is not under high load.
If this corrective action does not work, 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."
After field engineers carry out the hardware recovery operation, the iRMC asynchronous monitoring agent recovers automatically.
Content:
This message indicates that login is not allowed to iRMC.
Correct action:
The user name or password for logging into the iRMC registered in the cluster system is stored in iRMC is different from the set one. Configure iRMC asynchronous monitoring agent again.
If this corrective action does not work, 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:
This message indicates that iRMC operation cannot be performed because the authority of the user login to iRMC is incorrect.
Corrective action:
The user authority registered to iRMC is incorrect.
Change the user authority using iRMC.
If this corrective action does not work, 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:
This message indicates that an error was detected in the transmission route of iRMC.
Corrective action:
Check the following:
The normal lamp of the port connected to HUB and LAN cable is ON.
The LAN cable is connected to the iRMC port and HUB connectors.
Whether an incorrect IP address was specified for the iRMC IP address.
Whether an incorrect IP address was specified for the management LAN IP address that uses shutdown configuration.
If one of the above items is found to be the cause, iRMC asynchronous monitoring agent recovers automatically after the corrective action is taken. Automatic recovery takes up to 10 minutes.
If the connection fails even after the above items are checked, contact field engineers because there may be a network failure or a hardware failure, such as in the MMB of the HUB. If this corrective action does not work, 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."
After field engineers carry out the hardware recovery operation, the iRMC asynchronous monitoring agent function recovers automatically.
Content:
A communication error occurred due to an error in the iRMC of the node on which the message was displayed.
Corrective action:
An error may occur in the hardware failure, the system may be under high load, or a temporary error due to the setting change of hardware. Check if the following settings are correctly set:
iRMC does not have a failure.
MMB does not have a failure (except B model).
A node is not under high load.
In the cluster node environment, VGA/USB/rKVMS of Home SB is assigned to any one of the extended partitions of PRIMEQUEST 3000 series (except B model).
In the cluster node environment, assignment of VGA/USB/rKVMS of SB is changed between extended partitions of PRIMEQUEST 3000 series (except B model). (Automatically recovered from an error after the assignment change is completed.)
Eliminate the cause of the error then wait for 10 minutes, or restart the shutdown facility to check whether TestFailed state is resolved.
If this corrective action does not work, 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."
After field engineers carry out the hardware recovery operation, the iRMC asynchronous monitoring agent recovers automatically.
Content:
snmptrapd is not running on the node where the message was displayed.
Corrective action:
snmptrapd must be started on the node where the message is displayed.
If "OS" is output to detail, the snmptrapd service of OS is not running. Start the snmptrapd service. iRMC asynchronous monitoring agent recovers automatically after the snmptrapd service is started.
If "PCL" is output to detail or even if snmptrapd service is started and this corrective action does not work, 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:
The format of IP address set in iRMC does not match the IP address set in the shutdown configuration, or VGA/USB/rKVMS of Home SB is not assigned to any one of the extended partitions of PRIMEQUEST3000 series (except B model) in the cluster node environment.
Corrective action:
Perform one of the following:
Change the IP address of management LAN in the shutdown configuration to the format of IP address set in iRMC.
Set the IP address format set in the management LAN of the shutdown configuration in iRMC.
Assign VGA/USB/rKVMS of Home SB to any one of the extended partitions (except B model).
Content:
The format of IP address set in MMB does not match the IP address set in the shutdown configuration.
Corrective action:
Perform one of the following:
Change the IP address of management LAN in the shutdown configuration to the format of IP address set in MMB.
Set the IP address format set in the management LAN of the shutdown configuration in MMB.
Content:
This message indicates that IPMI service is not running.
Corrective action:
Start IPMI service.
Also, if IPMI service is not set to start automatically, change the settings to start automatically.
Content:
This message indicates that MMB operation cannot be performed because the authority of the user login to MMB is incorrect.
Corrective action:
The user authority registered to MMB is incorrect.
Change the user authority using MMB.
If this corrective action does not work, 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:
In the cluster system configuration using the extended partitions of PRIMEQUEST3000 series (except B model), the number of the settable cluster nodes exceeds the limit (node).
Corrective action:
Reconfigure the system with the settable number (node) of cluster nodes.