F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Messe's avatar
Messe
Icon for Nimbostratus rankNimbostratus
Oct 21, 2013

BNA and LTM 4200v TFTP not working.

I am running BNA for configuration backup. BNA logs in, TFTPs the files back, and saves them. If we needed to restore the LTM, I can have the LTM pull the config file back down. We have this working ...
management
Messe's avatar
Messe
Icon for Nimbostratus rankNimbostratus
Oct 21, 2013

text
Yes, my laptop has a route back to the device.

C:\Users\sbmesse>ping 10.171.58.6

Pinging 10.171.58.6 with 32 bytes of data: Reply from 10.171.58.6: bytes=32 time=169ms TTL=247 Reply from 10.171.58.6: bytes=32 time=169ms TTL=247

Ping statistics for 10.171.58.6: Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 169ms, Average = 169ms

The file is pushed the same way. F5 is the client and BNA is the server.

I get the same thing when I try to send it to BNA. THe LTM can ping the BNA server.

[root@LB-JP-SRV1-1:Active:In Sync] config tftp 161.173.59.48 tftp> verbose Verbose mode on. tftp> trace Packet tracing on. tftp> put /var/local/scf/agent-160249.tmp agent-160249.tmp putting /var/local/scf/agent-160249.tmp to 161.173.59.48:agent-160249.tmp [netascii] sent WRQ sent WRQ sent WRQ sent WRQ sent WRQ Transfer timed out.

tftp> quit [root@LB-JP-SRV1-1:Active:In Sync] config ping 161.173.59.48 PING 161.173.59.48 (161.173.59.48) 56(84) bytes of data. 64 bytes from 161.173.59.48: icmp_seq=1 ttl=55 time=168 ms 64 bytes from 161.173.59.48: icmp_seq=2 ttl=55 time=168 ms 64 bytes from 161.173.59.48: icmp_seq=3 ttl=55 time=168 ms 64 bytes from 161.173.59.48: icmp_seq=4 ttl=55 time=168 ms ^C --- 161.173.59.48 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 168.228/168.717/168.922/0.405 ms