On Jan 4, 2005, at 7:00 AM, Ivan Porro wrote:
Can I assign with Oscar 4.0 different IP to different services? i.e., can I
configure a sort of ListenAddress on LAM/MPI that's reside on a different
subnet from the NFS/NIS one? So, theoretically, whan NIC will be dedicated to
MPI and the other to "utility services"
LAM normally uses the IP addresses associated with the hostnames provided to lamboot (either via a hostfile or directly from PBS) to create TCP sockets for MPI communications. In the normal case, therefore, you don't need to do anything different -- what you lamboot on is what LAM uses for MPI communications.
However, for exactly this kind of situation (where you have a slow/commodity TCP network for NFS/NIS/other admin stuff as well as a fast TCP network for computational use), LAM 7.x includes a feature called "host mapping". It allows you to lamboot exactly as you have done before (indeed, if you're using the PBS boot module in LAM, you don't get a choice about which hosts you lamboot -- they're obtained directly from PBS, and OSCAR sets up PBS to use the "oscarnodeXX" hostnames, which is presumably your slow/admin network), but then remap the hostnames to be something else -- i.e., hostnames on your fast network.
This is documented more fully in the LAM/MPI Installation Guide, in the "After the Build" chapter, in the section named "Separating LAM and MPI TCP Traffic".
OSCAR does not install a LAM hostmap file by default, so you need to create it (this looks like an oversight -- it should be creating an empty/default hostmap that you can edit... will fix this for a future OSCAR release). Create the file /opt/lam-7.0.6/etc/lam-hostmap.txt. Here's the template that we normally ship with LAM -- it includes comments for documentation:
----- # Copyright (c) 2001-2003 The Trustees of Indiana University. # All rights reserved. # Copyright (c) 1998-2001 University of Notre Dame. # All rights reserved. # Copyright (c) 1994-1998 The Ohio State University. # All rights reserved. # # This file is part of the LAM/MPI software package. For license # information, see the LICENSE file in the top level directory of the # LAM/MPI source distribution. # # $HEADER$ # # This file is for re-mapping IP hostnames/addresses to be used for # MPI communications. Specifically, if a host is listed here and is # used in the LAM universe, the MPI SSI modules will use the remapped # address for all of its direct MPI communication. # # A common example of where this is useful is when you want to lamboot # over a "slow" TCP network but have your MPI communications go across # a different, "fast" TCP network. You would list your slow IP # names/addresses here and remap them to the fast names/addresses. # The LAM MPI SSI modules will automatically remap from the "slow" to # "fast" addresses whenever they create new connections for MPI-based # communications. # # Note that lamd-based communication (i.e., LAM run-time environment # native/out-of-band communication) will still use the original # addresses. Hence, the "lamd" rpi module will still use the original # addresses -- not the remapped addreses. # # Example entries: # # node1.slow.example.com mpi=node1.fast.example.come # node2.slow.example.com mpi=node2.fast.example.come # # The "fast" entries should be listed under the "mpi" key. # -----
You should be able to edit this file and setup the mapping from "slow" to "fast" hostnames.
Let me know if you any further questions.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
