FreeNAS iSCSI and static route

[mst]

Experts,

I plan to use LACP aggregation on FreeNAS with Cisco 4900 10GB links and Intel 10GB X540-T2 using 192.168.10.x network. Cisco 4900 has both 10GB link configured as:

Code:

interface TenGigabitEthernet2/7 and 2/8 as well:
description Supermicro
switchport access vlan 10
switchport mode access
spanning-tree portfast
spanning-tree bpduguard enable

port-channel:
description MDF 10GB Link
switchport
switchport trunk native vlan 5
switchport mode trunk
load-interval 30
ip dhcp snooping trust

My MGTM on the FreeNAS is 192.168.5.x

iSCSI should be visible only to ESX hosts and FreeNAS. However, I believe on the FreeNAS I should add static route to iSCSI network in order to access both networks from FreeNAS???

Previously I used openfiller with this static route in rc.local:

Code:

touch /var/lock/subsys/local
#ip route add 192.168.10.0/24 dev bond0 src 192.168.10.2 table ISCSI
#ip route add default via 192.168.10.1 dev bond0 table ISCSI
# Temporary routing rules while two public NICs are active_persistant on reboot
ip rule add from 192.168.10.2/32 table ISCSI
ip rule add to 192.168.10.2/32 table ISCSI
ip route flush cache

FreeNAS MGTM: 192.168.5.x | ISCSI network 192.168.10.x.

I am not sure if I should use GUI or FreeBSD for adding static route. In my case I should add 192.168.10.0/24

Code:

OpenFiler route-bond0 :	  192.168.10.0/24 dev bond0 src 192.168.10.9 table ISCSI
													default via 192.168.10.1 dev bond0 table ISCSI

So I believe I should:

create link aggregation with 192.168.10.9/24 address assigned - this has been completed.

My network looks:

lagg0 192.168.10.9/24
igb0 192.168.5.100/24
Nameserver
192.168.5.1
Default route
192.168.5.1

So now its time for adding static route on FreeNAS pointing to 192.168.10.1 otherwise I cant be able ping network 192.168.10.x from FreeNAS however:

Code:

Internet:
Destination		Gateway			Flags	  Netif Expire
default			192.168.5.1		UGS		igb0
127.0.0.1		  link#7			 UH		  lo0
192.168.5.0/24	 link#3			 U		  igb0
192.168.5.100		link#3			 UHS		 lo0
192.168.10.0/24	link#8			 U		 lagg0
192.168.10.9	   link#8			 UHS		 lo0

i am not able to ping iSCSI network 192.168.10.1 after adding static route through the GUI: destination network 192.168.10.0/32 and gateway 192.168.10.1 I get destination host down.

 

[pirateghost]

You shouldn't need a static route if you have an interface with an IP in that same subnet.

 

[mst]

wow I have just noticed both 10GB are not bounded to any port-channels on my Cisco so no LACP configured on Cisco side.

Can I still use both 10GB ports if decided not use LACP ? From what I see I have: both ports on Cisco as access ports with iscsi network vlan.

 

[mst]

Can I use bonded both interfaces as 20GB pipe in FreeNas? Maybe LACP should not be used here at all.

 

[pirateghost]

FreeNAS does not "bond" the 2 links. The max any one client can get will be 10gb, but if you have lots of clients/connections on that subnet, LACP can help distribution of the bandwidth.

 

[mst]

load balance is the way to go . With a couple of VM hosts does not make sense and difference use LACP, If I had hundreds VM hosts then yes but for less than 5 hosts I don't think I should go with LACP. Simply use load balance using two 10GB on FreeNas and two 10GB on Cisco switch as access ports should be enough for my small environment.

found this http://45drives.blogspot.com/2015/07/how-to-achieve-20gb-and-30gb-bandwidth.html link with usable information

 

[mst]

adding 192.168.10.x breaks something beacuse now I not able to update or either send a test email:

Jan 10 12:25:48 freenas manage.py: in create_connection
raise err
error: [Errno 65] No route to host
Jan 10 12:29:49 freenas manage.py: [common.system:294] Failed to send email: [Errno 65] No route to host

UPDATE:

Traceback (most recent call last):
File "/usr/local/www/freenasUI/../freenasUI/system/views.py", line 1451, in update_check
train=updateobj.get_train(),
File "/usr/local/www/freenasUI/../freenasUI/system/models.py", line 573, in get_train
trains = conf.AvailableTrains() or []
File "/usr/local/lib/freenasOS/Configuration.py", line 960, in AvailableTrains
fileref = self.TryGetNetworkFile(file=TRAIN_FILE, reason="FetchTrains")
File "/usr/local/lib/freenasOS/Configuration.py", line 728, in TryGetNetworkFile
raise url_exc
URLError: <urlopen error timed out>


I can open FreeNAS GUI and ping DSN. Even with adding static route to 192.168.5.0 network no luck. When only 192.168.5.0 network exists all is fine. It has to be routing problem.