Lustre 1.6 Operations Manual

Here is a more complicated situation, the route parameter is explained below. We
have:
■ Two TCP subnets
■ One Elan subnet
■ One machine set up as a router, with both TCP and Elan interfaces
■
IP over Elan configured, but only IP will be used to label the nodes.
options lnet ip2nets=”tcp198.129.135.* 192.128.88.98; \
elan 198.128.88.98 198.129.135.3;” \
routes=”tcp 1022@elan# Elan NID of router;\
elan 198.128.88.98@tcp # TCP NID of router “
31.2.1.2 networks ("tcp")
This is an alternative to "ip2nets" which can be used to specify the networks to be
instantiated explicitly. The syntax is a simple comma separated list of s
(see above). The default is only used if neither “ip2nets” nor “networks” is specified.
31.2.1.3 routes (“”)
This is a string that lists networks and the NIDs of routers that forward to them.
It has the following syntax ( is one or more whitespace characters):
:== { ; }
:== [[]{}
So a node on the network tcp1 that needs to go through a router to get to the Elan
network:
options lnet networks=tcp1 routes="elan 1 192.168.2.2@tcp1”
The hopcount is used to help choose the best path between multiply-routed
configurations.
A simple but powerful expansion syntax is provided, both for target networks and
router NIDs as follows.
:== "[" { "," } "]"
:== |
:== [ "-" [ "/" ] ]
Chapter 31 Configuration Files and Module Parameters (man5) 31-5