maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On 31/10/13 16:59, Julian Edwards wrote:
> I've attached a prototype script that works out the IP addresses of all the 
> BMCs it can find in the network range that you specify.
> 
> It works by nmap probing the RMCP port in the IP range and if it sees a 
> response it's already likely to be a BMC, but then goes on to verify it by 
> issuing an ipmiping command.
> 
> Seems to work in the lab at least:
> 
> ubuntu@lenovo-RD230-01:~$ ./bmc-detect.py 192.168.21.255/24
> ['192.168.21.50', '192.168.21.51', '192.168.21.52', '192.168.21.53']
> 
> I'm sure we can use this as inspiration to do something better inside the 
> pserv process.
> 
> 
> 

I found another way and it's simpler, but does have a drawback:

ubuntu@maas:~$ rmcp_ping
10-0-0-102.master IPMI
10-0-0-101.master IPMI

It's printing hostnames instead of IPs, which is rather annoying.

rcmp_ping is from the openipmi package and does broadcast pings by
default.  It's a shame ipmiping doesn't do that, and seemingly can't be
made to do it either:

ubuntu@maas:~$ sudo ipmiping 255.255.255.255
ipmiping 255.255.255.255 (255.255.255.255)
ipmiping: ipmi_sendto: Permission denied