Binding solaris zfs iscsi to a specific interface

jason — Tue, 17 Feb 2009 15:11:24 +0000

By default, when you enable iscsi sharing within zfs, the share is created and bound to all available ethernet interfaces. This isn’t necessarily a bad thing, but if for some reason you can reach your iscsi share via two paths, you run the chance of sending iscsi traffic over a non optimized path and really messing with your performance. Fortunately, a way exists to bind iscsi to specific interfaces using interface groups.

First, we need to create the interface group. This is assuming that the IP 192.168.1.1 is the IP address that is assigned to the interface (or in the case of bound channels, multiple interfaces) that you want a specific share to use.

iscsitadm create tpgt
iscsitadm modify tpgt -i 192.168.1.1 1

A quick

iscsitadm list tpgt -v 1

Will let you know if this worked.

Now that your interface group is created, all you have to do is bind it to a specific share.

iscsitadm modify target -p 1 zpool/iscsiTarget

Done! This leaves open some interesting opportunities for using the same iscsi SAN to service connections on different networks in a relatively secure manner. Have fun!

Adding more then 255 IPs to an interface in Solaris

jason — Mon, 26 May 2008 14:00:36 +0000

By default, solaris will only let you add 255 IP addresses to an interface. You’ll know you hit the limit when you get an out of buffer message when you try to add your next one. In Solaris 2.5, you’re pretty much stuck with this limitation. In solaris 2.6 and higher, you can run the followng to up that limit as high as 8192. Past 8192, you’ll need to add another interface.

/usr/sbin/ndd -set /dev/ip ip_addrs_per_if 8192

cyborgworkshop.org » interface

Binding solaris zfs iscsi to a specific interface

Adding more then 255 IPs to an interface in Solaris