Chapter 7
Examples
</rpc>]]>]]>
5.
Commit the changes:
<rpc message-id="234" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<commit/>
</rpc>]]>]]>
6.
Unlock the candidate configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="235">
<unlock>
<target>
<candidate/>
</target>
</unlock>
</rpc>]]>]]>
7.
Unlock the running configuration:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="236">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>]]>]]>
Section 7.42
Displaying the Status of the IPsec Service
Displays the status of the running IPsec service. This action does not take any parameters.
<rpc message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter type="subtree">
<tunnel xmlns="http://ruggedcom.com/ns/rmf_iftunnel">
<ipsec>
<status>
</status>
</ipsec>
</tunnel>
</filter>
</get>
</rpc>]]>]]>
Section 7.43
Selecting a Certificate for an IPSec Tunnel
This action selects a certificate to use for an IPSec tunnel. The certificate must be available on the device.
<rpc message-id="233"xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target><candidate/></target>
<config><tunnel xmlns="http://ruggedcom.com/ns/rmf_iftunnel">
<ipsec>
<connection>
118
RUGGEDCOM NETCONF
Reference Guide
Displaying the Status of the IPsec Service