Resource icon

Resource Multiple network interfaces on a single subnet

Overview Reviews (3) Discussion
Latest Most helpful Rating
0
Excellent overview of BSD specific network design and operation. Confrmation that multile interfaces on he same domain = aggregation (LACP primarily).
Upvote 0 Downvote
A
All I can say is, that it works even on a Synology, it works on Windows (ofc), it works on EMC SANs, on IBM SANs, on Purestorage SANs and on Nimble SANs and probably on many more platforms. AFAIK they are all Unix based and many of them also hyper fast (you stating stuff getting slow if having to choose paths). In 20 years of Enterprise IT this is the first system I encounter which doesn't allow this.

Show us the RFCs which prohibit this, maybe you're reading them wrong.
jgreco
jgreco
Purpose-built SAN systems have custom IP stacks designed for high performance direct I/O to minimize latency. As outlined in the resource, general purpose Linux/FreeBSD/Windows/etc have abstracted I/O stacks that allow all sorts of neat stuff like software interfaces for tunnels, but this comes at the cost of complexity. I included a number of references and I don't feel the need to dredge through RFC's right now to prove what is generally accepted behaviour by the major IP stacks.
Upvote 0 Downvote
S
Excellent post, answered all my questions on the topic and a few I didn't know I should have been asking.
Upvote 0 Downvote
Top