ipmievd.8 7.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231
  1. .TH "ipmievd" "8" "" "Duncan Laurie" ""
  2. .SH "NAME"
  3. ipmievd \- IPMI event daemon for sending events to syslog
  4. .SH "SYNOPSIS"
  5. ipmievd [\fB\-c\fR|\fB\-h\fR|\fB\-d \fIN\fP\fR|\fB\-v\fR|\fB\-V\fR]
  6. \fB\-I\fR \fIopen\fP <\fIopen\fR | \fIsel\fR> [<\fIoption\fP>]
  7. ipmievd [\fB\-c\fR|\fB\-h\fR|\fB\-v\fR|\fB\-V\fR]
  8. \fB\-I\fR \fIlan\fP \fB\-H\fR <\fIhostname\fP>
  9. [\fB\-p\fR <\fIport\fP>]
  10. [\fB\-U\fR <\fIusername\fP>]
  11. [\fB\-A\fR <\fIauthtype\fP>]
  12. [\fB\-L\fR <\fIprivlvl\fP>]
  13. [\fB\-a\fR|\fB\-E\fR|\fB\-P\fR|\fB\-f\fR <\fIpassword\fP>]
  14. [\fB\-o\fR <\fIoemtype\fP>]
  15. [\fB\-O\fR <\fIsel oem\fP>]
  16. \fIsel\fP [<\fIoption\fP>]
  17. ipmievd [\fB\-c\fR|\fB\-h\fR|\fB\-v\fR|\fB\-V\fR]
  18. \fB\-I\fR \fIlanplus\fP \fB\-H\fR <\fIhostname\fP>
  19. [\fB\-p\fR <\fIport\fP>]
  20. [\fB\-U\fR <\fIusername\fP>]
  21. [\fB\-L\fR <\fIprivlvl\fP>]
  22. [\fB\-a\fR|\fB\-E\fR|\fB\-P\fR|\fB\-f\fR <\fIpassword\fP>]
  23. [\fB\-o\fR <\fIoemtype\fP>]
  24. [\fB\-O\fR <\fIsel oem\fP>]
  25. [\fB\-C\fR <\fIciphersuite\fP>]
  26. \fIsel\fR [<\fIoption\fP>]
  27. .SH "DESCRIPTION"
  28. \fBipmievd\fP is a daemon which will listen for events from the
  29. BMC that are being sent to the SEL and also log those messages to
  30. syslog. It is able to run in one of two modes: either using the
  31. Event Message Buffer and asynchronous event notification from the
  32. OpenIPMI kernel driver or actively polling the contents of the
  33. SEL for new events. Upon receipt of an event via either mechanism
  34. it will be logged to syslog with the \fILOG_LOCAL4\fP facility.
  35. It is based on the \fBipmitool\fR utility and shares the same IPMI
  36. interface support and session setup options. Please see the
  37. \fBipmitool\fR manpage for more information on supported IPMI
  38. interfaces.
  39. .SH "OPTIONS"
  40. .TP
  41. \fB\-a\fR
  42. Prompt for the remote server password.
  43. .TP
  44. \fB\-A\fR <\fIauthtype\fP>
  45. Specify an authentication type to use during IPMIv1.5 \fIlan\fP
  46. session activation. Supported types are NONE, PASSWORD, MD2, MD5, or OEM.
  47. .TP
  48. \fB\-c\fR
  49. Present output in CSV (comma separated variable) format.
  50. This is not available with all commands.
  51. .TP
  52. \fB\-C\fR <\fIciphersuite\fP>
  53. The remote server authentication, integrity, and encryption algorithms
  54. to use for IPMIv2 \fIlanplus\fP connections. See table 22\-19 in the
  55. IPMIv2 specification. The default is 3 which specifies RAKP\-HMAC\-SHA1
  56. authentication, HMAC\-SHA1\-96 integrity, and AES\-CBC\-128 encryption algorightms.
  57. .TP
  58. \fB\-E\fR
  59. The remote server password is specified by the environment
  60. variable \fIIPMI_PASSWORD\fP.
  61. .TP
  62. \fB\-f\fR <\fIpassword_file\fP>
  63. Specifies a file containing the remote server password. If this
  64. option is absent, or if password_file is empty, the password
  65. will default to NULL.
  66. .TP
  67. \fB\-h\fR
  68. Get basic usage help from the command line.
  69. .TP
  70. \fB\-H\fR <\fIaddress\fP>
  71. Remote server address, can be IP address or hostname. This
  72. option is required for \fIlan\fP and \fIlanplus\fP interfaces.
  73. .TP
  74. \fB\-I\fR <\fIinterface\fP>
  75. Selects IPMI interface to use. Supported interfaces that are
  76. compiled in are visible in the usage help output.
  77. .TP
  78. \fB\-L\fR <\fIprivlvl\fP>
  79. Force session privilege level. Can be CALLBACK, USER,
  80. OPERATOR, ADMIN. Default is ADMIN.
  81. .TP
  82. \fB\-m\fR <\fIlocal_address\fP>
  83. Set the local IPMB address. The default is 0x20 and there
  84. should be no need to change it for normal operation.
  85. .TP
  86. \fB\-o\fR <\fIoemtype\fP>
  87. Select OEM type to support. This usually involves minor hacks
  88. in place in the code to work around quirks in various BMCs from
  89. various manufacturers. Use \fI\-o list\fP to see a list of
  90. current supported OEM types.
  91. .TP
  92. \fB\-O\fR <\fIsel oem\fP>
  93. Open selected file and read OEM SEL event descriptions to be used
  94. during SEL listings. See examples in contrib dir for file format.
  95. .TP
  96. \fB\-p\fR <\fIport\fP>
  97. Remote server UDP port to connect to. Default is 623.
  98. .TP
  99. \fB\-P\fR <\fIpassword\fP>
  100. Remote server password is specified on the command line.
  101. If supported it will be obscured in the process list.
  102. \fBNote!\fR Specifying the password as a command line
  103. option is not recommended.
  104. .TP
  105. \fB\-S\fR <\fIsdr_cache_file\fP>
  106. Use local file for remote SDR cache. Using a local SDR cache
  107. can drastically increase performance for commands that require
  108. knowledge of the entire SDR to perform their function.
  109. .TP
  110. \fB\-t\fR <\fItarget_address\fP>
  111. Bridge IPMI requests to the remote target address.
  112. .TP
  113. \fB\-U\fR <\fIusername\fP>
  114. Remote server username, default is NULL user.
  115. .TP
  116. \fB\-d \fIN\fP\fR
  117. Use device number N to specify the /dev/ipmiN (or
  118. /dev/ipmi/N or /dev/ipmidev/N) device to use for in-band
  119. BMC communication. Used to target a specific BMC on a
  120. multi-node, multi-BMC system through the ipmi device
  121. driver interface. Default is 0.
  122. .TP
  123. \fB\-v\fR
  124. Increase verbose output level. This option may be specified
  125. multiple times to increase the level of debug output. If given
  126. three times you will get hexdumps of all incoming and
  127. outgoing packets.
  128. .TP
  129. \fB\-V\fR
  130. Display version information.
  131. .LP
  132. If no password method is specified then ipmievd will prompt the
  133. user for a password. If no password is entered at the prompt,
  134. the remote server password will default to NULL.
  135. .SH "COMMANDS"
  136. .TP
  137. \fIhelp\fP
  138. This can be used to get command\-line help. It may also be
  139. placed at the end of commands to get option usage help.
  140. > ipmievd help
  141. .br
  142. Commands:
  143. open Use OpenIPMI for asyncronous notification of events
  144. sel Poll SEL for notification of events
  145. .TP
  146. \fIopen\fP
  147. This command starts ipmievd with the OpenIPMI event watching
  148. mechanism which relies on the Event Message Buffer feature of
  149. IPMI. This requires a properly installed and configured
  150. OpenIPMI driver on Linux and is only valid to be run through
  151. the \fIopen\fP interface. See the \fBipmitool\fR manpage
  152. and associated documentation for more information on setting
  153. up the OpenIPMI driver.
  154. \fBNote\fR: Some BMC do not support the Event Message Buffer
  155. required for this command. Other BMCs claim to support it but
  156. do not actually deliver events to it. If this is the case please
  157. use the \fIsel\fP method.
  158. .RS
  159. .TP
  160. \fIdaemon\fP
  161. Launch process as a daemon and reparent to init process.
  162. All messages will be sent to syslog. This is the default action.
  163. .TP
  164. \fInodaemon\fP
  165. Do NOT become a daemon, instead log all messages to stderr.
  166. .TP
  167. \fIpidfile\fP=<\fBfilename\fR>
  168. Save process ID to this file when in daemon mode. Defaults to
  169. /var/run/ipmievd.pid\fIN\fP (where \fIN\fP is the ipmi device
  170. number -- defaults to 0).
  171. .RE
  172. .TP
  173. \fIsel\fP
  174. This command starts ipmievd with the SEL Polling event watching
  175. mechanism. This will poll the SEL periodically to determine if
  176. new events have been logged. This command should work with all
  177. BMCs and is capable of using the LAN interface as well to monitor
  178. a remote system and log its events to a local syslog.
  179. .RS
  180. .TP
  181. \fIdaemon\fP
  182. Launch process as a daemon and reparent to init process.
  183. All messages will be sent to syslog. This is the default action.
  184. .TP
  185. \fInodaemon\fP
  186. Do NOT become a daemon, instead log all messages to stderr.
  187. .TP
  188. \fIpidfile\fP=<\fBfilename\fR>
  189. Save process ID to this file when in daemon mode. Defaults to
  190. /var/run/ipmievd.pid\fIN\fP (where \fIN\fP is the ipmi device
  191. number -- defaults to 0).
  192. .TP
  193. \fItimeout\fP=<\fBseconds\fR>
  194. Time between checks for SEL polling method. Default is 10 seconds.
  195. .RE
  196. .SH "EXAMPLES"
  197. .TP
  198. \fIExample 1\fP: Daemon process watching OpenIPMI for events
  199. > ipmievd \-I open open daemon
  200. .TP
  201. \fIExample 2\fP: Local non\-daemon process checking remote SEL every 30 seconds
  202. > ipmievd \-I lan \-H 1.2.3.4 \-f passfile sel nodaemon timeout=30
  203. .br
  204. Reading Sensors...
  205. .br
  206. Waiting for Events...
  207. .br
  208. .SH "AUTHOR"
  209. Duncan Laurie <duncan@iceblink.org>
  210. .SH "SEE ALSO"
  211. .TP
  212. IPMItool Homepage
  213. http://ipmitool.sourceforge.net
  214. .TP
  215. Intelligent Platform Management Interface Specification
  216. http://www.intel.com/design/servers/ipmi
  217. .TP
  218. OpenIPMI Homepage
  219. http://openipmi.sourceforge.net