<?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 ip problems in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080355#M127</link>
    <description>Stefan,&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply; I will be patient...&lt;BR /&gt;&lt;BR /&gt;Martijn</description>
    <pubDate>Tue, 30 Sep 2003 02:52:50 GMT</pubDate>
    <dc:creator>M.J. van der Meer</dc:creator>
    <dc:date>2003-09-30T02:52:50Z</dc:date>
    <item>
      <title>ISEE ip problems</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080353#M125</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;We have several middleware servers on HPUX 11.11 with clustered weblogic nodes. Because of the clustering there are two ip-addresses per server, so one for the server (machine) itself and one for weblogic clustering (crossover cable). Now the problem is that when ISEE submits its weekly cron information to HP, HP returns an information message that the incident has been closed or something similar.  The message from HP contains also an URL ("To view more details about this incident, click on the following link")with the ip-number of the weblogic internal clustering; with this link (ip-number) it is not possible to connect via the GUI to he server. Replacing this ip with the correct ip all goes fine. Now what can I do, so that the incoming message from HP contains the correct ip-address?&lt;BR /&gt;Thanks for all your replies in advance&lt;BR /&gt;Martijn</description>
      <pubDate>Mon, 29 Sep 2003 06:13:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080353#M125</guid>
      <dc:creator>M.J. van der Meer</dc:creator>
      <dc:date>2003-09-29T06:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE ip problems</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080354#M126</link>
      <description>Hi Martijn,&lt;BR /&gt;&lt;BR /&gt;this is a known problem and currently I'm not aware of any workaround. The problem is that ISEE always takes the LAST lan card's IP address/hostname (lan0, lan1, lan2 ...) to generate the mail. The ISEE Lab is aware of this error and a fix is planned for future releases of ISEE. If anybody finds a workaround, this would be a good place to post it.&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;BR /&gt;&lt;BR /&gt;Stefan</description>
      <pubDate>Mon, 29 Sep 2003 07:12:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080354#M126</guid>
      <dc:creator>Stefan Stechemesser</dc:creator>
      <dc:date>2003-09-29T07:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: ISEE ip problems</title>
      <link>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080355#M127</link>
      <description>Stefan,&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply; I will be patient...&lt;BR /&gt;&lt;BR /&gt;Martijn</description>
      <pubDate>Tue, 30 Sep 2003 02:52:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/isee-ip-problems/m-p/3080355#M127</guid>
      <dc:creator>M.J. van der Meer</dc:creator>
      <dc:date>2003-09-30T02:52:50Z</dc:date>
    </item>
  </channel>
</rss>

