Mike Christie wrote: > Ok let me clarify one other thing too. With the network layer we get a > ethX, or whatever you set up your udev rules to use, for each port. That > is what I am saying above represents the device name and port. The iscsi > drivers that interact with the linux net layer like bnx2i, cxgb3i and > iscsi_tcp supports using the netdevice name (same name you see in > /sys/class/net or ifconfig) for iscsi iface binding.
yep, understood. > We are talking about the iscsi iface.net_ifacename param right? It is > the name you see in sysfs or in ifconfig. You set it to > iface.net_ifacename and it gets passed directly down to in the > BINDTODEVICE setsockopt. sure, understood as well. > For drivers that do not have a netdevice name because they do not > interact with the network layer (they have an entire net stack in > firmware) we use the MAC. So this includes qla4xxx and be2iscsi, and > iscsi_tcp also supports this. In that case we loop over the net > interfaces and match the MAC with a ethX and then pass that to > BINDTODEVICE setsockopt. understood, as I have explained, mac is problematic for iser from two reasons: under bonding it will not function well (we use the fail_over_mac option of bonding), and also since some of the mac isn't persistent today so we have to enhance the iscsi code to allow using only a portion of it. Or. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
