2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→High Availability: Added "Command Line Interface etc" and beefed up other sections
(→ESX: Added more recent HA logs) |
(→High Availability: Added "Command Line Interface etc" and beefed up other sections) |
||
| Line 940: | Line 940: | ||
== High Availability == | == High Availability == | ||
'''Be aware that playing with HA can have disastrous effects, especially if the ''Isolation Response'' of your cluster is set to ''Power Off''''' If you can, consider waiting until outside of production hours before trying to resolve a problem. | '''Be aware that playing with HA can have disastrous effects, especially if the ''Isolation Response'' of your cluster is set to ''Power Off''''' If you can, consider waiting until outside of production hours before trying to resolve a problem. Unstable clusters can disintegrate if you're unlucky. | ||
There are 5 primaries in an HA cluster, the first ESX's to join the cluster become primaries, this only changes (through an election) when the following occurs (note - not during an ESX failure).. | |||
* Primary ESX goes into Maintenance Mode | |||
* Primary disconnected from the cluster | |||
* Primary removed from the cluster | |||
* Primary reconfigured for HA | |||
It's quite common for HA to go into an error state, normal course of action is to use the '''Reconfigure for HA''' option for the ESX that's experiencing the problem. This reinstalls the HA agent onto the ESX onto the ESX. It's also common to have to do this a couple of times for it to be successful. | It's quite common for HA to go into an error state, normal course of action is to use the '''Reconfigure for HA''' option for the ESX that's experiencing the problem. This reinstalls the HA agent onto the ESX onto the ESX. It's also common to have to do this a couple of times for it to be successful. | ||
| Line 965: | Line 971: | ||
If the VC Agent or HA Agent fails due to the uninstaller being unable to remove files/folders, and you can't remove them manually, this is an indication that the disk is becoming corrupt. Especially if installed on a USB key, consider replacing ASAP. | If the VC Agent or HA Agent fails due to the uninstaller being unable to remove files/folders, and you can't remove them manually, this is an indication that the disk is becoming corrupt. Especially if installed on a USB key, consider replacing ASAP. | ||
=== Command Line Interface etc === | |||
'''''Using the commands in this section isn't supported by VMware''''' | |||
To start the CLI run the following command... | |||
* <code> /opt/vmware/aam/bin/Cli </code> | |||
The interface is a bit dodgy, you can enter the same command twice, and it'll be rejected one time and accepted another, patience is required. | |||
{|cellpadding="4" cellspacing="0" border="1" | |||
|- style="background-color:#bbddff;" | |||
! Command !! Comments | |||
|- | |||
| <code> ln </code> || List cluster nodes and their status | |||
|- | |||
| <code> addNode <hostname> </code> || Add ESX/node to cluster (use ESX's short DNS name) | |||
|- | |||
| <code> promoteNode <hostname> </code> || Promote existing ESX/node to be a primary | |||
|- | |||
| <code> demoteNode <hostname> </code> || Demote existing ESX/node to be a secondary | |||
|} | |||
There's also the following scripts to be found which behave as you'd expect (found in <code> /opt/vmware/aam/bin </code>)... | |||
* <code> ./ft_setup </code> | |||
* <code> ./ft_startup </code> | |||
* <code> ./ft_shutdown </code> | |||
== Snapshots == | == Snapshots == | ||