LUSTRE_ROUTES_CONFIG(8)

💖 LUSTRE_ROUTES_CONFIG 💖

okay bestie, gather round, because this one is the glow-up page for lustre_routes_config(8) — straight out of the Lustre Configuration Utilities collection. if you've ever needed to spin up or tear down LNET routes without doing it by hand like some kind of medieval peasant, this is your moment. ✨

---

🌸 NAME 🌸

lustre_routes_config — Configure routes dynamically. no cap, that's the whole job description. 💅

---

🦋 SYNOPSIS 🦋

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

---

✨ DESCRIPTION ✨

so like, lustre_routes_config sets or cleans up</> LNET routes based on whatever you put in the config file you hand it. and here's the cute part: the /etc/lnet_routes.conf file can be used to automatically configure routes on LNET startup. automatic. iconic. 👑

the format of the config file is literally this:

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

yes, copy it exactly like that, bestie. the vibes are specific. 🎀

---

💅 OPTIONS 💅

• --setup — Configure routes listed in config_file. the "let's make it happen" energy. 🔥
• --cleanup — Unconfigure routes listed in config_file. the "we're done here, pack it up" energy. 🧹
• --dry-run — Echo commands to be run, but do not execute them. a little peek behind the curtain, no commitment. 👀
• --verbose — Echo commands before they are executed. so you can watch the whole thing unfold in real time. 🌈

---

🍓 FILES 🍓

• /etc/lnet_routes.conf

---

💀 NOTES 💀

okay this part matters, don't skip it. 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.

so 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. do that or the vibe check fails. 🫶

---

⭐ EXAMPLES ⭐

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>

look at that. gorgeous. main character behavior. 💜

---

👑 AUTHORS 👑

Amir Shehata

---

🌟 AVAILABILITY 🌟

lustre_routes_config is part of the lustre(7) filesystem package since release 2.4.0. it's been here, it's been serving. 💖

---

🔗 SEE ALSO 🔗

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

---

fr fr, that's the whole page. go configure some routes, bestie. slay. ✨

---

that's a wrap on this Lustre page, dated 2024-08-28, filed under LUSTRE_ROUTES_CONFIG(8). mwah. 💋