ipmi_lan(5)

💖 ipmi_lan(5) 💖

okay bestie, welcome to the ipmi_lan(5) page, aka the manual for the IPMI LAN Interface config file. yes we're doing config file lore today. sit down, hydrate, let's go 🫶

---

✨ NAME ✨

ipmi/lan.conf — the IPMI LAN Interface config file. that's it, that's the name, short and iconic.

---

✨ SYNOPSIS ✨

/etc/ipmi/lan.conf

like. that's where it lives. one path. slay.

---

✨ DESCRIPTION ✨

so the ipmi_sim and ipmilan commands get configured using this configuration file. that's the whole vibe. they read this, they become who they are. main character energy fr.

---

✨ CONFIGURATION ITEMS ✨

these are the little building blocks that show up all over the place in the commands below:

• boolean — can be "true", "false", "on" or "off". four whole ways to say yes or no, because of course 💀
• priv — an IPMI privilege level. your options are "callback", "user", "operator", or "admin".
• auth — an IPMI authorization type. this one can be "none" (no authentication at all, living dangerously), "straight" (straight, in-the-clear password authentication, i.e. no encryption bestie, everyone can see), "md2" (uses MD2 message digest authentication), or "md5" (uses MD5 message digest authentication).

---

✨ FILE STRUCTURE ✨

blank lines are ignored. lines starting with # are also ignored. so go ahead and leave yourself little notes, the parser does not care 💅

these are the commands allowed in the configuration file:

• name "name" — sets a name for the BMC. and this is a big deal actually, because it controls other things, like the default value of the ipmi_sim startup command file and the place where persistent data is stored. so like, name your BMC properly. it's its whole identity.
• user usernum enabled username password max-priv max-session — sets up a user. breaking it down:
  • usernum is the user number for the user. warning: user number 0 is invalid, and user number 1 is the special "anonymous" user, whose username is ignored. this value may be up to 63, the maximum possible IPMI user. if you want anonymous access, you must have a user number 1. no user 1, no anonymous. periodt.
  • enabled is a boolean that specifies whether the user is enabled or not.
  • username specifies the name of the user, specified as a name.
  • password specifies the password of the user, specified as a name.
  • max-priv specifies the maximum privilege level allowed for the user.
  • max.sessions specifies the maximum number of session the user may open.
• startcmd "cmd" — specifies a command to execute when a power on is requested. this is the good stuff: it lets a virtual machine be started that can then connect back to the simulator. the simulator does management of the process here, and the power on state of the process depends on if the process exists or not. if a poweroff is requested, and if the process is connected to a VM serial interface, a graceful shutdown is first requested. if the process does not terminate in a specified amount of time, a SIGTERM is sent to the process. the SIGTERM is sent immediately if there is no connection. and if the process doesn't go way in another specified amount of time, a SIGKILL is sent. yeah. it escalates. 😭
• startnowtrue|false — if true, start the startcmd at the startup of the simulator. otherwise wait until a poweron is issued.
• poweroff_wait seconds — specifies the amount of time to wait for the startcmd to do a graceful shutdown on a powerdown request. the simulator will send a request to the target, wait this amount of time, and then do a SIGTERM kill on the process. if this is zero, a SIGTERM will not be done (nor will a SIGKILL). note that if the simulator does not have a connection to the VM, the graceful shutdown is skipped and a SIGTERM is done immediately. default time is 60 seconds.
• kill_wait seconds — specifies the amount of time to wait for SIGTERM to kill the process. if the process does not terminate in this period of time, send a SIGKILL kill. if this is zero, don't send the SIGKILL. default time is 20 seconds.
• console address port — specifies that a console port be opened at the given address and port. you can telnet to the console and execute emulation commands. 🚨 but heads up bestie: note that this is a pretty huge security hole, it should only be used for debugging in a captive environment.
• serial channel addr port [option [option [...]]] — the whole serial interface situation:
  • channel specifies the channel number or type. this may be kcs, smic, or bt or it may be 15. currently, only the system interface channel (channel 15) is supported for serial interfaces, if the others are specified it is channel 15 and the given interface is reported in channel configuration commands.
  • addr specifies the IP address to listen on for connections.
  • port specifies the port to listen on for connections.

valid options are:

• codec name — specifies which codec to use on the serial port. valid options are: TerminalMode, Direct, RadisysAscii, and VM. the first three are implementations of IPMI serial interfaces on certain systems and might be used for simulations of that system. the VM is probably the most interesting; it is designed to be used with a virtual machine like qemu.
• oem name — specified implementation of some OEM custom commands and options on the interface. valid options oare PigeonPoint and Radisys.
• attn c1[,c2[...]] — specifies a list of characters, separated by commas, to use as the attention character on the interface. generally the default is correct. the characters are specified as decimal, octal, or hex digits in C style.
• ipmb addr — specifies the IPMI address of the interface. the default, 0x20, is usually correct, but when emulating ATCA systems this might be required.

