[cisco-voip] Upgrade from 10.5.2 ->11.5.1

Mon Oct 10 13:29:44 EDT 2016

Tac Gave me the wrong number from the case notes.

Here is correct info- 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva17964/?referring_site=bugquickviewredir

-- 

Michael T. Voity

Network Engineer

University of Vermont

From: NateCCIE [mailto:nateccie at gmail.com] 
Sent: Monday, October 10, 2016 13:05
To: Michael Voity <mvoity at uvm.edu>; 'voip puck' <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Upgrade from 10.5.2 ->11.5.1

Great news Mike.

I went to look up that bug, but I can’t find it, is it missing a digit?

Nate vanMaren

SOLUTIONS ARCHITECT

M 1 801 718-2308

E nvanmaren at convergeone.com <mailto:nvanmaren at convergeone.com> 

1226 East 6600 South
Salt Lake City, UT 84121

 <http://convergeone.com/> convergeone.com

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Michael Voity
Sent: Monday, October 10, 2016 10:06 AM
To: 'voip puck' <cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> >
Subject: Re: [cisco-voip] Upgrade from 10.5.2 ->11.5.1

Hello, 

I want to thank all of you for your advice on my upgrade.  This is how it went.

Used PCD to upgrade and switch CUC and CUCM.   Went flawless no issue whatsoever.

I manually upgrade CUPS because I had a but hit, CSCva1796, during upgrade.   

Once CUCM, CUC, and CUPS went back to normal, I upgraded VCS-E and C to 8.8.2.

All is working flawless now.

Thanks to all that responded!

-Mike

-- 

Michael T. Voity

Network Engineer

University of Vermont

From: avholloway at gmail.com <mailto:avholloway at gmail.com>  [mailto:avholloway at gmail.com] On Behalf Of Anthony Holloway
Sent: Thursday, October 06, 2016 15:26
To: NateCCIE <nateccie at gmail.com <mailto:nateccie at gmail.com> >
Cc: Ryan Huff <ryanhuff at outlook.com <mailto:ryanhuff at outlook.com> >; Michael Voity <mvoity at uvm.edu <mailto:mvoity at uvm.edu> >; voip puck <cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> >
Subject: Re: [cisco-voip] Upgrade from 10.5.2 ->11.5.1

Don't get me wrong, I didn't mean to imply that PCD as a whole is garbage.  I was only talking about his desire to use it to perform an L2 upgrade from 10.5 to 11.5.

Actually, L2 upgrades are now called SU, for Standard Upgrade.  You know, cause we weren't already using SU for anything else.

PCD is a life saver for 6x to 11x and Network Migrations.  But for an SU (in the newer sense of the meaning), it's just one more thing to read up on and manage.  Especially if you consider that there are already upgrade bugs to watch out for in CUCM <https://bst.cloudapps.cisco.com/bugsearch/bug/CSCva84316>  itself, and adding in PCD bugs <https://bst.cloudapps.cisco.com/bugsearch/bug/CSCul50567>  just makes things more complicated.

On Thu, Oct 6, 2016 at 10:00 AM, NateCCIE <nateccie at gmail.com <mailto:nateccie at gmail.com> > wrote:

I would like to say I love PCD.  It is I think the best way to go P to V.  It does upgrades and reboots so nicely.  It is great for installing phone firmware or device packs, instead of touching each node.  It is very cautious, making sure nodes are on-line before it proceeds.  It emails statuses as things succeed or crap out.

It is also great at deploying new nodes or whole new clusters.

I have no hesitation scheduling an upgrade overnight and checking on it in the morning.  It will  pause if something goes awry.

And on the upgrade to 11.5, I had one blow up really big (without PCD) where on the 3rd time the server rebooted after being upgraded to 11.5 SU1, it would no longer boot.  I ended up rebuilding the publisher from a subscriber (because I didn’t have a 11.5 backup yet) then when I rebooted the other 5 nodes to talk to the publisher, 3 of them also died.  I pushed TAC for a BU escalation, and they came back with a  procedure to reinstall vmtools and the servers were back online, then I did the same to the original publisher.  I was rebooting the cluster because I also had lots and lots of certificates that were expired and I prefer a reboot to restarting services when there are so many certs being messed with.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb21486/

