Chapter 6
RUGGEDCOM ROX II Actions
•
Section 6.5.8, "remove-crl (IPSEC)"
Section 6.5.1
display-public-key (IPSEC)
This action displays the public RSA key. This action does not take any parameters.
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<action xmlns="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<tunnel xmlns="http://ruggedcom.com/ns/rmf_iftunnel">
<ipsec>
<display-public-key/>
</ipsec>
</tunnel>
</data>
</action>
</rpc>]]>]]>
Section 6.5.2
status (IPSEC)
This action displays the status of the running IPSec service. This action does not take any parameters.
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<action xmlns="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<tunnel xmlns="http://ruggedcom.com/ns/rmf_iftunnel">
<ipsec>
<status/>
</ipsec>
</tunnel>
</data>
</action>
</rpc>]]>]]>
Section 6.5.3
install-certificate (IPSEC)
This action uploads an IPSec certificate to the device. The certificate must be located at a network location
accessible to the device. Parameters include <remote-host>, <remote-port>, <remote-pem-file-path>,
<remote-key-file-path>, <user>, and <password>.
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<action xmlns="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<tunnel xmlns="http://ruggedcom.com/ns/rmf_iftunnel">
<ipsec>
<certificate>
<install-certificate>
<remote-host>{remoteHost}</remote-host>
<remote-port>{remotePort}</remote-port>
<remote-pem-file-path>{pemFilePath}</remote-pem-file-path>
<remote-key-file-path>{keyFilePath}</remote-key-file-path>
72
RUGGEDCOM NETCONF
Reference Guide
display-public-key (IPSEC)