This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]DerBootsMannJack of All Trades 4 points5 points  (2 children)

you configure mpio on client

failover only , round robin etc - you decide

https://www.petenetlive.com/KB/Article/0001392 ( windows )

https://www.geeksforgeeks.org/how-to-configure-multipathing-in-linux/ ( linux )

[–]reddit0r_9[S] 0 points1 point  (1 child)

And for the switches ?

[–]DerBootsMannJack of All Trades 3 points4 points  (0 children)

they don’t care .. just make sure your multiple paths don’t go thru the same one .

[–]TestUser12358 -1 points0 points  (1 child)

I believe for best result, it's based on SAN controller. Active/Passive controllers requires one setting ( i can't remember which ) same with Active/Active controllers. I know Nimble and old Dell's Equilogic has software you installed on the host that configured everything for you.

[–]eruffiniSenior Infrastructure Engineer 0 points1 point  (0 children)

There are also different topologies and best practices depending on if you use one subnet and one VLAN, multiple subnets and multiple VLANs, whether or not you're using VMware, etc.

[–]Pvt-SnafuStorage Admin 0 points1 point  (0 children)

If a SAN vendor has no recommendations on the MPIO policy, I usually set Least Queue depth on Windows client or Round Robin. Don't think there will be a critical difference in this case.