# openipmi_conparms(7) - man - phpMan

[openipmi_conparms(7)](https://www.chedong.com/phpMan.php/man/openipmiconparms/7/markdown)             Connection Parameters for OpenIPMI             [openipmi_conparms(7)](https://www.chedong.com/phpMan.php/man/openipmiconparms/7/markdown)



## NAME
       openipmi_cmdparms - Connection parmeters for OpenIPMI


## SYNOPSIS
       **smi** _smi-num_

       **lan** [**-U** _username_] [**-P** _password_] [**-p[2]** _port_] [**-A** _authtype_] [**-L** _privilege_] [**-s**] [**-Ra** _auth_ _alg_]
       [**-Ri** _integ_ _alg_] [**-Rc** _conf_ _algo_] [**-Rl**] [**-Rk** _bmc_ _key_] [**-H** _hackname_] _host_ [ _host_]


## DESCRIPTION
       The connection parameters for OpenIPMI vary depending on the connection type.  This  document
       describes the standard connection types; others may be available from OEMs.


## OPTIONS
       _smi-num_
              The SMI interface for the local connection.  There may be more than one BMC connection
              on a system and they are generally numbered, like **/dev/ipmi0**, **/dev/ipmi1**, etc.


### -U
              Use the given _username_ for the LAN connection.  If none is given, then no username  is
              used.


### -P
              The _password_ to use for the connection.  If none is given, the user is assumed to have
              an empty password


### -p
              The UCP _port_ to connect to.  This defaults to the standard 623 port, so it is not nec‐
              essary  unless  a  special port is required.  Note that since you can have two connec‐
              tions (hosts), **-p** is for the first host and **-p2** is for the second host.


### -A
              The _authentication_ _type_ to use, one of **rmcp+**, **md5**, **md2**, **straight**,  or  **none**.   If  you
              don't  supply this, the most secure one available is chosen, in the order given in the
              previous list.


### -L
              The _privilege_ to use for the connection.  Lower privileges cannot  execute  some  com‐
              mands.   Privileges are: **callback**, **user**, **operator**, **admin**, and **oem**.  The default is **ad**‐‐
              **min**.


### -Ra
              Set the _RMCP+_ _authentication_ _algorithm_  to  use.   Options  are:  **bmcpick**,  **rakp**___**none**,
              **rakp**___**hmac**___**sha1**, and **rakp**___**hmac**___**md5**.  The **bmcpick** option is used by default, which means
              the BMC picks the algorithm it wants to use.


### -Ri
              The _RMCP+_ _integrity_ _algorithm_ to use.  This ensures that the data has not  be  altered
              between  the  sender  and  receiver.   Valid  options  are:  **bmcpick**, **none**, **hmac**___**sha1**,
              **hmac**___**md5**, and **md5**.  The **bmcpick** option is used by default, which means the  BMC  picks
              the algorithm it wants to use.


### -Rc
              The _RMCP+_ _confidentiality_ _(encryption)_ _algorithm_ to use.  This keeps evesdroppers from
              seeing the data.  Valid values are: **bmcpick**, **aes**___**cbc**___**128**, **xrc4**___**128**, and  **xrc**___**40**.   The
              **bmcpick** option is used by default, which means the BMC picks the algorithm it wants to
              use.


### -Rl
              the  username.   This  allows the same name to have different passwords with different
              privilege levels.


### -Rk
              If the system requires two-key lookups, this specifies the _second_ _key_ (the BMC key) to
              use.  This is ignored if two-key lookups are not enabled by the BMC.


### -H
              Well,  it always happens.  Things in the field don't work quite like they are supposed
              to.  There was some vagueness in the first IPMI specs  and  different  vendors  inter‐
              preted  RMCP+  in different ways.  This allows different options to be supported.  Try
              different hacks if your RMCP+ systems don't authenticate properly.  These are:


              **rakp3**___**wrong**___**rolem**
                     Some systems use the incorrect Role(m) field in a specific authentication  mes‐
                     sage (the RAKP3 message).  This is a common problem.


              **rmcpp**___**integ**___**sik**
                     The original IPMI 2.0 spec specified the incorrect key to use for the integrity
                     key.  This forces use of the Session Initiation Key.  The  default  is  to  use
                     [K(1)](https://www.chedong.com/phpMan.php/man/K/1/markdown)


### -s
              dresses/ports that are equivalent.  If this is specified, a second host must  be  sup‐
              plied.  This is not the same as two connections to two different BMCs.  This must be a
              connection to the same BMC.


       _host_   The IP address (either by name lookup or specified directly) to connect to.  If the **-s**
              is specified, two hosts must be supplied.


       The **-Ra**, **-Ri**, **-Rc**, **-Rk** and **-Rl** options only apply to RMCP+ connections and will be ignored if
       the connection does not support RMCP+ or if a non-RMCP+ authentication type is specified.



## SEE ALSO
       [**ipmish**(8)](https://www.chedong.com/phpMan.php/man/ipmish/8/markdown), [**openipmicmd**(8)](https://www.chedong.com/phpMan.php/man/openipmicmd/8/markdown), [**solterm**(1)](https://www.chedong.com/phpMan.php/man/solterm/1/markdown)


## KNOWN PROBLEMS
       This is excessively complicated, but the defaults should be good.


## AUTHOR
       Corey Minyard <<cminyard@mvista.com>>



OpenIPMI                                      05/13/03                          [openipmi_conparms(7)](https://www.chedong.com/phpMan.php/man/openipmiconparms/7/markdown)