<?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: BL 20p G3 running esx 2.5.1 clock problems in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652552#M46143</link>
    <description>Kov,&lt;BR /&gt;&lt;BR /&gt;Thanks for responce,  Trouble is that these are live systems, and whilst we can vmotion to other blades, we will impact performance to the other systems. Its certainly an idea to follow up.&lt;BR /&gt;&lt;BR /&gt;cheers mate</description>
    <pubDate>Wed, 19 Oct 2005 07:42:52 GMT</pubDate>
    <dc:creator>john_347</dc:creator>
    <dc:date>2005-10-19T07:42:52Z</dc:date>
    <item>
      <title>BL 20p G3 running esx 2.5.1 clock problems</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652550#M46141</link>
      <description>HI all,&lt;BR /&gt;&lt;BR /&gt;Has anyone come across blade servers hardware clocks running fast.  We are running racks of BL 20p G3 and we had a problem with one virtual server running slow by 1/2 hr (DFS server) which stopped connections to the server.  When we checked the clocks on the blades they seem to be running 1/2 hr fast ?????  The rest of the virutual servers seem to be fine..  &lt;BR /&gt;&lt;BR /&gt;Any thoughts welcomed.</description>
      <pubDate>Wed, 19 Oct 2005 05:04:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652550#M46141</guid>
      <dc:creator>john_347</dc:creator>
      <dc:date>2005-10-19T05:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: BL 20p G3 running esx 2.5.1 clock problems</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652551#M46142</link>
      <description>&lt;BR /&gt;Boot to F9 System ROM configuration and let system stand for usual time when you loose 1/2 hours.&lt;BR /&gt;Find firstly if problem Software or Hardware. &lt;BR /&gt;</description>
      <pubDate>Wed, 19 Oct 2005 07:30:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652551#M46142</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2005-10-19T07:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: BL 20p G3 running esx 2.5.1 clock problems</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652552#M46143</link>
      <description>Kov,&lt;BR /&gt;&lt;BR /&gt;Thanks for responce,  Trouble is that these are live systems, and whilst we can vmotion to other blades, we will impact performance to the other systems. Its certainly an idea to follow up.&lt;BR /&gt;&lt;BR /&gt;cheers mate</description>
      <pubDate>Wed, 19 Oct 2005 07:42:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl-20p-g3-running-esx-2-5-1-clock-problems/m-p/3652552#M46143</guid>
      <dc:creator>john_347</dc:creator>
      <dc:date>2005-10-19T07:42:52Z</dc:date>
    </item>
  </channel>
</rss>

