[cisco-voip] CCM4.1.3 - Add Secondary TFTP Server

[Jason Burns]

James,

2. All of the device configuration files like SEPXXXXXXXXXXXX.conf.xml are
generated in memory when the TFTP service starts. The TFTP service reads the
phone configuration from the database and by default never writes this file
out to disk. It's faster this way. You can change this behavior in the TFTP
Service Parameter page.

To get things like new phone loads onto the TFTP server you would have to
run through the phone load installer on the new TFTP server or extract the
zip files into the TFTP directory.

3. Whenever you add a new server, a cluster reboot is necessary to make sure
all the other servers in the cluster know it is there. This is so change
notification will work properly. This will be required even for a TFTP
server because it will have to get change notification to update the in
memory config files when you do something like change a CallManager group
around.

-Jason

On Fri, Oct 17, 2008 at 12:07 PM, James Brown <
james.m.h.brown at googlemail.com> wrote:

> James Brown wrote:
>
>> All,
>>
>> [...]
>>
>> 1. How do I get the new TFTP server recognised in the servicability page
>> on the publisher? My guess is that I'd need to momentarily start the Call
>> Manager service on the new TFTP to allow the heartbeat to begin. I can't see
>> any way of manually programming servers into the servicability page.
>>
>> 2. When I have all the services configured correctly on this new TFTP
>> server, how should I begin getting the publisher to sync the device config
>> files out to the new repository? Should this be done by a manual copy/paste,
>> or does the publisher automatically start writing the files when it
>> recognises a new TFTP service is started?
>>
>> 3. This is a new server in the cluster, with a copy of the CCM database,
>> but it's not actually going to have process callls. Is a cluster reboot
>> therefore necessary?
>>
>> [...]
>>
>
> I think I can answer question 1 now. On CCM 4.x, the server can be defined
> under System->Servers within CCMAdmin. Once it's added on this screen, it
> should also appear within Serviceability. No need to activate the CCM
> Service on a TFTP Server.
>
> I'm still unsure about questions 2 and 3 though.
>
>
> _______________________________________________
> 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/20081018/f938d839/attachment.html>