LCTL-NETWORK(8)

πŸ“¦ version 2.17.58, in ubuntu stonking

✨ LCTL-NETWORK πŸ’… (that's section 8 of the manual, bestie)

okay so this is lctl-network from the Lustre Configuration Utilities β€” yes it's an admin command, yes it's giving main character energy, and yes we're gonna walk through it together 🫢


🌸 NAME 🌸

lctl-network β€” start or stop an LNet network, or set the network type ✨


πŸŽ€ SYNOPSIS πŸŽ€

lctl network {up|down} | {configure|unconfigure} | {tcp|o2ib}

πŸ’– DESCRIPTION πŸ’–

okay so lctl network is your girl for starting or stopping LNet and LNet configuration on a client, a server, or a router. no cap.

and pssst β€” lctl net is literally just an alias for lctl network, they're the same thing, twins fr fr πŸ’•

BUT (and this is the plot twist) β€” netctl lnet is the preferred command for configuring and unconfiguring network interfaces. so like, lctl network still works, but the cool kids are using netctl lnet. iykyk 😌

here's the vibe: the Lustre software automatically starts and stops LNet all on its own, zero effort required. but you can also manually stop or start it in a standalone manner, and that's lowkey iconic for two reasons:

  • it's super useful for verifying that your networking setup actually works before you try to start the Lustre file system πŸ‘‘ (vibe check your network first, always)
  • it's necessary for Lustre routers, because routers only need the LND and LNet modules. that's it. that's the whole personality πŸ¦‹

✨ OPTIONS ✨

  • up β€” starts LNet πŸ’… the LNet modules must be loaded first though!! don't skip that step bestie, it will not go well 😭
  • down β€” stops LNet 🌈
  • configure β€” loads the LNet configuration πŸ“₯
  • unconfigure β€” clears the LNet configuration 🧹 this step is necessary for standalone routers so they can remove LNet references before the LNet modules can be removed. no unconfigure = no module removal, periodt.

πŸ”₯ NOTES πŸ”₯

okay important stuff, listen up πŸ“’

since Lustre 2.15.0, the lustre_rmmod script calls lnetctl lnet unconfigure or the lctl network down command internally to stop the LNet network interfaces. why does that matter?? because otherwise the lustre_rmmod utility does not work if you have manually run the lctl network up command. like. it just doesn't. πŸ™ˆ

⚠️ BIG WARNING, FOR REAL ⚠️ attempting to remove lustre(7) modules before stopping the network may result in a crash or an LNet hang πŸ’€ if that happens, the node must be rebooted (in most cases). so please, make sure that the Lustre network and the file system are stopped prior to unloading the modules. that's not a suggestion, that's the rule πŸ’œ

🌟 EXAMPLES 🌟

to load the module and start LNet:

# modprobe lnet
# lctl network up
LNet configured

to stop LNet and remove the module:

# lctl network down
LNet ready to unload
# rmmod lnet

to load LNet configuration in standalone mode:

# lctl network configure
LNet configured

to clear the LNet configuration:

# lctl network unconfigure
LNet ready to unload

πŸ¦‹ AVAILABILITY πŸ¦‹

lctl network is a subcommand of lctl(8) and is distributed as part of the lustre(7) filesystem package since release 0.6.0 πŸŽ€ she's been around a while, an absolute veteran, we stan.


πŸ‘‘ SEE ALSO πŸ‘‘

lctl(8), lnetctl(8)


okay that's the whole page bestie, you ate that πŸ’…βœ¨ this was Lustre, dated 2024-08-14, and you just finished reading LCTL-NETWORK(8) β€” go configure something iconic πŸ«ΆπŸ’–

πŸ“¦ where this page comes from