CUCM BK CEF0C471 00 Cucm-features-And-services-guide Chapter 01100
CUCM BK CEF0C471 00 Cucm-features-And-services-guide Chapter 01100
CUCM BK CEF0C471 00 Cucm-features-And-services-guide Chapter 01100
The Cisco Proxy TFTP Server allows all the endpoints in a large-scale deployment to download the configuration file and get registered to the Cisco Unified Communications Manager. Cisco proxy TFTP server deployment models, page 1 TFTP setup, page 3 Proxy TFTP server and centralized TFTP server, page 3 Phone behavior with proxy TFTP server, page 4 Cisco proxy TFTP server system requirements, page 4 Cisco proxy TFTP server interactions and restrictions, page 4 Cisco proxy TFTP server installation and activation, page 5 Cluster view settings, page 5 Cluster view manual override setup, page 10
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 1
Cisco proxy TFTP server Cisco proxy TFTP server deployment models
Cisco proxy TFTP server deployment model 1 For the deployment model illustrated in the following figure, the Primary TFTP Server should have Unified CM version 8.6 (2) or later.
Figure 1: Cisco proxy TFTP server deployment model 1
The two remote clusters - Cluster A and Cluster B have been configured to the Primary TFTP Server. However, you can configure any number of remote clusters to the Primary TFTP Server. Whenever an endpoint sends a request for configuration file, the Primary TFTP Server looks into the local cache and the configured remote clusters. Thus, an endpoint configured to the Primary TFTP Server Cluster, Cluster A and Cluster B can get the configuration file and get registered to the Cisco Unified Communications Manager.
Note
Cisco recommends that you use deployment model 1 for better system performance. However, if you do not wish to change your existing Centralized TFTP (8.6 (1) or earlier), you can use deployment model 2.
Cisco proxy TFTP server deployment model 2 In the deployment model illustrated in the following figure, the centralized Unified CM TFTP server acts as a Primary TFTP server.
Figure 2: Cisco proxy TFTP server deployment model 2
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) 2 OL-24921-01
The two remote clusters - Cluster A and Cluster B have been configured to the Primary TFTP Server. However, you can configure any number of remote clusters to the Primary TFTP Server. Two more remote clusters have been added to the Cluster A. Whenever an endpoint sends a request for configuration file, the Primary TFTP Server looks into the local cache and the configured remote clusters (Cluster A and Cluster B). Cluster A further looks into its configured remote clusters (Cluster C and Cluster D). Thus, all the endpoints configured to the Primary TFTP Server Cluster, Cluster A, Cluster B, Cluster C and Cluster D can get the configuration file and get registered to the Cisco Unified Communications Manager.
TFTP setup
Cisco Proxy TFTP Server can be configured manually as well as dynamically. This section provides configuration procedures for TFTP.
Procedure
Step 1 Create a new cluster. a) In Cisco Unified Communications Manager Administration, choose Advanced Features > Cluster View. b) Enter the Cluster Id and Fully Qualified Domain Name. Check the Enable check box for TFTP service. Click TFTP hyperlink. Remote Cluster Manually Override Configuration window appears. Choose Manually Configure Remote Service addresses. Enter IP addresses for the TFTP servers of the remote clusters. Click Save.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 3
Cisco proxy TFTP server Phone behavior with proxy TFTP server
Sometimes, endpoints are unable to download the configuration file because the primary TFTP server takes more time to get the configuration file from the alternate TFTP servers. By the time the primary TFTP server gets the file, the endpoints get timed out. As a result, endpoints never get registered to their Unified CM. Only 10 alternate TFTP servers can be added. These limitations are not applicable to Cisco Proxy TFTP Server.
Note
You must ensure that the Cisco TFTP service is active and in running state on the configured IP addresses.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) 4 OL-24921-01
Cisco proxy TFTP server Cisco proxy TFTP server installation and activation
Registering problems for phones with Security By Default (SBD) loads for previous versions of Cisco Unified Communications Manager 8.0 For remote cluster TFTP servers running on Cisco Unified Communications Manager 8.0 and later, the phones with Security By Default (SBD) load do not have any problem registering to these remote cluster Unified CMs via a proxy TFTP server. However, for the remote cluster TFTP servers running on a previous version of Cisco Unified Communications Manager 8.0, the phones with SBD load are unable to get registered to the remote cluster Unified CMs via a proxy TFTP server, since the Identity Trust List (ITL) file is unavailable in previous versions of Unified CM 8.0. Use the following procedure to overcome this problem. 1 Connect the endpoint directly to the remote cluster Unified CM: a Disable the DHCP option. b Enter the TFTP IP address on the phone manually. The phone gets the required SBD load and registers to the Unified CM. 2 Enable the DHCP option and reset the phone manually. The phone gets registered to the remote cluster via proxy TFTP.
Note
This procedure is applicable only if you have new phones with SBD load or if you plan to move the phones from a Unified CM with SBD support to a Unified CM without SBD support. This procedure is not applicable if the number of phones in a cluster is large.
Registering problems while moving a phone from one remote cluster to another When you move a phone from one remote cluster to another, you must delete the old ITL files from the phone, so that it registers successfully to the new Unified CM. Phones take time to register while upgrading the remote cluster When a remote cluster is upgraded, phones request for the new load file which needs to be downloaded to the PTFTP local cache. If you plug in an ethernet cable to a phone and then configure the phone to the Unified CM, the phone takes about 30 minutes to register. However, if you configure the phone to the Unified CM and then plug in the ethernet cable the phone gets registered immediately.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 5
Tips About Finding Remote Clusters The Find operation locates only those remote clusters that you added previously. The Find operation does not locate the clusters that belong to the enterprise automatically. Using the GUI For instructions on how to use the Cisco Unified Communications Manager Administration Graphical User Interface (GUI) to find, delete, configure, or copy records, see the Navigating the Cisco Unified Communications Manager Administration Application section in the Cisco Unified Communications Manager Administration Guide and its subsections, which explain how to use the GUI and detail the functions of the buttons and icons. Configuration Settings Table The following table provides detailed descriptions of the remote cluster settings that you configure in the Cluster View window (Advanced Features > Cluster View).
Table 1: Cluster View Settings
Description
Enter the cluster ID of the remote cluster. Valid values include alphanumeric characters, period (.), and hyphen (-).
Description
Enter a description for the remote cluster. This field accepts up to 128 characters. You may use any character except quotes (), close angle bracket (>), open angle bracket (<), backslash (\), dash (-), ampersand (&), and percent sign (%).
Enter the fully qualified name of the remote cluster/IP address. This field accepts up to 50 characters and allows the following characters: alphanumeric (a through z, A through Z, and 0 through 9), period (.), dash (-), asterisk (*), and space ( ).
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) 6 OL-24921-01
Field EMCC
Description For the EMCC service, the following column headings detail the configuration for this service: EnabledIf the EMCC service is enabled, this box gets checked. ServiceThis entry specifies the EMCC service. Remote ActivatedValid values specify true or false. Address 1This column lists the first address for this service. Address 2This column lists the second address for this service. Address 3This column lists the third address for this service.
PSTN Access
For the PSTN access, the following column headings detail the configuration for this service: EnabledIf the PSTN access is enabled, this box gets checked. ServiceThis entry specifies the PSTN access Remote ActivatedValid values specify true or false. Address 1This column lists the first address for this service. Address 2This column lists the second address for this service. Address 3This column lists the third address for this service.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 7
Description For the RSVP agent, the following column headings detail the configuration for this service: EnabledIf the RSVP agent is enabled, this box gets checked. ServiceThis entry specifies the RSVP agent Remote ActivatedValid values specify true or false. Address 1This column lists the first address for this service. Address 2This column lists the second address for this service. Address 3This column lists the third address for this service.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) 8 OL-24921-01
Field TFTP
Description For the TFTP service, the following column headings detail the configuration for this service: EnabledIf the TFTP service is enabled, this box gets checked. ServiceThis entry specifies the EMCC service. Remote ActivatedValid values specify true or false.
Note
The value of the Remote Activated column is set to true whenever remote IP addresses are configured either manually or dynamically.
Address 1This column lists the first address for this service.
Note
When you upgrade from Cisco Unified Communications Manager 8.6 (1) to Cisco Unified Communications Manager 8.6 (2) or later, Address 1 is automatically updated by the system. However, if this field is blank after the upgrade due to some reason such as DNS lookup failure, you must manually update it with the appropriate IP address of the TFTP service.
Address 2This column lists the second address for this service. Address 3This column lists the third address for this service. Enabled All Services Click this button to enable all services (EMCC, PSTN Access, and RSVP Agent). Click this button to disable all services (EMCC, PSTN Access, and RSVP Agent). Click this button to update the remote cluster immediately.
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 9
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) 10 OL-24921-01