Chapter 6
RUGGEDCOM ROX II Actions
RUGGEDCOM NETCONF
Reference Guide
72
display-public-key (IPSEC)
•
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>
Summary of Contents for RUGGEDCOM MX5000RE
Page 8: ...Table of Contents RUGGEDCOM NETCONF Reference Guide viii ...
Page 12: ...Preface RUGGEDCOM NETCONF Reference Guide xii Customer Support ...
Page 26: ...Chapter 1 Introduction RUGGEDCOM NETCONF Reference Guide 14 Sample Session Editing Data ...
Page 40: ...Chapter 3 NETCONF Sessions RUGGEDCOM NETCONF Reference Guide 28 Killing a Session ...
Page 64: ...Chapter 5 Changing Configuration Data RUGGEDCOM NETCONF Reference Guide 52 Committing Changes ...
Page 148: ...Chapter 8 NETCONF XML Elements RUGGEDCOM NETCONF Reference Guide 136 validate ...