Configuring the Commit Delay Timer

When the router first receives an SNMP nonvolatile set request, a JUNOScript session opens and prevents other users or applications from changing the candidate configuration (equivalent to the command-line interface [CLI] configure exclusive command). If the router does not receive new SNMP set requests within 5 seconds (the default value), the candidate configuration is committed and the JUNOScript session closes (the configuration lock is released). If the router receives new SNMP set requests while the candidate configuration is being committed, the SNMP set request is rejected and an error is generated. If the router receives new SNMP set requests before 5 seconds have elapsed, the commit-delay timer (the length of time between when the last SNMP request is received and the commit is requested) resets to 5 seconds.

By default, the timer is set to 5 seconds. To configure the timer for the SNMP set reply and start of the commit, include the commit-delay statement at the [edit snmp nonvolatile] hierarchy level:

[edit snmp nonvolatile]

commit-delay seconds;

seconds is the length of the time between when the SNMP request is received and the commit is requested for the candidate configuration. For more information about the configure exclusive command and locking the configuration, see the JUNOS System Basics Configuration Guide and the JUNOScript API References.