Siemens RX1400 - Page 131

RUGGEDCOM NETCONF
Reference Guide
Chapter 7
Examples
Selecting a Certificate for an IPSec Tunnel 119
<name>{name}</name>
<startup>{startup}</startup>
<authenticate>{authenticate}</authenticate>
<connection-type>{connection type}</connection-type>
<monitor-interface>{monitor interface}</monitor-interface>
<left>
<public-ip>
<type>{ip type}</type>
<value>{ip value}</value>
</public-ip>
<subnet>
<network>{network}</network>
</subnet>
<key>
<type>{key type}</type>
<certificate>{certificate}</certificate>
</key>
<nexthop>
<type>{nexthop type}</type>
<value>{nexthop value}</value>
</nexthop>
</left>
<right>
<public-ip>
<type>{ip type}</type>
<value>{ip value}</value>
</public-ip>
<subnet>
<network>{network}</network>
</subnet>
<key>
<type>{key type}</type>
<certificate>{certificate}</certificate>
</key>
<nexthop>
<type>{nexthop type}</type>
<value>{nexthop value}</value>
</nexthop>
</right>
</connection>
</ipsec>
</tunnel></config>
</edit-config>
</rpc>]]>]]>
• {name}
The name of the IPSec tunnel.
• {startup}
The action to take when IPSec is initialized. Must be one of the following: add, default, ignore, route, or
start.
• {authenticate}
The authentication method of the IPSec tunnel. Must be one of the following: rsasig, secret, or default.
• {connection type}
The IPSec connection type. Must be one of the following: tunnel, transport, passthrough, or default.
• {monitor interface}
The interface to monitor where the IPSec tunnel is running/established. For example: fe-cm-1, switch.0001,
etc.