- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: Non-simplivity host masquerading as a Simplivi...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2019 01:07 PM
12-16-2019 01:07 PM
Non-simplivity host masquerading as a Simplivity node.
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.
I'm worried that other Simplivity servers will try and connect to it at some point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2019 03:08 AM
12-17-2019 03:08 AM
Re: Non-simplivity host masquerading as a Simplivity node.
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.
I am an HPE employee
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2019 07:52 AM
12-17-2019 07:52 AM
Re: Non-simplivity host masquerading as a Simplivity node.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2019 03:19 AM
12-18-2019 03:19 AM
Re: Non-simplivity host masquerading as a Simplivity node.
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.
I am an HPE employee
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]