[cisco-voip] ITL Files and UC Upgrades

Wed Jan 15 14:04:08 EST 2014

That is true.
We hadn't restricted web access etc on v7 so it wasn't an issue for me at
the time.
We had approx 1000 handsets that had an issue county wide in the UK. So
trying to manage that in a timely fashion was a very big issue and at the
time we faced having to try and track down them individually.
So this tool saved us a significant amount of time.
 On 15 Jan 2014 18:52, "Brian Meade (brmeade)" <brmeade at cisco.com> wrote:

>  Andy,
>
>
>
> The issue with the tool is that it requires settings access and web access
> to already have been enabled on the phones prior to the outage.  Also,
> there’s usually many other ways to resolve ITL issues rather than deleting
> the ITLs from all the phones in the cluster.
>
>
>
> Brian
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Andy
> *Sent:* Wednesday, January 15, 2014 1:39 PM
> *To:* Lelio Fulgenzi; Adam Frankel (afrankel)
> *Cc:* cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
> *Subject:* Re: [cisco-voip] ITL Files and UC Upgrades
>
>
>
> If you get into problems with rolling back TAC have a tool they will send
> you which will erase ITL config on a handset list.
> I have had to use this in the past with good results.
>
>  Regards
>
>
>
> Andy
>
> On 15/01/2014 17:35, Lelio Fulgenzi wrote:
>
>  Thanks, I'd definitely have to consider that. What I would do, is make
> sure to see what the factory loads are first, and if they are not our
> default loads, re-install the default loads to update those xml files
> accordingly. Or at least that's what I gathered I can do. Reinstalling an
> existing file should be fine.
>
> Lelio
>
>  ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
>  ------------------------------
>
> *From: *"Adam Frankel (afrankel)" <afrankel at cisco.com><afrankel at cisco.com>
> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca> <lelio at uoguelph.ca>
> *Cc: *"cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)"<cisco-voip at puck.nether.net(cisco-voip at puck.nether.net)>
> <cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net>
> *Sent: *Wednesday, January 15, 2014 11:55:16 AM
> *Subject: *RE: [cisco-voip] ITL Files and UC Upgrades
>
> A factory reset removes the ITL, but could also put you on a firmware that
> is not a direct jump to your current Device Defaults, leaving the user
> stuck on the older load.
>
>
>
> --
>
> Adam
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Lelio Fulgenzi
> *Sent:* Wednesday, January 15, 2014 11:04 AM
> *To:* Brian Meade (brmeade)
> *Cc:* cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
> *Subject:* Re: [cisco-voip] ITL Files and UC Upgrades
>
>
>
>
> hi Brian,
>
> I'm planning a v7 to v9 upgrade and will be looking at (and testing) back
> out procedures. My hope is that if we need to roll back to v7, using the
> roll back parameter will help, but in the event it doesn't we'll have to
> manually fix things. The document you reference talks about deleting the
> ITL files manually, but I'm wondering if performing a factory reset does
> the same thing?
>
> My concern is that the instructions to delete the ITL file are (might be)
> a little more complicated than a factory reset.
>
> Thoughts?
>
> Lelio
>
>
>  ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
>  ------------------------------
>
> *From: *"Brian Meade (brmeade)" <brmeade at cisco.com>
> *To: *"Dana Tong" <Dana_Tong at bridgepoint.com.au>, "cisco-voip at puck.nether.net
> (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>
> *Sent: *Wednesday, January 15, 2014 9:23:25 AM
> *Subject: *Re: [cisco-voip] ITL Files and UC Upgrades
>
> Dana,
>
>
>
> The rollback option requires all phones to be reset after changing the
> Enterprise Parameter so that the phones can get the new blank ITL.  After
> they get the new blank ITL is when you can then move it to the other
> cluster.  The rollback option isn’t preferred since phones on the old
> cluster will have problems with secure services such as corporate directory
> before they are moved to the new cluster.  I’d suggest using the Bulk
> Certificate Export/Consolidate/Import option to maintain 100% functionality
> while also allowing you to roll phones back to the old cluster if something
> went wrong with the upgrade easily.  Check out
> https://supportforums.cisco.com/docs/DOC-15799 for more info on this.
>
>
>
> Brian
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<cisco-voip-bounces at puck.nether.net>]
> *On Behalf Of *Dana Tong
> *Sent:* Wednesday, January 15, 2014 12:25 AM
> *To:* cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
> *Subject:* [cisco-voip] ITL Files and UC Upgrades
>
>
>
> Hi all,
>
>
>
> I was just testing the process for migrating handsets from an old 8.0
> cluster on MCS hardware to new virtualised UCM.
>
>
>
> ·         I set the Enterprise Parameter – Prepare cluster for rollback
> to pre 8.0.
>
> ·         Restarted the Trust Verification Service on all nodes.
>
> ·         Restarted the TFTP service on all nodes.
>
> ·         Restarted my pilot handset.
>
>
>
> ·         Once this was completed I changed the TFTP servers to point to
> the new cluster and restarted the phone.
>
> ·         The phone came back on the old cluster.
>
>
>
> I had to manually go in to the phone and delete the ITL file and reset it
> again before it would register to the new cluster.
>
>
>
> Am I doing something wrong? What is the correct procedure? (I am aware of
> other third-party applications which will do this for me).
>
>
> Cheers
>
> Dana
>
>
>
>
> _______________________________________________
> 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/20140115/b57bc690/attachment.html>