Description

This article explains how to fix the issue when staging an image on a device via Junos Space returns the error: Failed - Backup RE Validation failed

Symptoms

You will get the below error from the server.log:
  
2024-07-17 11:49:03,551 ERROR [net.juniper.jmp.cmp.netconf.ejb.rpc.NetconfChannel] (JobThread819669, Parent JobThread819668) parseRPCReply:: Found rpc-error.<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/21.4R0/junos" message-id="1">

<rpc-error>

<error-type>protocol</error-type>

<error-tag>operation-failed</error-tag>

<error-severity>error</error-severity>

<error-message>

Could not connect to re0 : No route to host

</error-message>

</rpc-error>

</rpc-reply>

 

To identify the issue, please enable netconf traceoption in the device using the below command:
  
set system services netconf traceoptions file netconf-ops.log
set system services netconf traceoptions file size 3m
set system services netconf traceoptions file files 20
set system services netconf traceoptions file world-readable
set system services netconf traceoptions flag all
Once you enable this, the netconf transaction will be logged under /var/log/netconf-ops.log in the device.

You will find the below error in the logs while staging:
  
Jul 18 11:17:36 [NETCONF] - [4109] Incoming: <?xml version="1.0" encoding="UTF-8"?><hello><capabilities><capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability></capabilities></hello>]]>]]>

Jul 18 11:17:36 [NETCONF] - [4109] Incoming: <?xml version="1.0" encoding="UTF-8"?><rpc message-id="1"><get-checksum-information><path>re1:/var/tmp/junos-srxmr-x86-64-22.4R3-S2.11.tgz</path><method>md5</method></get-checksum-information></rpc>

]]>]]>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/21.4R0/junos" message-id="1">

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <rpc-error>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <error-type>protocol</error-type>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <error-tag>operation-failed</error-tag>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <error-severity>error</error-severity>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: <error-message>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: Could not connect to re1 : No route to host

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: </error-message>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: </rpc-error>

Jul 18 11:17:36 [NETCONF] - [4109] Outgoing: </rpc-reply>

 

Space is trying to get the md5sum using the routing engine 1 and since there is no RE1, it is failing

This could be due to the Routing Engine configuration existing in the Junos space database for the device



 

Solution

To fix the issue. please run the Device Import Cleanup on the device using the below command: 
cd /var/log/space-debug/debug-utilities/deviceImport
sh cleanupDeviceImportTables.sh <hostname of the device>

Once done, please resync with the Network on the device from the WebUI. Refer Resynchronizing Managed Devices with the Network

Modification History

2024-07-25 : Article Created