You are configuring a switch as a LISP xTR. You plan to use the LISP xTR when deploying redundant map servers.
Which action do you take?
A . Register the LISP xTR to the anycast IP address of the map resolver.
B . Register the LISP xTR to the IP address of each map server.
C . Configure the map-notify group command by using the anycast IP address of the map resolver.
D . Configure the map-notify group command by using the IP address of each map server.
Answer: B
Explanation:
Map-Server and Map-Resolver Considerations
The Map-Server and Map-Resolver are critical components in a LISP deployment. They provide capabilities to store and resolve the EID-to-RLOC mapping information for the LISP routers to enable routing between LISP sites.
The Map-Server is a network infrastructure component that learns EID-to-RLOC mapping entries from ETRs, which are authoritative sources and which publish (register) their EID-to-RLOC mapping relationships with the Map-Server. A Map-Resolver is a network infrastructure component that accepts LISP-encapsulated Map-Requests, typically from an ITR, and finds the appropriate EID-to-RLOC mapping by checking with a co-located Map-Server (typically) or by consulting the distributed mapping system.
This section discusses Map-Server and Map-Resolver deployment considerations for an enterprise data center LISP deployment. Note that you should deploy redundant standalone coexistent Map-Servers and Map-Resolvers. When redundant standalone Map-Servers and Map-Resolvers are deployed, all xTRs must register with both Map-Servers so that each has a consistent view of the registered LISP EID namespace. For Map-Resolver functions, use of an anycast address is desirable, because it will improve mapping lookup performance by choosing the Map-Resolver that is topologically closest to the requesting ITR.