[cisco-voip] 8.6 Upgrades L2 Upgrade vs Refresh Upgrade

[Lelio Fulgenzi]

OK. Thanks, I think I understand now. The underlying problem is the move to RHEL v5. I'm guessing this move doesn't happen to often. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Adam Frankel (afrankel)" <afrankel at cisco.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>, "Jason Aarons (AM)" <jason.aarons at dimensiondata.com> 
Sent: Monday, August 15, 2011 1:45:53 PM 
Subject: Re: [cisco-voip] 8.6 Upgrades L2 Upgrade vs Refresh Upgrade 


You cannot DRF backup and restore to a different version. Normal L2 upgrades make the use of "to side" (new version) binaries while still running in the "from side" (old version). In previous versions this was not an issue as binaries from different rhel versions could be run across versions. Rhel5 binaries cannot be run in Rhel4, creating the need for the RU upgrade. 

HTH, 
Adam 

------------Original Message-------------- 
From: Lelio Fulgenzi <lelio at uoguelph.ca> 
Sent: Mon, Aug 15, 2011 12:45:11 Am 
To: Adam Frankel (afrankel) <afrankel at cisco.com> 
CC: "cisco-voip ( cisco-voip at puck.nether.net )" <cisco-voip at puck.nether.net> , "Jason Aarons (AM)" <jason.aarons at dimensiondata.com> 
Subject: Re: [cisco-voip] 8.6 Upgrades L2 Upgrade vs Refresh Upgrade 



I haven't read through the release notes as to why the 128GB device is necessary, but is there any reason why this couldn't be done using the standard DRF utilities? I'm sure every entity is different, but now if I start having to purchase additional hardware for these upgrades after the whole "we can upgrade to a non-active partition" speech, it's gonna be difficult. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Adam Frankel (afrankel)" <afrankel at cisco.com> 
To: "Jason Aarons (AM)" <jason.aarons at dimensiondata.com> 
Cc: "cisco-voip ( cisco-voip at puck.nether.net )" <cisco-voip at puck.nether.net> 
Sent: Monday, August 15, 2011 12:32:00 PM 
Subject: Re: [cisco-voip] 8.6 Upgrades L2 Upgrade vs Refresh Upgrade 


Both are considered refresh upgrades because of the RHEL version change underneath. CUCM upgrade requires a USB drive and wipes the drives as well but only for 7825H3 and 7828H3. 

http://www.cisco.com/en/US 
/partner/docs/voice_ip_comm/cucm/rel_notes/8_6_1/cucm-rel_notes-861a.html#wp1996982 

https://supportforums.cisco.com/docs/DOC-16898 

Adam 
------------Original Message-------------- 
From: Jason Aarons (AM) <jason.aarons at dimensiondata.com> 
Sent: Mon, Aug 15, 2011 11:51:24 Am 
To: cisco-voip ( cisco-voip at puck.nether.net ) <cisco-voip at puck.nether.net> 
CC: 
Subject: [cisco-voip] 8.6 Upgrades L2 Upgrade vs Refresh Upgrade 





Per the Release Notes; 



For CallManger 8.6 is L2 Upgrade, upgrades using Inactive partition. 

For Unity Connection 8.6 is a Refresh Upgrade (wipes drive, 128GB USB required) 



How come they aren’t both a Refresh Upgrades? Why the difference under the hood? 



https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application/blog/2011/08/11/checklist-before-upgrading-to-unity-connection-86 



_______________________________________________
cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 

_______________________________________________ 
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/20110815/94b0c46b/attachment.html>