IDISCOVER(8)

πŸ’– IDISCOVER(8) β€” like, the system manager's manual, but make it cute πŸ’–

okay bestie, sit down, we're learning about ipmiutil_discover today and honestly? it's giving network detective. ✨


🌸 NAME 🌸

ipmiutil_discover β€” go find yourself some IPMI LAN-enabled nodes πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

idiscover [-abegisx]

πŸ’… DESCRIPTION πŸ’…

so idiscover is that girl πŸ’β€β™€οΈ β€” she runs IPMI LAN commands to sniff out any nodes chilling on the LAN that are available, by probing the RMCP port (623) on those nodes. and the best part? because this utility uses IPMI LAN, you need zero IPMI drivers. no cap, none. πŸ™Œ

there are three methods she can use, and you pick one like you're picking a fit:

  • -a = the broadcast RMCP ping method (this is the default, the main character 🫢)
  • -g = the GetChannelAuthCap command method
  • else = the specific RMCP ping method

you can also hand her a beginning IP address with -b, and that works for both the broadcast and specific methods. an ending IP can be specified for the non-broadcast methods. 🌈


✨ OPTIONS ✨

the command line options, explained below. slay.

  • -a β€” All nodes, using the broadcast ping method. this is the default if you specify no options at all (she just knows what to do πŸ’…). it'll detect the first enabled ethernet interface, and it defaults to the broadcast address x.x.x.255 (where x.x.x.x is the IP address) β€” unless you use -b to specify otherwise. πŸ‘‘
  • -b <ip> β€” Beginning IP address. this one is required, unless you're using broadcast with the defaults. it could be a specific IP address, or a broadcast address ending in 255 if you're using the broadcast method (-a). πŸ“
  • -e <ip> β€” Ending IP address of the range. not used for the broadcast method. if you don't specify this, a range of one IP address matching the beginning IP is assumed. so it's just her, alone, one IP. 😭
  • -g β€” use the GetChannelAuthenticationCapabilities command method over IPMI LAN instead of the RMCP ping. not compatible with broadcast, bestie, don't even try it. this may be useful if the vendor BMC does not support RMCP ping for some reason. 🧚
  • -i eth0 β€” the interface name to use when sending the probes. the default is to detect the first enabled ethernet interface (e.g. eth0). 🌸
  • -m β€” shows MAC address. uses the broadcast ping method, but uses a raw socket so that the MAC address can be displayed. this detects the first enabled ethernet interface, and defaults to the broadcast address 255.255.255.255 like -a does. > heads up: using -m with raw sockets requires root privilege. πŸ”₯
  • -r N β€” repeat the ping N times to each node. default is to send 1 ping per node. consistency, queen. πŸ’œ
  • -x β€” causes extra debug messages to be displayed. for when you need to see everything. πŸ”

🌈 EXAMPLES 🌈

idiscover -a -b 192.168.1.255

sends a broadcast RMCP ping to discover IPMI LAN nodes on the specified subnet. πŸŽ€

idiscover -b 192.168.1.100 -e 192.168.1.254

sends RMCP pings to a range of IP addresses. πŸ“‘

idiscover -g -b 192.168.1.100 -e 192.168.1.254

sends GetChannelAuthCap commands to a range of IP addresses. ✨


🫢 SEE ALSO 🫢

ipmiutil(8) ialarms(8) iconfig(8) icmd(8) ievents(8) ifru(8) igetevent(8) ihealth(8) ilan(8) ireset(8) isel(8) isensor(8) iserial(8) isol(8) iwdt(8)

the whole friend group, honestly. 😌


⚠️ WARNINGS ⚠️

See http://ipmiutil.sourceforge.net/ for the latest version of ipmiutil and any bug fix list. go check it, bestie, don't be running stale software. πŸ’€

Copyright (C) 2009 Kontron America, Inc.

See the file COPYING in the distribution for more details regarding redistribution.

This utility is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. (she's doing her best, ok 😭)


πŸ’– AUTHOR πŸ’–

Andy Cress <arcress at users.sourceforge.net>


and that's the whole page!! this one's Version 1.0, dated 02 May 2007 β€” an icon, a legend, and she's still out here discovering nodes. periodt. πŸ’…βœ¨