Question on bound interfaces
Posted: Thu Sep 01, 2016 3:01 am
I have what I hope is a simple question.
In my home lab, I originally had five network interfaces in the free version of Virtual SAN. I noticed that there was iSCSI traffic on my XenServers in what I considered the management network. To make it easier to visualize, for each host, I had:
192.168.1.x: Management traffic
192.168.101.x: iSCSI path 1
192.168.102.x iSCSI path 2
192.168.103.x iSCSI path 3
192.168.104.x iSCSI path 4
I originally set this up in March (with a lot of help from Anton and Vlad), but was not aware that StarWind would automatically setup each NIC/IP in Windows to listen on 3260. I'm not sure where I found it, but I believe I had removed the management network (1.x) from the target. A netstat -an in fact showed 3260 listening on the management interface, but not in fact connected. All other paths show "established".
Fast forward to today. I installed 10gbe networking in the home lab rack and cabled everything up. I added three new 2TB drives in a RAID5 array on the hardware controller, and created a new target. As with the last time, it was painfully easy, and there were no real network options to speak of. I was able to attach the storage in XS and create an SR.
While it is awesome how easy this is to setup, I'd really like to leave the old target with the four iSCSI connections in MPIO, and have the new target only have the 10gbe network bound. The disk arrays are exactly the same, as I made sure to buy the exact same disks so I could benchmark both setups. Obviously, the 10gbe target would likely do better, but only if there is sufficient I/O bandwidth from the three 2TB disks.
I can't seem to find anything in the documentation that alludes to configuring bindings for IPs to iSCSI targets, nor can I find anything in the StarWind management console to affect bindings (though I swear I did before). The closest I can find to networking options is under <server> -> Configuration -> Network, which shows all the network interfaces.
Thanks in advance!
In my home lab, I originally had five network interfaces in the free version of Virtual SAN. I noticed that there was iSCSI traffic on my XenServers in what I considered the management network. To make it easier to visualize, for each host, I had:
192.168.1.x: Management traffic
192.168.101.x: iSCSI path 1
192.168.102.x iSCSI path 2
192.168.103.x iSCSI path 3
192.168.104.x iSCSI path 4
I originally set this up in March (with a lot of help from Anton and Vlad), but was not aware that StarWind would automatically setup each NIC/IP in Windows to listen on 3260. I'm not sure where I found it, but I believe I had removed the management network (1.x) from the target. A netstat -an in fact showed 3260 listening on the management interface, but not in fact connected. All other paths show "established".
Fast forward to today. I installed 10gbe networking in the home lab rack and cabled everything up. I added three new 2TB drives in a RAID5 array on the hardware controller, and created a new target. As with the last time, it was painfully easy, and there were no real network options to speak of. I was able to attach the storage in XS and create an SR.
While it is awesome how easy this is to setup, I'd really like to leave the old target with the four iSCSI connections in MPIO, and have the new target only have the 10gbe network bound. The disk arrays are exactly the same, as I made sure to buy the exact same disks so I could benchmark both setups. Obviously, the 10gbe target would likely do better, but only if there is sufficient I/O bandwidth from the three 2TB disks.
I can't seem to find anything in the documentation that alludes to configuring bindings for IPs to iSCSI targets, nor can I find anything in the StarWind management console to affect bindings (though I swear I did before). The closest I can find to networking options is under <server> -> Configuration -> Network, which shows all the network interfaces.
Thanks in advance!