NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas Pro 6 and open-iSCSI
Hi everyone,
I reall hope someone can point me in the right direction.
I have a HP DL360 G7 with 12GB of ram, a couple of disks and 4 nic's and running Ubuntu Server 11.04, I have bound the nic's into 2 pairs, one pair for a private iSCSI lan and the other pair go off into the network.
The private lan iSCSI bonding has an ip of 192.168.1.50 and subnet of 255.255.255.0, this connects directly to the Readynas nic 2, this has an ip of 192.168.1.51 and subnet of 255.255.255.0.
The network bonding on the server has an ip of 128.100.90.50, subnet of 255.255.0.0 and a gateway of 128.100.100.4, nic 1 on the Readynas has the same config except for the ip address which is 128.100.90.51.
I have set up a new target and set up a lun, this all works, no problem.
The iSCSI initiator software on the server is Open-iSCSI and after I perform a discovery, I see 2 targets available with different ip address from the readynas, I connect to the private lan and format the lun, everything is fine, but after a reboot the server may connect and push traffic down the network lan and not use the private lan, on the private lan I can see transfer rates of around 120 MB/s, obviously as it is connected directly, I don't see anything like that if it uses the network lan.
is it possible to tell readynas to only use a specific nic for iscsi or am I missing something here, I can get around this by unplugging the network lan on the readynas, thus forcing the iscsi traffic down it, but I then lose the connection to the management console and any email functions from the readynas for reporting erros etc, I know it may be open-iscsi that is also causing this but I have to start somewhere and maybe some networking guru's here could tell me a different way of doing this.
This setup is for using backuppc to backup clients to the readynas over iscsi, well I hope anyway ;-)
Best regards
Dale
I reall hope someone can point me in the right direction.
I have a HP DL360 G7 with 12GB of ram, a couple of disks and 4 nic's and running Ubuntu Server 11.04, I have bound the nic's into 2 pairs, one pair for a private iSCSI lan and the other pair go off into the network.
The private lan iSCSI bonding has an ip of 192.168.1.50 and subnet of 255.255.255.0, this connects directly to the Readynas nic 2, this has an ip of 192.168.1.51 and subnet of 255.255.255.0.
The network bonding on the server has an ip of 128.100.90.50, subnet of 255.255.0.0 and a gateway of 128.100.100.4, nic 1 on the Readynas has the same config except for the ip address which is 128.100.90.51.
I have set up a new target and set up a lun, this all works, no problem.
The iSCSI initiator software on the server is Open-iSCSI and after I perform a discovery, I see 2 targets available with different ip address from the readynas, I connect to the private lan and format the lun, everything is fine, but after a reboot the server may connect and push traffic down the network lan and not use the private lan, on the private lan I can see transfer rates of around 120 MB/s, obviously as it is connected directly, I don't see anything like that if it uses the network lan.
is it possible to tell readynas to only use a specific nic for iscsi or am I missing something here, I can get around this by unplugging the network lan on the readynas, thus forcing the iscsi traffic down it, but I then lose the connection to the management console and any email functions from the readynas for reporting erros etc, I know it may be open-iscsi that is also causing this but I have to start somewhere and maybe some networking guru's here could tell me a different way of doing this.
This setup is for using backuppc to backup clients to the readynas over iscsi, well I hope anyway ;-)
Best regards
Dale
2 Replies
Replies have been turned off for this discussion
- The ReadyNAS does not offer binding services to specific NICs at this time.
Only thing I can think of off hand, would be using iptables on the NAS, to block iSCSI traffic on the LAN NIC, so your server can only discover it on the pLAN. Someone else may have a better idea... - Many thanks chirpa for the fast reply,
Rather than mess with the NAS, I have just tested using the UFW (Uncomplicated Firewall) package on the server and blocked out all iSCSI traffic on the network lan, this seems to work and has only detected the target on the private lan, will test more tomorrow, again many thanks for the pointer.
Regards
Dale
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
