OS Manuals

lustre_routes_config(8)

lustre_routes_config - Configure routes dynamically

LUSTRE_ROUTES_CONFIG(8) Lustre Configuration Utilities LUSTRE_ROUTES_CONFIG(8)

lustre_routes_config - Configure routes dynamically

lustre_routes_config [--setup|--cleanup|--dry-run|--verbose] CONFIG_FILE

lustre_routes_config sets or cleans up LNET routes from the specified config file. /etc/lnet_routes.conf file can be used to automatically configure routes on LNET startup.

The format of the config file is:

NETWORK: { gateway: GATEWAY@EXIT_NETWORK [hop: HOP] [priority: PRIOIRTY] }

Configure routes listed in config_file
Unconfigure routes listed in config_file
Echo commands to be run, but do not execute them
Echo commands before they are executed

/etc/lnet_routes.conf

An LNET router is identified when its local NID appears within the list of routes. However, this can not be achieved by the use of this script, since the script only adds extra routes after the role of the router is determined. To ensure that a router is identified correctly, make sure to add its local NID in the routes parameter in the modprobe lustre configuration file.

An example of a config file that the script expects:

tcp1: { gateway: 10.1.1.2@tcp0, priority: 3 }
tcp4: { gateway: 10.3.3.4@tcp }
tcp6: { gateway: 10.3.3.6@tcp, hop: 2, priority: 5 }
tcp7: { gateway: 10.3.3.[6-12]@tcp, priority: 20, hop: 8 }

An example of script execution:

lustre_routes_config --setup <path/to/routes_config_file>
lustre_routes_config --cleanup <path/to/routes_config_file>

Amir Shehata

lustre_routes_config is part of the lustre(7) filesystem package since release 2.4.0

nids(5), lustre(7), lctl(8), lustre_routes_conversion(8)

2024-08-28 Lustre

lustre 2.17.60-r0 · enterprise-packages · ingested 2026-10-22