1openipmi_conparms(7) Connection Parameters for OpenIPMI openipmi_conparms(7)
2
6 openipmi_cmdparms - Connection parmeters for OpenIPMI
7
10 smi smi-num
11 lan [-U username] [-P password] [-p[2] port] [-A authtype] [-L privi‐
13 lege] [-s] [-Ra auth alg] [-Ri integ alg] [-Rc conf algo] [-Rl] [-Rk
14 bmc key] [-H hackname] host [ host]
15
18 The connection parameters for OpenIPMI vary depending on the connection
19 type. This document describes the standard connection types; others
20 may be available from OEMs.
21
24 smi-num
25 The SMI interface for the local connection. There may be more
26 than one BMC connection on a system and they are generally num‐
27 bered, like /dev/ipmi0, /dev/ipmi1, etc.
28 -U username
31 Use the given username for the LAN connection. If none is
32 given, then no username is used.
33 -P password
36 The password to use for the connection. If none is given, the
37 user is assumed to have an empty password
38 -p[2] port
41 The UCP port to connect to. This defaults to the standard 623
42 port, so it is not necessary unless a special port is required.
43 Note that since you can have two connections (hosts), -p is for
44 the first host and -p2 is for the second host.
45 -A authtype
48 The authentication type to use, one of rmcp+, md5, md2,
49 straight, or none. If you don't supply this, the most secure
50 one available is chosen, in the order given in the previous
51 list.
52 -L privilege
55 The privilege to use for the connection. Lower privileges can‐
56 not execute some commands. Privileges are: callback, user,
57 operator, admin, and oem. The default is admin.
58 -Ra authentication algorithm
61 Set the RMCP+ authentication algorithm to use. Options are:
62 bmcpick, rakp_none, rakp_hmac_sha1, and rakp_hmac_md5. The
63 bmcpick option is used by default, which means the BMC picks the
64 algorithm it wants to use.
65 -Ri integrity algorithm
68 The RMCP+ integrity algorithm to use. This ensures that the
69 data has not be altered between the sender and receiver. Valid
70 options are: bmcpick, none, hmac_sha1, hmac_md5, and md5. The
71 bmcpick option is used by default, which means the BMC picks the
72 algorithm it wants to use.
73 -Rc confidentiality algorithm
76 The RMCP+ confidentiality (encryption) algorithm to use. This
77 keeps evesdroppers from seeing the data. Valid values are:
78 bmcpick, aes_cbc_128, xrc4_128, and xrc_40. The bmcpick option
79 is used by default, which means the BMC picks the algorithm it
80 wants to use.
81 -Rl If this is specified, the username is looked up using the privi‐
84 lege level along with the username. This allows the same name
85 to have different passwords with different privilege levels.
86 -Rk BMC Key
89 If the system requires two-key lookups, this specifies the sec‐
90 ond key (the BMC key) to use. This is ignored if two-key
91 lookups are not enabled by the BMC.
92 -H hackname
95 Well, it always happens. Things in the field don't work quite
96 like they are supposed to. There was some vagueness in the
97 first IPMI specs and different vendors interpreted RMCP+ in dif‐
98 ferent ways. This allows different options to be supported.
99 Try different hacks if your RMCP+ systems don't authenticate
100 properly. These are:
101 rakp3_wrong_rolem
104 Some systems use the incorrect Role(m) field in a spe‐
105 cific authentication message (the RAKP3 message). This
106 is a common problem.
107 rmcpp_integ_sik
110 The original IPMI 2.0 spec specified the incorrect key to
111 use for the integrity key. This forces use of the Ses‐
112 sion Initiation Key. The default is to use K(1)
113 -s Make two connections to the BMC. This means the BMC has two
116 different IP addresses/ports that are equivalent. If this is
117 specified, a second host must be supplied. This is not the same
118 as two connections to two different BMCs. This must be a con‐
119 nection to the same BMC.
120 host The IP address (either by name lookup or specified directly) to
123 connect to. If the -s is specified, two hosts must be supplied.
124 The -Ra, -Ri, -Rc, -Rk and -Rl options only apply to RMCP+ connections
127 and will be ignored if the connection does not support RMCP+ or if a
128 non-RMCP+ authentication type is specified.
129
133 ipmish(8), openipmicmd(8), solterm(1)
134
137 This is excessively complicated, but the defaults should be good.
138
141 Corey Minyard <cminyard@mvista.org>
142OpenIPMI 05/13/03 openipmi_conparms(7)