> If you do not use ifaces, then IO will be routed based on the route table. > So I think probably, IO would go through the same NIC on the server. Is this > what you are seeing?
I don't actually have the env. setup yet. Right now I'm just trying to determine what would be the best way to setup the env. without creating another subnet for the iscsi SAN traffic. > If you wanted to use dm-multipath to round robin over both NICs on the > linux server then you would use a ifaces to bind each session to each NIC. > > Ok, good to know. > Are the two switches connected to each other? If they were and you are > using one subnet, you would have better redundancy. Above you have 2 paths > to the target, but if the switches are connected you have 4 paths. > > I'm not sure I'll check this out with the networking crew. > The network layer should figure out there is another NIC that can be used > and just use it. A problem might be while we are switching nics IO could > time out and both paths could be down if they both ended up using the same > nic due to the routing table. So you would want to setup dm-multipath with a > higher no_path_retry, because when you switch over you might also have to > relogin to the target through the new nic. > > If you used ifaces then the failover should be smoother. The other path > would already be logged in, so dm-multipath could just restart the IO right > away. Perfect, this is exactly the information I was looking for. Thank you for the help, I really appreciate your response. -- Romeo Theriault System Administrator Information Technology Services -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.