Description

Stale configuration entries present in the backup routing-engine, the stale entries cannot be removed from master and backup routing-engine with 'commit synchronize' and 'commit synchronize force'.

 

Symptoms

In the dual Routing Engine scenario, the backup Routing Engine does not sync up the configuration change while deleting an inactivated interface/routing-instances from the master. So after the operation, the inactivated interface/routing-instances still exists on the backup Routing Engine.

Solution

This issue has been addressed via PR/1586229.

 

Workaround:

 

Step 1:

Check the stale entries in the backup RE via executing following command:

In config mode

Show | compare re1:/config/juniper.conf

Step 2:

Disable commit sync on the active RE > RE0.

deactivate system commit synchronize

commit

> Then login to RE1 and remove the stale entries which we saw in the first step

> commit

Step 3:

Login back to RE0 and enable commit sync

activate system commit synchronize

commit

 

 

Modification History

2024-03-07 : Article Created