<?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 ISEE Events in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895195#M54</link>
    <description>Is it possible for ISEE to pick up Serious Events as well as Critical ones? The reason is that of our power supplies failed on a FC10 and ISEE did not pick this up because it was classed a Serious Event and not Critical Event.&lt;BR /&gt;This did cause us some problems as you can guess and questions were raised why we was using ISEE when Predictive support would have picked it up.&lt;BR /&gt;&lt;BR /&gt;Any help welcome.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Jeff&lt;BR /&gt;</description>
    <pubDate>Mon, 03 Feb 2003 15:43:16 GMT</pubDate>
    <dc:creator>Jeff Souter</dc:creator>
    <dc:date>2003-02-03T15:43:16Z</dc:date>
    <item>
      <title>ISEE Events</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895195#M54</link>
      <description>Is it possible for ISEE to pick up Serious Events as well as Critical ones? The reason is that of our power supplies failed on a FC10 and ISEE did not pick this up because it was classed a Serious Event and not Critical Event.&lt;BR /&gt;This did cause us some problems as you can guess and questions were raised why we was using ISEE when Predictive support would have picked it up.&lt;BR /&gt;&lt;BR /&gt;Any help welcome.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Jeff&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Feb 2003 15:43:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895195#M54</guid>
      <dc:creator>Jeff Souter</dc:creator>
      <dc:date>2003-02-03T15:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE Events</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895196#M55</link>
      <description>I believe it is possible. Weve had power supplies go down on L's/N's and via ISEE HP have called us to notify us. Either you need to configure it in resmon (under /etc/opt) or if your ISEE isnt working properly. &lt;BR /&gt;</description>
      <pubDate>Mon, 03 Feb 2003 15:56:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895196#M55</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-02-03T15:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE Events</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895197#M56</link>
      <description>Jeff,&lt;BR /&gt;&lt;BR /&gt;The intention in the A.02.50 ISEE is to be really proactive, probably that's why you didn't receive any anotification. The follow page shows the active monitors on ISEE.&lt;BR /&gt;&lt;A href="http://sstwww.fc.hp.com/cgi-bin/TrueCM/%5BEMS_listeners/Current%5D/docs/emsMonitors.htm" target="_blank"&gt;http://sstwww.fc.hp.com/cgi-bin/TrueCM/%5BEMS_listeners/Current%5D/docs/emsMonitors.htm&lt;/A&gt;&lt;BR /&gt;However, you can add monitors modifiyng the configuration files.&lt;BR /&gt;Please review the Troubleshooting guide &lt;A href="http://grnd.fc.hp.com/rst_support/docs/hot_topics.htm." target="_blank"&gt;http://grnd.fc.hp.com/rst_support/docs/hot_topics.htm.&lt;/A&gt;&lt;BR /&gt;From page 12 to 14 explains which are the configuration files in the /var/stm/config/tools/monitor, the rst* files are the ISEE confuration ones. In those files you can change the flag of the event number in order to add to the monitor.</description>
      <pubDate>Tue, 04 Feb 2003 15:57:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-events/m-p/2895197#M56</guid>
      <dc:creator>Arturo Acevedo</dc:creator>
      <dc:date>2003-02-04T15:57:14Z</dc:date>
    </item>
  </channel>
</rss>

