A large campus system is deployed using three clusters, and each cluster contains a TFTP server. TFTP1, the TFTP server for Cluster1, is configured as the centralized TFTP server for the campus. The other clusters and TFTP servers are named in sequence as TFTP2 for Cluster2 and TFTP3 for Cluster3. In all subnets, the DHCP scope provides TFTP1's IP address as Option 150.
First, TFTP2 and TFTP3 are configured to write their configuration files to TFTP1's drive, each in a different subdirectory, as follows:
?TFTP2's alternate file location is set to: \\TFTP1_IP\Program Files\Cisco\TFTPpath\TFTP2
?TFTP3's alternate file location is set to: \\TFTP1_IP\Program Files\Cisco\TFTPpath\TFTP3
Second, TFTP1 is configured to search in the alternate file locations as follows:
Re: TFTP question for large site with multiple clusters
TFTP1 will look for the configuration file on it owns location and if it is not there, it will search on TFTP2, then TFTP3 and so on, if you have a different cluster on n the Alternate 2, CCM TFTP1 will search on it's own TFTP, if nothing there it will look for the configuration file on TFTP2 and then it will send the configuration file located at TFTP2 to the phone and the phone will register with CCM2 (TFTP2) as per the SEP.cnf.xml file settings, if no configuration file is located for that phone on the alternate TFTPs, the phone will auto-register with CCM1 (if auto-registration is enabled). Noticed that this feature was included on CCM 4.2.
You can specify alternate TFTP paths if you have multiple clusters. You only want to configure one server for many DHCP scopes or want to have one DHCP scope. The TFTP server stores files for the cluster that contains the TFTP server in the primary path and stores the files for the other clusters in alternate paths. You can specify up to 10 alternate paths by entering a value for the Alternate File Location fields of the service parameter. For more information on service parameters, refer to the "Service Parameters Configuration" in the Cisco CallManager Administration Guide.
The primary TFTP server should have the alternate path values set for external Cisco CallManager clusters. The primary TFTP server serves configuration files from the alternate path for phones and devices in the external clusters. You ensure that the TFTP servers on the external clusters point to this shared file path by setting it as their primary path (that is, by setting it as the File Location service parameter). Note that TFTP servers in the external clusters build and write the configuration files on the shared "alternate path" location, so the path should be a shared accessible directory across all clusters. The main TFTP server can have caching on, but other TFTP servers must have it off.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...