Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Associating the Configured Security Association with a Logical Interface

Configuring the ES PIC associates the configured SA with a logical interface. This configuration defines the tunnel itself (logical subunit, tunnel addresses, maximum transmission unit [MTU], optional interface addresses, and the name of the SA to apply to traffic).

The addresses configured as the tunnel source and destination are the addresses in the outer IP header of the tunnel.

Note: The tunnel source address must be configured locally on the router, and the tunnel destination address must be a valid address for the security gateway terminating the tunnel.

The M5, M10, M20, and M40 routers support the ES PIC.

The SA must be a valid tunnel-mode SA. The interface address and destination address listed are optional. The destination address allows the user to configure a static route to encrypt traffic. If a static route uses that destination address as the next hop, traffic is forwarded through the portion of the tunnel in which encryption occurs.

The following example shows how to configure an IPsec tunnel as a logical interface on the ES PIC. The logical interface specifies the tunnel through which the encrypted traffic travels. The ipsec-sa statement associates the security profile with the interface.

[edit interfaces]
es-0/0/0 {unit 0 {tunnel {source tunnel 10.5.5.5; # tunnel source addressdestination 10.6.6.6; # tunnel destination address}family inet {ipsec-sa ipsec-sa; # name of security association to apply to packetaddress 10.1.1.8/32 { # local interface address inside local VPNdestination 10.2.2.254; # destination address inside remote VPN}}}

Published: 2013-02-22