HP-MPI Version 2.2.5 for HP-UX Release Note

HP-MPI V2.2.5 for HP-UX Release Note
What’s in This Version
9
and it will print out an IP and port. Then when running mpirun, the extra option
-nameserver with an IP address and port must be provided:
% $MPI_ROOT/bin/mpirun -spawn -nameserver <IP:port> ...
The scope over which names are published and retrieved consists of all mpiruns which are
started using the same IP:port for the nameserver.
New mpirun option -netaddr
-netaddr is similar to -subnet, but allows finer control of the selection process for TCP/IP
connections. MPI has two main sets of connections: those between ranks and/or daemons
where all the real message traffic occurs, and connections between mpirun and the daemons,
which are necessary, but few have message traffic.
The -netaddr option can be used to specify a single IP/mask to use for both of these purposes,
or to specify them individually.
The latter might be needed if mpirun happens to be run on a remote machine that doesn’t
have access to the same ethernet as the rest of the cluster. To specify both, the syntax would
be -netaddr IP-specification[/mask]. To specify them individually it would be -netaddr
mpirun:spec,rank:spec. The string "launch:" can be used in place of "mpirun:".
The IP-specification can be a numeric IP address like 172.20.0.1 or can be a hostname. If a
hostname is used, the value will be the first IP address returned by gethostbyname(). The
optional mask can be specified as a dotted quad, or can be given as a number representing
how many bits are to be matched. So, for example, a mask of "11" would be equivalent to a
mask of "255.224.0.0".
If an IP and mask are given, then it is expected that one and only one IP will match at each
lookup. An error or warning is printed as appropriate if there are no matches, or too many. If
no mask is specified, then the IP matching will simply be done by the longest matching prefix.
This functionality can also be accessed using the environment variable MPI_NETADDR.
NOTE The -subnet option will be deprecated in a future release.
New Environment Variables
The following section provides brief descriptions of the new environment variables included in
this release.