iPMi and open-Source tools - Kontron
iPMi and open-Source tools - Kontron
iPMi and open-Source tools - Kontron
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
WhitePaper «<br />
» Whitepaper «<br />
»<br />
<strong>iPMi</strong> <strong>and</strong> <strong>open</strong>-<strong>Source</strong> <strong>tools</strong>:<br />
Sorting out the Confusion<br />
Appendix C: Specifi c Examples of IPMI usage<br />
If it’s embedded, it’s <strong>Kontron</strong>.
APPENDIX C - Specific Examples of IPMI usage Platforms used for the examples: <strong>Kontron</strong> CG2100 <strong>and</strong> <strong>Kontron</strong> NSN2U<br />
C.1 EXAMPlES of IPMI SEl INtErPrEtAtIoN<br />
Whitepaper<br />
ipmitool sel list [elist] 108 | 06/11/2009 | 16:59:28 | temperature #0x20 | lower Non-critical going low<br />
(shows no sensor values by default for threshold events)<br />
108 | 06/11/2009 | 16:59:28 | temperature Baseboard temp | lower Non-critical going low | reading 30 < threshold 34 degrees C<br />
(shows extended decoding for threshold events with elist)<br />
[…]<br />
688 | 03/05/2010 | 11:54:16 | Physical Security #0x04 | General Chassis intrusion | Deasserted<br />
689 | 03/05/2010 | 11:54:16 | Physical Security #0x04 | General Chassis intrusion | Asserted<br />
(recognizes deassert/ok <strong>and</strong> assert)<br />
[…]<br />
690 | 03/05/2010 | 11:55:23 | System firmware Error #0x06 | Unknown Error | Asserted<br />
(firmware event is cryptic, <strong>and</strong> important data is obscured – the PoSt code)<br />
[…]<br />
791 | 07/30/2010 | 12:24:31 | Unknown #0x06 | State Asserted<br />
792 | 07/30/2010 | 12:24:31 | Unknown #0x06 | State Asserted<br />
(Event unrecognized, ‘Unknown’ so actual data is not shown)<br />
[…]<br />
25c | 08/30/2010 | 16:31:31 | oS Stop/Shutdown #0x64 | run-time critical stop | Asserted<br />
270 | linux kernel panic: dopanic: in<br />
284 | linux kernel panic: it_module c<br />
298 | linux kernel panic: alls panic<br />
(recognizes Critical Stop <strong>and</strong> oEM string records, but does not show custom bytes in stop event)<br />
ipmiutil sel [-e] 0108 06/11/09 12:59:28 MIN BMC temperature #20 lo Noncrit thresh act=1e thr=22<br />
(shows raw sensor values for threshold events, includes severity)<br />
0108 06/11/09 12:59:28 MIN BMC temperature #20 Baseboard temp lo Noncrit thresh actual=30.00 C, threshold=34.00 C<br />
(shows extended sensor values for threshold events with –e, includes severity)<br />
[…]<br />
0688 03/05/10 06:54:16 INf BMC Platform Security #04 Chassis oK ef [00 ff ff]<br />
0689 03/05/10 06:54:16 MIN BMC Platform Security #04 Chassis Intrusion 6f [00 ff ff]<br />
(recognizes deassert/ok <strong>and</strong> assert, includes MINor severity)<br />
[…]<br />
0690 03/05/10 06:55:23 MAJ 0033 System firmware #06 PoSt Code 8545 6f [a0 45 85]<br />
(recognizes the firmware PoSt code, shown as documented in the platform docs, includes MAJor severity)<br />
[…]<br />
0791 07/30/10 08:24:31 Crt BMC SMI timeout #06 SMI asserted 03 [01 ff ff]<br />
0792 07/30/10 08:24:31 INf BMC SMI timeout #06 SMI de-asserted 83 [01 ff ff]<br />
(recognizes SMI event, <strong>and</strong> includes data for vendor interpretation if needed, includes Crt severity)<br />
[…]<br />
025c 08/30/10 12:31:31 Crt SMI oS Critical Stop #64 panic(dop) 6f [a1 6f 70]<br />
0270 INf f0 oEM Event 20 00 dopanic: in<br />
0284 INf f0 oEM Event 20 01 it_module c<br />
0298 INf f0 oEM Event 20 02 alls panic<br />
(recognizes Critical Stop record, custom data “dop”, <strong>and</strong> oEM string records, includes Crt severity)<br />
freeipmi (ipmi-sel) 264 | Jun-11-2009 | 12:59:28 | Baseboard temp | temperature | lower Non-critical - going low ; Sensor reading = 30.00 C ;<br />
threshold = 34.00 C<br />
(shows sensor values for threshold events)<br />
[…]<br />
1672 | Mar-05-2010 | 06:54:16 | Sensor #4 | Physical Security | General Chassis Intrusion<br />
1673 | Mar-05-2010 | 06:54:16 | Sensor #4 | Physical Security | General Chassis Intrusion<br />
(decodes the event but fails to recognize the difference between deassert/assert)<br />
[…]<br />
1680 | Mar-05-2010 | 06:55:23 | Mem Mirr Sensor | System firmware Progress | System firmware Error ; oEM Event Data2<br />
code = 45h ; oEM Event Data3 code = 85h<br />
(recognizes it as a firmware event, <strong>and</strong> shows the data in raw form)<br />
[…]<br />
1937 | Jul-30-2010 | 08:24:31 | SMI timeout | oEM reserved | State Asserted<br />
1938 | Jul-30-2010 | 08:24:31 | SMI timeout | oEM reserved | State Asserted<br />
(recognizes SMI event, but labels both as asserted, no data2/data3 included)<br />
[…]<br />
604 | Aug-30-2010 | 12:31:31 | Sensor #100 | oS Critical Stop | run-time Critical Stop ; oEM Event Data2 code =<br />
6fh ; oEM Event Data3 code = 70h<br />
624 | oEM defined = 20h 00h 64h 6fh 70h 61h 6Eh 69h 63h 3Ah 20h 69h 6Eh<br />
644 | oEM defined = 20h 01h 69h 74h 5fh 6Dh 6fh 64h 75h 6Ch 65h 20h 63h<br />
664 | oEM defined = 20h 02h 61h 6Ch 6Ch 73h 20h 70h 61h 6Eh 69h 63h 00h<br />
(recognizes Critical Stop record, shows hex custom data, but oEM string records are in hex)<br />
<strong>open</strong>ipmish (sel list) (all events are shown uninterpreted in hex)<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 264<br />
Event type: 2<br />
timestamp: 1244739568000000000<br />
Data: 0xf0 0x37 0x31 0x4a 0x20 0x00 0x04 0x01<br />
0x20 0x01 0x50 0x1e 0x22<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1672<br />
Event type: 2<br />
timestamp: 1267790056000000000<br />
Data: 0xe8 0xf0 0x90 0x4b 0x20 0x00 0x04 0x05<br />
0x04 0xef 0x00 0xff 0xff<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1673<br />
Event type: 2<br />
timestamp: 1267790056000000000<br />
Data: 0xe8 0xf0 0x90 0x4b 0x20 0x00 0x04 0x05<br />
0x04 0x6f 0x00 0xff 0xff<br />
www.kontron.com/ocp
APPENDIX C - Specific Examples of IPMI usage (continued)<br />
<strong>open</strong>ipmish (sel list) (all events are shown uninterpreted in hex)<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 264<br />
Event type: 2<br />
timestamp: 1244739568000000000<br />
Data: 0xf0 0x37 0x31 0x4a 0x20 0x00 0x04 0x01<br />
0x20 0x01 0x50 0x1e 0x22<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1672<br />
Event type: 2<br />
timestamp: 1267790056000000000<br />
Data: 0xe8 0xf0 0x90 0x4b 0x20 0x00 0x04 0x05<br />
0x04 0xef 0x00 0xff 0xff<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1673<br />
Event type: 2<br />
timestamp: 1267790056000000000<br />
Data: 0xe8 0xf0 0x90 0x4b 0x20 0x00 0x04 0x05<br />
0x04 0x6f 0x00 0xff 0xff<br />
[…]<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1680<br />
Event type: 2<br />
timestamp: 1267790123000000000<br />
Data: 0x2b 0xf1 0x90 0x4b 0x33 0x00 0x04 0x0f<br />
0x06 0x6f 0xa0 0x45 0x85<br />
[…]<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1937<br />
Event type: 2<br />
timestamp: 1280492671000000000<br />
Data: 0x7f 0xc4 0x52 0x4c 0x20 0x00 0x04 0xf3<br />
0x06 0x03 0x01 0xff 0xff<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 1938<br />
Event type: 2<br />
timestamp: 1280492671000000000<br />
Data: 0x7f 0xc4 0x52 0x4c 0x20 0x00 0x04 0xf3<br />
0x06 0x83 0x01 0xff 0xff<br />
[…]<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 604<br />
Event type: 2<br />
timestamp: 1283185891000000000<br />
Data: 0xe3 0xdc 0x7b 0x4c 0x21 0x00 0x04 0x20<br />
0x64 0x6f 0xa1 0x6f 0x70<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 624<br />
Event type: 240<br />
timestamp: -1<br />
Data: 0x20 0x00 0x64 0x6f 0x70 0x61 0x6e 0x69<br />
0x63 0x3a 0x20 0x69 0x6e<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 644<br />
Event type: 240<br />
timestamp: -1<br />
Data: 0x20 0x01 0x69 0x74 0x5f 0x6d 0x6f 0x64<br />
0x75 0x6c 0x65 0x20 0x63<br />
Event<br />
MC: dom1(0.20)<br />
record ID: 664<br />
Event type: 240<br />
timestamp: -1<br />
Data: 0x20 0x02 0x61 0x6c 0x6c 0x73 0x20 0x70<br />
0x61 0x6e 0x69 0x63 0x00<br />
C.2 EXAMPlES of EvENt MoNItorING DAEMoN, AS vIEWED froM thE SySloG.<br />
ipmitool (ipmievd) Aug 31 15:34:06 ac3-nsn2u ipmievd: reading sensors...<br />
Whitepaper<br />
Aug 31 15:34:11 ac3-nsn2u ipmievd: Waiting for events...<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Non-critical going high (reading 32 ><br />
threshold 25 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Critical going high (reading 32 > threshold<br />
26 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Critical going high (reading 32 > threshold<br />
55 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Non-critical going high (reading 32 ><br />
threshold 54 degrees C)<br />
www.kontron.com/ocp
APPENDIX C - Specific Examples of IPMI usage (continued)<br />
Whitepaper<br />
ipmitool (ipmievd) Aug 31 15:34:06 ac3-nsn2u ipmievd: reading sensors...<br />
Aug 31 15:34:11 ac3-nsn2u ipmievd: Waiting for events...<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Non-critical going high (reading 32 ><br />
threshold 25 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Critical going high (reading 32 > threshold<br />
26 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Critical going high (reading 32 > threshold<br />
55 degrees C)<br />
Aug 31 15:34:21 ac3-nsn2u ipmievd: temperature sensor Baseboard temp Upper Non-critical going high (reading 32 ><br />
threshold 54 degrees C)<br />
ipmiutil_evt (getevt -s) Aug 31 16:27:08 ac3-nsn2u ipmiutil: igetevent reading sensors ...<br />
Aug 31 16:27:09 ac3-nsn2u ipmiutil: igetevent waiting for events ...<br />
Aug 31 16:27:09 ac3-nsn2u ipmiutil: igetevent: 0806 08/31/10 12:02:45 MIN BMC temperature #20 Baseboard temp hi<br />
Noncrit thresh actual=32.00 C, threshold=25.00 C<br />
Aug 31 16:27:09 ac3-nsn2u ipmiutil: igetevent: 0807 08/31/10 12:02:45 MAJ BMC temperature #20 Baseboard temp hi Crit<br />
thresh actual=32.00 C, threshold=26.00 C<br />
Aug 31 16:27:09 ac3-nsn2u ipmiutil: igetevent: 0808 08/31/10 12:02:47 INf BMC temperature #20 Baseboard temp hiC<br />
thresh oK now actual=32.00 C, threshold=55.00 C<br />
Aug 31 16:27:09 ac3-nsn2u ipmiutil: igetevent: 0809 08/31/10 12:02:47 INf BMC<br />
temperature #20 Baseboard temp hiN thresh oK now actual=32.00 C, threshold=54.00 C<br />
freeipmi Does not have a daemon to wait for IPMI events. the ipmimonitoring app just reads a sensor snapshot, interpreting their<br />
state.<br />
<strong>open</strong>IPMI the ipmi_ui will show events on the screen in hex, but does not attempt to interpret them, or send them to syslog<br />
C.3 EXAMPlES of WAtChDoG tIMEr USAGE<br />
ipmitool Watchdog is not supported<br />
ipmiutil # service ipmiutil_wdt start<br />
this utilitizes the cron daemon, so if it cannot launch a process, the watchdog will expire.<br />
freeipmi # service bmc-watchdog start<br />
If this service can no longer run, the watchdog will expire.<br />
<strong>open</strong>IPMI Supports a simple method via ipmi_watchdog kernel driver module <strong>and</strong> /dev/watchdog access. there are options to the<br />
ipmi_watchdog driver module to configure <strong>and</strong> start the watchdog (like ‘start_now=1’). If the kernel driver can no longer run,<br />
the watchdog will expire.<br />
C.4 Examples of configuring IPMI lAN <strong>and</strong> Sol<br />
Ipmitool ipmitool lan set 1 cipher_privs <br />
ipmitool lan set 1 ipaddr 192.168.1.193<br />
ipmitool lan set 1 password “”<br />
Ipmiutil ipmiutil lan –e –I 192.168.1.193 –p “”<br />
(user1 null password shown, can use –u / -p to set any username. Note that this comm<strong>and</strong> will do everything to produce a<br />
sane IPMI lAN configuration.)<br />
freeipmi bmc-config –n mybmc.cfg –-checkout<br />
(now edit mybmc.cfg to change all parameters needed, includes Sol)<br />
bmc-config –n mybmc.cfg --commit<br />
<strong>open</strong>IPMI In <strong>open</strong>ipmish or ipmi_ui: use raw, iterative ‘lanparm config’ <strong>and</strong> ‘solparm config’ comm<strong>and</strong>s.<br />
C.5 Examples of configuring IPMI PEf rules <strong>and</strong> SNMP alert destination<br />
Ipmitool ipmitool pef [info|status|policy|list]<br />
Supports showing PEf parameters, but not configuring them.<br />
(PEf is not implemented as a st<strong>and</strong>ard feature on <strong>Kontron</strong> AtCA boards since the shelf manager h<strong>and</strong>les PEf for the entire chassis)<br />
Ipmiutil ipmiutil lan –e –I 192.168.1.193 –p “” –A 192.168.1.161<br />
(-A gives explicit snmp alert destination, which is not needed if it was configured in snmpd.conf, also configures default or<br />
custom PEf rules)<br />
freeipmi ipmi-pef-config –n mypef.cfg –-checkout<br />
(now edit mypef.cfg to change all parameters needed, includes lAN alerting)<br />
ipmi-pef-config –n mypef.cfg –commit<br />
<strong>open</strong>IPMI In <strong>open</strong>ipmish or ipmi_ui, use raw, iterative ‘pef config’ <strong>and</strong> ‘lanparm config’ comm<strong>and</strong>s<br />
www.kontron.com/ocp
About <strong>Kontron</strong><br />
<strong>Kontron</strong> designs <strong>and</strong> manufactures embedded <strong>and</strong> communications st<strong>and</strong>ards-based, rugged CotS<br />
<strong>and</strong> custom solutions for oEMs, systems integrators, <strong>and</strong> application providers in a variety of<br />
markets. <strong>Kontron</strong> engineering <strong>and</strong> manufacturing facilities, located throughout Europe, North<br />
America, <strong>and</strong> Asia-Pacific, work together with streamlined global sales <strong>and</strong> support services to<br />
help customers reduce their time-to-market <strong>and</strong> gain a competitive advantage. <strong>Kontron</strong>’s diverse<br />
product portfolio includes: boards & mezzanines, Computer-on-Modules, hMIs & displays, systems<br />
& platforms, <strong>and</strong> rugged & custom capabilities.<br />
<strong>Kontron</strong> is a Premier member of the Intel® Embedded Alliance <strong>and</strong> has been a vDC Platinum<br />
vendor for Embedded Computer Boards 5 years running.<br />
<strong>Kontron</strong> is listed on the German tecDAX stock exchange under the symbol “KBC“.<br />
for more information, please visit: www.kontron.com<br />
CorPorAtE offiCES<br />
Europe, Middle East & Africa<br />
oskar-von-Miller-Str. 1<br />
85386 Eching/Munich<br />
Germany<br />
tel.: +49 (0)8165/ 77 777<br />
fax: +49 (0)8165/ 77 385<br />
sales@kontron.com<br />
North America<br />
14118 Stowe Drive<br />
Poway, CA 92064-7147<br />
USA<br />
tel.: +1 888 294 4558<br />
fax: +1 858 677 0898<br />
sales@kontron.com<br />
Asia Pacific<br />
17 Building,Block #1,ABP.<br />
188 Southern West 4th ring road<br />
Beijing 100070, P.r.China<br />
tel.: + 86 10 63751188<br />
fax: + 86 10 83682438<br />
knc@kontron.cn<br />
Whitepaper<br />
www.kontron.com/ocp<br />
www.kontron.com<br />
Copyright © 2011 <strong>Kontron</strong> Whitepaper - IPMI # 2011 PKM<br />
All data is for information purposes only <strong>and</strong> not guaranteed for legal purposes. Subject to change without notice. Information in this datasheet has been carefully checked <strong>and</strong> is<br />
believed to be accurate; however, no responsibilty is assumed for inaccurancies. All br<strong>and</strong> or product names are trademarks or registered trademarks of their respective owners.
Change language