If all the requirements listed in OVA
deployment problems are met and IBM® Netezza® Platform Development
Software still
fails to start, there might be some other causes for the failure.
- There is not enough
resources in vSphere HA to run new VMs. A set of parameters in vSphere
HA determines how many nodes, CPU and memory must be available, otherwise
vSphere does not allow any new VM to start. You can disable the feature
by turning off the admission control in vSphere HA properties in vSphere
Client.
- vSphere checks the amount of memory for a VM that
is to start, and compares it with memory available on ESXi. If there
is not enough memory, vSphere does not start the VM. To solve the
issue, add more memory or migrate virtual machines to other ESXi nodes.
- If storage redundancy is not handled in the hardware (RAID), then,
when a disk that is a part of the data store used by a virtual machine
fails, vSphere does not allow the machine to start. Therefore, mirroring
for storage must always be used for virtual disks of IBM Netezza Platform Development
Software hardware.
- Virtual machine might start but might not be able to communicate
over the network. To identify the reason for this issue use the procedure
described in Network configuration problems for SPU boot problem.
IBM PureData System for Analytics, Version 7.1