So, I've been experimenting with implementing 10Gb stuffs on my home network given that it's now becoming reasonably cheap and power-efficient to do so. One of the surprising caveats I ran into was realising that apparently neither of the Intel NIC's I'm using support Wake-on-LAN (something I use in combination with rtcwake on my backup server).
No problem says I, I'll just replace those routines with the handy ipmitool and use that to wake up the box instead. However I couldn't get it to work against my backup server, and on further testing I couldn't get it to work against other motherboards either. ssh and http work fine of course.
Basically every command I end up throwing at the IPMI interface fails with an error that indicates it's unable to communicate with it:
I figured it might be a firewall issue of some description but even after turning off all the rules between my regular server LAN and the IPMI LAN, I got the same result.
Bizarrely however, ipmitool remoting to offsite works perfectly:
Is there some IPMI setting I need to flip or some firewall ports that need opening? The only discrepancy I can see in the nmap scans of working vs. non-working hosts is 623/udp being shown as "filtered";
Working host nowwhat (offsite):
Non-working host lamuella:
The only thing I could find on the net matching the above was a Dell user (not Supermicro) although there was mention there that a setting needed to be changed to allow the IPMI interface to accept remote instructions; does such a thing need to be done for some SM boards? I did worry it was the firewall rules I use to govern access from one VLAN to the other, but even disabling them temporarily made no difference.
And failing that, does anyone have any idea what might be wrong with my IPMI setup here?
No problem says I, I'll just replace those routines with the handy ipmitool and use that to wake up the box instead. However I couldn't get it to work against my backup server, and on further testing I couldn't get it to work against other motherboards either. ssh and http work fine of course.
Basically every command I end up throwing at the IPMI interface fails with an error that indicates it's unable to communicate with it:
Code:
effrafax@wug:~$ ipmitool -v -I lanplus -H lamuella -U admin power status
Password:
Get Auth Capabilities error
Error issuing Get Channel Authentication Capabilities request
Error: Unable to establish IPMI v2 / RMCP+ session
Bizarrely however, ipmitool remoting to offsite works perfectly:
Code:
effrafax@wug:~$ ipmitool -I lanplus -H nowwhat.ipmi -U admin power status
Password:
Chassis Power is on
Working host nowwhat (offsite):
Code:
root@wug:~# nmap nowwhat.ipmi
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp open https
5900/tcp open vnc
root@wug:~# nmap -sU nowwhat.ipmi
PORT STATE SERVICE
123/udp open ntp
623/udp open asf-rmcp
Code:
root@wug:~# nmap lamuella.ipmi
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp open https
5900/tcp open vnc
root@wug:~# nmap -sU lamuella.ipmi
PORT STATE SERVICE
123/udp open ntp
623/udp open|filtered asf-rmcp
And failing that, does anyone have any idea what might be wrong with my IPMI setup here?