I have stumbled upon an interesting blog conversation regarding the AoE protocol, a cornerstone of the Coraid Etherdrive storage systems we recommend. I have come across many storage professionals who just don’t seem to like simplicity in anything and AoE is so simple it does take a lot of convincing for some to take it seriously – this is no exception!
The blog to which I am referring to was entitled “ATA over Ethernet for converged data center networks? No way” and originally published here. Many points were raised but were picked up by Coraid and the response makes some interesting reading, not only for the way in which the points raised were dealt with, but also in the way it shows just how far we still need to go to convince some storage professionals that you can have simple in an Enterprise!
The response in its entirety appears below:
No sequencing
The protocol does not contain a single sequence number that would allow servers and storage arrays to differentiate between requests or split a single request into multiple Ethernet frames. A server can thus have only a single outstanding request with any particular storage array. (Or maybe LUN — who knows? The protocol specifications are silent.)
Answer:
As packets between initiator and target are not connection based, sequence numbers are irrelevant. A client can, however, have multiple requests outstanding with different tag values which is how a target differentiates between requests. Spreading between Ethernet frames is performed by the client who is responsible for turning a large request into a series of MTU sized requests (a 64KB request becomes 8 – 8KB requests, eg). All storage protocols do this somewhere – right down to the SATA/SAS wire which chunks blocks into 4KB data FIS.
An AoE Major.Minor is used in practice to reflect a Shelf#.Lun. Shelf# is your IP equivalent and is assigned per storage server.
No retransmissions
The protocol does not specify any packet loss detection or recovery mechanism. I can only assume that the only recovery the creators envision is request retransmission after a timeout, hoping that all requests can be repeated multiple times without side effects.
Answer:
Yes, because retransmitted requests do not change in lba/data they are idempotent. Initiator drivers possess a TCP-like congestion avoidance algorithm to control the retransmit time as well as the outstanding window of requests. Initial negotiation of the window is performed via the query-config message type.
No fragmentation
ATAoE requests fit directly into Ethernet frames, and there’s no way to fragment a single request into multiple frames and achieve streamlined data flow. Unless you use jumbo frames, you’ll be able to transfer at most two sectors (at 512 bytes) in each request. (iSCSI can transfer megabytes in a single transaction.) Add a few switches to the mix, and watch performance plummet.
Answer:
As I mentioned this above, the initiator chops up large requests into multiple MTU sized requests. Adding switches to the mix does not cause performance to plummet. Conversely, because AoE is not connection based you can achieve performance you simply can’t with iSCSI. It is a simple matter to connect multiple network ports on initiator and target and have all AoE requests flow across all possible network paths without any higher level (ie: bonding) configuration necessary. This round-robin mechanism is also provided by the initiator driver. Coraid’s performance numbers are achievable because it’s just this simple to attain performance.
No authentication
Can you imagine that? A protocol proposed for use in the data center that has no authentication whatsoever! The Wikipedia article proves that whoever designed (or described) this protocol was a total stranger to the finer details of network security when they wrote: “The non-routability of AoE is a source of inherent security.”
Answer:
Security is intentionally disregarded in the protocol. What users need is a way to have shared block storage on a SAN without the fuss. iSCSI was designed originally to provide shared block storage over the internet. It has many bells and knobs that you just don’t need in a closed environment with, eg, tens of servers running your VM architecture of choice connected to a single SAN storage pool.
The “security” comes from not being able to route AoE packets, so people outside your SAN broadcast d omain don’t see your data “accidentally”. The designers didn’t trumpet that, but some people think it’s a benefit.
No sessions
Another amazing omission. A server does not have to establish a session with the storage. As soon as you guess a LUN number, you can start reading and writing its data.
Answer:
If your SAN isn’t secure, neither is your data. If you plug in a host to your SAN that can do all sorts of root-like things and explore your SAN maliciously, yes, you have a problem. Root users can also scramble your local disks.
Weak support of asynchronous writes
Due to lack of sequencing and retransmissions, asynchronous writes are handled in a truly cavalier fashion: You can use them and the storage array always returns a success status, but the actual operation might fail — and the server will never be informed. I thought it would be nice to know if your write operation fails (after all, you might need that data in the future), but apparently that’s not the case.
Answer:
That’s a wart in the protocol that will be removed in the next revision. No one uses asynchronous writes. We have had custom configurations where responses were not needed, but we’ve worked around this another way.
Conclusion
A protocol like this could have been good enough 30 years ago when TFTP was designed, but today it would make a great example of a totally broken protocol in any protocol design class. As for its usability: Go ahead and use it when building your home network. I would definitely not consider it for mission-critical data center applications.
Answer:
I challenge you to dig a little deeper and correct your article. Many, many people use AoE based products for mission-critical data in situations where fast, affordable, scalable, easy to configure storage is needed. I think your primary complaint is that the protocol definition itself does not clarify all aspects of how AoE functions in practice. That’s a fair argument. Our history is one of Bell Labs culture and in writing this we documented the essential core leaving many details up to discretion.
