<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
If you really don’t want mac changing then you should use a static mac address on the VM, similar to ELM/PLM.
<div class=""><br class="">
</div>
<div class=""><a href="https://kb.vmware.com/s/article/219" class="">https://kb.vmware.com/s/article/219</a></div>
<div class=""><br class="">
<div class="">-Ryan </div>
<div><br class="">
<div class="">On Dec 5, 2017, at 6:48 AM, Nathan Reeves <<a href="mailto:nathan.a.reeves@gmail.com" class="">nathan.a.reeves@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Licensing on the expressway VM's is tied to the BIOS UUID (uuid.bios) and the Ethernet0 MAC Address (ethernet0.address) of the VM's. The Serial number (and subsequently generated Release Keys based on the Serial number) should remain
the same across upgrades. Moving the VM between ESXi Hosts (assuming a VMware cluster) should not impact the Licensing in any way. Move of the machine to a new host manually will most likely prompt asking if you copied or moved, I would suggest choosing
moved, but not 100% sure that this maintains the machine UUID or just the VC uuid.
<div class="">
<div class=""><br class="">
</div>
<div class="">Recovery wise, you can record the UUID and Mac address (grab the VMX file from the ESXi host) of the current VM's, along with the Serial and Release keys. </div>
<div class=""><br class="">
</div>
<div class="">Once you've deployed the new VM from OVA, manually update the VM vmx file:</div>
<div class="">- Remove the VM from Inventory (not delete from disk).</div>
<div class="">- Download the new vmx file, update the uuid.bios and ethernet0.address values, and then upload to the VM folder on the ESXi Datastore.</div>
<div class="">- Right click on the vmx file and choose 'Add to inventory'.</div>
<div class=""><br class="">
</div>
<div class="">This ~should~ end up giving you the same serial number on the VM on boot and allow you to re-enter the release keys. If you don't see the same serial number, double check your values in the vmx.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">HTH</div>
<div class=""><br class="">
</div>
<div class="">Nathan</div>
</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Tue, Nov 28, 2017 at 10:52 PM, Lelio Fulgenzi <span dir="ltr" class="">
<<a href="mailto:lelio@uoguelph.ca" target="_blank" class="">lelio@uoguelph.ca</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
I'm new to the Expressway world, so new, we had a partner come in and help us set them up. :O<br class="">
<br class="">
We had a weird experience with the licensing with one host, which needed manual intervention, but for the most things went ok.<br class="">
<br class="">
This raises the question, however, of how I can plan to move these VMs to another host, upgrade them, then move them again.<br class="">
<br class="">
As far as I can tell, the serial number to which the license is tied is generated at installation time and is not changed when a VM is moved, but I'm not sure this holds when the expressway o/s is upgraded.<br class="">
<br class="">
My goal is to upgrade the 4 vm cluster (2C+2E) offline then move them to the online network, rebalancing our ESXi hosts as we do this.<br class="">
<br class="">
I understand that even if we are successful in moving the VMs without rehosting the license, if we ever encounter a situation where we need to recover from backup, we need to consider if this will fail because of the licenses or is there a way around that?<br class="">
<br class="">
Thoughts?<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
Lelio<br class="">
</font></span><br class="">
______________________________<wbr class="">_________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" class="">cisco-voip@puck.nether.net</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank" class="">https://puck.nether.net/<wbr class="">mailman/listinfo/cisco-voip</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br class="">
cisco-voip mailing list<br class="">
<a href="mailto:cisco-voip@puck.nether.net" class="">cisco-voip@puck.nether.net</a><br class="">
https://puck.nether.net/mailman/listinfo/cisco-voip<br class="">
</div>
</div>
<br class="">
</div>
</body>
</html>