Last week i bought a used X9SCM-iiF on ebay, threw in a E3-1225v2 (according to SM the E3-xxx5 variants with integrated graphics are not 'recommended', for now i assume that doesn't cause the IPMI issue..) and 2x8GB DDR3. It's working fine except the IPMI is causing trouble;
The IPMI interface wasn't pulling an IP via DHCP on its dedicated NIC, so i've set a static one trough BIOS and rebooted (complete power off, i read a lot of horror stories about SM IPMI..) but couldn't ping the address, BIOS says IPMI is 'working' and shows the correct settings. I checked the other 2 ports as well, nothing, so i installed Win7 on the machine to be able to use the ipmitools from SM. I found IPMICFG and used -fed to reset to factory defaults, rebooted and tried configuring it from scratch to no avail, still no ping to the set address.
Next stop: firmware updates. I got the latest IPMI firmware and while i was already at it, updated the BIOS as well with the FreeDOS bootdisk method. Went fine, still the same issues. So i started suspecting my network, specifically my switch (1820-24G). The port i connected the IPMI NIC to was configured for VLAN1, untagged at that time. I tried setting VLAN tag through IPMICFG, different settings on the switch port (tagged/untagged, even in non-sensical combinations) and after nothing helped tried different switch ports. Still nothing.
Out of pure frustration (and after contemplating ditching IPMI on that machine alltogether) i put a live ubuntu disk in my notebook (to have nothing VLAN related in the network configs) and connected that directly to the IPMI and BAM, link. I proceeded to open the webGUI, set the IPMI NIC config to 'dedicated', rebooted (via power off) and connected the IPMI NIC to an untagged port on the switch again: again no connection. The link LED on the jack is lit alright.
I tried disabling jumbo frames on the switch which is (apart from VLAN) the only setting that sets this switch apart from a 'dumb' switch. Do you have any idea in which direction i should look or might this be a busted IPMI? Maybe for some reason it just hates my switch?
FWIW, after the IPMI firmware update the SuperDoctor program (as well as the IPMI webGUI) didn't show the CPU temp anymore, only 'LOW' and 'MEDIUM' and the other 2 temps are both displayed as 28°C and 34°C statically which must be bogus, during a Prime95 test the CPU went up to 78°C (transitioned from 'LOW' to 'MEDIUM' which i would consider 'HIGH'..) and the exhaust air was quite warm , the other system temps must have changed during that time but always show 28/34. Memtest86 shows plausible CPU temps though so the on-die sensors must be fine. I'm quite certain the CPU temp value was displayed as °C before the firmware update.
The IPMI interface wasn't pulling an IP via DHCP on its dedicated NIC, so i've set a static one trough BIOS and rebooted (complete power off, i read a lot of horror stories about SM IPMI..) but couldn't ping the address, BIOS says IPMI is 'working' and shows the correct settings. I checked the other 2 ports as well, nothing, so i installed Win7 on the machine to be able to use the ipmitools from SM. I found IPMICFG and used -fed to reset to factory defaults, rebooted and tried configuring it from scratch to no avail, still no ping to the set address.
Next stop: firmware updates. I got the latest IPMI firmware and while i was already at it, updated the BIOS as well with the FreeDOS bootdisk method. Went fine, still the same issues. So i started suspecting my network, specifically my switch (1820-24G). The port i connected the IPMI NIC to was configured for VLAN1, untagged at that time. I tried setting VLAN tag through IPMICFG, different settings on the switch port (tagged/untagged, even in non-sensical combinations) and after nothing helped tried different switch ports. Still nothing.
Out of pure frustration (and after contemplating ditching IPMI on that machine alltogether) i put a live ubuntu disk in my notebook (to have nothing VLAN related in the network configs) and connected that directly to the IPMI and BAM, link. I proceeded to open the webGUI, set the IPMI NIC config to 'dedicated', rebooted (via power off) and connected the IPMI NIC to an untagged port on the switch again: again no connection. The link LED on the jack is lit alright.
I tried disabling jumbo frames on the switch which is (apart from VLAN) the only setting that sets this switch apart from a 'dumb' switch. Do you have any idea in which direction i should look or might this be a busted IPMI? Maybe for some reason it just hates my switch?
FWIW, after the IPMI firmware update the SuperDoctor program (as well as the IPMI webGUI) didn't show the CPU temp anymore, only 'LOW' and 'MEDIUM' and the other 2 temps are both displayed as 28°C and 34°C statically which must be bogus, during a Prime95 test the CPU went up to 78°C (transitioned from 'LOW' to 'MEDIUM' which i would consider 'HIGH'..) and the exhaust air was quite warm , the other system temps must have changed during that time but always show 28/34. Memtest86 shows plausible CPU temps though so the on-die sensors must be fine. I'm quite certain the CPU temp value was displayed as °C before the firmware update.