The Parallel/Network/Configure... menu item opens the Network Configuration panel.
| The ability to manually spawn additional compute nodes before reading the case file using the
Network Configuration panel is only availabe when using the
net option (e.g.,
-mpi=net). While this feature is still available in
FLUENT 6.3, its use is discouraged.
Network Configuration Panel
Compute nodes are labeled sequentially starting at 0. In addition to the compute node processes, there is one host process. The host process is automatically started when FLUENT starts, and it is killed when FLUENT exits. It cannot be killed while running. Compute nodes, however, can be killed at any time, with the exception that compute node 0 can only be killed if it is the last remaining compute node process. The host process always spawns compute node 0. Compute node 0 spawns all other compute nodes.
If you want to spawn compute nodes on several different machines, or if you want to make any changes to the current network configuration (e.g., if you accidentally spawned too many compute nodes on the host machine when you started the solver), the Network Configuration panel allows you to control the configuration of your parallel network.
Parallel Network Configure...
To add a host to the Available Hosts list manually, you can enter the internet name of the remote machine in the Hostname field under Host Entry, enter your login name on that machine in the Username field (unless your accounts all have the same login name, in which case you need not specify a username), and then click the Add button. The specified host will be added to the Available Hosts list.
To delete a host from the Available Hosts list in the Network Configuration panel, select the host and click the Delete button. The host name will be removed from the Available Hosts list (but the Hosts Database panel will not be affected).
| Remember that compute node 0 can only be killed if it is the last remaining compute node process.
The basic steps for spawning compute nodes are as follows:
Common Problems Encountered During Node Spawning
The spawning process will try to establish a connection with a new compute node, but if after 50 seconds it receives no response from the new compute node, it will assume the spawn was unsuccessful. The spawn will be unsuccessful, for example, if the remote machine is unable to find the FLUENT executable. To manually test if the spawning machine can start a new compute node, you can type
fluent -t0 -v
from a shell prompt on the spawning machine. hostname should be replaced with the internet name of the machine on which you want to spawn a compute node, and username should be replaced with your login name on the remote machine specified by hostname.
| If all your accounts have the same login name, you do not need to specify a username. (The square brackets around
username indicate that it is not always required; if you do enter a login name, do not include the square brackets.) Note that on some systems, the remote shell command is
remsh instead of
The spawn test could fail for several reasons:
parallel network path