<?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 discovery the Server, which has multi-ip address in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120618#M30684</link>
    <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;I installed SIM 5.1.0.2. After discovery there are some systems found, however some systems are actually the one server. for example,&lt;BR /&gt;&lt;BR /&gt;System abc-etl-1 (ip:172.8.1.130)&lt;BR /&gt;System abc-etl-1-330 (ip:172.8.2.130)&lt;BR /&gt;System abc-etl-1-out (ip:192.168.18.130)&lt;BR /&gt;System Serv_CNG742S0S0 (type:Server, no IP)&lt;BR /&gt;System 29.6.10.130 in Server Serv_CNG742S0S0 (type:Management Processor, ip:29.6.10.130)&lt;BR /&gt;&lt;BR /&gt;Above 5 systems actually stands for the one Server. How can I let SIM combine them to one?&lt;BR /&gt;&lt;BR /&gt;because of requirement of application, different ip address in the one server should be different DNS name.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
    <pubDate>Mon, 24 Dec 2007 13:59:32 GMT</pubDate>
    <dc:creator>Buzhou</dc:creator>
    <dc:date>2007-12-24T13:59:32Z</dc:date>
    <item>
      <title>discovery the Server, which has multi-ip address</title>
      <link>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120618#M30684</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;I installed SIM 5.1.0.2. After discovery there are some systems found, however some systems are actually the one server. for example,&lt;BR /&gt;&lt;BR /&gt;System abc-etl-1 (ip:172.8.1.130)&lt;BR /&gt;System abc-etl-1-330 (ip:172.8.2.130)&lt;BR /&gt;System abc-etl-1-out (ip:192.168.18.130)&lt;BR /&gt;System Serv_CNG742S0S0 (type:Server, no IP)&lt;BR /&gt;System 29.6.10.130 in Server Serv_CNG742S0S0 (type:Management Processor, ip:29.6.10.130)&lt;BR /&gt;&lt;BR /&gt;Above 5 systems actually stands for the one Server. How can I let SIM combine them to one?&lt;BR /&gt;&lt;BR /&gt;because of requirement of application, different ip address in the one server should be different DNS name.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Mon, 24 Dec 2007 13:59:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120618#M30684</guid>
      <dc:creator>Buzhou</dc:creator>
      <dc:date>2007-12-24T13:59:32Z</dc:date>
    </item>
    <item>
      <title>Re: discovery the Server, which has multi-ip address</title>
      <link>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120619#M30685</link>
      <description>I generally add the additional IP addresses to the Discovery exclusion list.</description>
      <pubDate>Tue, 25 Dec 2007 23:54:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120619#M30685</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2007-12-25T23:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: discovery the Server, which has multi-ip address</title>
      <link>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120620#M30686</link>
      <description>Also in additon what Rob suggested ,&lt;BR /&gt;Consider implementing tighter firewall rules that don't allow all traffic from all segments.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Dec 2007 12:11:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/discovery-the-server-which-has-multi-ip-address/m-p/4120620#M30686</guid>
      <dc:creator>Carlsberg</dc:creator>
      <dc:date>2007-12-27T12:11:21Z</dc:date>
    </item>
  </channel>
</rss>

