- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Vendor pathing policies on vSphere Essentials Plus...
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
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
11-04-2014 12:55 PM
11-04-2014 12:55 PM
This is a question I've been pondering for awhile and never got a clear answer. I know VMware lists Storage APIs for Array Integration/MPIO as an Enterprise and Enterprise+ license feature, but its been my experience that a vendor supplied PSP plugins (Nimbles NCM, EqualLogic MEM, etc) seem to install fine on Hosts licensed for Essentials Plus and above. I was surprised after discovering this, and even more so after finding that all available paths were active and working as expected.
I hadn't thought about it for awhile until I noticed in Nimble's 2.1.x guide it just lists ESXi 5.x Hosts with no license level requirement.
Anybody else ever notice this? Is this one of those "it works, but isn't supported" type of deals?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2014 11:30 PM
11-05-2014 11:30 PM
SolutionIndeed, this is a topic of debate inside Nimble too at the time.
Speaking with VMware engineers the consensus is that Enterprise or Enterprise Plus licensing is required for this functionality, but vSphere doesn't enforce that restriction should it find a lower license key - this is up to 5.5 u1 where we are today.
Our vSphere installation MPIO vib actually installs two services - NCM (Connection Manager) and NCS (Connection Services); whilst it may appear to be working on the front end it's unknown whether the Connection Service daemon is running as expected; so in an example of an multi-array scaleout cluster having NCS not working as we expect could be detrimental. This is where Engineering (including Wen Yu and a few others) are trying to figure this out right now.
Whether this will change in vSphere 6 is unknown and is something we're trying to clarify! Stay tuned...
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2014 05:15 AM
11-06-2014 05:15 AM
Re: Vendor pathing policies on vSphere Essentials Plus/Standard?
Glad to hear I'm not the only one who noticed this
Thank you for the response, I'll keep an eye out on what engineering figures out - especially when working with a scaleout cluster!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2015 06:09 AM
04-01-2015 06:09 AM
Re: Vendor pathing policies on vSphere Essentials Plus/Standard?
Do you have an update on this?
According to the webpage below, vSphere 6.0 Standard licensing includes Virtual Volumes, but does not include Storage APIs for Array Integration, Multipathing.
Compare VMware vSphere Editions and Kits Comparison | United States
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2015 06:13 AM
04-01-2015 06:13 AM
Re: Vendor pathing policies on vSphere Essentials Plus/Standard?
Hello Kevin,
Nothing's changed it seems from my statement on 5.5 above. Note: VVOLs isn't solely reliant on the 3rd party MPIO enhancement that we can provide... but it sure helps!
twitter: @nick_dyer_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2018 01:57 PM
07-06-2018 01:57 PM
Re: Vendor pathing policies on vSphere Essentials Plus/Standard?
I figured I'd post a quick update here. I want to point out that the MPIO / Third-Party Multi-pathing and vSphere Storage APIs for Array Integration features are indeed supported with vSphere 6.x Standard edition license.
While they may technically work, they are still not licensed/supported with lower editions (Essentials Plus, Essentials, and free Hypervisor).
References:
VMware KB article: Product offerings for vSphere 6.x (2109507)
VMware PDF: Compare VMware vSphere Editions
Page from HPE Nimble Storage Deployment Considerations for VMware vSphere 6