Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EOL/EOE] [EX] File-fetch failed error while saving the rescue configuration

0

0

Article ID: KB32712 KB Last Updated: 28 Dec 2020Version: 2.0
Summary:

Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.


 

When trying to save a rescue configuration on the EX series of devices, the "File-fetch failed" error is logged. This article explains the reason for the error and the workaround.

 

Symptoms:

The following error message is seen on the VC environment when trying to save a rescue configuration:

root> request system configuration rescue save
error: File-fetch failed

 

Cause:

The error is logged when saving a recently committed configuration as a rescue configuration.

 

Solution:

This issue has been fixed in Junos OS releases 14.1X53-D30, 15.1R2, and 16.1R1 as per PR1074772.

Meanwhile, a workaround for other releases is as follows:

  1. Manually copy the current configuration to a rescue configuration:
    root> file copy /config/juniper.conf.gz /config/rescue.conf.gz
  2. Copy the rescue configuration from the master to the backup routing engine:
root> file copy /config/rescue.conf.gz fpcX:/config/rescue.conf.gz

Note: In the command, fpcX refers to the backup engine where you want to copy the rescue configuration. For example, if fpc1 is the backup routing engine, the following command would be used:

root> file copy /config/rescue.conf.gz fpc1:/config/rescue.conf.gz

Note: To execute the above commands, the file needs to be changed to be writable at the shell prompt by using the command "%chmod 777 /config/rescue.conf.gz" or the user would require root permission.

 

Modification History:

2020-12-28: Tagged article for EOL/EOE

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search