Confirmed-commit from Junos Space Network Management Platform
Junos Space Network Management Platform supports the Junos OS confirmed-commit functionality. By default, Junos Space Platform uses confirmed-commit for all commit operations on all devices that are discovered on Junos Space Platform and that support the confirmed-commit NETCONF capability. The default timeout value for the confirmed-commit operations issued by Junos Space Platform is 10 minutes. Junos Space Platform sends a remote procedure call (RPC) for confirmed-commit immediately after sending the RPC for a commit. The devices stay connected even if the commit operation contains an incorrect configuration edit that may disconnect the device from Junos Space Platform. An EJB callback method is used to verify the change in configuration on the device.
A candidate configuration created using the Schema-based Configuration Editor and Configuration Guides support the confirmed-commit functionality. If you are deploying the configuration by using a template, you need to publish these templates to the candidate configuration of the device. When you push the configuration to the devices by using the Schema-based Configuration Editor, templates, or the Configuration Guide, the job triggered for these tasks display the timeout value of confirmed-commit. Job details include the time taken for the EJB callback method to return a value and the time taken to confirm the commit operation or perform a rollback operation.
Table 1 lists the managed status of the device in NSOR and SSOR modes when a candidate configuration is deployed to a device that supports the confirmed-commit NETCONF capability. It also lists the status of the job details when the confirmed-commit operation is a success or failure in these modes.
Confirmed-commit and EJB Callback Method Success and Failure Conditions |
NSOR Mode |
SSOR Mode |
Job Result and Details |
|---|---|---|---|
Junos Space Platform issues a confirmed-commit operation with a timeout value. |
In Sync |
Space Changed |
NA |
An EJB callback is sent to the device to verify the change in configuration on the device. |
NA |
NA |
NA |
The EJB callback method does not return any value within the confirmed-commit timeout interval. |
In Sync |
Space Changed |
Failed |
The EJB callback method returns True and the commit is confirmed. |
Out Of Sync followed by resynchronization by Junos Space Platform |
In Sync or Space Changed (if new changes are added to the candidate configuration) |
Success |
The EJB callback method returns False and the configuration is rolled back. |
Out Of Sync followed by resynchronization by Junos Space Platform |
Space Changed |
Failure with the |
The EJB callback method returns False and the device is automatically rolled back to the currently active configuration. |
Out Of Sync followed by resynchronization by Junos Space Platform |
Space Changed, Device Changed (after Junos Space Platform receives the system log about the auto-rollback operation on the device) |
Failure with auto-rollback details |
In SSOR mode, if a confirmed-commit is not successful and if the device is automatically rolled back, you need to manually accept the change by using the Resolve Out-of-band Changes workflow to change the managed status of the device to In Sync.
If a device is disconnected from Junos Space Platform (that is, Connection Status is down) after Junos Space Platform issues a confirmed-commit and is automatically rolled back before connecting back to Junos Space Platform, you need to manually check the device configuration from the CLI to confirm that the commit operation was successful.