
Possible cause and recommendationSymptom
VM host was recently moved into or out of Maintenance mode
1. In the CloudSystem Console, select Integrated Tools from the main menu,
then open the Edit VMware vCenter Server screen and click Save.
2. Retry the activate action.
The cluster or compute node might be rebooting
1. Check the status on the Compute Nodes screen.
2. Wait for a reboot to complete. The status icon will be green.
3. Retry the activate action.
A dependency on the KVM compute node was not met
KVM compute node activation fails or
hangs and no error message is displayed
1. Log on to the KVM compute node and obtain a support dump. The detailed
activation log is in /var/log/isc/activation<hostname>.log
2. Scroll through the log and find the start of the roll back procedure. The
error details are displayed just above the start of the roll back procedure.
An activated compute node was selected for activation again
and is not responding
1. Log on to the KVM compute node.
2. Open /etc/yum.repos.d and set all repositories to enabled=0.
3. Switch to the CloudSystem Console and retry the activate action.
RHEL 6.4 compute node default kernel value must be increased
Configure KVM compute nodes with a be2net NIC driver so that the
rx_frag_size kernel parameter value is set to 8192. (The default is 2048.)
This setting avoids packet loss and network communication drop issues.
KVM compute node activation fails with
Neutron client authentication
failed: Connection to neutron
failed: timed out. Getting
disk size of
1. Check for the be2net NIC driver by entering the following command on
the KVM compute node command line:
# ethtool -i eth0
instance-00000001: [Errno 2]
No such file or directory in the
nova log file.
If the driver is loaded, you see driver: be2net.
2. If the be2net driver is loaded, check for the current rx_frag_size value
by entering:
# cat /sys/module/be2net/parameters/rx_frag_size
3. If the value is less than 8192, set the value to 8192 by adding the
following line in the file /etc/modprobe.d/be2net.conf on the
compute node. If the file does not exist, create it, then add the following
line.
options be2net rx_frag_size=8192
4. Reboot the compute node.
Troubleshooting compute nodes 175
Commentaires sur ces manuels