Hello, looking for assistance on licensing PowerPath on ESXi in a large environment. How does EMC recommend doing this so that we do not have to type the username and password of each host in the environment? I have read about served and unserved and would like EMC's recommendation for doing this.
We normally advice sites with more than 50 ESXi hosts to user the “served” license so you don’t need to manually register each one of the hosts.
Itzik Reich | Advisory vSpecialist | EMC Israel
Thanks for the reply and served is what we have decided to use. Now could you help us with the setup of the served licensing? How do we enter credentials only one time and have all hosts licensed? Does this continue to work after we change host passwords?
We have served licenses. So far, the easiest way is to use the lockbox. Granted we'll have to update the lockbox when the VMware admins change the root password but we can script this piece. The other missing component is adding the ESXi server to Powerpath Viewer and having to authenticate again. Any easy way of accomplishing this task?
I am glad Mark Wright has joined to keep me in line. As he stated the storage team has already setup the licensing as served and decided that the easist way to license the VMware ESXi hosts is to use the lockbox feature. Unfortunately it has to be scripted outside of PowerPath (easily done) and every time the VMware support team changes host root password (every 90 days) this process must be done again. As Mark stated, the other issue is that again the hosts must be authenticated again to use PowerPath viewer. There must be a better and more enterprise way of performing these actions. The site here is much greater than 50 ESXi hosts as it is over 200 globally. Please help us here to make this better for both teams.
We have the same problems too.
Served license which is itself a mess if you reinstall a host from scratch and get a new UUID. EMC licensing support needed weeks to create new licenses for us.
After the upgrade to ESXi we realized one day that most of the host were running in unlicensed mode. We opened an SR and got the explanation that it is expected behaviour that after rebooting a host you need to "autoregister" it by issuing a command using rpowermt.
We keep the SR open because for us it is not acceptable that rebooting a host results in violating the license terms.
This was my thread https://community.emc.com/message/641362#641362
I will redirect all readers to this thread. Let's collect voices and show EMC that we have a problem with this limitation.
Sorry for the delay in responding - we usually monitor the PowerPath /VE forum for these types of questions but we'll start monitoring this site as well.
I want to make sure the EMC is clear in communicating to you and all forum readers that PowerPath/VE 5.7 for VMware is NOT in an unlicensed state upon ESX reboot. Once PowerPath/VE 5.7 is installed in the ESX kernel and licensed it is always licensed across reboots until it is specifically removed. I'll make sure that our documentation and future conversations reinforce this. The Primus Solution emc281559 that Conor refers to in your thread describes how to automatically re-register the license for display, monitoring, and configuration change purposes. At no time is PPVE multipathing disabled upon ESX reboot.
I appreciate your feedback that this is not an ideal situation and we are working with VMware and internally to make the reboot process even more automated in the future.
Thanks for your interest and input in making PowerPath/VE an even better product. Should you have any additional feedback please do not hesitate to leave it here or contact me off-line.
PowerPath Product Manager
We have a document that might help answer this and other PP/VE License related questions.
Home > Products > Software P-R > PowerPath > FAQs Frequently Asked Questions: PowerPath/VE Licensing
For the lockbox-related question, some users might want to take advantage of vSphere CIM tickets. It is documented in the Installation and Administration Guide on Powerlink:
Home > Support > Technical Documentation and Advisories > Software ~ P-R ~ Documentation > PowerPath Family > PowerPath/VE > Installation/Configuration
Look for "CIM Ticket Authentication"
Also see this VMware link:
We have tried using the CIM ticket. If I recall the CIM ticket expires within a few minutes, and if you reboot the host you have to reregister the host. The lockbox is ok for now, however it would be really nice if we could just use a read only account to register the host. Also, why do I need to specify the root user when adding to Powerpath Viewer.