Cannot access NAS on LAGG

[ColinJack]

I'm assuming I have got something wrong (although I have been battling this for days without success) and hopefully someone will put me right.

Running 9.2.1.3 rel

I have 3 NICs - I have set em0 up as a management NIC on our normal LAN subnet (192.168.128.0/24) and created a round robin LAGG with the other two (em1 & em2) and put them into a VLAN with a different subnet to our production subnet (10.10.10.0/24) with a view to using this for the VMWare iSCSI connection. Both em0 and lagg are setup as interfaces.

I have created an iSCSI target and set the portal to 0.0.0.0

I can access iSCSI on the 192.168.128.0 subnet fine.
I cannot get any response from the LAGG interface - can't even ping it, no access to management GUI etc. Yes, I am trying to access this from the correct subnet/vlan.

I have set the options on the LAGG to 'up mtu 9000'

Can anybody tell me what I have done wrong please? This is driving me nuts!

Thanks

Colin

 

[ColinJack]

Also noticed that although I have set mtu 9000 in the options for all interfaces only em0 seems to have the correct setting:

[root@freenas] ~# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:18:71:ea:dc:55
inet 192.168.128.155 netmask 0xffffff00 broadcast 192.168.128.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 20:cf:30:06:88:3d
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 20:cf:30:06:88:3d
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ipfw0: flags=8800<SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 20:cf:30:06:88:3d
inet 10.10.10.155 netmask 0xffffff00 broadcast 10.10.10.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: active
laggproto roundrobin lagghash l2,l3,l4
laggport: em2 flags=4<ACTIVE>
laggport: em1 flags=4<ACTIVE>
vlan10: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 20:cf:30:06:88:3d
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: active
vlan: 10 parent interface: lagg0
[root@freenas] ~#

Maybe this is part of the problem?

 

[survive]

Hi ColinJack,

This might help you sidestep your problem:

Don't use lagg for iscsi, set your rig up to do MPIO instead.

-Will

 

[ColinJack]

Hi ColinJack,

This might help you sidestep your problem:

Don't use lagg for iscsi, set your rig up to do MPIO instead.

-Will

Thanks Will,

Tried that as well - just had the two interfaces on 10.10.10.0/24 subnet and still couldn't ping them ;(
That was why I tried lagg route.

Got to be something dumb! I will try taking it all apart and redoing it.

Using for VSphere and that works better with MPIO anyway.

Colin

 

[cyberjock]

Uh.... MPIO means that your 2 NICs MUST be on different subnets.

Sounds like you need some "networking 101" skills...

 

[ColinJack]

No - I must be more careful about what I type :)

I had them on 10.10.10.0/24 and 10.10.11.0/24 ... and same on vsphere

 

[ColinJack]

Redone it but no better:

[root@freenas] ~# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:18:71:ea:dc:55
inet 192.168.128.155 netmask 0xffffff00 broadcast 192.168.128.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 20:cf:30:06:88:3d
inet 10.10.10.155 netmask 0xffffff00 broadcast 10.10.10.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 20:cf:30:06:89:30
inet 10.10.20.155 netmask 0xffffff00 broadcast 10.10.20.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ipfw0: flags=8800<SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vlan10: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:00:00:00:00:00
nd6 options=9<PERFORMNUD,IFDISABLED>
vlan: 0 parent interface: <none>

[root@freenas] ~#
Not sure why I still have vlan10 left over ... deleted it using the GUI but still seems to be there. That may be part of the problem? It had em1 and em2 in it, although now showing no parent interface.
G

 

[ColinJack]

Started again from scratch (had no data on there yet) and have now got it working. Some silly mistake somewhere!
Thanks for the help.