<?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: Non-simplivity host masquerading as a Simplivity node. in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073361#M1101</link>
    <description>&lt;P&gt;&lt;EM&gt;DM is just trying to accertain the layout of a potential federation for the deployment , there is no reference within the federation itself&amp;nbsp; so other then the deployment there is no issue going forward.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Dec 2019 11:19:04 GMT</pubDate>
    <dc:creator>DaveOb</dc:creator>
    <dc:date>2019-12-18T11:19:04Z</dc:date>
    <item>
      <title>Non-simplivity host masquerading as a Simplivity node.</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073082#M1080</link>
      <description>&lt;DIV&gt;&lt;FONT&gt;We are deploying a new Simplivity node in our cluster.&lt;BR /&gt;The HPE deployment team ran into an issue where the deployment was getting an error connecting to a non-simplivity host.&lt;BR /&gt;They were able to bypass the error, but does anyone know why a non-simplivity host would be broadcasting (for lack of a better term) as a Simplivity node.&lt;BR /&gt;The technician checked and that host wasn't sharing any storage with Simplivity.&amp;nbsp; It also doesn't show up running svt-federation-show.&amp;nbsp; It never was part of a simplivity cluster.&amp;nbsp; It actually was an old Windows box we converted over to ESXi.&lt;BR /&gt;The server is an older HP DL380p Gen8.&amp;nbsp; We actually have 2 others in that cluster, but for some reason the Simplivity Deployment Manager wanted to connect to it to verify connectivity.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT&gt;Has annyone ever seen this and know of any settings to change to stop that from happening.&lt;BR /&gt;I'm worried that other Simplivity servers will try and connect to it at some point.&amp;nbsp; &lt;/FONT&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 16 Dec 2019 21:07:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073082#M1080</guid>
      <dc:creator>policeman51</dc:creator>
      <dc:date>2019-12-16T21:07:26Z</dc:date>
    </item>
    <item>
      <title>Re: Non-simplivity host masquerading as a Simplivity node.</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073163#M1087</link>
      <description>&lt;P&gt;Deployment manager will try to verify the deployed nodes in cluster to check if they are compatible with the version of Simplivity you are trying to deploy, I imagine the ESXi was not contactable by whatever method the DM is using to verify.&lt;/P&gt;&lt;P&gt;Was the ESXi in an existing cluster ?&lt;/P&gt;&lt;P&gt;Its definitly not going to cause an issue with anything trying to connect to simplivity neither the ESXi or Simplivity will have an idea of the existance of each other.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2019 11:08:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073163#M1087</guid>
      <dc:creator>DaveOb</dc:creator>
      <dc:date>2019-12-17T11:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: Non-simplivity host masquerading as a Simplivity node.</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073210#M1092</link>
      <description>&lt;P&gt;Thanks for the reply.&amp;nbsp; The deployment tech stated the same thing that it wouldn't harm anything.&lt;/P&gt;&lt;P&gt;Yes, the host is in an existing cluster, but not the cluster the new Simplivity node was going to so I thought that was strange.&lt;/P&gt;&lt;P&gt;When deploying we even put the troublesome host in maintenance mode, but the deployment manager still tried contacting it.&amp;nbsp; Seems like there is some reference to the host in the federation somewhere. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2019 15:52:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073210#M1092</guid>
      <dc:creator>policeman51</dc:creator>
      <dc:date>2019-12-17T15:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: Non-simplivity host masquerading as a Simplivity node.</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073361#M1101</link>
      <description>&lt;P&gt;&lt;EM&gt;DM is just trying to accertain the layout of a potential federation for the deployment , there is no reference within the federation itself&amp;nbsp; so other then the deployment there is no issue going forward.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 11:19:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/non-simplivity-host-masquerading-as-a-simplivity-node/m-p/7073361#M1101</guid>
      <dc:creator>DaveOb</dc:creator>
      <dc:date>2019-12-18T11:19:04Z</dc:date>
    </item>
  </channel>
</rss>

