[cisco-voip] upgrade during install from 9.0 to 9.1

[Garrett Skjelstad]

Back are the days of voice consultants carrying around binders of DVDs for every single version they could run across... As they are usually called when someone didn't do DRS planning that well...

Sent from my iPhone 5

On Jan 7, 2013, at 8:21, Ryan Ratliff <rratliff at cisco.com> wrote:

> Is there any way you can be entitled to the upgrade and not request media either be mailed to you or downloaded via e-delivery?  
> 
> Successful planning for DRS and an upgrade is itself a time consuming process.  Adding an extra line item to that checklist to get the correct media is going to be much less time consuming than having to troubleshoot a failure in the middle of a maintenance window that could be caused by any number of component interaction issues that aren't tested by anybody.
> 
> 
> -Ryan
> 
> On Jan 5, 2013, at 10:31 AM, Justin Steinberg <jsteinberg at gmail.com> wrote:
> 
> Agreed.  Especially when you can download the non-bootable upgrade ISO to go from 9.0 to 9.1.   Then if a subscriber fails, you have to get with TAC to get a bootable 9.1 (hours), or go through the edelivery (days) all over again.    This is a time consuming process. 
> 
> On Fri, Jan 4, 2013 at 5:10 PM, Nate VanMaren <VanMarenNP at ldschurch.org> wrote:
>>  
>> 
>> This just causes trouble for rebuilding/ adding new servers to an existing cluster.  Because you have to install the same version that is running on the cluster.
>> 
>>  
>> 
>> -Nate
>> 
>> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
>> Sent: Friday, January 04, 2013 1:26 PM
>> To: Matthew Loraditch
>> 
>> 
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] upgrade during install from 9.0 to 9.1
>> 
>>  
>> 
>> To close the loop on this the restriction was added in 8.6 (when refresh upgrade came in) because we don't test this upgrade between major versions and the fact that we started having to do OS reinstalls (refresh) for some combinations made the likelihood of failure too high.
>> 
>>  
>> 
>> It is not documented, and that will remedied in the Release Notes for 9.1 shortly and in the Upgrade/Install docs at some point in the future (they can't be changed as fast as release notes).
>> 
>>  
>> 
>> -Ryan
>> 
>>  
>> 
>> On Jan 2, 2013, at 4:34 PM, Matthew Loraditch <MLoraditch at heliontechnologies.com> wrote:
>> 
>>  
>> 
>> Well that’s good, I can just put a PUT order in edelivery and get it. Let’s see if it works.
>> 
>>  
>> 
>>  
>> 
>> Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA
>> 
>> 1965 Greenspring Drive
>> Timonium, MD 21093
>> 
>> voice. 410.252.8830
>> fax.  410.252.9284    
>> 
>> Twitter  |  Facebook  | Website  |  Email Support
>> 
>>  
>> 
>>  
>> 
>> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
>> Sent: Wednesday, January 02, 2013 4:22 PM
>> To: Tim Frazee
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] upgrade during install from 9.0 to 9.1
>> 
>>  
>> 
>> I was told this restriction was added around 8.5 but I'm still waiting on some other folks to comment.
>> 
>>  
>> 
>> To get to 9.1 you either do a fresh install or you upgrade, same as any other version.  I understand the release of 9.1 has immediately replaced 9.0 on new 9.x orders (much like 8.6 did for 8.5) so any 9.x media kit ordered today will be sent 9.1 bootable media.
>> 
>>  
>> 
>> -Ryan
>> 
>>  
>> 
>> On Jan 2, 2013, at 4:12 PM, Tim Frazee <tfrazee at gmail.com> wrote:
>> 
>> 
>> I could see that.
>> 
>> But tell that to my 8.5 upgrade from an 8.0 boot disk I was able to do back in the day......
>> 
>> In short, you say that the only way currently to get to 9.1 is upgrade from an already installed support version, not during the install process.
>> 
>> 
>> 
>> for the record and I know its not supported, I did try the hack of grabbing the boot info file from 9.0 and pushing it into the 9.1 iso. The install process failed post installing everything.
>> 
>> Thanks for digging Ryan.
>> 
>> 
>> 
>> 
>> On Wed, Jan 2, 2013 at 12:21 PM, Ryan Ratliff <rratliff at cisco.com> wrote:
>> 
>> Confirmed I see it here in the lab and it looks to be intentional, though I'm still digging.  
>> 
>> Initial word is for a while now upgrade-during-install is only supported to the same major/minor version.  
>> 
>>  
>> 
>> Anything beyond that requires a separate upgrade after install.
>> 
>>  
>> 
>> -Ryan
>> 
>>  
>> 
>> On Jan 2, 2013, at 11:18 AM, Tim Frazee <tfrazee at gmail.com> wrote:
>> 
>> 
>> I did just that. after I tried with the pre-release, I used my NFR iso. Same result.
>> 
>> I only used the pre-release because it was already on my datastore and i was feeling a bit lazy over vacation. After I attempted the same procedure with 9.0(1) -37 iso, I received the exact same error.
>> 
>> Ryan, should I be able to boot off of 9.0 and upgrade-during-install with 9.1?
>> 
>> On Wed, Jan 2, 2013 at 9:47 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
>> 
>> 9.0.0.99101-22 is not a 9.0 ES, it's a pre-release build of 9.1.  Throw it in the trash and try with a real 9.0 build (I'm going to start this now). 
>> 
>>  
>> 
>> -Ryan
>> 
>>  
>> 
>> On Jan 2, 2013, at 9:50 AM, Tim Frazee <tfrazee at gmail.com> wrote:
>> 
>> 
>> I didnt test to see if the 9.1 from CCO is bootable. In the past they havent been.
>> 
>> attached is a screenshoot of the error I received when I tried to feed the 9.1 via CCO during a booted-from-nfr9.0 media
>> 
>> On Mon, Dec 31, 2012 at 5:02 PM, Nate VanMaren <VanMarenNP at ldschurch.org> wrote:
>> 
>> I had lots of problems doing upgrade during installs with 9.0 ESs.  The ESs are usually bootable so I just gave up and installed fresh.  Is the 9.1 download bootable?
>> 
>>  
>> 
>>  
>> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130107/f08f297a/attachment.html>