This article describes the error message, 'rcmd: re1: No such file or directory' and provides workaround for the same.

1) Below error message is observed when trying to log into the other RE.

For example, here RE1 is in error state and is inaccessible via RE0.

RE0@labroot> request routing-engine login other-routing-engine

rcmd: re1: No such file or directory

2) Console access would not be present, or might be stuck in a loop.

3) Versions on both REs would the same.

4) No alarms, no core-dumps generated, and no suspecious logs present that would point towards any potential cause.

5) Because of no connection to RE1, the commits to RE1 fail as well.

6) Attempting to reboot RE1 through RE0 would not work.

RE0@labroot>request system reboot other-routing-engine

Rebooting re1

error: error communicating with

error: request-reboot failed on re1

7) Attempting to restart CB1 through CLI would not work as well, since RE1 is online.

RE0@labroot>request chassis cb slot 1 offline

Backup CB 1 cannot be set offline, backup RE is online

These symptoms indicate either communication failure between both the routing-engines, or file system issues due to which RE1 is not accessible.

Hence as next actions, the recommendation it is is to perform CB1/RE1 reseat in a maintenance window, along with a spare RE handy during the MW.

[Note that CLI reseat of CB1 will not work as RE1 is still online]