<validate>

The following is the list of supported :validate operations.

The validate:1.1 and :validate:1.0 capabilities are advertised in the NETCONF server <hello> as the following:

<capability>urn:ietf:params:netconf:capability:validate:1.0</capability>

<capability>urn:ietf:params:netconf:capability:validate:1.1</capability>

To validate BOF configurations, the ‟bof” <configuration-region> must be specified within the <validate> <source>. For example:

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

To validate LI configurations, the ‟li” <configuration-region> must be specified within the <validate> <source>. For example:

<validate>
  <source>
    <configuration-region>li</configuration-region>
    <candidate/>
  </source>
</validate>

Alternatively, the <source> can be specified in the format of ‟configuration-region”-”datastore”. For example:

<validate>
  <source>
    <li-candidate/>
  </source>
</validate>

When both the <configuration-region> and the ‟configuration-region”-‟datastore” format are used, SR OS applies the last tag used in the XML request. For example:

<validate>
  <source>
    <configuration-region>configure</configuration-region>
    <li-candidate/>
  </source>
</validate>

In the preceding example, the <validate> is used on the ‟li” <candidate> datastore.

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