TFTP server: Publisher or Subscriber

[ysanadiga01]

Hi there,

I got a customer whose TFTP server is Subscriber. I read somewhere that TFTP is either Publisher or a separate server is configured to work as TFTP server.

Now I'm a bit confused. What are the "Best Practice" as far as TFTP server is concerned.

Thanks.

Regards,

YSana

[Jaime Valencia · Accepted solution]

depends mostly on deployment model

Unified CM Provisioning for Local Failover

You can run the TFTP service on either a publisher or a subscriber server, depending on the site and the available capacity of the server. The TFTP server option must be correctly set in the DHCP servers at each site. If DHCP is not in use or if the TFTP server is manually configured, you should configure the correct address for the site.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/models_ps556_TSD_Products_Implementation_Design_Guide_Chapter.html

TFTP Server

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/callpros.html#wp1043790

Whenever you look for best practices read the SRND

HTH

java

if this helps, please rate

[fishtacos]

In the TFTP documentation link you have above, it mentions:

"Therefore, you can assign half of the devices to use TFTP server A as the primary and TFTP server B as the backup, and the other half to use TFTP server B as the primary and TFTP server A as the backup. To improve performance on dedicated TFTP servers, you can set service parameters to increase the number of simultaneous TFTP sessions allowed on the server. "

Do you have a reference of how to configure this in call manager? Is this done through creating 2 different call manager server groups and 2 device groups and assigning them that way? (in addition to DHCP option 150 [primary secondary] settings? Thank you!

[Jaime Valencia]

Nothing to do in CUCM (besides making sure the service is running), that just refers to DHCP option 150 settings.

TFTP and registration via CUCM groups are completely separate things

[fishtacos]

Copy that Jaime. Thank you. I finally got it all working and tested.