Non-simplivity host masquerading as a Simplivity node.

[policeman51]

We are deploying a new Simplivity node in our cluster.
The HPE deployment team ran into an issue where the deployment was getting an error connecting to a non-simplivity host.
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.
The technician checked and that host wasn't sharing any storage with Simplivity.  It also doesn't show up running svt-federation-show.  It never was part of a simplivity cluster.  It actually was an old Windows box we converted over to ESXi.
The server is an older HP DL380p Gen8.  We actually have 2 others in that cluster, but for some reason the Simplivity Deployment Manager wanted to connect to it to verify connectivity.

Has annyone ever seen this and know of any settings to change to stop that from happening.
I'm worried that other Simplivity servers will try and connect to it at some point. 

[DaveOb]

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.

Was the ESXi in an existing cluster ?

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.

[policeman51]

Thanks for the reply.  The deployment tech stated the same thing that it wouldn't harm anything.

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.

When deploying we even put the troublesome host in maintenance mode, but the deployment manager still tried contacting it.  Seems like there is some reference to the host in the federation somewhere.  

[DaveOb]

DM is just trying to accertain the layout of a potential federation for the deployment , there is no reference within the federation itself  so other then the deployment there is no issue going forward.