23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

31.2.1.4 forwarding ("")<br />

This is a string that can be set either to "enabled" or "disabled" for explicit control of<br />

whether this node should act as a router, forwarding communications between all<br />

local networks.<br />

A standalone router can be started by simply starting LNET (“modprobe ptlrpc”)<br />

with appropriate network topology options.<br />

Variable<br />

acceptor<br />

accept_port<br />

(988)<br />

accept_backlog<br />

(127)<br />

accept_timeout<br />

(5, W)<br />

accept_proto_version<br />

Description<br />

The acceptor is a TCP/IP service that some LNDs use to establish<br />

communications. If a local network requires it and it has not been<br />

disabled, the acceptor listens on a single port for connection<br />

requests that it redirects to the appropriate local network. The<br />

acceptor is part of the LNET module and configured by the<br />

following options:<br />

• secure - Accept connections only from reserved TCP ports (<<br />

1023).<br />

• all - Accept connections from any TCP port. NOTE: this is<br />

required for liblustre clients to allow connections on nonprivileged<br />

ports.<br />

• none - Do not run the acceptor.<br />

Port number on which the acceptor should listen for connection<br />

requests. All nodes in a site configuration that require an acceptor<br />

must use the same port.<br />

Maximum length that the queue of pending connections may grow<br />

to (see listen(2)).<br />

Maximum time in seconds the acceptor is allowed to block while<br />

communicating with a peer.<br />

Version of the acceptor protocol that should be used by outgoing<br />

connection requests. It defaults to the most recent acceptor protocol<br />

version, but it may be set to the previous version to allow the node<br />

to initiate connections with nodes that only understand that<br />

version of the acceptor protocol. The acceptor can, with some<br />

restrictions, handle either version (that is, it can accept connections<br />

from both 'old' and 'new' peers). For the current version of the<br />

acceptor protocol (version 1), the acceptor is compatible with old<br />

peers if it is only required by a single local network.<br />

Chapter 31 Configuration Files and Module Parameters (man5) 31-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!