[LU-14939] Allow specifying source NI for lnetctl ping

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.15.0
• Type: Improvement
• Priority: Minor
• Reporter: Chris Horn
• Assignee: Chris Horn
• Resolution: Fixed

Description

It would be useful for network troubleshooting if we were able to deterministically exercise specific network paths (i.e. send from a particular local NI to a particular remote peer NI). The multi-rail implementation makes this difficult today because the lnetctl ping is a "source ANY" send. i.e. by default it will send from any local NI to any remote NI on a multi-rail peer.
This ticket tracks enhancement to lnetctl ping command so that we can specify a source NI. By definition, this will also fix the destination NID so we can obtain the desired deterministic behavior.

Comments

[Cory Spitz]

https://review.whamcloud.com/#/c/44727/ was submitted for this, but this LU wasn't automatically updated presumably because the original commit message referenced LU-14943 instead.

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/44727/
Subject: LU-14939 lnet: Allow specifying a source NID for lnetctl ping
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 48ef9982c474a02c460293bce17c9e45f9829eab

[Peter Jones]

Landed for 2.15