<?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: Multiple IP causes discovery problems in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722909#M18111</link>
    <description>Have you looked into if there is any way you could solve that ? &lt;BR /&gt;&lt;BR /&gt;Does anyone know if there's some way to "lock" a record so that the name does not change ?</description>
    <pubDate>Thu, 09 Feb 2006 03:22:10 GMT</pubDate>
    <dc:creator>Mikael Rönnbäck</dc:creator>
    <dc:date>2006-02-09T03:22:10Z</dc:date>
    <item>
      <title>Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722905#M18107</link>
      <description>I've got several systems with multiple IP adresses and different names bound to the different adresses, does anyone know how I can prevent SIM from taking one of those names at "random" when displaying the servername in a query ? &lt;BR /&gt;&lt;BR /&gt;For example I want the server to be shown as "Server-123" and not as "DNS-Alias-1" or "DNS-Alias-2".</description>
      <pubDate>Thu, 02 Feb 2006 05:03:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722905#M18107</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-02T05:03:02Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722906#M18108</link>
      <description>I have two servers with multiple IP's. I just excluded the other IP's in auto discovery.</description>
      <pubDate>Thu, 02 Feb 2006 10:16:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722906#M18108</guid>
      <dc:creator>John Stalzer</dc:creator>
      <dc:date>2006-02-02T10:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722907#M18109</link>
      <description>Well, I have approx 2000 servers with over 50 different administrators spread out over a few hundred class A,B and C subnets, so I was hoping for an easier way to solve this since I have very little control over when someone might add another IP adress to a specific server ;-)</description>
      <pubDate>Thu, 02 Feb 2006 10:22:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722907#M18109</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-02T10:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722908#M18110</link>
      <description>I'm also having the same problem were the nodes are properly identified during discovery but then the name changes to a virutal server on my clusters.  This is also breaking the ability to get a software status on the servers.</description>
      <pubDate>Wed, 08 Feb 2006 18:06:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722908#M18110</guid>
      <dc:creator>Jim Reynolds_4</dc:creator>
      <dc:date>2006-02-08T18:06:59Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722909#M18111</link>
      <description>Have you looked into if there is any way you could solve that ? &lt;BR /&gt;&lt;BR /&gt;Does anyone know if there's some way to "lock" a record so that the name does not change ?</description>
      <pubDate>Thu, 09 Feb 2006 03:22:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722909#M18111</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T03:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722910#M18112</link>
      <description>Hiya,&lt;BR /&gt;&lt;BR /&gt;I found binding the SMH to a specific IP on the cluster helped:&lt;BR /&gt;settings -&amp;gt; system management homepage -&amp;gt; security -&amp;gt;ip binding&lt;BR /&gt;&lt;BR /&gt;After enabling that it stopped picking up the CNAME addresses</description>
      <pubDate>Thu, 09 Feb 2006 03:22:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722910#M18112</guid>
      <dc:creator>Craig McK</dc:creator>
      <dc:date>2006-02-09T03:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722911#M18113</link>
      <description>Ah, good idea I will try that one, however I'm not having only (MSCS-)clusters, I'm also having Veritas-clusters (which SIM does not recognize and so causes data corruption in the SIM database every time they fail over and SIM detects a node change), NLB-clusters (which does not seem to give me any problems), and simple multi-IP-systems, where one IP is used for the "real" machine, and additional IP's are used for example for separate websites or specific application needs, these also go bananas whenever SIM discovers the additional IP's.&lt;BR /&gt;But I'll check up if IP binding will help, though I can't say it will make life much happier if it does consideing the number of monitored devices to configure, still thanks for the idea :-)&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Feb 2006 03:45:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722911#M18113</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T03:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722912#M18114</link>
      <description>Hmm, this may be a stupid question but should I need to boot the machine for this to work ? &lt;BR /&gt;&lt;BR /&gt;I enabled IP binding on one machine and now it won't show the SMH except via the localhost interface, it said it only required restarting the SMH but I can't access the SMH remotely via the adress I specified in the binding ?</description>
      <pubDate>Thu, 09 Feb 2006 03:58:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722912#M18114</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T03:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722913#M18115</link>
      <description>You shouldn't need to reboot - I just restarted the SMH.&lt;BR /&gt;&lt;BR /&gt;I'm trying to look at this just now, but have just updated to SP4 and haven't reset the path as per the previous post =)&lt;BR /&gt;</description>
      <pubDate>Thu, 09 Feb 2006 04:08:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722913#M18115</guid>
      <dc:creator>Craig McK</dc:creator>
      <dc:date>2006-02-09T04:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722914#M18116</link>
      <description>Ok, well, seems I either did something wrong or I don't quite understand what the problem is, since I disabled the IP binding and restarted the SMH and it still won't respond except via localhost. Doesn't seem too reliable to me ?</description>
      <pubDate>Thu, 09 Feb 2006 04:15:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722914#M18116</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T04:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722915#M18117</link>
      <description>Which version of the SMH do you have installed?</description>
      <pubDate>Thu, 09 Feb 2006 04:28:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722915#M18117</guid>
      <dc:creator>Craig McK</dc:creator>
      <dc:date>2006-02-09T04:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722916#M18118</link>
      <description>On this particular system: 2.1.0.121 (which I think places it with the SSD 7.30 bundle)</description>
      <pubDate>Thu, 09 Feb 2006 04:37:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722916#M18118</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T04:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722917#M18119</link>
      <description>ah, I'd updated to 2.1.4.143 which I believe fixed a few issues regarding IP Binding?&lt;BR /&gt;&lt;BR /&gt;Same as this post:&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=966278" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=966278&lt;/A&gt;</description>
      <pubDate>Thu, 09 Feb 2006 04:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722917#M18119</guid>
      <dc:creator>Craig McK</dc:creator>
      <dc:date>2006-02-09T04:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple IP causes discovery problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722918#M18120</link>
      <description>Thanks, I did think of that after you mentioned it so I did an upgrade after posting my answer and yes now the IP binding seems to work. Should be interesting to see if it helps out in the multiple IP issue.</description>
      <pubDate>Thu, 09 Feb 2006 04:47:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/multiple-ip-causes-discovery-problems/m-p/3722918#M18120</guid>
      <dc:creator>Mikael Rönnbäck</dc:creator>
      <dc:date>2006-02-09T04:47:46Z</dc:date>
    </item>
  </channel>
</rss>

