Stephen P.
Cadet
- Joined
- May 7, 2017
- Messages
- 5
Good afternoon everyone,
I will start with a big thanks to all in this forum as reading it has been greatly helpful as I am quite new to FreeNAS.
To start I would like to describe my setup slightly... I have a FreeNAS system directly connected to 3 cluster nodes and 1 backup server. The direct connection is made on 2 dual port 40GbE ChelsIO NICs (T580-SO-CR). With the connections I wanted to allow the cluster nodes to communicate with eachother over this high speed connection, therefore I create a bridge on boot every startup as I was unable to find a way to do it in the GUI (not a complaint just an observation). The 40GbE link works great between servers and works wonders on my iSCSI as well as live VM migrations between cluster nodes although it seems sometimes to get timeouts when the system gets really busy. Therefore because I also have our local lan interfaces (LACP bonded) I wanted to setup MPIO with a fail-over for my iSCSI.
When I go to set them up in the GUI I am faced with a problematic situation, when adding a Portal I am only given options for the "lagg0" (1Gb bonds) or "0.0.0.0" (all IPs). This would not be an issue other than the windows systems that I connect it to understand them as the same thing. I am hoping that someone may point me in the direction of directly editing the config in the raw DB that creates "/etc/ctl.conf" as if I edit the ctl.conf file and modify the 0.0.0.0 to my "private" 40GbE ip and keep my lagg0 ip than it works.. but every time I modify the iSCSI settings on the gui the file is overwritten. If this is not possible is there any way that I can manually enter a "listen" ip for my portal as opposed to using the drop-down that is on there.
I really appreciate anyone's help in advance!
Thanks;
Stephen
This block is the code I use to create the bridge for use with FreeNAS (run at boot)
The following is the pertinent data from my ifconfig output.
This is the snippet from ctl.conf
ORIG:
Changed/Working (but overwritten every time GUI is modified):
I added a couple other screenshots in here as I noticed that the reporting shows the stats and existance of the bridge and it's interfaces but "Interfaces" under "Networking" does not. Also it is possible to see the bridge in the "Network Summary"
I will start with a big thanks to all in this forum as reading it has been greatly helpful as I am quite new to FreeNAS.
To start I would like to describe my setup slightly... I have a FreeNAS system directly connected to 3 cluster nodes and 1 backup server. The direct connection is made on 2 dual port 40GbE ChelsIO NICs (T580-SO-CR). With the connections I wanted to allow the cluster nodes to communicate with eachother over this high speed connection, therefore I create a bridge on boot every startup as I was unable to find a way to do it in the GUI (not a complaint just an observation). The 40GbE link works great between servers and works wonders on my iSCSI as well as live VM migrations between cluster nodes although it seems sometimes to get timeouts when the system gets really busy. Therefore because I also have our local lan interfaces (LACP bonded) I wanted to setup MPIO with a fail-over for my iSCSI.
When I go to set them up in the GUI I am faced with a problematic situation, when adding a Portal I am only given options for the "lagg0" (1Gb bonds) or "0.0.0.0" (all IPs). This would not be an issue other than the windows systems that I connect it to understand them as the same thing. I am hoping that someone may point me in the direction of directly editing the config in the raw DB that creates "/etc/ctl.conf" as if I edit the ctl.conf file and modify the 0.0.0.0 to my "private" 40GbE ip and keep my lagg0 ip than it works.. but every time I modify the iSCSI settings on the gui the file is overwritten. If this is not possible is there any way that I can manually enter a "listen" ip for my portal as opposed to using the drop-down that is on there.
I really appreciate anyone's help in advance!
Thanks;
Stephen






This block is the code I use to create the bridge for use with FreeNAS (run at boot)
Code:
#!/bin/bash ifconfig cxl0 up ifconfig cxl1 up ifconfig cxl2 up ifconfig cxl3 up ifconfig bridge create ifconfig bridge0 addm cxl0 addm cxl1 addm cxl2 addm cxl3 ifconfig bridge0 inet 10.20.0.5 netmask 255.255.255.0
The following is the pertinent data from my ifconfig output.
Code:
cxl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec03bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:3b:29:00 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 40Gbase-CR4 <full-duplex> status: active cxl1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec03bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:3b:29:08 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 40Gbase-CR4 <full-duplex> status: active ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 0c:c4:7a:de:d6:1e nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex,rxpause,txpause>) status: active ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 0c:c4:7a:de:d6:1e nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex,rxpause,txpause>) status: active cxl2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec03bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:3b:23:a0 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 40Gbase-CR4 <full-duplex> status: active cxl3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec03bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:3b:23:a8 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 40Gbase-CR4 <full-duplex> status: active lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=e407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> ether 0c:c4:7a:de:d6:1e inet 10.5.0.37 netmask 0xfffffc00 broadcast 10.5.3.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: active laggproto loadbalance lagghash l2,l3,l4 laggport: ix0 flags=4<ACTIVE> laggport: ix1 flags=4<ACTIVE> bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 02:8f:0e:fe:68:00 inet 10.20.0.5 netmask 0xffffff00 broadcast 10.20.0.255 nd6 options=1<PERFORMNUD> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: cxl3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 6 priority 128 path cost 2000000 member: cxl2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 5 priority 128 path cost 55 member: cxl1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 2 priority 128 path cost 55 member: cxl0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 1 priority 128 path cost 55
This is the snippet from ctl.conf
ORIG:
Code:
portal-group pg1 { discovery-filter portal-name discovery-auth-group no-authentication listen 0.0.0.0:3260 listen 10.5.0.37:3260 option ha_shared on }
Changed/Working (but overwritten every time GUI is modified):
Code:
portal-group pg1 { discovery-filter portal-name discovery-auth-group no-authentication listen 10.20.0.5:3260 listen 10.5.0.37:3260 option ha_shared on }
I added a couple other screenshots in here as I noticed that the reporting shows the stats and existance of the bridge and it's interfaces but "Interfaces" under "Networking" does not. Also it is possible to see the bridge in the "Network Summary"