<?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 MS 2000 and Veritas Cluster afecting SIM server name discovery in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/ms-2000-and-veritas-cluster-afecting-sim-server-name-discovery/m-p/3921005#M24644</link>
    <description>I have 4 MS servers running veritas cluster software and when discovered in SIM the primary IP is not th server itself, When oters servers belomgimg to this cluster are then added some of them force previous to change anem or the manual discovery error come up as we already have that server name, How to force SIM to use the server primary IP ....</description>
    <pubDate>Thu, 04 Jan 2007 13:33:57 GMT</pubDate>
    <dc:creator>CA1499584</dc:creator>
    <dc:date>2007-01-04T13:33:57Z</dc:date>
    <item>
      <title>MS 2000 and Veritas Cluster afecting SIM server name discovery</title>
      <link>https://community.hpe.com/t5/server-management-systems/ms-2000-and-veritas-cluster-afecting-sim-server-name-discovery/m-p/3921005#M24644</link>
      <description>I have 4 MS servers running veritas cluster software and when discovered in SIM the primary IP is not th server itself, When oters servers belomgimg to this cluster are then added some of them force previous to change anem or the manual discovery error come up as we already have that server name, How to force SIM to use the server primary IP ....</description>
      <pubDate>Thu, 04 Jan 2007 13:33:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/ms-2000-and-veritas-cluster-afecting-sim-server-name-discovery/m-p/3921005#M24644</guid>
      <dc:creator>CA1499584</dc:creator>
      <dc:date>2007-01-04T13:33:57Z</dc:date>
    </item>
  </channel>
</rss>

