[ <w> ]
<net-spec> :== <network> [ "(" <interface-list> ")" ]
<network> :== <nettype> [ <number> ]
-<nettype> :== "tcp" | "elan" | "openib" | ...
+<nettype> :== "tcp" | "elan" | "o2ib" | ...
<iface-list> :== <interface> [ "," <iface-list> ]
<ip-range> :== <r-expr> "." <r-expr> "." <r-expr> "." <r-expr>
<r-expr> :== <number> | "*" | "[" <r-list> "]"
<net-sep> :== ";" | "\n"
<w> :== <whitespace-chars> { <whitespace-chars> }
</screen>
- <para><literal><net-spec></literal> contains enough information to uniquely identify the network and load an appropriate LND. The LND determines the missing "address-within-network" part of the NID based on the interfaces it can use.</para>
- <para><literal><iface-list></literal> specifies which hardware interface the network can use. If omitted, all interfaces are used. LNDs that do not support the <literal><iface-list></literal> syntax cannot be configured to use particular interfaces and just use what is there. Only a single instance of these LNDs can exist on a node at any time, and <literal><iface-list></literal> must be omitted.</para>
- <para><literal><net-match></literal> entries are scanned in the order declared to see if one of the node's IP addresses matches one of the <literal><ip-range></literal> expressions. If there is a match, <literal><net-spec></literal> specifies the network to instantiate. Note that it is the first match for a particular network that counts. This can be used to simplify the match expression for the general case by placing it after the special cases. For example:</para>
+ <para><literal><net-spec></literal> contains enough information to
+ uniquely identify the network and load an appropriate LND. The LND
+ determines the missing "address-within-network" part of the
+ NID based on the interfaces it can use.</para>
+ <para><literal><iface-list></literal> specifies which hardware
+ interface the network can use. If omitted, all interfaces are used. LNDs
+ that do not support the <literal><iface-list></literal> syntax
+ cannot be configured to use particular interfaces and just use what is
+ there. Only a single instance of these LNDs can exist on a node at any
+ time, and <literal><iface-list></literal> must be omitted.</para>
+ <para><literal><net-match></literal> entries are scanned in the
+ order declared to see if one of the node's IP addresses matches one
+ of the <literal><ip-range></literal> expressions. If there is a
+ match, <literal><net-spec></literal> specifies the network to
+ instantiate. Note that it is the first match for a particular network
+ that counts. This can be used to simplify the match expression for the
+ general case by placing it after the special cases. For example:</para>
<screen>ip2nets="tcp(eth1,eth2) 134.32.1.[4-10/2]; tcp(eth1) *.*.*.*"</screen>
- <para>4 nodes on the 134.32.1.* network have 2 interfaces (134.32.1.{4,6,8,10}) but all the rest have 1.</para>
- <screen>ip2nets="<emphasis role="bold">vib</emphasis> 192.168.0.*; tcp(eth2) 192.168.0.[1,7,4,12]" </screen>
- <para>This describes an IB cluster on 192.168.0.*. Four of these nodes also have IP interfaces; these four could be used as routers.</para>
- <para>Note that match-all expressions (For instance, <literal>*.*.*.*</literal>) effectively mask all other</para>
- <para> <literal><net-match></literal> entries specified after them. They should be used with caution.</para>
- <para>Here is a more complicated situation, the route parameter is explained below. We have:</para>
+ <para>4 nodes on the 134.32.1.* network have 2 interfaces
+ (134.32.1.{4,6,8,10}) but all the rest have 1.</para>
+ <screen>ip2nets="<emphasis role="bold">o2ib</emphasis> 192.168.0.*; tcp(eth2) 192.168.0.[1,7,4,12]" </screen>
+ <para>This describes an IB cluster on 192.168.0.*. Four of these nodes
+ also have IP interfaces; these four could be used as routers.</para>
+ <para>Note that match-all expressions (For instance,
+ <literal>*.*.*.*</literal>) effectively mask all other</para>
+ <para> <literal><net-match></literal> entries specified after
+ them. They should be used with caution.</para>
+ <para>Here is a more complicated situation, the route parameter is
+ explained below. We have:</para>
<itemizedlist>
<listitem>
<para>Two TCP subnets</para>
<para>One Elan subnet</para>
</listitem>
<listitem>
- <para>One machine set up as a router, with both TCP and Elan interfaces</para>
+ <para>One machine set up as a router, with both TCP and Elan
+ interfaces</para>
</listitem>
<listitem>
- <para>IP over Elan configured, but only IP will be used to label the nodes.</para>
+ <para>IP over Elan configured, but only IP will be used to label the
+ nodes.</para>
</listitem>
</itemizedlist>
<screen>options lnet ip2nets=â€tcp 198.129.135.* 192.128.88.98; \
elan 198.128.88.98@tcp # TCP NID of router '</screen>
</section>
<section remap="h4">
- <title><indexterm><primary>configuring</primary><secondary>network</secondary><tertiary>tcp</tertiary></indexterm>
-networks ("tcp")</title>
- <para>This is an alternative to "<literal>ip2nets</literal>" which can be used to specify the networks to be instantiated explicitly. The syntax is a simple comma separated list of <literal><net-spec></literal>s (see above). The default is only used if neither 'ip2nets' nor 'networks' is specified.</para>
+ <title><indexterm><primary>configuring</primary>
+ <secondary>network</secondary><tertiary>tcp</tertiary></indexterm>
+ networks ("tcp")</title>
+ <para>This is an alternative to "<literal>ip2nets</literal>"
+ which can be used to specify the networks to be instantiated explicitly.
+ The syntax is a simple comma separated list of
+ <literal><net-spec></literal>s (see above). The default is only
+ used if neither 'ip2nets' nor 'networks' is
+ specified.</para>
</section>
<section remap="h4">
<title><indexterm><primary>configuring</primary><secondary>network</secondary><tertiary>routes</tertiary></indexterm>
<entry> :== <numeric range> | <non-numeric item>
<numeric range> :== <number> [ "-" <number> [ "/" <number> ] ]</screen>
<para>The expansion is a list enclosed in square brackets. Numeric items in the list may be a single number, a contiguous range of numbers, or a strided range of numbers. For example, <literal>routes="elan 192.168.1.[22-24]@tcp"</literal> says that network <literal>elan0</literal> is adjacent (hopcount defaults to 1); and is accessible via 3 routers on the <literal>tcp0</literal> network (<literal>192.168.1.22@tcp</literal>, <literal>192.168.1.23@tcp</literal> and <literal>192.168.1.24@tcp</literal>).</para>
- <para><literal>routes="[tcp,vib] 2 [8-14/2]@elan"</literal> says that 2 networks (<literal>tcp0</literal> and <literal>vib0</literal>) are accessible through 4 routers (<literal>8@elan</literal>, <literal>10@elan</literal>, <literal>12@elan</literal> and <literal>14@elan</literal>). The hopcount of 2 means that traffic to both these networks will be traversed 2 routers - first one of the routers specified in this entry, then one more.</para>
+ <para><literal>routes="[tcp,o2ib] 2 [8-14/2]@elan"</literal>
+says that 2 networks (<literal>tcp0</literal> and <literal>o2ib0</literal>) are accessible through 4 routers (<literal>8@elan</literal>, <literal>10@elan</literal>, <literal>12@elan</literal> and <literal>14@elan</literal>). The hopcount of 2 means that traffic to both these networks will be traversed 2 routers - first one of the routers specified in this entry, then one more.</para>
<para>Duplicate entries, entries that route to a local network, and entries that specify routers on a non-local network are ignored.</para>
<para>Prior to release 2.5, a conflict between equivalent entries was resolved in favor of the route with the shorter hopcount. The hopcount, if omitted, defaults to 1 (the remote network is adjacent)..</para>
<para condition='l25'>Since 2.5, equivalent entries are resolved in favor of the route with the lowest priority number or shorter hopcount if the priorities are equal. The priority, if omitted, defaults to 0. The hopcount, if omitted, defaults to 1 (the remote network is adjacent).</para>
parameter, all non-loopback IP interfaces are used. The address-within-network is determined
by the address of the first IP interface an instance of the <literal>socklnd</literal>
encounters.</para>
- <para>Consider a node on the 'edge' of an InfiniBand network, with a low-bandwidth
- management Ethernet (<literal>eth0</literal>), IP over IB configured
- (<literal>ipoib0</literal>), and a pair of GigE NICs
- (<literal>eth1</literal>,<literal>eth2</literal>) providing off-cluster connectivity. This
- node should be configured with '<literal>networks=vib,tcp(eth1,eth2)</literal>' to
- ensure that the <literal>socklnd</literal> ignores the management Ethernet and IPoIB.</para>
+ <para>Consider a node on the 'edge' of an InfiniBand network,
+ with a low-bandwidth management Ethernet (<literal>eth0</literal>), IP
+ over IB configured (<literal>ipoib0</literal>), and a pair of GigE NICs
+ (<literal>eth1</literal>,<literal>eth2</literal>) providing off-cluster
+ connectivity. This node should be configured with '
+ <literal>networks=o2ib,tcp(eth1,eth2)</literal>' to ensure that the
+ <literal>socklnd</literal> ignores the management Ethernet and IPoIB.
+ </para>
<informaltable frame="all">
<tgroup cols="2">
<colspec colname="c1" colwidth="50*"/>
git://git.whamcloud.com / doc / manual.git / commitdiff