[cisco-voip] BE5K to BE6K upgrade

Brian Meade bmeade90 at vt.edu
Fri Apr 4 09:58:22 EDT 2014


Russell,

Transfering and conferencing will work fine.  You'll only have issues with
secure services such as corporate directory.  If both clusters are going to
be up at the same time, I'd really suggest doing the Bulk Certificate
Export/Consolidate/Import method instead of the rollback method.  That way
your users won't lose any features prior to the migration.

https://supportforums.cisco.com/document/60716/migrating-ip-phones-between-clusters-cucm-8-and-itl-files

Brian


On Fri, Apr 4, 2014 at 4:04 AM, Russell Chaseling
<rchaseling at plannet21.ie>wrote:

>  Thanks all!!!
>
>
>
> Another query as I don't have access to a lab at the moment to test. Once
> Rollback Parameter has been set to True and phones reset and the ITL has
> been removed has anyone done any testing of phone functionality?
>
>
>
> I understand directory services (ie Extension Mobility, Corporate
> Directory etc ) will not work but TAC engineer is telling me that
> transferring and conferencing etc will not work either?? In fact he's
> saying that nothing will work except for basic calling. I sort of find this
> hard to believe so just wondering if anyone can confirm or deny this
>
>
>
> The customers preference is to reset the phones very early in the morning
> before we upgrade that night - they can do without directory services but
> transferring......not willing to take this risk
>
>
>
> Cheers
>
> Russell
>
>
>
> *From:* Erick Bergquist [mailto:erickbee at gmail.com]
> *Sent:* 04 April 2014 06:50
> *To:* Mehtab Shinwari
> *Cc:* Russell Chaseling; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] BE5K to BE6K upgrade
>
>
>
> How many phones are you resetting with the rollback set to true on old
> cluster?
>
>
>
> You want to make sure ALL the phones reset and get the clear ITL file. You
> may want to do them in batches of 50-100 at a time and make sure they
> unregister and re-register. I know it sounds paranoid, but I've seen where
> all phones don't reset when your doing a lot of phone resets at the same
> time.
>
>
>
> Also migrate a handful over to start to make sure things are fine (set
> alternate TFTP, etc) before doing all the phones.
>
>
>
> Be prepared to have to deal with a small % of phone/endpoint issues.
>
>
>
>
>
>
>
> On Thu, Apr 3, 2014 at 9:17 PM, Mehtab Shinwari <mshinwari at fidelus.com>
> wrote:
>
> Russell,
>
> So when you change the parameter thats one rest to clear the ITL.
>
> The second reset will be once you cutover. During the second reset it will
> first download the ITL and then do a mini-reset of its own before pulling
> the files from the tftp. The mini-reset is pretty quick but a required step
> so that the right certs/hash is applied.
>
> I do not see the need for a third reset since the firmware is remaining
> the same post upgrade.
>
> Good luck.
>
> Regards
>
>
> Mehtab Shinwari | CCNP RS/V
> Senior Support Engineer
>
>
>
>
> -------- Original message --------
> From: Russell Chaseling <rchaseling at plannet21.ie>
> Date:
> To: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>
> Subject: [cisco-voip] BE5K to BE6K upgrade
>
>
> Hi,
>
> About to do one of these upgrades and following Cisco's official guide.
> Customer is looking for a seamless cutover as they are 24hour. I've got all
> the phone firmware identical etc . Part of the process is changing the
> "Prepare Cluster for Rollback to pre 8.0 Required Field" to True and
> resetting all the phones to clear the ITL file so they will register to the
> new CUCM. I've got a window to reset all these phones in advance but my
> question is will the phones reset again when I cut over to the new CUCM ?
> I'm assuming they will see the new Call Manager and pull down the new ITL
> file and reset? Or will I have to reset the phones after manually?
>
> IF anyone has done one of these upgrades I'd love to know any gotchas?
>
> Thanks
> Russell
>
> _______________________________________________
> 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/20140404/98366c16/attachment.html>


More information about the cisco-voip mailing list