- Community Home
- >
- Software
- >
- HPE OneView
- >
- HPE ONEView CommandLet New-OVClusterProfile
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
Forums
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
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
8 hours ago - last edited 7 hours ago
8 hours ago - last edited 7 hours ago
HPE ONEView CommandLet New-OVClusterProfile
I’m having an issue creating a Hypervisor Cluster Profile in HPE OneView using the PowerShell module. When I run the New-OVClusterProfile cmdlet, I immediately get this error:
New-OVClusterProfile: The "type" field content, "HypervisorClusterProfileV3", included in this request is not valid. Correct the content in the 'type' field of the JSON and retry the request.When I check the PowerShell module source, it still uses HypervisorClusterProfileV3 as the cluster profile type (see screenshot).
Version 3 in psm
However, when I look at existing cluster profiles created through the OneView GUI, they are all using HypervisorClusterProfileV6 (screenshot)Version 6 by gui-created.
So OneView clearly expects V6, but the PowerShell library is still hardcoded to V3.
I tried manually updating the PSM file so the cmdlet outputs “HypervisorClusterProfileV6”, but after doing that, the JSON that gets generated becomes invalid, and OneView returns errors saying there are “multiple problems with the JSON file.” So at this point V3 is rejected by the appliance, and V6 breaks the JSON structure if I try to force it.
problems with json
My questions:
Is there official PowerShell support for HypervisorClusterProfileV6?
Is the OneView PowerShell module outdated compared to the REST API schema?
Is there a supported or documented method to create V6 Hypervisor Cluster Profiles via PowerShell?
Why does modifying the PSM file cause the JSON to become invalid—are there additional schema fields required for V6 that the module doesn’t know about?
Any help or clarification would be really appreciated. I’ll add screenshots below.