nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

13-3.
Example 13-3. Define the Global Mapping That Identifies the IP Subnets in the Data
Center Assigned to the Servers
Click here to view code image
xTR#
xTR# conf t
Enter configuration commands, one per line. End with
CNTL/Z.
xTR(config)# ip lisp database-mapping 172.20.0.0/16
10.1.1.1 priority 1 weight 50
xTR(config)# ip lisp database-mapping 172.20.0.0/16
10.1.1.2 priority 1 weight 50
xTR(config)# exit
xTR# copy running-configuration startup-configuration
The mapping configuration enables the aggregate prefix 172.20.0.0/16 to the two
RLOC IP addresses; the RLOC IP addresses identifies the data center xTR LISP
devices. The priority and weight are centrally configured and managed; this allows the
administrator to influence the inbound traffic to a specific xTR. Example 13-3 has the
priority and weights the same for both xTRs that enable load-balancing across both the
data center xTRs.
4. Define the map-server (MS) and map-resolvers (MR) on the Nexus 7000, as shown in
Example 13-4.
Example 13-4. Define the Map-Servers and Map-Resolvers
Click here to view code image
xTR#
xTR# conf t
Enter configuration commands, one per line. End with
CNTL/Z.
xTR(config)# ip lisp itr map-resolver 10.1.1.7
xTR(config)# ip lisp etr map-server 10.1.1.5 key cisco
xTR(config)# ip lisp etr map-server 10.1.1.6 key cisco
xTR(config)# exit
xTR# copy running-configuration startup-configuration
The map-servers are deployed in a redundant fashion; map-servers do not share state
information. Because the map-servers are stateless, the two entries are needed to
define both map-servers in the Layer 3 infrastructure to have each xTR register the