To change the candidate configuration on a routing platform, a client application emits the <copy-config>, the <edit-config>, or the <discard-changes> tag element and the corresponding tag subelements within the <rpc> tag element.
The following example shows the various tag elements available:
<rpc>
<copy-config>
<target><candidate/></target>
<default-operation> (merge | none | replace) </default-operation>
<error-operation> (ignore-error | stop-on-error) </error-operation>
<source><url>location</url></source>
</copy-config>
<edit-config>
<target><candidate/></target>
<default-operation>operation</default-operation>
<error-operation>error</error-operation>
<(config | config-text | url)>
<!- - configuration change file or data - ->
</(config | config-test | url)>
</edit-config>
<discard-changes/>
</rpc>
]]>]]>
![]() |
Note: Although the example shows the <copy-config>, <edit-config>, and <discard-changes> used in the same <rpc> data stream, in actual practice, you can only use one of these first-level tag elements within a set of <rpc> tags. |
Notice that the three tags—<copy-config>, <edit-config>, and <discard-changes>—correspond to the three basic configuration tasks available to you:
Notice also that the <copy-config> and the <edit-config> tags both have additional subtags related to each tag element. These subtag elements are described in the following sections: