When trying to commit the configuration on virtual chassis, there shows an error and the configuration cannot be committed.
Following error is seeing when trying to commit on the virtual chassis:
{master:0}[edit]
root@VC# commit
configuration check succeeds
error: failed to copy file '//var/etc/stp_context.id' to 'fpc1'
This issue is related to the following PR:
PROBLEM
In some rare conditions, "commit synchronize" might fail with following error messages:
user@router# commit synchronize
re1:
error: failed to copy file '//var/etc/stp_context.id' to 're0'
Following error also can be seen in /var/log/messages:
%DAEMON-3-LIBJNX_REPLICATE_RCP_ERROR: rcp -l -Ji //var/etc/stp_context.id+ re0://var/etc/stp_context.id+ : rcmd: socket: Can't assign requested address rcmd: socket: Can't assign requested address
This PR is similar to PR1027898. The issue has not been fully fixed in PR1027898 on releases from 13.3 and is fully solved via this PR.
Reference link: https://prsearch.juniper.net/problemreport/PR1177692
PR mentions when the commit synchronized is issue, error is seeing. However, the issue will be also seeing with normal commit within VCs.
We do have the following workarounds:
WORKAROUND
There are two workarounds for resolving this issue:
1. Perform the Routing Engine (RE) switchover.
request chassis routing-engine master switch
2. Commit the new configuration.
commit synchronize
If above workaround doesn't help clear the issue, then use the following:
1. Reboot the backup RE (Note: Make sure that you are logged in to the backup RE.)
request system reboot
2. Commit the configuration after rebooting of the backup RE is complete.
And related to the fix, the issue should not be seeing on the following releases:
RESOLVED IN
13.3R10
13.3R4-S11
14.1R8
14.1X50-D91
14.1X53-D40
14.2R8
15.1F5-S4
15.1F6-S3
15.1F7
15.1R5
15.1X49-D150
15.1X53-D34
15.1X53-D50
15.1X53-D60
16.1R2
16.1X70-D10
16.2R117.1R1