free website hit counter Limiting MPI (1.2x) traffic to one NIC - The Cluster Agenda
The Cluster AgendaMain Page | About | Help | FAQ | Special pages | Log in

Printable version | Disclaimers | Privacy policy

Limiting MPI (1.2x) traffic to one NIC

From The Cluster Agenda

As an example, say you want to run your nodes with a FastEther port for the admin and reporting functions but leave the GigaEther for the MPI traffic.

IP addresses are setup accordingly and they have their own host names. eg. borg1 is the GigaEther (eth1) while borg1_m (eth0) is the "management" interface. Now, if you don't tell MPI that there's a difference then it's going reach out and touch the machines with eth0.

To limit the MPI traffic to a specific interface you need to tell it which interface to use. A bit if string work in your mpirun.args file does the trick.

In this case:

MPI_HOST=`hostname | sed "s/_m//"`

This slices the "_m" off the end of the hostname.

(thanks to Reuti at the Uni of Marburg, Germany from the Beowulf email list)

Retrieved from "http://agenda.clustermonkey.net/index.php/Limiting_MPI_%281.2x%29_traffic_to_one_NIC"

This page has been accessed 901 times. This page was last modified 03:36, 22 February 2006. Content is available under Attribution-NonCommercial-ShareAlike 2.5.


Find
Browse
Main Page
Community portal
Current events
Recent changes
Random page
Help
Donations
Edit
Edit this page
Editing help
This page
Discuss this page
Post a comment
Printable version
Context
Page history
What links here
Related changes
My pages
Log in / create account
Special pages
New pages
File list
Statistics
Bug reports
More...