thill1982
asked on
Unable to upload Cisco router config(running-config) using FTP
My company has a Cisco 2851 Router which I am trying to configure to allow FTP access for uploading/downloading of the running-config.
I have managed to download the running-config from the router to our FTP server successfully, however I am unable to upload the running-config back up to the router properly. I get the following when I try to upload:
Accessing ftp://194.80.112.21/running-config...
Loading running-config !!!!
[OK - 19629/4096 bytes]
Aim slot is empty or does not support clock participate
Aim slot is empty or does not support clock participate
19629 bytes copied in 0.796 secs (24660 bytes/sec)
Is the router perhaps not configured to look in the right location for the running-config?
I have looked at the "ftp-server topdir" command which I thought might be what needs to be set but I am not sure where I would need to point this to?
Thanks in advance.
I have managed to download the running-config from the router to our FTP server successfully, however I am unable to upload the running-config back up to the router properly. I get the following when I try to upload:
Accessing ftp://194.80.112.21/running-config...
Loading running-config !!!!
[OK - 19629/4096 bytes]
Aim slot is empty or does not support clock participate
Aim slot is empty or does not support clock participate
19629 bytes copied in 0.796 secs (24660 bytes/sec)
Is the router perhaps not configured to look in the right location for the running-config?
I have looked at the "ftp-server topdir" command which I thought might be what needs to be set but I am not sure where I would need to point this to?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Should be no difference FTP vs. TFTP - copy <blah> run is always an overlay.
I normally do my TFTP uploads as small chunks written to assume they're an overlay (blow away the ACL, rewrite the ACL, include 'no shut' everywhere appropriate, etc.).
I normally do my TFTP uploads as small chunks written to assume they're an overlay (blow away the ACL, rewrite the ACL, include 'no shut' everywhere appropriate, etc.).
ASKER
Okay, thanks for your help.
ASKER
We used to make changes to the running-config via TFTP for testing(adding, changing or removing), then simply copy it to the startup config when we were happy. (We have not been able to use TFTP this time for some reason, it keeps timing out, not sure why)
Does this make sense? Is there a difference between what we used to do for uploads via TFTP and what we are doing now with FTP, or perhaps are there differences in the IOS versions?
Thanks