Cisco Bug: CSCte12068 - copy run ftp:/tftp: should not prompt for confirmation
Jan 10, 2017
- Cisco Carrier Routing System
Known Affected Releases
Symptom: When you issue the commands copy run ftp: or copy run tftp: and specify the full syntax of the command with all required information such as username:password@hostname the parser will still prompt you for confirmation and make you hit returns. Some customers don't like the fact that when you use the copy run ftp: and specify the username:password and filename in the command it still prompts you for confirmation. This give them problems when they use scripts to write the running configurations to ftp or tftp servers. router#copy run ftp://user:firstname.lastname@example.org/running12-30-2009 Wed Dec 30 09:01:53.681 EST Host name or IP address (control-c to abort): [user:*@10.10.10.1]? Destination file name (control-c to abort): [running12-30-2009]? Building configuration.. 1182 lines built in 2 seconds (591)lines/sec [OK] The same behavior is seen with copy run tftp: router#copy run tftp://10.10.10.1/tftpboot/crs-c12302009 Wed Dec 30 09:09:58.189 EST Host name or IP address (control-c to abort): [10.10.10.1]? Destination file name (control-c to abort): [/tftpboot/crs-c12302009]? But a command like install add does not prompt for confirmation. router(admin)#install add ftp://user:email@example.com/tftpboot/pie This is a feature request to eliminate this prompting behavior in a future release. Conditions: This is a request to change a behavior that appears to be a day 1 IOS-XR behavior.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases