<discard-changes>

The <discard-changes> operation causes the <candidate> datastore to revert to match the <running> datastore and discard any uncommitted configuration changes.

To discard BOF configuration changes, the ‟bof” <configuration-region> must be specified within the <discard-changes> RPC. For example:

<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
    <discard-changes>
                       <configuration-region>bof</configuration-region>
              </discard-changes>
</rpc>
]]>]]>

To discard LI configuration changes, the ‟li” <configuration-region> must be specified within the <discard-changes> RPC. For example:

<discard-changes>
  <configuration-region>li</configuration-region>
</discard-changes>

The <discard-changes> RPC can only be used with LI configuration changes if all of the following conditions are true.

• The NETCONF user is a LI user.

• The NETCONF session has an exclusive lock on the LI configuration region and <candidate> datastore.

• The specified <configuration-region> is ‟li”.

• The YANG modules used are the Nokia SR OS YANG modules.

If any of the preceding conditions are false, SR OS returns an error.

See Table: Protocol operations and level of support in Nokia SR OS NETCONF servers for more information.