Saving configs to TFTP... does file extension matter?
JohnnyBiggles
Member Posts: 273
in Off-Topic
I'm using a TFTP server to collect configs from devices... and on a few Dell devices (switches), the command is as follows (very much like Cisco's CLI):
copy startup-config tftp://xxx.xxx.xxx.xxx/filename
It does not automatically add an extension to the file name unless you specify one. But my concern is, if I save it to the TFTP server as a .bak file, a .txt file, or even without an extension at all, and I needed to restore the configs at some point later on, would it automatically be able to distinguish the contents of the file no matter what extension it is? Does it require a certain file extension? Does Cisco equipment work this way also? Anyone familiar with this?
copy startup-config tftp://xxx.xxx.xxx.xxx/filename
It does not automatically add an extension to the file name unless you specify one. But my concern is, if I save it to the TFTP server as a .bak file, a .txt file, or even without an extension at all, and I needed to restore the configs at some point later on, would it automatically be able to distinguish the contents of the file no matter what extension it is? Does it require a certain file extension? Does Cisco equipment work this way also? Anyone familiar with this?
Comments
-
networker050184
Mod Posts: 11,962 Mod
A plain text file is usually good to go.An expert is a man who has made all the mistakes which can be made.