Cisco Nexus 7000 Series Command Reference Manual page 90

Cisco Nexus 7000 Series LISP Commands
ipv6 lisp database-mapping
S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m .
When you configure a Cisco NX-OS Series device is as an egress tunnel router (ETR), these LISP
database-mapping parameters are advertised within a Map-Reply message to indicate the ingress traffic
preferences of the site for the associated EID-prefix block. An ingress tunnel router (ITR) then selects a
source locator (outer header) address for encapsulating packets destined to the EID-prefix based on these
advertised parameters.
When a LISP site has multiple locators associated with the same EID-prefix block, you use multiple ipv6
lisp database mapping commands to configure all of the locators for a given EID-prefix block. Each
locator may be assigned the same or a different priority value between 0 and 255. When multiple locators
are assigned different priority values, the priority value alone is used to determine which locator to
prefer. A lower value indicates a more preferable path. A value of 255 indicates that the locator must not
be used for unicast traffic forwarding.
When multiple locators have the same priority, they can be used in a load-sharing manner. In this case,
for a given priority, the weight given to each locator is used to determine how to load-balance unicast
packets between them. Weight is a value between 0 and 100 and represents the percentage of traffic to
be load shared to that locator. If you assign a nonzero weight value to any locator for a given EID-prefix
block, you must assign all locators with the same priority for that same EID-prefix block with a nonzero
weight value and the sum of all weight values must equal 100. If you assign a weight value of zero to
any locator for a given EID prefix block, you must assign all locators with the same priority for that same
EID-prefix block a weight value of zero. A weight value of zero indicates to an ITR that receives the
Map-Reply that it can decide how to load-share traffic destined to that EID-prefix block.
When you assign a LISP site with multiple IPv6 EID-prefixes, the ipv6 lisp database-mapping is
configured for each IPv4 EID-prefix assigned to the site and for each locator that has a reachable IPv6
EID-prefix.
When multiple ETRs are used at a LISP site, you must enter the ipv6 lisp database-mapping command
on all ETRs for all locators to make an IPv4 EID-prefix block reachable even when the locator is not
local to the specific ETR that is being configured.
If the ETR receives its RLOC through a dynamic process such as DHCP, or if it is sited behind NAT
device and the routing locator belongs to the private address space that the NAT device translates to a
public globally routed address, you might not be able to specify a locator in the ip lisp database-mapping
entry. When this is the case, add the dynamic keyword with the ipv6 lisp database-mapping command
so that the RLOC for this Cisco NX-OS device will be determined dynamically rather than being
statically defined in each ip lisp database-mapping entry.
When an ETR is sited behind NAT, it needs to know the public global locator address; this is address
that is required for Map-Register and Map-Reply messages. In this case, you should enter the {ip | ipv6}
lisp nat-traversal command. For more information, see the {ip | ipv6} lisp nat-traversal command.
This command does not require a license.
This example shows how to configure lisp database-mapping entries for a single IPv6 EID-prefix block
Examples
and two IPv4 locators that are associated with the EID-prefix block:
switch# configure terminal
switch(config)# ipv6 lisp database-mapping 2001:DB8:BB::/48 10.1.1.1 priority 1 weight 100
switch(config)# ipv6 lisp database-mapping 2001:DB8:BB::/48 10.1.2.1 priority 1 weight 100
Cisco Nexus 7000 Series NX-OS LISP Command Reference
LSP-80