July 20, 201213 yr I have one cable connected to the server in the port shown as ethernet 1 in the manual...NOT the IPMI dedicated port. Unraid comes up, and I can get IPMI working. eth0 shows that it has link, and has the correct IP address on it...but it is unreachable from the network and it can't get out. The odd thing is that Linux has 192.168.1.2 configured on eth0 as it should, but IPMI shows up in the scan as 192.168.1.154 I'm not sure how to track this one down. Should I just disable both of the onboard eth ports and use the IPMI port....or....amm. I'm actually out of ideas.
July 20, 201213 yr Author Tried to get the syslog, but without network it is kind of a pain. It is finding eth0 with the e1000e driver
July 20, 201213 yr Can you ping 192.168.1.2 from another PC? You didnt say what version of unraid you running. due to different E1000 drivers, 4.7 uses one NIC and 5.x uses the OTHER NIC. This is because of the order they are seen during boot. The best solution is run a separate cable for the IPMI to the IPMI port then a data cable to the data port. the IPMI port only needs 10/100 if thats easier for you.
July 20, 201213 yr Author Nope, I can fire up IPMI and it works just fine, but nothing from eth0. This is 5.0-rc5 I've restarted and have the IPMI port connected (The one next to the keyboard jack, just over the USB ports) and the closest ethernet port to the power supply (of the two "normal" ports).
July 20, 201213 yr Author Ahhh, I think I see what you are saying. Let me reboot again with the ethernet cable in the other on-board port.
July 20, 201213 yr Author That was it...how silly of me...just had it in the wrong port. Sorry for the stupid question!
Archived
This topic is now archived and is closed to further replies.