There should be an ES out tomorrow that fixes another one of my favorite 11.5 bugs https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb09481.  I have grown to depend on that feature in RTMT.

Thanks,

-Nate

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net <mailto:cisco-voip-bounces at puck.nether.net> ] On Behalf Of Ryan Huff
Sent: Thursday, October 06, 2016 8:20 AM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com <mailto:avholloway%2Bcisco-voip at gmail.com> >
Cc: voip puck <cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> >
Subject: Re: [cisco-voip] Upgrade from 10.5.2 ->11.5.1

I would also add that, even if you do let PCD run wild, at best it is another server to setup and get working (assuming new PCD install and not re tasking an existing) on top of reading the PCD guides ... etc.

So even if it all goes perfect, you're still down the time it takes to get PCD up and working from a OS/network perspective. 

Basically, you're adding in a layer to a process that yields no more benefit (IMO) other than to be able to say you used PCD.

I'm not trying to be negative to PCD; it's actually a fantastic idea -just not "there" yet from a development perspective.

I would love a product that could completely automate the migration process in all circumstances (although, I would miss my ANSI art installation menus); however, I'm not sure Cisco has a ton of emphasis on that right now (IMO) so ....

In practice, I would not use PCD because there are enough caveats that it isn't worth it to me. I would have to be able to blindly trust it to get the value out of it that I'd need and in my opinion, PCD is not at a point where it can be trusted in that manner.

-Ryan

Sent from my iPhone

On Oct 6, 2016, at 10:02 AM, Anthony Holloway <avholloway+cisco-voip at gmail.com <mailto:avholloway+cisco-voip at gmail.com> > wrote:

I think the most important thing to know is, upgrading your apps via PCD is no different than you upgrading them yourself.  That is, unless you plan to be asleep while it's happening, and just wake up in the morning on 11.5. 

If instead you plan to babysit the PCD process, you really are not gaining anything by using PCD to do the upgrade for you.  You still have to plan for the upgrade as if PCD were not involved: read upgrade guides, release notes, read mes, install COP files, clear disk space, plan the phone firmware upgrade, check compatible phones (and yes you're going to lose phone support in 11.5), check gateway compatibility, upgrade Jabber, and the list goes on.

PCD is going to save you zero time and effort, and in fact, it will increase your work effort, because on top of everything you are already responsible for in planning and executing the upgrade normally, now you need to read the PCD guides and cross your fingers you don't hit a PCD bug in the process. 

So, like I said, unless you're going to let PCD run all by itself while you're away, I wouldn't bother with it.  But really, who is ready to trust PCD to an unattended upgrade, to include a switch version?

That's my opinion on the matter.  Let's hear from you, why you are using PCD for this task in the first place, and what benefits you think it brings to your project.

On Thu, Oct 6, 2016 at 8:17 AM, Michael Voity <mvoity at uvm.edu <mailto:mvoity at uvm.edu> > wrote:

Hello, 

This weekend I am going to be upgrading our CUCM, CUC and CUPS cluster from 10.5.2 to 11.5.1.

I will be using PCD to execute and switch the upgrade.    Upgrade will be applied Friday, and Sunday the switch will happen.

I have read the doc:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115.html

It seems pretty straight forward.  

My question to the group is, are there any issues I should be concerned about or is there something the doc missed that I need to do?

As always, thanks for reading.

-Mike

-- 

Michael T. Voity

Network Engineer

University of Vermont

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161010/00adbc7a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3145 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161010/00adbc7a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 121034 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161010/00adbc7a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 111765 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161010/00adbc7a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5984 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161010/00adbc7a/attachment.p7s>