[cisco-voip] Centralized TFTP and Auto Registration

[Anthony Holloway]

Hey Jason,

Looks like you found some good enough on the topic.  Thank you for jumping
in and sharing this.

-Anthony

On Sat, Nov 5, 2011 at 8:28 AM, Jason Burns <burns.jason at gmail.com> wrote:

> I think auto registration is specifically addressed in the documentation
> regarding centralized TFTP. The two can't be used together.
>
> I love the System Guide!
>
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_5_1/ccmsys/a02tftp.html#wp1106441
>
> Jason Burns
>
>
> When phones are configured in a Cisco Unified Communications Manager other
> than the cluster where the master TFTP server is configured, and
> auto-registration is enabled, and the off-cluster Cisco Unified
> Communications Manager goes down, if the phones are configured to submit a
> request from the centralized TFTP server, they may inadvertently get
> auto-registered on the central Cisco Unified Communications Manager.
> Therefore, you should disable auto-registration if it is not already
> disabled or delete the inadvertently registered phone after making sure
> that the cluster to which it belongs is up and running.
>
>
> On Fri, Nov 4, 2011 at 8:50 PM, Wes Sisk <wsisk at cisco.com> wrote:
>
>> Hi Anthony,
>>
>> At the moment this looks like it would be a feature request.  The prudent
>> path forward is to open a TAC case for more formal investigation.  Then if
>> it turns into feature request we can engage your account team.
>>
>> Regards,
>> Wes
>>
>>
>> On Nov 4, 2011, at 2:47 PM, Anthony Holloway wrote:
>>
>> Thanks for the reply Wes.
>>
>> Is Cisco somehow intentionally ignoring this feature pairing for the time
>> being?  I find it odd that it's not listed as a limitation or restriction
>> of centralized TFTP.
>>
>> -Anthony
>>
>> On Fri, Nov 4, 2011 at 12:31 PM, Wes Sisk <wsisk at cisco.com> wrote:
>>
>>> auto reg isn't going to work so well with centralized TFTP.
>>>
>>> centralized TFTP very basically does this:
>>> If file is not found locally then request it from the defined peer TFTP
>>> servers
>>>
>>> In this case autoreg uses information in xmldefault.cnf.xml which will
>>> always be found on the centralized server. *if* it works your phones would
>>> all register in the cluster that performs as the centralized TFTP server.
>>>
>>> /wes
>>>
>>>   On Nov 4, 2011, at 1:12 PM, Anthony Holloway wrote:
>>>
>>> Cisco VoIP Group,
>>>
>>> I am reading the following section of the UC SRND:
>>>
>>> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#Centralized_TFTP_Services
>>>
>>> And I am wondering how phone auto registration is affected by the
>>> Centralized TFTP model?  Or if it's even supported?  If so, what are the
>>> limitations?
>>>
>>> I don't see this referenced in the SRND, and would be open to reading
>>> any supporting documentation I am pointed to.
>>>
>>> Thank you,
>>>
>>> Anthony
>>> _______________________________________________
>>> 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/20111105/9a74b628/attachment.html>