You can start, stop, and restart local, remote, and multiple Windows hosts. Find information on each of these options.
On Windows 2008 with the default security policy settings and Symphony in advanced workload execution mode, if you installed with the Windows local system administrator account (Administrator), you must also use that account to start EGO. If the current logon user is not Administrator, you will need to input the password of the Administrator account every time you start EGO. To start, use the followingcommand: runas Administrator egosh ego start
Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.
On Windows 2008 with the default security policy settings and Symphony in advanced workload execution mode, if you installed with the Windows local system administrator account (Administrator), you must also use that account to start EGO. If the current logon user is not Administrator, you will need to input the password of the Administrator account every time you start EGO. To start, use the followingcommand: runas Administrator egosh ego start host_name
Log on as egoadmin. If the master host is up, log onto any host in the cluster; if the master is down, log onto a management host.
egosh ego start host_name host_name ...
Replace host_name with the names of your remote hosts. Separate host names with a space.
On Windows 2008 with the default security policy settings and Symphony in advanced workload execution mode, if you installed with the Windows local system administrator account (Administrator), you must also use that account to start EGO. If the current logon user is not Administrator, you will need to input the password of the Administrator account every time you start EGO. To start, use the followingcommand: runas Administrator egosh ego start host_name...
By default, all hosts that join the cluster remain in the cluster, even if they become unusable.
Optionally, after a period of time in the Unavailable state, a compute host can expire from the cluster—it no longer appears in the Console, or in egosh resource list or resource view output, and it is not affected by egosh start all or restart all commands.
Host expiry is not irreversible. If you restart an expired host (for example, run egosh ego start host_name or restart the host while automatic system startup is configured), it can rejoin the cluster in the same way that a newly installed host joins the cluster.
If you want to remove a management host from the cluster, a different procedure is required.
To configure the host expiry feature, take the following steps.