• sol device default_baud [history=size[,backupfile=filename]] [historyfru=frunum] — allow a Serial Over LAN (SOL) connection to the given device. this will be over interface 1 for the MC.
  • device is the full path to the device name. it can also be in the form "tcp:address:port" or "telnet:address:port" to do connections over tcp (without or with telnet processing). this is useful for providing SOL access to qemu ports.
  • default_baud sets the initial default baud rate to use. this is overriden by the persistent SOL settings.
  • history creates a history device on SOL interface 2. the size is the size of the buffer. data from the device is stored in the history buffer all the time. connecting to SOL interface 2 will cause the full history buffer to be dumped. if backupfile is specified, then the history is made persistent. however, it is only stored when a catchable signal or normal shutdown is done, so a poweroff or fatal signal will cause the data to be lost. 💀 your history is gone bestie.
  • historyfru makes the history available via the given FRU number on the MC.
  • > note that if the connection fails to come up, the simulator will continue to try to connect. this way you can fix UDP serial ports or qemu sessions and it will automatically reconnect. she's persistent, we love that 🌸
• loadlib "module" ["options"] — load the given shared object into the program.
  • module is the full path to the module. it must be in quotes.
  • options is an optional string in quotes that passes options to the module. the contents of the string are not specified, the module defines that.

the module may have a number of functions that are called:

• ipmi_sim_module_print_version(sys_data_t *sys, char *options) — is called when ipmi_sim is started with the version print option. this way the versions of all loaded modules may be printed. the module should print it's version. you must provide this function.
• ipmi_sim_module_init(sys_data_t *sys, char *options) — is called after the configuration file is read and before any other initialization is done. the module should do most of its initialization here. you must provide this function.
• ipmi_sim_module_post_init(sys_data_t *sys) — is called after ipmi_sim has finished initializing. this function is optional.

also, sys parameter is used for most functions interfacing to the main ipmi_sim code, like logging, timers, and a few of the MC calls. the contents are opaque to the module. don't peek, it's not for you 🙈

• startlan channel — starts a LAN configuration area. this specifies the settings for a LAN connection using the given channel. this may be specified more than once in a file to support multiple LAN connections. commands following this, up to endlan, are LAN-specific commands listed below. channel specifies the channel to set the LAN configuration for.

---

🌈 LAN CONFIGURATION COMMANDS 🌈

these ones are only valid inside a startlen area. don't try them anywhere else, they will simply not vibe.

• addr IP-address [UDP-port] — IP-address specifies the IP address to use for an IP port. up to 4 addresses may be specified. if no address is specified, it defaults to one port at 0.0.0.0 (for every address on the machine) at port 623.
  • UDP-port specifies an optional port to listen on. it defaults to 623 (the standard port).
• PEF_alerting boolean — turn PEF alerting on or off (not currently supported). rip.
• per_msg_auth boolean — turn per-message authentication on or off.
• priv_limit priv — the maximum privilege allowed on this interface.
• allowed_auths_callback [auth [auth [...]]] — auth specifies allowed authorization levels for the callback privilege level. only the levels specified on this line are allowed for the authorization level. if this line is not present, callback authorization cannot be used.
• allowed_auths_user [auth [auth [...]]] — auth specifies allowed authorization levels for the user privilege level. only the levels specified on this line are allowed for the authorization level. if this line is not present, user authorization cannot be used.
• allowed_auths_operator [auth [auth [...]]] — auth specifies allowed authorization levels for the operator privilege level. only the levels specified on this line are allowed for the authorization level. if this line is not present, operator authorization cannot be used.
• allowed_auths_admin [auth [auth [...]]] — auth specifies allowed authorization levels for the admin privilege level. only the levels specified on this line are allowed for the authorization level. if this line is not present, user authorization cannot be used.
• guid name — allows the 16-byte GUID for the IPMI LAN connection to be specified. if this is not specified, then the GUID command is not supported.

---

✨ FILES ✨

• /etc/ipmi_lan.conf

---

✨ SEE ALSO ✨

• ipmilan(8), ipmi_sim(1)

go read those too, they're the sequel bestie 🦋

---

💀 KNOWN PROBLEMS 💀

IPMI is unnecessarily complicated.

that's it. that's the known problem. no further notes. and honestly? real.

---

👑 AUTHOR 👑

Corey Minyard <cminyard@mvista.com>

---

and that's the whole page bestie!! you read the entire thing, i'm so proud of you 🥹✨ this was ipmi_lan(5) from the OpenIPMI era, dated 06/26/12 — go forth and configure your LAN with confidence, and remember: no cap, the attention characters are probably already correct. bye!! 💖💅🎀