[cisco-voip] CUCM 8.6 licenses disappear on reboot

Ryan Ratliff rratliff at cisco.com
Tue Jul 10 11:50:20 EDT 2012


This would be my exact recommendation.  Slow-roll the new major releases but once you commit to the upgrade go straight to the latest available in that version.  

-Ryan

On Jul 10, 2012, at 11:34 AM, Buchanan, James wrote:

Speaking from the channel side, I certainly don't take that position. That said, when a new major release comes out (like 9.0), I exercise caution and make sure to read the release notes closely as well as the SRND. With a minor release and a service release, there generally is a reason for it, such as SU1, so in a situation like this one that's been described, I would go straight to SU1, still having read the release notes. A lot of this comes back to experience, and lists like this help all of us share our experiences and go forth better informed. 

James Buchanan| UC Technology Manager | Presidio South | Presidio Networked Solutions 
12 Cadillac Dr Ste 130 Brentwood, TN 37027 | jbuchanan at presidio.com
D: 615-866-5729 | F:615-866-5781  www.presidio.com


-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Gurtz
Sent: Tuesday, July 10, 2012 10:26 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 8.6 licenses disappear on reboot

> I'm curious why each of you would do an upgrade to 8.6(2) base when 
> SU1 is out there on cisco.com?  You still have to order the 8.6(2) 
> upgrade via PUT to get the license but there's no reason to do the 
> 2-step
upgrade
> when SU1 is the desired destination (or should be).

I can't speak for any others of course but I can say that our reseller is staunchly against upgrading...period. The only time they will recommend an upgrade is when we are actively experiencing a known bug and there is no workaround. This goes for Cisco VOIP as well as more traditional IOS/ASAOS devices. There seems to be a perception and intense fear of "spaghetti code" type issues. e.g. fix this; break that, general likelihood of regressions, etc... With all the bugs and warts experienced I'm not sure I would say the fear is unfounded! With no Linux CLI access to actually fix anything, the fear increases.

Internally, we are not allowed to do anything unless recommended/approved by our reseller.

It would be great if Cisco could (broadly) inform the channel
(VARs/Resellers/Etc...) about the benefits of keeping software up-to-date vs. the "Mainframe Mentality." Also, best practices WRT testing/QA for bugs before roll-out...

Again, that's our situation, hoping it's not a widespread one.

~JasonG

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
This message w/attachments (message) is intended solely for the use of the intended recipient and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments.  Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120710/94666067/attachment.html>


More information about the cisco-voip mailing list