aoe-sancheck(8)

🌸 NAME 🌸

aoe-sancheck — verify storage network capabilities 💅

---

✨ SYNOPSIS ✨

aoe-sancheck [-v]

---

🫶 DESCRIPTION 🫶

Okay bestie, so aoe-sancheck is the girl who goes around and collects information about your local interfaces, then probes the network for ATA over Ethernet devices and validates the paths for each one. Iconic behavior, truly.

The cute part? It does not use the aoe kernel module — it uses the bpf interface to evaluate the network instead. So the aoe module does not need to be loaded to perform the test. No cap. 🎀

The output is split into two sections, like a two-part TikTok: first the local interface info, then a list of detected AoE devices.

Section one shows the local interfaces — whether each one is up or down, its configured MTU, and the PCI ID for the interface.

Section two lists the detected AoE devices, one per line, and each line has this info:

• Device — the device name in the form eX.Y, where X is the AoE device shelf address and Y is the AoE device slot address.
• Macs — the number of mac addresses detected for this device.
• Payload — the number of bytes of data the device can handle in a single AoE request. This number does not represent the total frame size, because it does not include bytes from ethernet or AoE headers.
• Local Interfaces — the list of local interfaces from which the device is visible.

🌈 Options 🌈

• -v — Prints out additional raw information.

---

💀 DIAGNOSIS 💀

For each device, aoe-sancheck may print out additional lines of suggestions or warnings. These are the checks it makes, bestie:

• The MTU of the local interfaces is set high enough to handle the AoE device's reported payload. Depending on the host NIC's capabilities and the storage network switch's capabilities, best performance may or may not be with the local interface MTU set higher than a device's payload size.
• The number of local interfaces matches the number of interfaces on the device. Best performance comes from having a host and device with comparable bandwidth. Aoe-sancheck simply counts the number of interfaces involved and does not figure link bandwidth in its comparison.
• All local interfaces for an AoE device have the same MTU. If one interface for a device has a smaller MTU than the others, the AoE driver must use the smaller payload size for all interfaces.
• Each path to the device is capable of the configured payload size. This check detects the situation where a local interface is configured for jumbo frames and the AoE device is capable of jumbo frames, but some aspect of the network is incapable of passing frames that size — for example, a misconfigured switch. Aoe-sancheck reports the maximum payload size the path is capable of if it's less than the configured payload size. 😭

---

🙈 BUGS 🙈

The program may sometimes display inconsistent results between runs, showing that a path is capable of a smaller frame size than it actually is. So if you see this behavior, please email one of the authors with your verbose output. Fr fr, they wanna see it. 💌

---

👑 SEE ALSO 👑

aoeping(8), aoetools(8)

---

💜 AUTHORS 💜

Justin Sanders (justin@coraid.com), Sam Hopkins (sah@coraid.com)

---

That's the whole page, bestie — straight out of the System Manager's Manual, the one and only aoe-sancheck(8). Go run it and slay your storage network. 💅✨