The messages that userApplication Configuration Wizard GUI displays are listed below:
Information Message
Corrective action:
To exit the userApplication Configuration Wizard GUI, select Yes. If you do not want to exit the GUI, select No.
Corrective action:
To interrupt the process being operated by the userApplication Configuration Wizard GUI, select Yes. To cancel the interruption, select No.
Corrective action:
To register the setup information to the system, select Yes. If you do not want to register the setup information to the system, select No.
Corrective action:
This message is automatically cleared when RMS Configuration generation is completed. Wait until this message is cleared.
Corrective action:
To delete only userApplication, select userApplication only. To delete all resources under userApplication as well, select All. To cancel the deletion, select Cancel. "userApplication name" represents the name of userApplication to be deleted.
Corrective action:
To delete the resource indicated by "resource name" in the message and the resources under that resource, select Yes. If you do not want to delete the resources, select No.
Corrective action:
As soon as the setup process is completed, restart all SysNode that contain userApplication for which node name takeover was set.
Corrective action:
The userApplication Configuration Wizard GUI collects RMS Configuration information.
The GUI cannot be closed until the process in the GUI ends.
Corrective action:
The userApplication Configuration Wizard GUI collects RMS Configuration information.
The GUI cannot be closed until the process in the GUI ends.
Corrective action:
The userApplication Configuration Wizard GUI collects RMS Configuration information.
The GUI cannot be closed until the process in the GUI ends.
Corrective action:
If you want the userApplication Configuration Wizard GUI to generate RMS Configuration information, select Yes. If you do not want the GUI to generate the information, select No.
Corrective action:
If you want the userApplication Configuration Wizard GUI to distribute RMS Configuration information, select Yes. If you do not want the GUI to distribute the information, select No.
Corrective action:
If you want the userApplication Configuration Wizard GUI to delete the scalable settings for the userApplication, select Yes. Otherwise, select No.
Warning Messages
Corrective action:
Check whether the userApplication Configuration Wizard GUI has already been started in another client or whether another client is using the "hvw" command. After the other operation is completed, start the GUI or command again.
Even if the Web browser or the cluster management server of Web-Based Admin View is restarted while the GUI is being displayed, this message may be displayed at the next startup. If this is the case, wait about five minutes, and then restart the Web browser and the GUI.
Corrective action:
Reasons for this occurring include the following:
Cause 1
A node for which initial setup has not yet been completed is included among the nodes to be monitored with Web-Based Admin View.
Cause 2
A node on which the cluster resource management facility is not running is included among the nodes to be monitored with Web-Based Admin View.
How to confirm cause 1
Confirm whether a node for which initial setup of the cluster resource management facility has not yet been completed is included among the nodes to be monitored with Web-Based Admin View.
Make the confirmation as follows:
Confirm the nodes to be monitored with Web-Based Admin View.
Execute the wvstat (1M) command to confirm the monitoring target nodes for each operation management server.
For details on wvstat(1M), see the relevant manual page.
Confirm the settings of the resource database.
Use the CRM main window of Cluster Admin or the clgettree(1) command to confirm whether all the nodes that were confirmed in 1) can be displayed.
For details on clgettree(1), see the relevant manual page.
If Web-Based Admin View uses a network other than a public LAN for operation management, the node names displayed in 1) and 2) will be different.
Corrective action for cause 1
If the initial setup of the cluster resource management facility has not yet been completed, use the userApplication Configuration Wizard GUI after performing initial setup, and then automatic configuration on the node on which initial setup of the cluster resource management facility has not been completed. For details on the initial setup of the cluster resource management facility, see "5.1.3 Initial Setup of the Cluster Resource Management Facility."
Once installation of the product package has been completed, use the userApplication Configuration Wizard GUI after node expansion, as explained in "9.1 Adding a Node."
For all other cases, change the settings of the operation management server of Web-Based Admin View to a host that is not the current operation management server.
For details on how to change the operation management server of Web-Based Admin View, see "4.2.3.1 Initial setup of the operation management server."
How to confirm cause 2
Confirm whether the node for which the cluster resource management facility is not operating is contained among the Web-Based Admin View monitoring target nodes.
Make the confirmation as follows:
Confirm the nodes to be monitored with Web-Based Admin View.
Execute the wvstat (1M) command to confirm the monitoring target nodes of each operation management server.
For details on wvstat(1M), see the relevant manual page.
Confirm the operation status of the cluster resource management facility.
Use the CRM main window of Cluster Admin or the clgettree(1) command to confirm which node is in other than the "NO" state.
For details on clgettree(1), see the relevant manual page.
Corrective action for cause 2
Boot the node on which the cluster resource management facility is not operating.
Corrective action:
RMS is running. You might fail to generate or distribute the configuration information that you were trying to create or modify. Stop RMS, and then re-execute the operation.
Corrective action:
A userApplication name, a resource name, a script name, or a script path includes an disabled character. Reenter the correct value.
Corrective action:
The system is about to delete all resources under userApplication.
To delete userApplication indicated by "userApplication name" in the message and all resources under userApplication, select Yes. If you do not want to execute deletion processing, select No.
Corrective action:
Enter the userApplication name, the resource name, or the script name.
Corrective action:
The number that was entered for TIMEOUT or net mask is a disabled value. Enter an appropriate value.
Corrective action:
Enter another takeover IP address.
Corrective action:
Change the attribute (that has the incorrect data), and continue the operation.
Corrective action:
Information on the takeover network is already specified in the /usr/opt/reliant/etc/hvipalias file. To use the values that were set, select Yes.
If you select No, the userApplication Configuration Wizard GUI re-creates the takeover network information in the previous file and in /etc/inet/hosts. In this case, the takeover network information can be deleted automatically from /usr/opt/reliant/etc/hvipalias and /etc/inet/hosts when the Ipaddress resource is deleted.
Corrective action:
Review if the displayed attribute is correct. If it is correct, select Yes.
Corrective action:
Enter the path of the reference file.
Corrective action:
Set the required items in the screen.
Corrective action:
You need to set two or more userApplication for one exclusion group.
Corrective action:
Change the userApplication name or resource name, and execute the setup process again.
Corrective action:
Enter another IP address or host name.
Corrective action:
Enter another reference file path.
Corrective action:
The file to be created already exists. If you select Yes, the existing file will be replaced. If you select No, the existing file will not be replaced.
Corrective action:
The IP address segment that is assigned to the network interface card (NIC) for the takeover network is different. To continue the setup with the assigned IP address segment, select Yes. To select the NIC again, select No.
Corrective action:
The file system that you tried to create is already being used. Set another device path and mount point.
Corrective action:
Candidate interfaces to be set to the resource could not be obtained. Check whether interfaces were previously registered to the cluster resource management facility, and then re-execute the operation.
Corrective action:
The specified file is not executable. Use another file, or add an execute permission to the file.
Error messages
Corrective action:
An error occurred in the userApplication Configuration Wizard GUI.
Collect Java console information, detailed error information, and maintenance information, and contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
An internal server contradiction or an event that caused a network disconnection between the Web browser and the cluster management server (restart, shutdown, emergency stop, LAN cable disconnection) may have occurred.
If a Web-Based Admin View message is displayed, take corrective action for that message.
If a Web-Based Admin View message is not displayed, respond to this message and restart the userApplication Configuration Wizard.
If the problem cannot be resolved by the action described above, collect Java console information, detailed error information, and maintenance information, and contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
A package having a different version from the package version required by the userApplication Configuration Wizard GUI is installed in the cluster node. See the information that was output to (detailed information), and reinstall the correct package of the cluster node.
Corrective action:
The file cannot be edited because it is not a Bourne, C, or Korn shell file. Specify another file.
Corrective action:
A candidate list of the information to be set to Resource could not be obtained. Check whether the cluster resource management facility is operating, whether automatic resource registration was executed, and whether Gds and Gls have been set up. If any of these setup operations has not been completed, correct them, and execute the process again.
Corrective action:
Execute the command again, and if you still have the same problem, collect Java console information, detailed error information, and maintenance information, and then contact field engineers.
The message that is output from the command may contain the "FJSVcluster" keyword and a message number. In this case, take corrective action described in "11.10 Resource Database messages" in the "CF Configuration and Administration Guide."
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
Execute the command again, and if you still have the same problem, collect Java console information, detailed error information, and maintenance information, and then contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
When the three-layer configuration of Web-Based Admin View is used, no cluster node, which can be accessed from the management server, can be found. The operating status of Web-Based Admin View can be confirmed by executing /etc/opt/FJSVwvbs/etc/bin/wvstat.
If the problem cannot be improved when the environment of Web-Based Admin View has no problem, collect Java console information, detailed error information, and maintenance information, and then contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
The RMS configuration information cannot be analyzed.
If userApplication or Resource is not created, change to other Configuration information.
If the problem cannot be improved, collect Java console information, detailed error information, and maintenance information, and then contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
Start the operation again from the beginning.
If the problem is not resolved by the above action, collect Java console information, detailed error information, and maintenance information, and then contact field engineers.
For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
Check the following:
Whether there are resources that are not related to any userApplication
Whether there is userApplication that does not have any resources
If one or both of the above conditions are found, delete any unnecessary userApplication and resources. If none of the above conditions is found, do the operation again from the beginning. If an error still occurs, collect Java console information, detailed error information, and maintenance information, and then contact field engineers. For maintenance information, see "Appendix C Troubleshooting."
Corrective action:
A list of candidate information to be set in Resource could not be acquired. Check if the cluster resource management facility is operating and whether the procedure resource has already been set up. If it has not yet been set up, first set up the procedure resource, and then re-execute the processing.
