friolator
Explorer
- Joined
- Jun 9, 2016
- Messages
- 80
First, two things happpened:
1) I realized that the IPv4 Default Gateway was the wrong IP address in the FreeNAS GUI, so I changed it to the correct address.
2) Checked for FreeNAS updates and saw 9.10.1, so I installed that
Upon reboot, our 40Gb network isn't working. FreeNAS shows the link to the switch as active, the switch shows everything as ok, and the other machine on that network looks to be fine. That network is on a different subnet (using 10.0.0.2/8 for the FreeNAS server and 10.0.0.4/8 for the one workstation on the network). Our gigabit network (which the FreeNAS admin interface is accessed through), is on 192.168.1.*/24. The Default gateway I specified in step 1 is 192.168.1.1
I don't think they're related, but I figured I'd throw that out there in case I haven't had enough coffee yet.
When I check ifconfig, I see that the 40Gb network interface (cxl0) isn't getting an IP address, and that it's showing the wrong MTU (should be 9614). But the gigabit network (igb0) looks right, and has an IP address. The Admin UI shows the IP for cxl0 as 10.0.0.2/8 with the custom MTU setting.
Any idea what's going on here? It was working fine before the upgrade/reboot.
1) I realized that the IPv4 Default Gateway was the wrong IP address in the FreeNAS GUI, so I changed it to the correct address.
2) Checked for FreeNAS updates and saw 9.10.1, so I installed that
Upon reboot, our 40Gb network isn't working. FreeNAS shows the link to the switch as active, the switch shows everything as ok, and the other machine on that network looks to be fine. That network is on a different subnet (using 10.0.0.2/8 for the FreeNAS server and 10.0.0.4/8 for the one workstation on the network). Our gigabit network (which the FreeNAS admin interface is accessed through), is on 192.168.1.*/24. The Default gateway I specified in step 1 is 192.168.1.1
I don't think they're related, but I figured I'd throw that out there in case I haven't had enough coffee yet.
When I check ifconfig, I see that the 40Gb network interface (cxl0) isn't getting an IP address, and that it's showing the wrong MTU (should be 9614). But the gigabit network (igb0) looks right, and has an IP address. The Admin UI shows the IP for cxl0 as 10.0.0.2/8 with the custom MTU setting.
Code:
[root@freenas] ~# ifconfig cxl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:28:a5:e0 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet 40Gbase-CR4 <full-duplex> status: active cxl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> ether 00:07:43:28:a5:e8 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet none status: no carrier igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO> ether 0c:c4:7a:ac:26:94 inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex>) status: active igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO> ether 0c:c4:7a:ac:26:95 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: no carrier 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 0x5 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Any idea what's going on here? It was working fine before the upgrade/reboot.