- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Simplivity Deployment Failed / step 32 of 33 - In...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
06-20-2019 12:52 AM
06-20-2019 12:52 AM
Simplivity Deployment Failed / step 32 of 33 - Invalid HMS session supplied when joining Federation
Hi guys,
I'm trying to deploy a 2 nodes HyperV cluster. The install of the first node works fine.
When adding the second node, the deployment failed at step 32 of 33 Invalid HMS session supplied when joining Federation.
Unexpected error trying to obtain a session token for url: https://x.x.x.x/pi/oauth/token
Connect to x.x.x.x:443 [/x.x.x.x] failed: Connection refused: connect
Any ideas why this step failed ?
Thanks.
Laurent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-21-2019 12:51 AM - edited 06-21-2019 12:56 AM
06-21-2019 12:51 AM - edited 06-21-2019 12:56 AM
Re: Simplivity Deployment Failed / step 32 of 33 - Invalid HMS session supplied when joining Federa
Hi Laurent,
At this stage of the deployment the node itself is fully deployed and should be functional. Some intermittent network issue may have caused the node to fail to join the federation. Typically have seen this to have been caused by MTU mismatches on storage or federation networks.
A simple test would be to login to the new OVC and attempt to manually join the federation using the below command:
sudo dsv-federation-join --peerip <ip-address>
*Where the peerip is the IP of the already deployed node.
If this fails then I would advise opening a support case for us to take a look. I would also be checking on the SCVMM server that the node successfully deployed to the cluster correctly.
Hope this helps, thanks!
I work for HPE

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP