nerdexam
Cisco

350-401 · Question #179

Which two LISP infrastructure elements are needed to support LISP to non-LISP internetworking? (Choose two)

The correct answer is A. PETR C. MR. To enable communication between LISP and non-LISP networks, Proxy Egress Tunnel Routers (PETR) are needed for traffic originating from LISP, while Map Resolvers (MR) facilitate the necessary EID-to-RLOC mapping lookups.

Submitted by ashley.k· Mar 6, 2026Mobility Services

Question

Which two LISP infrastructure elements are needed to support LISP to non-LISP internetworking? (Choose two)

Options

  • APETR
  • BPITR
  • CMR
  • DMS
  • EALT

How the community answered

(16 responses)
  • A
    94% (15)
  • D
    6% (1)

Why each option

To enable communication between LISP and non-LISP networks, Proxy Egress Tunnel Routers (PETR) are needed for traffic originating from LISP, while Map Resolvers (MR) facilitate the necessary EID-to-RLOC mapping lookups.

APETRCorrect

A Proxy Egress Tunnel Router (PETR) is a specialized LISP device that encapsulates traffic from a LISP site destined for a non-LISP network and sends it into the traditional internet, acting as the egress point for LISP-originated traffic.

BPITR

A Proxy Ingress Tunnel Router (PITR) is used when a non-LISP site initiates communication to a LISP site; it receives traffic from a non-LISP network, encapsulates it, and sends it into the LISP domain.

CMRCorrect

A Map Resolver (MR) is a LISP infrastructure device that receives Map-Request messages from Ingress Tunnel Routers (ITRs) or PITRs, and then forwards these requests to the appropriate Map Servers (MS) to resolve EID-to-RLOC mappings, which is crucial for LISP routers to find the RLOCs of PETRs or other LISP sites to forward traffic correctly.

DMS

A Map Server (MS) stores EID-to-RLOC mappings for LISP sites and responds to Map-Requests; while crucial for LISP operation, it doesn't directly handle the internetworking encapsulation/decapsulation for LISP to non-LISP traffic like a PETR.

EALT

ALT (Alternative Logical Topology) is a routing protocol used by Map Servers and Map Resolvers to find each other and exchange mapping information, but it is an internal LISP mechanism rather than an infrastructure element directly responsible for LISP to non-LISP internetworking.

Concept tested: LISP to non-LISP internetworking components

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_lisp/configuration/xe-3s/irl-xe-3s-book/irl-lisp-non-lisp.html

Topics

#LISP#PETR#PITR#non-LISP internetworking

Community Discussion

No community discussion yet for this question.

Full 350-401 Practice