Problem setting up Intel MPI on two Nodes

Problem setting up Intel MPI on two Nodes

I have two Nodes, both with Windows XP and Intel MPI Runtime Environment installed.
-smpd is running on both nodes
-the nodes are connected vie lan, both in the network 192.168.145.*
-all firewalls are disabled, pinging works
I've got a simple pinpong-program on both the nodes, when I execute the program with two processes on one node, it works fine, but executing it with one process per node doesn't work, because it deadlocks in the first cummunication(in my case a send and a recv). What does work is the MPI_Init and the transfer of stdout from both nodes to the node where mpiexec was run.
I've set I_MPI_DEVICE to sock.
Here are the two commands, both run on
working: mpiexec -hosts 2 -env I_MPI_DEVICE sock "C:\\pingpong.exe"
not-working: mpiexec -hosts 2 -env
I_MPI_DEVICE sock "C:\\pingpong.exe"
So the problem seems to be the communikation between the two nodes, but I don't know why.
Does anyone have an Idea what the problem is?

5 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.

Hi Christian,

What is the library version?
If you are using Intel MPI Library 4.0 you'd better use "I_MPI_FABRICS tcp" instead of "I_MPI_DEVICE sock".

Could you also check library versions in the following runs:
mpiexec -hosts 1 2 -genv
I_MPI_DEBUG 9 "C:\pingpong.exe"
mpiexec -hosts 1 2 -genv
I_MPI_DEBUG 9 "C:\pingpong.exe"

Are they the same?


The library version is, but using fabrics instead of device doesn't change the locking behavior.
With the specified runs it says "Intel MPI Library, Version 4.0 Build 20100218" on both nodes.

I just found the Problem, and it really isn't what I expected.
The both Maschines had the same networkname.
Now they have different networknames and everything works fine.


Just one notice: Using "-genv I_MPI_FABRICS tcp" means that shared memory will not be used.
To improve performance either use default settings (don't use I_MPI_FABRICS) or set "-genv I_MPI_FABRICS shm:tcp"


Laisser un commentaire

Veuillez ouvrir une session pour ajouter un commentaire. Pas encore membre ? Rejoignez-nous dès aujourd’hui