Configuring Tunnel Interfaces for Routing Table Lookup
To configure tunnel interfaces to facilitate routing table lookups for VPNs, you specify a tunnel’s endpoint IP addresses and associate them with a routing instance that belongs to a particular routing table. This enables the Junos OS to search in the appropriate routing table for the route prefix, because the same prefix can appear in multiple routing tables. To configure the destination VPN, include the routing-instance statement:
You can include this statement at the following hierarchy levels:
- [edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel]
- [edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number tunnel]
This configuration indicates that the tunnel’s destination address is in routing instance routing-instance-name. By default, the tunnel route prefixes are assumed to be in the default Internet routing table inet.0.
 | Note: If you configure a virtual loopback tunnel interface and the vrf-table-label statement on the same routing instance, the vrf-table-label statement takes precedence over the virtual loopback tunnel interface. For more information, see Configuring Virtual Loopback Tunnels for VRF Table Lookup. |
For more information about VPNs, see the Junos VPNs Configuration Guide.
