<?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: SIM 5.1 alert problem in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036691#M48665</link>
    <description>closing thread</description>
    <pubDate>Thu, 29 Mar 2007 06:40:56 GMT</pubDate>
    <dc:creator>Peter Scaringi</dc:creator>
    <dc:date>2007-03-29T06:40:56Z</dc:date>
    <item>
      <title>SIM 5.1 alert problem</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036689#M48663</link>
      <description>I have HP SIM 5.1 working great, but a problem exists with my MS clustered DL380G4 and MSA1500.  I have had two predictive failure drives this month and SIM/OSEM/ISEE did not send the trap out to create a case number.  OSEM is not showing the alert either.  Is this because I do not have SMI-S installed ?  Before 5.1, I had the OSEM/ISEE installed and the traps would originate from both nodes to OSEM/ISEE, thus opening two HP case numbers.  Now with 5.1 I can not get failure traps on this cluster to go through OSEM/ISEE.  I know it works for single servers as I had another server get a predictive failure hard drive and it processed through get a HP case number.  Is there is something I am missing ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Claude&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Mar 2007 10:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036689#M48663</guid>
      <dc:creator>Peter Scaringi</dc:creator>
      <dc:date>2007-03-27T10:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 alert problem</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036690#M48664</link>
      <description>I fixed this one myself.  The bug in cluster monitoring in HP SIM 5.1 still exists.  After the cluster was switch nodes last week, HP SIM took the virtual IP on node 1 instead of it's physical IP.  I removed the server and readded/discovered it and now it seems to be working.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Mar 2007 06:40:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036690#M48664</guid>
      <dc:creator>Peter Scaringi</dc:creator>
      <dc:date>2007-03-29T06:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 alert problem</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036691#M48665</link>
      <description>closing thread</description>
      <pubDate>Thu, 29 Mar 2007 06:40:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-5-1-alert-problem/m-p/5036691#M48665</guid>
      <dc:creator>Peter Scaringi</dc:creator>
      <dc:date>2007-03-29T06:40:56Z</dc:date>
    </item>
  </channel>
</rss>

