BTW
Dabbler
- Joined
- Feb 1, 2014
- Messages
- 33
Hello,
I am relatively new to FreeNAS, so apologizes if this is a newbie question/problem.
**Please see below for system details and configurations**
Problem:
I have a new build of Freenas 9.2. This system has 3 nics (two as a lagg [lagg0] for iSCSI and one for management [re2]). I also have VLAN interface configured with IP's assigned to the VLAN interfaces. The problem is that my network configurations say all interfaces are active after a reboot but no traffic is passed (if i try to ping anything, receive "host not up").
Workaround:
I will enter the shell and type the following commands (in order), my network works fine:
What I can assume is the VLANs are trying to come up before the actual interfaces are fully active. If i just restart the physical interface + lagg0, it does not fix the network. I have to bring all physical interfaces + lagg0 up then the VLANs.
I have also attached files with outputs from "ifconfig" & "ifconfig -m" while the system is functioning and not (I did not want to paste in the thread as they are long). The only main difference I can see is:
I also tried this with a completely fresh install of FreeNAS and only one nic (onboard) and get the exact same results.
Any help?
Thanks
System Details:
MoBo = Asus E35M1-I Deluxe
Nic = dual port Startech
Switch = Cisco 3650 (I also tried this with a Netgear GB and DLink hub, same results)
FreeNAS = FreeNAS-9.2.0-RELEASE-x64 (ab098f4)
Network Conf = re0 + re1 > lagg0
re2 > standalone
vlan220 > 192.168.15.16/24
vlan221 > 192.168.8.110/24
default route > 192.168.8.1
I am relatively new to FreeNAS, so apologizes if this is a newbie question/problem.
**Please see below for system details and configurations**
Problem:
I have a new build of Freenas 9.2. This system has 3 nics (two as a lagg [lagg0] for iSCSI and one for management [re2]). I also have VLAN interface configured with IP's assigned to the VLAN interfaces. The problem is that my network configurations say all interfaces are active after a reboot but no traffic is passed (if i try to ping anything, receive "host not up").
Workaround:
I will enter the shell and type the following commands (in order), my network works fine:
Code:
ifconfig re0 down ifconfig re1 down ifconfig re2 down ifconfig lagg0 down ifconfig vlan220 down ifconfig vlan221 down ifconfig re0 up ifconfig re1 up ifconfig re2 up ifconfig lagg0 up ifconfig vlan220 up ifconfig vlan221 up
What I can assume is the VLANs are trying to come up before the actual interfaces are fully active. If i just restart the physical interface + lagg0, it does not fix the network. I have to bring all physical interfaces + lagg0 up then the VLANs.
I have also attached files with outputs from "ifconfig" & "ifconfig -m" while the system is functioning and not (I did not want to paste in the thread as they are long). The only main difference I can see is:
- When the system first boots
- media of interface = 10baseT/UTP <half-duplex>
- When I run the commands to fix
- media of interface = 1000baseT <full-duplex>
I also tried this with a completely fresh install of FreeNAS and only one nic (onboard) and get the exact same results.
Any help?
Thanks
System Details:
MoBo = Asus E35M1-I Deluxe
Nic = dual port Startech
Switch = Cisco 3650 (I also tried this with a Netgear GB and DLink hub, same results)
FreeNAS = FreeNAS-9.2.0-RELEASE-x64 (ab098f4)
Network Conf = re0 + re1 > lagg0
re2 > standalone
vlan220 > 192.168.15.16/24
vlan221 > 192.168.8.110/24
default route > 192.168.8.1
Attachments
-
notworking_network.txt2.6 KB · Views: 405
-
notworking_nic_lagg0.txt540 bytes · Views: 388
-
notworking_nic_re0.txt1 KB · Views: 385
-
notworking_nic_re1.txt1 KB · Views: 359
-
notworking_nic_re2.txt974 bytes · Views: 393
-
notworking_nic_vlan220.txt460 bytes · Views: 384
-
notworking_nic_vlan221.txt486 bytes · Views: 413
-
working_network.txt2.6 KB · Views: 469
-
working_nic_lagg0.txt529 bytes · Views: 358
-
working_nic_re0.txt1 KB · Views: 398