HP Insight Cluster Management Utility manual Cloning issues, Administration command problems

A.4 Cloning issues

If only one node cannot be cloned:

1.Verify that you can boot in network mode.

2.Verify that the node has the same hardware as other nodes.

3.Verify that the node does not have a hardware problem.

4.Power off manually, then relaunch cloning.

If no nodes in a network entity can be cloned:

1.Clone all nodes except the first node in the network entity again.

2.Verify that you can boot in network mode.

If no node in the cluster can be cloned:

1.Verify that you can boot in network mode.

2.Verify that the image is not corrupted using the tar tvfz command on the archive located in the image directory /opt/cmu/image.

3.Repeat the backup to replace the existing image.

4.Verify that the partition is not full.

NOTE: Prior to backup, half the partition must be free. Otherwise, the cloning fails. A /boot partition is mandatory to avoid grub-install errors on some Red Hat releases.

5.Verify that an error is not in the reconf.sh file associated with the image.

A.5 Administration command problems

To fix problems associated with administration commands:

1.Verify that rsh, telnet, or ssh is configured on nodes.

2.Verify that the rsh or ssh root is enabled with the node password to all nodes of the cluster.

3.Verify that the HP Insight CMU database contains the correct IP address and hostname.

4.Verify that a fully functional X server is running on the workstation and accepts connections from the management node.

A.6 GUI problems

If the GUI cannot contact the remote HP Insight CMU service:

1.Verify that the HP Insight CMU service is running properly on the management node:

# /etc/init.d/cmu status

If not, restart the HP Insight CMU service:

# /etc/init.d/cmu restart

2.Verify that the HP Insight CMU GUI on the remote workstation is connected to the correct server.

3.Verify the GENERAL_RMI_HOST setting in the cmu_gui_local_settings file on the remote workstation.

4.If cmuserver is running properly on the management node, verify the firewall configuration on the management node and the GUI workstation. Verify that RMI and X Window connections are allowed between the two hosts.

If the GUI is running but the monitoring sensors are not updated:

1.Verify that the HP Insight CMU service is running properly on the management node:

# /etc/init.d/cmu status

If not, restart the HP Insight CMU service:

# /etc/init.d/cmu restart

2.Verify that the host file of the nodes is configured properly. Each node must have access to the IP address of all nodes in the cluster.

128 Troubleshooting