<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CMU v5.1.2 and BL460 Gen8 monitoring in Server Clustering</title>
    <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5960483#M454</link>
    <description>&lt;P&gt;Typically "no time to perform" means collectl does not yet have enough data to display yet. &amp;nbsp;I think it could also mean that the collectl daemon on that node may not be set up to collect disk, ethernet, and interconnect data. &amp;nbsp;can you post the daemon line from that node in /etc/collectl.conf. &amp;nbsp;If you &amp;nbsp;look at the manpage for collectl, under the section for subsystems you see the various parts of a system you can monitor; lowercase is summary information, and uppercase is detailed information.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Feb 2013 16:13:47 GMT</pubDate>
    <dc:creator>Dave-SBS</dc:creator>
    <dc:date>2013-02-11T16:13:47Z</dc:date>
    <item>
      <title>CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5958847#M453</link>
      <description>&lt;P&gt;Hi, we have SSH to and from nodes ok, but some fields show up as "No time to perform" instead of real data.&lt;/P&gt;&lt;P&gt;cpuload, disk_write/read, net_out/in and ib0_out/in just show "No time to perform" - all other fields are okey.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;We run SLES 11 SP2 on the nodes.&lt;/P&gt;&lt;P&gt;See picture. Anyone with a good suggestion?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2013 17:15:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5958847#M453</guid>
      <dc:creator>Ronny Horgen</dc:creator>
      <dc:date>2013-02-08T17:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5960483#M454</link>
      <description>&lt;P&gt;Typically "no time to perform" means collectl does not yet have enough data to display yet. &amp;nbsp;I think it could also mean that the collectl daemon on that node may not be set up to collect disk, ethernet, and interconnect data. &amp;nbsp;can you post the daemon line from that node in /etc/collectl.conf. &amp;nbsp;If you &amp;nbsp;look at the manpage for collectl, under the section for subsystems you see the various parts of a system you can monitor; lowercase is summary information, and uppercase is detailed information.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2013 16:13:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5960483#M454</guid>
      <dc:creator>Dave-SBS</dc:creator>
      <dc:date>2013-02-11T16:13:47Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5960619#M455</link>
      <description>We don't use collectl , and on an old shelf with bl460g6 and SLES 11 SP1 it works fine with just the standard monitoring in CMU.</description>
      <pubDate>Mon, 11 Feb 2013 19:34:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5960619#M455</guid>
      <dc:creator>Ronny Horgen</dc:creator>
      <dc:date>2013-02-11T19:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961245#M456</link>
      <description>&lt;P&gt;Sorry. My bad. &amp;nbsp;You don't say if you did this or not, so I will ask. Did you:&lt;/P&gt;&lt;P&gt;1. reinstall monitoriing on the gen8 nodes?&lt;/P&gt;&lt;P&gt;2. stop and restart monitoring?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 13:42:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961245#M456</guid>
      <dc:creator>Dave-SBS</dc:creator>
      <dc:date>2013-02-12T13:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961329#M457</link>
      <description>1. yes, I have tried this several time&lt;BR /&gt;2. yes, I have done this.&lt;BR /&gt;No change - still showing "No time to perform" for the fields indicated.</description>
      <pubDate>Tue, 12 Feb 2013 15:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961329#M457</guid>
      <dc:creator>Ronny Horgen</dc:creator>
      <dc:date>2013-02-12T15:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961647#M458</link>
      <description>&lt;P&gt;Hi again, you maybe are right. It looks like collectl are set up on the head-node and first part of the cluster. I will check more on this tomorrow, and report back.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Feb 2013 20:25:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5961647#M458</guid>
      <dc:creator>Ronny Horgen</dc:creator>
      <dc:date>2013-02-12T20:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5962029#M459</link>
      <description>Thanks Dave for getting me in the right direction. I installed and configured collectl on the new nodes, and now everything is fine.</description>
      <pubDate>Wed, 13 Feb 2013 08:17:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5962029#M459</guid>
      <dc:creator>Ronny Horgen</dc:creator>
      <dc:date>2013-02-13T08:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: CMU v5.1.2 and BL460 Gen8 monitoring</title>
      <link>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5962435#M460</link>
      <description>Well, good; I'm glad you got that fixed. Collectl is a great tool to use both in and outside of CMU.</description>
      <pubDate>Wed, 13 Feb 2013 14:50:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/cmu-v5-1-2-and-bl460-gen8-monitoring/m-p/5962435#M460</guid>
      <dc:creator>Dave-SBS</dc:creator>
      <dc:date>2013-02-13T14:50:35Z</dc:date>
    </item>
  </channel>
</rss>

