[cisco-voip] ITL Files and UC Upgrades

Wed Jan 15 18:56:22 EST 2014

FYI.

Just testing the Bulk Certificate Export as discussed here:
https://supportforums.cisco.com/docs/DOC-15799#Bulk_Certificate_Export

Thanks to Brian Meade for the link.

Should be good because we have the systems side-by-side.

Cheers
D

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Smith
Sent: Thursday, 16 January 2014 9:38 AM
To: Lelio Fulgenzi; MManly at TEP.com
Cc: cisco-voip at puck.nether.net; Semyon Taskin
Subject: Re: [cisco-voip] ITL Files and UC Upgrades

Hey mate,

I asked the same question of my colleague the other day. Why not just the rollback parameter?
In his case, they were doing a phased migration.
The rollback parameter affects all phones in the new cluster (including the ones that are working successfully)
As Brian mentioned, the rollback causes other service issues and again – and it would affect all your phones in this case.

In terms of registration, if the old cluster is there still (I.e. you stood them up in parallel), then you should be able to remote control them and delete ITL. (I did this to roll some back to a 4.1.3 cluster once)

Out of curiosity more than anything..
I don’t think the phone actually needs to be registered to remote control it.
The RC products would use CUCM to get the list of devices, and eventually the IP addresses (to target the web servers of the phones for RC)
By default CUCM would also be used for authorisation of the web request to phone (but this could be proxied – point Auth URL to web page that always returns Authorized message to phone)
Then it’s just a question of when the web server is running on the phone – i.e. if it’s looping through trying to find a CM, but it’s on the network, does it answer web requests, not too sure on this part.
Maybe someone else knows for sure, or has messed around with this a bit more.

Cheers,

Tim.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, 16 January 2014 4:33 AM
To: MManly at TEP.com<mailto:MManly at TEP.com>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] ITL Files and UC Upgrades

The problem with those remote control tools, is that as far as I know, the phones need to be registered. If the phones are registered, then the roll back parameter should suffice.

I'm not clear where the remote control tool will help really.

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: MManly at TEP.com<mailto:MManly at TEP.com>
To: lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>, afrankel at cisco.com<mailto:afrankel at cisco.com>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, January 15, 2014 12:07:42 PM
Subject: RE: [cisco-voip] ITL Files and UC Upgrades

Phone view from unified fx is a really useful product for phone management. We used it in my previous job to delete ctl files when moving from secure to non secure mode and it worked great.

I think there is now a YouTube video demonstrating the deletion of itl files using it.

It's not free, but we'll worth it, IMHO.

Sent from my Android phone using TouchDown (www.nitrodesk.com<http://www.nitrodesk.com>)

-----Original Message-----
From: Adam Frankel (afrankel) [afrankel at cisco.com]
Received: Wednesday, 15 Jan 2014, 9:58AM
To: Lelio Fulgenzi [lelio at uoguelph.ca]
CC: 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>) [cisco-voip at puck.nether.net]
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] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, January 15, 2014 11:04 AM
To: Brian Meade (brmeade)
Cc: 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: 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/12e71698/attachment.html>