<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ibm-Bladecenter-H on BAFM</title><link>https://christian.blog.pakiheim.de/tags/ibm-bladecenter-h/</link><description>Recent content in Ibm-Bladecenter-H on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Tue, 10 Feb 2009 11:40:00 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/ibm-bladecenter-h/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitoring the IBM BladeCenter chassis with Nagios</title><link>https://christian.blog.pakiheim.de/posts/2009-02-10_monitoring-the-ibm-bladecenter-chassis-with-nagios/</link><pubDate>Tue, 10 Feb 2009 11:40:00 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1729</guid><description>&lt;p&gt;Today I ended up working out the details on what we want to monitor regarding our BladeCenter. The most interesting details (for us that is) are these:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fan speeds for Chassis Cooling/Power Module Cooling Bay(s)&lt;/li&gt;
&lt;li&gt;Temperature&lt;/li&gt;
&lt;li&gt;Power Domain utilization&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It wasn&amp;rsquo;t * &lt;strong&gt;that&lt;/strong&gt;* hard to implement. Only trouble(s) I ran into, were ( &lt;strong&gt;1&lt;/strong&gt;) IBM did a real shitty job with the &lt;a href="http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5078305&amp;amp;brandind=5000020"&gt;MIB&amp;rsquo;s&lt;/a&gt;. If you look closely into the mmblade.mib, you&amp;rsquo;re gonna notice, that not a single OID is specified for the events. ( &lt;strong&gt;2&lt;/strong&gt;) As the MIB&amp;rsquo;s weren&amp;rsquo;t documented anywhere, I had to look them up via &lt;em&gt;snmpwalk&lt;/em&gt; (which I had never used before). So as a reminder (to myself), here&amp;rsquo;s how it is done:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;div class="chroma"&gt;
&lt;table class="lntable"&gt;&lt;tr&gt;&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code&gt;&lt;span class="lnt" id="hl-0-1"&gt;&lt;a class="lnlinks" href="#hl-0-1"&gt;1&lt;/a&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;
&lt;td class="lntd"&gt;
&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;snmpwalk -v1 -c public -O n 10.0.0.35 .1.3.6.1.4.1.2.3.51.2.2
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;p&gt;This will get you a list, with a lot of output (5154 lines to be exact). Lucky me, the web interface of the management module/ssh interface is rather verbose, so all you need to do is compare those values with what you are looking for.&lt;/p&gt;
&lt;p&gt;So for myself (and anyone interested) read ahead for the list of checks we are currently running on the management module.&lt;/p&gt;</description></item></channel></rss>