<?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: isee with proxy squid in Insight Remote Security</title>
    <link>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819155#M86</link>
    <description>Hello Rene,&lt;BR /&gt;what do you want to monitor with ISEE? It it is a storage device like an EVA you surely need Webes but not OSEM.&lt;BR /&gt;If you want to monitor a server like a proliant you will as well need the insight agents.&lt;BR /&gt;If the wesea test sends an evetn but no ISEE case is generated type the command &lt;BR /&gt;wsea status&lt;BR /&gt;and check wether ISEE notification is enabled. Is not you can turn is on with &lt;BR /&gt;desta isee on&lt;BR /&gt;If OSEM does not send trapt to isee, check the OSEM view (setting --&amp;gt; internal) wether communications to ISEE is enabled.&lt;BR /&gt;You can as well check the corresponding logfile for any error messages, the default directory is &lt;BR /&gt;C:\Program Files\Hewlett-Packard\OSEM\logs&lt;BR /&gt;check the RSM_log.0.log&lt;BR /&gt;&lt;BR /&gt;If OSEM/Webes is configured correctly and everything works fine you should see the test events in the client user interface.&lt;BR /&gt;&lt;BR /&gt;An other thing is wether ISEE is really sending the events to HP. To check this, opened a console session and execute the command&lt;BR /&gt;C:\Program Files\Hewlett-Packard\ISEE\RemoteSupport\config\iseeConnectivityTest.bat&lt;BR /&gt;This should generate a manual connectivity test in the user interface. Click on the event and check the status - it should change to recieved and in the end to closed&lt;BR /&gt;If this does not happen, check the ISEE logfile:&lt;BR /&gt;C:\Program Files\Hewlett-Packard\ISEE\MotiveChorus\log\mad.log&lt;BR /&gt;Hope this help a bit&lt;BR /&gt;Frauke&lt;BR /&gt;</description>
    <pubDate>Sat, 08 Jul 2006 03:16:56 GMT</pubDate>
    <dc:creator>Frauke Denker_2</dc:creator>
    <dc:date>2006-07-08T03:16:56Z</dc:date>
    <item>
      <title>isee with proxy squid</title>
      <link>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819154#M85</link>
      <description>Plase your help.&lt;BR /&gt;I install:&lt;BR /&gt;Isee 3.95&lt;BR /&gt;Osem 1.4&lt;BR /&gt;Webes 444&lt;BR /&gt;Proxy squid 2.5&lt;BR /&gt;Iexplorer v 6.02&lt;BR /&gt;&lt;BR /&gt;Osem send traps &lt;BR /&gt;Wsea test send mail&lt;BR /&gt;But Isee no send data to isee.americas.hp.com&lt;BR /&gt;&lt;BR /&gt;Iexplorer view: &lt;A href="http://isee.americas.hp.com/mots/motserv" target="_blank"&gt;http://isee.americas.hp.com/mots/motserv&lt;/A&gt; ; &lt;A href="http://isee.americas.hp.com:80/mots/motserv" target="_blank"&gt;http://isee.americas.hp.com:80/mots/motserv&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Telnet isee.americas.hp.com 80 is ok&lt;BR /&gt;&lt;BR /&gt;Regards Rene&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jul 2006 20:09:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819154#M85</guid>
      <dc:creator>Rene Mendez_4</dc:creator>
      <dc:date>2006-07-06T20:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: isee with proxy squid</title>
      <link>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819155#M86</link>
      <description>Hello Rene,&lt;BR /&gt;what do you want to monitor with ISEE? It it is a storage device like an EVA you surely need Webes but not OSEM.&lt;BR /&gt;If you want to monitor a server like a proliant you will as well need the insight agents.&lt;BR /&gt;If the wesea test sends an evetn but no ISEE case is generated type the command &lt;BR /&gt;wsea status&lt;BR /&gt;and check wether ISEE notification is enabled. Is not you can turn is on with &lt;BR /&gt;desta isee on&lt;BR /&gt;If OSEM does not send trapt to isee, check the OSEM view (setting --&amp;gt; internal) wether communications to ISEE is enabled.&lt;BR /&gt;You can as well check the corresponding logfile for any error messages, the default directory is &lt;BR /&gt;C:\Program Files\Hewlett-Packard\OSEM\logs&lt;BR /&gt;check the RSM_log.0.log&lt;BR /&gt;&lt;BR /&gt;If OSEM/Webes is configured correctly and everything works fine you should see the test events in the client user interface.&lt;BR /&gt;&lt;BR /&gt;An other thing is wether ISEE is really sending the events to HP. To check this, opened a console session and execute the command&lt;BR /&gt;C:\Program Files\Hewlett-Packard\ISEE\RemoteSupport\config\iseeConnectivityTest.bat&lt;BR /&gt;This should generate a manual connectivity test in the user interface. Click on the event and check the status - it should change to recieved and in the end to closed&lt;BR /&gt;If this does not happen, check the ISEE logfile:&lt;BR /&gt;C:\Program Files\Hewlett-Packard\ISEE\MotiveChorus\log\mad.log&lt;BR /&gt;Hope this help a bit&lt;BR /&gt;Frauke&lt;BR /&gt;</description>
      <pubDate>Sat, 08 Jul 2006 03:16:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819155#M86</guid>
      <dc:creator>Frauke Denker_2</dc:creator>
      <dc:date>2006-07-08T03:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: isee with proxy squid</title>
      <link>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819156#M87</link>
      <description>Plase how to verify if conexion with proxy es correctly.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Rene</description>
      <pubDate>Mon, 10 Jul 2006 16:18:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-security/isee-with-proxy-squid/m-p/3819156#M87</guid>
      <dc:creator>Rene Mendez_4</dc:creator>
      <dc:date>2006-07-10T16:18:52Z</dc:date>
    </item>
  </channel>
</rss>

