[cisco-voip] unexpected behaviour with "Prepare Cluster for Rollback" and migrating phones between v9 and v7 cluster

Lelio Fulgenzi lelio at uoguelph.ca
Wed Feb 19 17:30:02 EST 2014


Thanks Tommy. 

Is this documented anywhere or is this through trial and error?

Sent from my iPhone

On 2014-02-19, at 5:04 PM, Tommy Schlotterer <tschlotterer at netechcorp.com> wrote:

> Lelio,
>  
> After you change the “Prepare cluster for Rollback to Pre 8” according to CCM you MUST restart the following services on all nodes, in the order described, immediately after setting this parameter to True: First, restart the Trust Verification Service (TVS) on all nodes; next, restart the TFTP service on all nodes that have TFTP activated; last, return to the Enterprise Parameters Configuration window and click the Reset button to reset all phones. When those three steps are completed and have been performed in the specified order, the cluster will be ready for rollback.
>  
>  
> To Change the cluster back to a “Secure Cluster” you must follow the same instructions after you change the parameter back.
>  
> Tommy
>  
> Tommy Schlotterer | Systems Engineer
>  
> CCNA, CCNA Voice
> <image001.png>
> 48325 Alpha Dr. Ste. 150
> Wixom, MI 48393
> p 248.468.0710
> e tschlotterer at netechcorp.com
> w netechcorp.com
>  
> From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
> Sent: Wednesday, February 19, 2014 4:38 PM
> To: cisco-voip voyp list
> Subject: [cisco-voip] unexpected behaviour with "Prepare Cluster for Rollback" and migrating phones between v9 and v7 cluster
>  
> 
> OK, now I am officially confused. ;)
> 
> I was under the impression that once a phone has registered to a v9 cluster, it downloads an ITL trust list/file which prevents it from registering to a v7 cluster. To help with this, the "Prepare Cluster for Rollback" enterprise parameter was introduced.
> 
> Here's what I did:
> upgraded offline cluster (all servers had same hostname and IP address)
> set the "Prepare Cluster for Rollback" parameter to True and clicked Save (because there were no phones registered, I did not "Apply Changes")
> plugged phones into the offline network
> phones registered to the new offline v9 cluster
> checked phone security pages - they showed ITL files listed (that long string of numbers)
> thinking it was the "Apply Changes" that missed something, I clicked that
> phones restarted, but still showed an ITL file
> brought a phone back to the live network, phone registered to the v7 cluster (still has an ITL file listed)
> on offline cluster, change the "Prepare Cluster for Rollback" to False, clicked Save, clicked Apply Changes (phones restarted, and showed an ITL file)
> I picked up one of the phones from the offline network (now in rollback=false mode) and brought it to the live network. It registered to the v7 cluster.
> So what I see are a few things confusing me:
> Why do phones still have ITL files if the cluster is in rollback mode. This is not a big deal, but I'd like to be able to tell from the phone when it's registered with the "Prepare Cluster for Rollback" set to TRUE.
> Why does a phone that registers to a v7 cluster still have it's ITL file set?
> Why (and this is the one that gets me) does a phone that was on v9 with "Prepare Cluster for Rollback" set to FALSE successfully register to the v7 cluster?
> Is the ITL trust list a simple hash of the IP addresses and host names of the cluster members? If I don't change anything, things will continue to work?
>  
> Is something wrong with my logic and steps? I was testing with a 7942 and a 7962.
>  
> 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
>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140219/7e620a5e/attachment.html>


More information about the cisco-voip mailing list