An IP-IP tunnel must meet which two requirements to function correctly? (Choose two.)
A.
The tunnel end points must have a valid route to each other.
B.
The tunnel end points must be distributed inside the IGP.
C.
A GRE tunnel must be established first to carry the IP-IP tunnel.
D.
All devices in between the tunnel end points must have a valid route to the tunnel end points.
Explanation:
Tunnel Services Overview
By encapsulating arbitrary packets inside a transport protocol, tunneling provides a private, secure path through an otherwise public network. Tunnels connect discontinuous subnetworks and enable encryption interfaces, virtual private networks (VPNs), and Multiprotocol Label Switching (MPLS). If you have a Tunnel Physical Interface Card (PIC) installed in your router, you can configure unicast, multicast, and logical tunnels.
You can configure two types of tunnels for VPNs: one to facilitate routing table lookups and another to facilitate VPN routing and forwarding instance (VRF) table lookups.
For information about encryption interfaces, see Encryption Interfaces Configuration Guidelines and the JUNOS System Basics Configuration Guide. For information about VPNs, see the JUNOS VPNs Configuration Guide. For information about MPLS, see the JUNOS MPLS Applications Configuration Guide.
The JUNOS software supports the tunnel types shown in Table 25.
Table 25: Tunnel Interface Types
Interface
Description
gr-0/0/0
Configurable generic routing encapsulation (GRE) interface. GRE allows the encapsulation of one routing protocol over another routing protocol.
Within a router, packets are routed to this internal interface, where they are first encapsulated with a GRE packet and then re-encapsulated with another protocol packet to complete the GRE. The GRE interface is an internal interface only and is not associated with a physical medium or PIC. You must configure the interface for it to perform GRE.
gre
Internally generated GRE interface. This interface is generated by the JUNOS software to handle GRE. It is not a configurable interface.
ip-0/0/0
Configurable IP-over-IP encapsulation (also called IP tunneling) interface. IP tunneling allows the encapsulation of one IP packet over another IP packet.
Generally, IP routing allows packets to be routed directly to a particular address. However, in some instances you might need to route an IP packet to one address and then encapsulate it for forwarding to a different address. In a mobile environment in which the location of the end device changes, a different IP address might be used as the end device migrates between networks.
Within a router, packets are routed to this internal interface where they are encapsulated with an IP packet and then forwarded to the encapsulating packet’s destination address. The IP-IP interface is an internal interface only and is not associated with a physical medium or PIC. You must configure the interface for it to perform IP tunneling.
ipip
Internally generated IP-over-IP interface. This interface is generated by the JUNOS software to handle IP-over-IP encapsulation. It is not a configurable interface.
lt-0/0/0
The lt interface on M-series and T-series routing platforms supports configuration of logical systemsthe capability to partition a single physical router into multiple logical devices that perform independent routing tasks.
On J-series Services Routers, it has a different function: it provides class-of-service (CoS) support for data link switching (DLSw) traffic and real-time performance monitoring (RPM) probe packets.
Within a Services Router, packets are routed to this internal interface for services. The lt interface is an internal interface only and is not associated with a physical medium or PIM. You must configure the interface for it to perform CoS for DLSW and RPM services.
mt-0/0/0
Internally generated multicast tunnel interface. Multicast tunnels filter all unicast packets; if an incoming packet is not destined for a 224/8-or-greater prefix, the packet is dropped and a counter is incremented.
Within a router, packets are routed to this internal interface for multicast filtering. The multicast tunnel interface is an internal interface only and is not associated with a physical medium or PIC. If your routing platform has a Tunnel Services PIC, the JUNOS software automatically configures one multicast tunnel interface (mt-) for each virtual private network (VPN) you configure. You do not need to configure multicast tunnel interfaces. However, you can configure properties on mt- interfaces, such as the multicast-only statement.
mtun
Internally generated multicast tunnel interface. This interface is generated by the JUNOS software to handle multicast tunnel services. It is not a configurable interface.
pd-0/0/0
Configurable Protocol Independent Multicast (PIM) de-encapsulation interface. In PIM sparse mode, the first-hop routing platform encapsulates packets destined for the rendezvous point router. The packets are encapsulated with a unicast header and are forwarded through a unicast tunnel to the rendezvous point. The rendezvous point then de-encapsulates the packets and transmits them through its multicast tree.
Within a router, packets are routed to this internal interface for de-encapsulation. The PIM de-encapsulation interface is an internal interface only and is not associated with a physical medium or PIC. You must configure the interface for it to perform PIM de-encapsulation.
pe-0/0/0
Configurable Protocol Independent Multicast (PIM) encapsulation interface. In PIM sparse mode, the first-hop routing platform encapsulates packets destined for the rendezvous point router. The packets are encapsulated with a unicast header and are forwarded through a unicast tunnel to the rendezvous point. The rendezvous point then de-encapsulates the packets and transmits them through its multicast tree.
Within a router, packets are routed to this internal interface for encapsulation. The PIM encapsulation interface is an internal interface only and is not associated with a physical medium or PIC. You must configure the interface for it to perform PIM encapsulation.
pimd
Internally generated Protocol Independent Multicast (PIM) de-encapsulation interface. This interface is generated by the JUNOS software to handle PIM de-encapsulation. It is not a configurable interface.
pime
Internally generated Protocol Independent Multicast (PIM) encapsulation interface. This interface is generated by the JUNOS software to handle PIM encapsulation. It is not a configurable interface.
vt-0/0/0
Configurable virtual loopback tunnel interface. Facilitates VRF table lookup based on MPLS labels. This interface type is supported on M-series and T-series routing platforms, but not on J-series Services Routers.
To configure a virtual loopback tunnel to facilitate VRF table lookup based on MPLS labels, you specify a virtual loopback tunnel interface name and associate it with a routing instance that belongs to a particular routing table. The packet loops back through the virtual loopback tunnel for route lookup.