<?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: Traps from ESX Servers in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585243#M40170</link>
    <description>That looks like a problem with the ILO itself. I would log a call with HP.</description>
    <pubDate>Wed, 17 Feb 2010 19:33:17 GMT</pubDate>
    <dc:creator>Rob Buxton</dc:creator>
    <dc:date>2010-02-17T19:33:17Z</dc:date>
    <item>
      <title>Traps from ESX Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585242#M40169</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I try to manage my two ESX 4.0 Update1 in HP SIM 5.3 sp1. I installed on ESX Server "HP ManagementAgents for VMware ESX 4.x" version 8.3.1&lt;BR /&gt;The SNMP work and the 2 nodes was discovered as server "Proliant DLXX G5" with OS Linux - VMware Esx Server.&lt;BR /&gt;&lt;BR /&gt;I receive traps from both ESX servers:&lt;BR /&gt;Remote Insight mouse cable disconnected (9009)&lt;BR /&gt;Remote Insight keyboard cable disconnected (9008)&lt;BR /&gt;Remote Insight/Integrated LightsOut Self Test Error (9005)&lt;BR /&gt;&lt;BR /&gt;I receive this messages several times a day into HP SIM&lt;BR /&gt;&lt;BR /&gt;What's going Wrong.&lt;BR /&gt;&lt;BR /&gt;Thank</description>
      <pubDate>Wed, 17 Feb 2010 07:03:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585242#M40169</guid>
      <dc:creator>Ales Kostohryz</dc:creator>
      <dc:date>2010-02-17T07:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Traps from ESX Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585243#M40170</link>
      <description>That looks like a problem with the ILO itself. I would log a call with HP.</description>
      <pubDate>Wed, 17 Feb 2010 19:33:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585243#M40170</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2010-02-17T19:33:17Z</dc:date>
    </item>
    <item>
      <title>Re: Traps from ESX Servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585244#M40171</link>
      <description>I just experienced the same issue. I logged into the iLo Management and in "Diagnostics" I reset the iLo agent, it cleared up the issue.&lt;BR /&gt;I am running ESX vSphere 4 on 2 DL360 G5 servers. If you are unable to get into the iLo management console you can download "sp19719.exe" and follow the instructions, this will let you reset the diagnostics on the iLo agent.</description>
      <pubDate>Wed, 17 Feb 2010 20:36:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/traps-from-esx-servers/m-p/4585244#M40171</guid>
      <dc:creator>john_eco</dc:creator>
      <dc:date>2010-02-17T20:36:50Z</dc:date>
    </item>
  </channel>
</rss>

