Because my router was sourcing TFTP traffic from its outside interface, CUCM was not able to route the traffic back to 7960 phone. In fact, the source IP was the IP of the outside interface of my 2811!Īfter some quick google’ing I came across this article on the ip tftp source-interface command. It would appear that the phone is contacting the TFTP server, but its IP address was not part of my voice VLAN. As I was perusing the TFTP trace logs a few lines popped out at me. You should now have a wealth of information to dive into to try and troubleshoot your issue.
Cisco router tftp client does not work download#
Scroll down to find Cisco Tftp and select either All Servers or an individual server.gulde Posted One issue, it utilizes the First Ethernet IP address, not the IP address of the NIC directly connected to the LAN my target machine was on (CLIENT TFTP). When you run the program it will ask you for the IP of the CUCM server and the GUI username/password. Simple and works, however needs interface improvement and DOES NOT CLEAN UP AFTER ITSELF ON UNINSTALL (shortcuts, firewall rules, event log).Download the tool for your appropriate os and install.Near the bottom of the plugins page find the download link for Cisco Unified Real-Time Monitoring tools.From the CUCM Administration page navigate to Application -> Plugins.To download the tool, follow these steps. To download the trace files you’ll need to use the Cisco Unified Real-Time Monitoring Tool which comes bundled with CUCM. Once I verified the issue was still occurring it was time to grab the trace files. With the detailed TFTP trace enabled, I tried resetting the phones to duplicate the issue. Be sure Trace On is selected then change the Trace Level to Detailed.For Service select Cisco Tftp then click Go.Select your CUCM Server running the TFTP service for Server then select CM Services under Service Group.On the Cisco Unified Serviceability page select Trace -> Configuration.
From the CUCM Console: select Cisco Unified Serviceability from the Navigation drop down, and click Go.Sounded like a TFTP issue to me, and here are the steps I followed to resolve the issue.įirst, I setup a trace to capture TFTP logs from my CUCM server. If I moved the phones back to the same VLAN as CUCM the phones would work properly. The phones started having issues contacting CUCM and downloading new configuration files or firmware. My lab server has a dedicated NIC which connects to the lab network and hosts a domain controller, workstation, and CUCM 11.5 virtual machines.Īll this was working well until I configured the switches to have a separate dedicated voice VLAN. Nothing too fancy, a 2811 with PVDMs and FXO/FXS cards, 2 3750 PoE switches, and 2 Cisco 7960 VOIP phones. I’ve recently began studying for my CCNA Collaboration exam and to help with my studies I’ve built a small collaboration lab.
0 kommentar(er)
