[cisco-voip] ITL Files and UC Upgrades

[Adam Frankel (afrankel)]

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] 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<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
To: "Dana Tong" <Dana_Tong at bridgepoint.com.au<mailto:Dana_Tong at bridgepoint.com.au>>, "cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)<mailto:cisco-voip at puck.nether.net%20(cisco-voip at puck.nether.net)>" <cisco-voip at puck.nether.net<mailto: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] On Behalf Of Dana Tong
Sent: Wednesday, January 15, 2014 12:25 AM
To: 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: [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<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/20140115/1c5eda0c/attachment.html>