[cisco-voip] Staging/ Bridge server upgrades.

Andy andy.carse at gmail.com
Mon Jul 2 12:27:29 EDT 2012


Thank you guys for the pointers

Rgds

Andy

On 02/07/2012 14:33, Ryan Ratliff wrote:
> To add to Dennis' previous email keep in mind if you go through an 8.x 
> interim release you are doing security due to SBD.  With SBD it is 
> imperative you do a full cluster restore (from 8.x to 8.x+) and that 
> database replication is good before you point phones to the cluster 
> because we keep certificates in the database and private keys on the 
> filesystem and DRS backup.
>
> We are working to update the documentation to call out these risks and 
> the recommended mitigations.
>
> -Ryan
>
> On Jun 30, 2012, at 9:55 AM, Heim, Dennis wrote:
>
> And doing a “show itl” from the ssh of each cucm node will give you an 
> idea if you got a shot of having valid SBD (security by default) 
> working on the new cluster.
> Dennis Heim
> Sr. UC Engineer
> World Wide Technology
> Office: 314.212.1814
> Email:dennis.heim at wwt.com <mailto:dennis.heim at wwt.com>
> www.wwt.com <http://www.wwt.com/>
> *From:*Jason Aarons (AM) [mailto:jason.aarons at dimensiondata.com]
> *Sent:*Saturday, June 30, 2012 9:27 AM
> *To:*andy.carse at gmail.com <mailto:andy.carse at gmail.com>; 
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>; Heim, 
> Dennis
> *Subject:*Re: [cisco-voip] Staging/ Bridge server upgrades.
>
> I would consider restoring tftp servers if you have a lot of custom 
> ringtones, wallpaper, etc. Else you can restore them from tar backup file.
>
> Sent from my Android phone using TouchDown (www.nitrodesk.com 
> <http://www.nitrodesk.com/>)
>
> -----Original Message-----
> *From:*Heim, Dennis [Dennis.Heim at wwt.com <mailto:Dennis.Heim at wwt.com>]
> *Received:*Saturday, 30 Jun 2012, 7:22am
> *To:*Andy [andy.carse at gmail.com 
> <mailto:andy.carse at gmail.com>];cisco-voip at puck.nether.net 
> <mailto:cisco-voip at puck.nether.net>[cisco-voip at puck.nether.net 
> <mailto:cisco-voip at puck.nether.net>]
> *Subject:*Re: [cisco-voip] Staging/ Bridge server upgrades.
>
>
>
> Unless you are doing stuff with security/certificates or have a lot of 
> MOH files where it would be painful to copy them over, there is no 
> reason to bring the subscribers with you through multi-stage upgrades. 
> I have almost always just moved the pub through the various versions 
> and then reinstalled the subs from scratch. I think you are supposed 
> to be able to go from 7.1(3) to 8.0(3), but it never works for me, I 
> have to stop as 7.1(5). It has been awhile, so I can't remember exactly.
>
> Dennis Heim
> Sr. UC Engineer
> World Wide Technology
> Office: 314.212.1814
> Email:dennis.heim at wwt.com <mailto:dennis.heim at wwt.com>
> www.wwt.com <http://www.wwt.com/>
>
> -----Original Message-----
> From:cisco-voip-bounces at puck.nether.net 
> <mailto:cisco-voip-bounces at puck.nether.net>[mailto:cisco-voip-bounces at puck.nether.net] 
> <mailto:[mailto:cisco-voip-bounces at puck.nether.net]>On Behalf Of Andy
> Sent: Saturday, June 30, 2012 1:02 AM
> To:cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> Subject: [cisco-voip] Staging/ Bridge server upgrades.
>
> I know this subject has been covered in many other conversations, but 
> I can't find this particular question/ answer in them.
>
> I have been trying to complete an upgrade from 7.0.2 to 8.5.1 (via
> 7.1.5) using a set of staging servers, but the process I have been 
> given requires that replication is checked after each version upgrade.
> This has caused me quite a lot of pain!
>
> So for what I think should be a quite straightforward process
>
> 1. Take DRS bakup from production.
> 2. Build Staging server to Production CUCM version.
> 3. DRS Restore to Staging Server (Publisher only?) 4. Upgrade via an 
> intermediate version of CUCM (if required) 5. Install Software licence 
> files for new version of CUCM on Staging server 6. DRS Backup on the 
> required version of CUCM.
> 7. Build new version on UCS.
> 8. DRS Restore.
> 9. Rehome licences to new Publisher.
> 10. Build new Subscribers.
> 11. Test
> 12. Cutover
>
> Why would you upgrade subscribers as well as we are really only 
> interested in getting the publisher database to the correct version of 
> code.
>
> So assuming the process in Ok, is there any benefit from trying to 
> test after each upgrade.
>
> Is it required?
>
> Or as I've found you just open yourself up to a "world of pain" and 
> frustration.
>
> I don't suppose there is a cisco doc for this that someone can point 
> me at, as I'd really not want to go through this again
>
> --
> Rgds
>
> Andy
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> itevomcid
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto: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/20120702/1fb43eba/attachment.html>


More information about the cisco-voip mailing list