You can configure the ephemeral database to execute commit synchronize operations using a synchronous commit model on dual Routing Engine devices or MX Series Virtual Chassis. The synchronous commit model enables you to reliably use the ephemeral database on devices that have Graceful Routing Engine switchover (GRES) or non-stop routing (NSR) enabled. To use the synchronous commit model for the ephemeral database, configure the commit-synchronize-model synchronous statement at the [edit system configuration-database ephemeral] hierarchy level.
Note: Starting in 25.4, we've changed the default commit synchronize model for the ephemeral database from the asynchronous model to the synchronous model. The synchronous model provides better assurance that the ephemeral configuration is synchronized across Routing Engines or Virtual Chassis members by processing commits synchronously. With this change, only the synchronous model supports synchronizing ephemeral data on devices that have graceful Routing Engine switchover (GRES) or nonstop active routing (NSR) enabled.
| Product / Application | Software | Introduced Release |
|---|---|---|
| MX240 | Junos OS | 21.1R1 |
| MX301 | Junos OS | 25.4R1 |
| MX304 | Junos OS | 22.2R3 |
| MX480 | Junos OS | 21.1R1 |
| MX960 | Junos OS | 21.1R1 |
| MX2010 | Junos OS | 21.1R1 |
| MX2020 | Junos OS | 21.1R1 |
| MX10003 | Junos OS | 21.1R1 |
| MX10004 | Junos OS | 22.3R1 |
| MX10008 | Junos OS | 21.1R1 |
| MX10016 | Junos OS | 21.1R1 |
| Next Generation Port Extender | Junos OS | 25.4R1 |