Actually, not so important although I'm still curious as to the answers. My bonding issue it seems is a bug that when you have multiple bonded interfaces the second one can pull it's config data from the first one and ignore the options passed to it. In my case this means that my second bonded interface was setup as active/backup (which are the settings of my first bonded interface) rather than receive-alb. I've just switch them both to receive-alb and that should resolve it.
Thanks From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Watkins Sent: Tuesday, 4 March 2008 9:32 a.m. To: [email protected] Subject: [OF-users] MC/S iSCSI support Hi ALl Does anyone know if the iSCSI target software supports MC/S? Obviously with the network bonding pages in the GUI now MC/S makes more sense to use than MPIO (MPIO requires separate physical networks, or VLANs I believe but I could be wrong). If not there was some talk a while ago about dropping ietd and moving to another target software, did that happen for 2.3? Actually it's probably also worth asking if ietd supports MPIO as well. This has mostly come about because my current ifconfig output looks like this where almost all my iSCSI traffic is flowing through eth2 when eth2-eth5 are in a single bonded interface. eth2 Link encap:Ethernet HWaddr 00:0E:0C:B9:E2:40 inet addr:192.168.79.1 Bcast:192.168.79.255 Mask:255.255.255.0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1 RX packets:464042439 errors:0 dropped:0 overruns:0 frame:0 TX packets:480356751 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:775449899249 (739526.6 Mb) TX bytes:1429507341558 (1363284.4 Mb) Base address:0x4000 Memory:de100000-de120000 eth3 Link encap:Ethernet HWaddr 00:0E:0C:B9:E2:40 inet addr:192.168.79.1 Bcast:192.168.79.255 Mask:255.255.255.0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1 RX packets:2471296 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:168718987 (160.9 Mb) TX bytes:0 (0.0 b) Base address:0x4040 Memory:de120000-de140000 eth4 Link encap:Ethernet HWaddr 00:0E:0C:B9:E2:40 inet addr:192.168.79.1 Bcast:192.168.79.255 Mask:255.255.255.0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1 RX packets:2471296 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:168719055 (160.9 Mb) TX bytes:0 (0.0 b) Base address:0x4080 Memory:de140000-de160000 eth5 Link encap:Ethernet HWaddr 00:0E:0C:B9:E2:40 inet addr:192.168.79.1 Bcast:192.168.79.255 Mask:255.255.255.0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1 RX packets:2471296 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:168718987 (160.9 Mb) TX bytes:0 (0.0 b) Base address:0x40c0 Memory:de160000-de180000 Anyone have any thoughts? Thanks Dave
_______________________________________________ Openfiler-users mailing list [email protected] https://lists.openfiler.com/mailman/listinfo/openfiler-users
