#Emc powerpath license license key
#Emc powerpath license install
#Emc powerpath license update

At the time of this writing, the 6.2 release is named: Grab your PowerPath bundle from EMCвЂ™s website. You will probably need to unregister the licenses and re-register unfortunately do that via command line on the PPMA server: rpowermt unregister host=192.0.2.1 So anyway, shut the old ELMS down and switch to PPMA much better experience for new hosts, old hosts, and ongoing maintenance/licensing since it pulls all that data from vCenter. The 2.2 PPMA can manage older PowerPath versions too so youвЂ™re safe there. No more running the stupid rpowermt stuff to license your hosts, query them to see if PowerPath has gone through its inevitable forgetting of its license, etc. You get your new license from them, paste it into the web interface of PPMA, bam, all your licenses are now there. YouвЂ™ll find your old key on your ELMS server in /etc/emc/licenses.

#Emc powerpath license license key

It will get all your vSphere hosts from vCenter, then talk to them to see if theyвЂ™re using PowerPath, if theyвЂ™re licensed, and can push licenses to them if thatвЂ™s what you want.ДЄ simple support ticket with your old ELMS license key is all you need to have them issue a new license key for your PPMA system. Where it gets interesting is the web interface itвЂ™s a web-driven system that communicates with vCenter and your PowerPath hosts on your behalf (along with any non-vmware systems using PowerPath if you want it to). What does it do that is different? Well, it has the same command line RTOOLS stuff that the ELMS appliance has, so you wonвЂ™t miss anything there. YouвЂ™ll need the 2.2 release if youвЂ™re on vCenter 6.5 2.1 doesnвЂ™t support it and wonвЂ™t deploy correctly using the OVF on vSphere/vCenter 6.5. It is the PowerPath Management Appliance (PPMA). Then we get to work on PowerPath.ДЇirst things first if youвЂ™re using an older style ELMS license appliance, thereвЂ™s a new kid in town. It will upgrade, you reboot, now your host is on 6.5.

#Emc powerpath license update

Then run: esxcli software profile update -d /vmfs/volumes//update-from-esxi6.5-6.5_update01.zip -p It will spit out your options for profile names, typically youвЂ™d want the -standard option without the s, not the no-tools version or the s version. You MUST give the esxcli command the full path even if youвЂ™re in the same directory.

ThatвЂ™s the current filename for the 6.5 offline upgrade.

If youвЂ™re not familiar with the offline bundle process, hereвЂ™s a page that documents it:Д«asically you download the offline bundle (a zip file) from the vmware site, stick it on a LUN your vSphere host has mounted, put the host in maintenance mode, enable ssh, log in, then run: esxcli software sources profile list -d /vmfs/volumes//update-from-esxi6.5-6.5_update01.zip Or this if youвЂ™re on 5.5U2 or 6.0: esxcli software vib remove -vibname= -vibname= -vibname= SSH in, run this if youвЂ™re on 5.5: esxcli software vib remove -nВ В -n -n Skip ahead if you donвЂ™t want info on that vSphere upgrade or PowerPath removal.Д«efore starting, I recommend you get rid of your old PowerPath once youвЂ™re in maintenance mode.

#Emc powerpath license install

My steps were maintenance mode, remove PowerPath, reboot, вЂњofflineвЂќ upgrade to 6.5, reboot, install PowerPath 6.2, re-license. My upgrade path was 5.5 to 6.5, with PowerPath 5.9 to 6.2. VMware is up to 6.5 on vSphere/vCenter, the web-based interface continues to suck, North Korea has ballistic missiles wtf is going on.ДЄnyway, letвЂ™s get on with the show. Wow, four years have gone by since my article about upgrading PowerPath to 5.9 for vSphere 5.5 support.