1bmc-config.conf(5) System Commands bmc-config.conf(5)
2
6 bmc-config - BMC configuration file format and details
7
9 Before many IPMI tools can be used over a network, a machine's Base‐
10 board Management Controller (BMC) must be configured. The configuration
11 of a BMC can be quite daunting for those who do not know much about
12 IPMI. This manpage hopes to provide enough information on BMC configu‐
13 ration so that you can configure the BMC for your system. When appro‐
14 priate, typical BMC configurations will be suggested.
15 The following is an example BMC configuration file partially generated
17 from the bmc-config(1) command. This example configuration should be
18 sufficient for most users after the appropriate local IP and MAC
19 addresses are input. Following this example, separate sections of this
20 manpage will discuss the different sections of the BMC configuration
21 file in more detail with explanations of how the BMC can be configured
22 for different environments.
23 Note that many options may or may not be available on your particular
25 machine. For example, Serial-Over-Lan (SOL) is available only on IPMI
26 2.0 machines. Therefore, if you are looking to configure an IPMI 1.5
27 machine, many of the SOL or IPMI 2.0 related options will be be
28 unavailable to you. The number of configurable users may also vary for
29 your particular machine.
30 The below configuration file and most of this manpage assume the user
32 is interested in configuring a BMC for use with IPMI over LAN. Various
33 configuration options from bmc-config(1) have been left out or skipped
34 because it is considered unnecessary. Future versions of this manpage
35 will try to include more information.
36 Section User1
38 ## Give username
39 ## Username NULL
40 ## Give password or leave it blank to clear password
41 Password mypassword
42 ## Possible values: Yes/No or blank to not set
43 Enable_User Yes
44 ## Possible values: Yes/No
45 Lan_Enable_Ipmi_Msgs Yes
46 ## Possible values: Callback/User/Operator/Administrator/OEM_Pro‐
47 prietary/No_Access
48 Lan_Privilege_Limit Administrator
49 ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if
50 not specified
51 ## Lan_Session_Limit
52 ## Possible values: Yes/No
53 SOL_Payload_Access Yes
54 EndSection
55 Section User2
56 ## Give username
57 Username user2
58 ## Give password or leave it blank to clear password
59 Password userpass
60 ## Possible values: Yes/No or blank to not set
61 Enable_User No
62 ## Give password for IPMI 2.0 or blank to clear. MAX 20 chars.
63 Lan_Enable_Ipmi_Msgs No
64 ## Possible values: Callback/User/Operator/Administrator/OEM_Pro‐
65 prietary/No_Access
66 Lan_Privilege_Limit No_Access
67 ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if
68 not specified
69 ## Lan_Session_Limit
70 ## Possible values: Yes/No
71 SOL_Payload_Access No
72 EndSection
73 Section Lan_Channel
74 ## Possible values: Disabled/Pre_Boot_Only/Always_Avail‐
75 able/Shared
76 Volatile_Access_Mode Always_Available
77 ## Possible values: Yes/No
78 Volatile_Enable_User_Level_Auth Yes
79 ## Possible values: Yes/No
80 Volatile_Enable_Per_Message_Auth Yes
81 ## Possible values: Yes/No
82 Volatile_Enable_Pef_Alerting No
83 ## Possible values: Callback/User/Operator/Administrator/OEM_Pro‐
84 prietary/No_Access
85 Volatile_Channel_Privilege_Limit Administrator
86 ## Possible values: Disabled/Pre_Boot_Only/Always_Avail‐
87 able/Shared
88 Non_Volatile_Access_Mode Always_Available
89 ## Possible values: Yes/No
90 Non_Volatile_Enable_User_Level_Auth Yes
91 ## Possible values: Yes/No
92 Non_Volatile_Enable_Per_Message_Auth Yes
93 ## Possible values: Yes/No
94 Non_Volatile_Enable_Pef_Alerting No
95 ## Possible values: Callback/User/Operator/Administrator/OEM_Pro‐
96 prietary/No_Access
97 Non_Volatile_Channel_Privilege_Limit Administrator
98 EndSection
99 Section Lan_Conf
100 ## Possible values: Unspecified/Static/Use_DHCP/Use_BIOS/Use_Oth‐
101 ers
102 Ip_Address_Source Static
103 ## Give valid IP Address
104 Ip_Address 192.168.1.100
105 ## Give valid MAC Address
106 Mac_Address 00:0E:0E:FF:AA:12
107 ## Give valid Subnet mask
108 Subnet_Mask 255.255.255.0
109 ## Give valid IP Address
110 Default_Gateway_Ip_Address 192.168.1.1
111 ## Give valid MAC Address
112 Default_Gateway_Mac_Address 00:0E:0E:FF:AA:18
113 ## Give valid IP Address
114 Backup_Gateway_Ip_Address 192.168.1.2
115 ## Give valid MAC Address
116 Backup_Gateway_Mac_Address 00:0E:0E:FF:AA:15
117 EndSection
118 Section Lan_Conf_Auth
119 ## Possible values: Yes/No
120 Callback_Enable_Auth_Type_None No
121 ## Possible values: Yes/No
122 Callback_Enable_Auth_Type_Md2 No
123 ## Possible values: Yes/No
124 Callback_Enable_Auth_Type_Md5 No
125 ## Possible values: Yes/No
126 Callback_Enable_Auth_Type_Straight_Password No
127 ## Possible values: Yes/No
128 Callback_Enable_Auth_Type_Oem_Proprietary No
129 ## Possible values: Yes/No
130 User_Enable_Auth_Type_None No
131 ## Possible values: Yes/No
132 User_Enable_Auth_Type_Md2 Yes
133 ## Possible values: Yes/No
134 User_Enable_Auth_Type_Md5 Yes
135 ## Possible values: Yes/No
136 User_Enable_Auth_Type_Straight_Password No
137 ## Possible values: Yes/No
138 User_Enable_Auth_Type_Oem_Proprietary No
139 ## Possible values: Yes/No
140 Operator_Enable_Auth_Type_None No
141 ## Possible values: Yes/No
142 Operator_Enable_Auth_Type_Md2 Yes
143 ## Possible values: Yes/No
144 Operator_Enable_Auth_Type_Md5 Yes
145 ## Possible values: Yes/No
146 Operator_Enable_Auth_Type_Straight_Password No
147 ## Possible values: Yes/No
148 Operator_Enable_Auth_Type_Oem_Proprietary No
149 ## Possible values: Yes/No
150 Admin_Enable_Auth_Type_None No
151 ## Possible values: Yes/No
152 Admin_Enable_Auth_Type_Md2 Yes
153 ## Possible values: Yes/No
154 Admin_Enable_Auth_Type_Md5 Yes
155 ## Possible values: Yes/No
156 Admin_Enable_Auth_Type_Straight_Password No
157 ## Possible values: Yes/No
158 Admin_Enable_Auth_Type_Oem_Proprietary No
159 ## Possible values: Yes/No
160 Oem_Enable_Auth_Type_None No
161 ## Possible values: Yes/No
162 Oem_Enable_Auth_Type_Md2 No
163 ## Possible values: Yes/No
164 Oem_Enable_Auth_Type_Md5 No
165 ## Possible values: Yes/No
166 Oem_Enable_Auth_Type_Straight_Password No
167 ## Possible values: Yes/No
168 Oem_Enable_Auth_Type_Oem_Proprietary No
169 EndSection
170 Section Lan_Conf_Security_Keys
171 ## Give string or blank to clear. Max 20 chars
172 K_G
173 EndSection
174 Section Lan_Conf_Misc
175 ## Possible values: Yes/No
176 Enable_Gratuitous_Arps Yes
177 ## Possible values: Yes/No
178 Enable_Arp_Response No
179 ## Give valid number. Intervals are 500 ms.
180 Gratuitous_Arp_Interval 4
181 EndSection
182 Section Rmcpplus_Conf_Privilege
183 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
184 prietary
185 Maximum_Privilege_Cipher_Suite_Id_0 Unused
186 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
187 prietary
188 Maximum_Privilege_Cipher_Suite_Id_1 Unused
189 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
190 prietary
191 Maximum_Privilege_Cipher_Suite_Id_2 Unused
192 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
193 prietary
194 Maximum_Privilege_Cipher_Suite_Id_3 Administrator
195 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
196 prietary
197 Maximum_Privilege_Cipher_Suite_Id_4 Administrator
198 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
199 prietary
200 Maximum_Privilege_Cipher_Suite_Id_5 Administrator
201 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
202 prietary
203 Maximum_Privilege_Cipher_Suite_Id_6 Unused
204 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
205 prietary
206 Maximum_Privilege_Cipher_Suite_Id_7 Unused
207 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
208 prietary
209 Maximum_Privilege_Cipher_Suite_Id_8 Administrator
210 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
211 prietary
212 Maximum_Privilege_Cipher_Suite_Id_9 Administrator
213 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
214 prietary
215 Maximum_Privilege_Cipher_Suite_Id_10 Administrator
216 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
217 prietary
218 Maximum_Privilege_Cipher_Suite_Id_11 Unused
219 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
220 prietary
221 Maximum_Privilege_Cipher_Suite_Id_12 Administrator
222 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
223 prietary
224 Maximum_Privilege_Cipher_Suite_Id_13 Administrator
225 ## Possible values: Unused/User/Operator/Administrator/OEM_Pro‐
226 prietary
227 Maximum_Privilege_Cipher_Suite_Id_14 Administrator
228 EndSection
229 Section SOL_Conf
230 ## Possible values: Yes/No
231 Enable_SOL Yes
232 ## Possible values: Callback/User/Operator/Administrator/OEM_Pro‐
233 prietary
234 SOL_Privilege_Level Administrator
235 ## Possible values: Yes/No
236 Force_SOL_Payload_Authentication Yes
237 ## Possible values: Yes/No
238 Force_SOL_Payload_Encryption Yes
239 ## Give a valid integer. Each unit is 5ms
240 Character_Accumulate_Interval 50
241 ## Give a valid number
242 Character_Send_Threshold 100
243 ## Give a valid integer
244 SOL_Retry_Count 5
245 ## Give a valid integer. Interval unit is 10ms
246 SOL_Retry_Interval 50
247 ## Possible values: Serial/9600/19200/38400/57600/115200
248 Non_Volatile_Bit_Rate 115200
249 ## Possible values: Serial/9600/19200/38400/57600/115200
250 Volatile_Bit_Rate 115200
251 EndSection
252 Section Misc
253 ## Possible Values:
254 Off_State_AC_Apply/Restore_State_AC_Apply/On_State_AC_Apply
255 Power_Restore_Policy Restore_State_Ac_Apply
256 EndSection
257
260 The User sections of the BMC configuration file are for username con‐
261 figuration for IPMI over LAN communication. The number of users avail‐
262 able to be configured on your system will vary by manufacturer. With
263 the exception of the Username for User1, all sections are identical.
264 The username(s) you wish to configure the BMC with are defined with
266 Username. The first username under Section User1 is typically the NULL
267 username and cannot be modified. The password for the username can be
268 specified with Password. It can be left empty to define a NULL pass‐
269 word. Each user you wish to enable must be enabled through the
270 Enable_User configuration option. It is recommended that all usernames
271 have non-NULL passwords or be disabled for security reasons.
272 Lan_Enable_Ipmi_Msgs is used to enable or disable IPMI over LAN access
274 for the user. This should be set to "Yes" to allow IPMI over LAN tools
275 to work.
276 Lan_Privilege_Limit specifies the maximum privilege level limit the
278 user is allowed. Different IPMI commands have different privilege
279 restrictions. For example, determining the power status of a machine
280 only requires the "User" privilege level. However, power cycling
281 requires the "Operator" privilege. Typically, you will want to assign
282 atleast one user with a privilege limit of "Administrator" so that all
283 system functions are available to atleast one user via IPMI over LAN.
284 Lan_Session_Limit specifies the number of simultaneous IPMI sessions
286 allowed for the user. Most users will wish to set this to "0" to allow
287 unlimited simultaneous IPMI sessions. This field is considered optional
288 by IPMI standards, and may result in errors when attempting to config‐
289 ure it to a non-zero value. If errors to occur, setting the value back
290 to 0 should resolve problems.
291 SOL_Payload_Access specifies if a particular user is allowed to connect
293 with Serial-Over-LAN (SOL). This should be set to "Yes" to allow this
294 username to use SOL.
295 The example configuration above disables "User2" but enables the
297 default "NULL" (i.e. anonymous) user. Many IPMI tools (both open-source
298 and vendor) do not allow the user to input a username and assume the
299 NULL username by default. If the tools you are interested in using
300 allow usernames to be input, then it is recommended that one of the
301 non-NULL usernames be enabled and the NULL username disabled for secu‐
302 rity reasons. It is recommeneded that you disable the NULL username in
303 section User1, so that users are required to specify a username for
304 IPMI over LAN communication.
305 Some motherboards may require a Username to be configured prior to
307 other fields being read/written. If this is the case, those fields will
308 be set to <username-not-set-yet>.
309
312 The Lan_Channel section configures a variety of IPMI over LAN configu‐
313 ration parameters. Both Volatile and Non_Volatile configurations can be
314 set. Volatile configurations are immediately configured onto the BMC
315 and will have immediate effect on the system. Non_Volatile configura‐
316 tions are only available after the next system reset. Generally, both
317 the Volatile and Non_Volatile should be configured identically.
318 The Access_Mode parameter configures the availability of IPMI over LAN
320 on the system. Typically this should be set to "Always_Available" to
321 enable IPMI over LAN.
322 The Privilege_Limit sets the maximum privilege any user of the system
324 can have when performing IPMI over LAN. This should be set to the maxi‐
325 mum privilege level configured to a username. Typically, this should be
326 set to "Administrator".
327 Typically User_Level_Auth and Per_Message_Auth should be set to "Yes"
329 for additional security. Disabling User_Level_Auth allows "User" privi‐
330 leged IPMI commands to be executed without authentication. Disabling
331 Per_Message_Auth allows fewer individual IPMI messages to require
332 authentication.
333
336 Those familiar with setting up networks should find most of the fields
337 in this section self explanatory. The example BMC configuration above
338 illustrates the setup of a static IP address. The field
339 IP_Address_Source is configured with "Static". The IP address, subnet
340 mask, and gateway IP addresses of the machine are respecitvely config‐
341 ured with the IP_Address, Subnet_Mask, Default_Gateway_Ip_Address, and
342 Backup_Gateway_Ip_Address fields. The respective MAC addresses for the
343 IP addresses are configured under Mac_Address, Default_Gate‐
344 way_Mac_Address, and Backup_Gateway_Mac_Address.
345 It is not required to setup the BMC IP_Address to be the same P_Address
347 used by your operating system for that network interface. However, if
348 you choose to use a different address, an alternate ARP configuration
349 may need to be setup.
350 To instead setup your BMC network information via DHCP, the field
352 IP_Address_Source should be configured with "Use_DHCP".
353 It is recommended that static IP addresses be configured for address
355 resolution reasons. See Lan_Conf_Misc below for a more detailed expla‐
356 nation.
357
360 This section determines what types of password authentication mecha‐
361 nisms are allowed for users at different privilege levels under the
362 IPMI 1.5 protocol. The currently supported authentication methods for
363 IPMI 1.5 are None (no username/password required), Straight_Password
364 (passwords are sent in the clear), MD2 (passwords are MD2 hashed), and
365 MD5 (passwords are MD5 hashed). Different usernames at different priv‐
366 ilege levels may be allowed to authenticate differently through this
367 configuration. For example, a username with "User" privileges may be
368 allowed to authenticate with a straight password, but a username with
369 "Administrator" privileges may be allowed only authenticate with MD5.
370 The above example configuration supports MD2 and MD5 authentication for
372 all users at the "User", "Operator", and "Administrator" privilege lev‐
373 els. All authentication mechanisms have been disabled for the "Call‐
374 back" privilege level.
375 Generally speaking, you do not want to allow any user to authenticate
377 with None or Straight_Password for security reasons. MD2 and MD5 are
378 digital signature algorithms that can minimally encrypt passwords. If
379 you have chosen to support the NULL username (enabled User1) and NULL
380 passwords (NULL password for User1), you will have to enable the None
381 authentication fields above to allow users to connect via None.
382
385 This section supports configuration of the IPMI 2.0 (including Serial-
386 over-LAN) K_g key. If your machine does not support IPMI 2.0, this
387 field will not be configurable.
388 The key is used for two-key authentication in IPMI 2.0. In most tools,
390 when doing IPMI 2.0, the K_g can be optionally specified. It is not
391 required for IPMI 2.0 operation.
392 In the above example, we have elected to leave this field blank so the
394 K_g key is not used.
395
398 This section lists miscellaneous IPMI over LAN configuration options.
399 These are optional IPMI configuration options that are not implemented
400 on all BMCs.
401 Normally, a client cannot resolve the ethernet MAC address without the
403 remote operating system running. However, IPMI over LAN would not work
404 when a machine is powered off or if the IP address used by the operat‐
405 ing system for that network interface differs from the BMC IP Address.
406 One way to work around this is through gratuitous ARPs. Gratuitous
407 ARPs are ARP packets generated by the BMC and sent out to advertise the
408 BMC's IP and MAC address. Other machines on the network can store this
409 information in their local ARP cache for later IP/hostname resolution.
410 This would allow IPMI over LAN to work when the remote machine is pow‐
411 ered off. The Enable_Gratuitous_Arps option allows you to enable or
412 disable this feature. The Gratuitous_Arp_Interval option allows you to
413 configure the frequency at which gratuitous ARPs are sent onto the net‐
414 work.
415 Instead of gratuitous ARPs some BMCs are able to respond to ARP
417 requests, even when powered off. If offerred, this feature can be
418 enabled through the Enable_Arp_Response option.
419 Generally speaking, turning on gratuitous ARPs is acceptable. However,
421 it will increase traffic on your network. If you are using IPMI on a
422 large cluster, the gratuitous ARPs may easily flood your network. They
423 should be tuned to occur less frequently or disabled. If disabled, the
424 remote machine's MAC address should be permanently stored in the local
425 ARP cache through arp(8).
426 See bmc-watchdog(8) for a method which allows gratuitous ARPs to be
428 disabled when the operating system is running, but enabled when the
429 system is down.
430
433 This section supports configuration of the IPMI 2.0 (including Serial-
434 over-LAN) cipher suite IDs. If your machine does not support IPMI 2.0,
435 the fields will not be configurable.
436 Each cipher suite ID describes a combination of an authentication algo‐
438 rithm, integrity algorithm, and encryption algorithm for IPMI 2.0. The
439 authentication algorithm is used for user authentication with the BMC.
440 The integrity algorithm is used for generating signatures on IPMI pack‐
441 ets. The confidentiality algorithm is used for encrypting data. The
442 configuration in this section enables certain cipher suite IDs to be
443 enabled or disabled, and the maximum privilege level a username can
444 authenticate with.
445 The following table shows the cipher suite ID to algorithms mapping:
447 0 - Authentication Algorithm = None; Integrity Algorithm = None; Confi‐
449 dentiality Algorithm = None
450 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = None;
452 Confidentiality Algorithm = None
453 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-
455 SHA1-96; Confidentiality Algorithm = None
456 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-
458 SHA1-96; Confidentiality Algorithm = AES-CBC-128
459 4 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-
461 SHA1-96; Confidentiality Algorithm = xRC4-128
462 5 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-
464 SHA1-96; Confidentiality Algorithm = xRC4-40
465 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm = None;
467 Confidentiality Algorithm = None
468 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-
470 MD5-128; Confidentiality Algorithm = None
471 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-
473 MD5-128; Confidentiality Algorithm = AES-CBC-128
474 9 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-
476 MD5-128; Confidentiality Algorithm = xRC4-128
477 10 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-
479 MD5-128; Confidentiality Algorithm = xRC4-40
480 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
482 MD5-128; Confidentiality Algorithm = None
483 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
485 MD5-128; Confidentiality Algorithm = AES-CBC-128
486 13 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
488 MD5-128; Confidentiality Algorithm = xRC4-128
489 14 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
491 MD5-128; Confidentiality Algorithm = xRC4-40
492 Generally speaking, HMAC-SHA1 based algorithms are stronger than HMAC-
494 MD5, which are better than MD5-128 algorithms. AES-CBC-128 confiden‐
495 tiality algorithms are stronger than xRC4-128 algorithms, which are
496 better than xRC4-40 algorithms. Cipher suite ID 3 is therefore typi‐
497 cally considered the most secure. Some users may wish to set cipher
498 suite ID 3 to a privilege level and disable all remaining cipher suite
499 IDs.
500 The above example configuration has decided to allow any user with
502 "Administrator" privileges use any Cipher Suite algorithm suite which
503 requires an authentication, integrity, and confidentiality algorithm.
504 Typically, the maximum privilege level configured to a username should
505 be set for atleast one cipher suite ID. Typically, this is the "Admin‐
506 istrator" privilege.
507 A number of cipher suite IDs are optionally implemented, so the avail‐
509 able cipher suite IDs available your system may vary.
510
513 This section is for setting up Serial-Over-Lan (SOL) and will only be
514 available for configuration on those machines. SOL can be enabled with
515 the Enable_SOL field. The minimum privilege level required for connect‐
516 ing with SOL is specified by SOL_Privilege_Level. This should be set
517 to the maximum privilege level configured to a username that has SOL
518 enabled. Typically, this is the "Administrator" privilege. Authentica‐
519 tion and Encryption can be forced or not using the fields
520 Force_SOL_Payload_Authentication and Force_SOL_Payload_Encryption
521 respectively. It is recommended that these be set on. However, forced
522 authentication and/or encryption support depend on the cipher suite IDs
523 supported.
524 The Character_Accumulate_Interval, Character_Send_Threshold ,
526 SOL_Retry_Count and , SOL_Retry_Interval options are used to set SOL
527 character output speeds. Character_Accumulate_Interval determines how
528 often serial data should be regularly sent and Character_Send_Threshold
529 indicates the character count that if passed, will force serial data to
530 be sent. SOL_Retry_Count indicates how many times packets must be
531 retransmitted if acknowledgements are not received. SOL_Retry_Interval
532 indicates the timeout interval. Generally, the manufacturer recommended
533 numbers will be sufficient. However, you may wish to experiment with
534 these values for faster SOL throughput.
535 The Non_Volatile_Bit_Rate and Volatile_Bit_Rate determine the baudrate
537 the BMC should use. This should match the baudrate set in the BIOS and
538 operating system, such as agetty(8). Generally speaking, both the
539 Volatile and Non_Volatile options should be set identically.
540 In addition to enabling SOL in this section, individual users most also
542 be capable of connecting with SOL. See the section Section User1,
543 User2, ... above for details.
544
547 The Power_Restore_Policy determines the behavior of the machine when AC
548 power returns after a power loss. The behavior can be set to always
549 power on the machine ("On_State_AC_Apply"), power off the machine
550 ("Off_State_AC_Apply"), or return the power to the state that existed
551 before the power loss ("Restore_State_AC_Apply").
552
554 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
555
557 freeipmi(7), bmc-config(8), bmc-watchdog(8), agetty(8)
558 http://www.gnu.org/software/freeipmi/
560bmc-config 0.8.8 2010-07-21 bmc-config.conf(5)