Question

Only one switch unable to contact the TFTP when archiving config


I have only one switch out of 22 that is getting an error when running archive in Inventory Manager. It gets "The device was unable to contact the TFTP server. Check that the TFTP server is running and connectivity is okay." All of my other switches contact it just fine and this switch does function properly. Anyone have any ideas? Thanks.

15 replies

Userlevel 7
Are you able to ping the TFTP from the switch CLI? If not what is the output? Will the tftp work manually from the CLI?
Userlevel 4
Last time that happened to me there was a firewall rule blocking TFTP to that network.
Well after getting the CLI proxy installed I could not ping anything on that particular subnet... which is weird because all the other switches in the stack and that go through that switch can.
Userlevel 7
Are you able to access the switch using putty? Where are you pinging from? Can you please elaborate?
Sorry I am in the switches screen play using the CLI shell and these are my results:
Slot-2 FES_E_TC6.1 # ping 10.254.1.75
Ping(ICMP) 10.254.1.75: 4 packets, 8 data bytes, interval 1 second(s).

--- 10.254.1.75 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 ms
Userlevel 7
Try putting in "vr vr-default" into the ping command. Like so:

ping vr vr-default 10.254.1.75

Is the IP address above the netsight/tftp server?
Yes it is the netsight server.

Slot-2 FES_E_TC6.2 # ping vr vr-default 10.254.1.75
Ping(ICMP) 10.254.1.75: 4 packets, 8 data bytes, interval 1 second(s).

--- 10.254.1.75 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 ms
Userlevel 7
Can you ping the switch from the netsight server?
Yes the netsight server was able to ping the switch and the switch shows up in netsights with status of contact and shows everything is proper besides the archive failing.
Userlevel 7
Typically when pings don't work and tftp is not going through there is some kind of firewall issue. Could you try disabling the firewall temporarily on the netsight server to see if this resolves your issue?
Here is the firewall for the netsight server.

Userlevel 7
Did you attempt disabling it and see if the tftp went through?
Well basically with accept policies wouldn't it be open? Not 100% my Linux isn't so strong.
"ufw status verbose" comes back with inactive on my Ubuntu server
Userlevel 7
William, do you still need assistance with this issue?

Reply