<div>There seems to have been a lapse of planning on Cisco's part especially when moving from physical hardware to VMWare. They are pusing people toward VMWare but don't give us a decent upgrade path to get there.</div>
<div> </div>
<div> <br><br></div>
<div class="gmail_quote">On Thu, May 3, 2012 at 10:39 AM, Ki Wi <span dir="ltr"><<a href="mailto:kiwi.voice@gmail.com" target="_blank">kiwi.voice@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi Beck,<br>Do you have 7.1.4 something ? Can you try that? Hope you have took some snapshot along the way.<br>
<br>Sent from my iPhone<br>Pls pardon my fat fingers.<br><br>On 3 May, 2012, at 10:22 PM, "Beck, Andre" <<a href="mailto:cisco-voip@ibh.net">cisco-voip@ibh.net</a>> wrote:<br><br>> Hi Ki Wi,<br>><br>
> I'm currently trying to do something similar, coming from 6.1(2).<br>><br>> On Tue, Apr 24, 2012 at 01:36:25AM +0800, Ki Wi wrote:<br>>> It is working. Just make sure you don't start the CM services till you are at the final version with actual license file.<br>
><br>> I've tried that:<br>><br>> * Establish VM with same MAC as the original Publisher<br>> * Install 6.1(2) and restore Pub from DRF backup<br>> --> Here I have a fully working (and licensed) copy of the Pub running<br>
> * Upgrade to 6.1.4.2190-3 as 6.1(2) is mostly a dead end for upgrades<br>> --> Still a licensed and working Pub<br>> * Now disable all services that can be disabled, install<br>> ciscocm.refresh_upgrade_v1.1.cop, then upgrade to <a href="tel:7.1.5.33900-10" value="+17153390010">7.1.5.33900-10</a>.<br>
><br>> After that step, all services are still deactivated. But the next step<br>> of upgrading to 8.6(2a) is made impossible by the silly<br>><br>> Upgrades are prohibited during Licensing Grace Period.<br>
><br>> problem. I hoped you found a way around that (in not starting services),<br>> but either I pulled it off wrongly, or it doesn't always work. Must I<br>> make sure they never run once after DRF import? Or maybe things are<br>
> different when coming from DMA then they are when coming from DRF...<br>><br>>> I have done upgrade from 3.x to 8.0 or 8.5 in VMware environment. A couple of upgrade before I can do DMA. A couple of upgrade before I can hit 8.x since DMA don't go 8.x directly.<br>
><br>> That sounds extremly interesting. I'd like to know which versions you used<br>> exactly, as this seems to make a difference more often than not. For<br>> instance, I'm trying to hop via 7.1.5 mainly because going from 6.1.x<br>
> to 8.x doesn't seem to work in a VM, it's always ending with a hardware<br>> platform unsupported bailout (seemingly due to wrong detection of disk<br>> size).<br>><br>>> Unsupported method but definitely it's working.<br>
><br>> Sometimes you have no other way to upgrade. Cisco seems to think that you<br>> should have a complete lab copy of your production hardware or even do<br>> your upgrades in the production environment. Even the swing server method<br>
> is unnecessarily complicated by the prevention of upgrades in license<br>> grace period. I'm getting the feeling that they don't think a lot about<br>> the people who actually have to maintain those installations. Reading<br>
> <a href="http://docwiki.cisco.com/wiki/Licensing_Model_for_Virtualized_UC_Applications" target="_blank">http://docwiki.cisco.com/wiki/Licensing_Model_for_Virtualized_UC_Applications</a><br>> almost made me cry. Now you have to relicense when your SMTP server changes<br>
> name? My Goodness...<br>><br>> TIA,<br>> Andre.<br>> --<br>> Cool .signatures are so 90s...<br>><br>> -> Andre Beck +++ ABP-RIPE +++ IBH IT-Service GmbH, Dresden <-<br>
<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br>