Cisco Nexus 7000 Series Command Reference Manual page 64

ip lisp map-cache
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 .
The first use of the ip lisp map-cache command is to configure an ingress tunnel router (ITR) with a
Usage Guidelines
static IPv4 EID-to-RLOC mapping relationship and its associated traffic policy. For each entry, you must
enter a destination IPv4 EID-prefix block and its associated locator, priority, and weight. The IPv4
EID-prefix/prefix-length is the LISP EID-prefix block at the destination site. The locator is an IPv4 or
IPv6 address of the remote site where the IPv4 EID-prefix can be reached. The locator address has a
priority and weight that are used to define traffic policies when multiple RLOCs are defined for the same
EID-prefix block. You can enter this command up to four times for a given EID-prefix. Static IPv4
EID-to-RLOC mapping entries configured when you enter the ip lisp map-cache command take
precedence over dynamic mappings learned through Map-Request/Map-Reply exchanges.
The second, optional use of the ip lisp map-cache command is to statically configure the packet
handling behavior associated with a specified destination IPv4 EID-prefix. For each entry, a destination
IPv4 EID-prefix block is associated with a configured forwarding behavior. When a packet's destination
address matches the EID-prefix, one of the following packet handling options:
•
•
•
This command does not require a license.
This example shows how to configure a destination EID-to-RLOC mapping and associated traffic policy
Examples
for the IPv4 EID-prefix block 192.168.1.0/24. In this example, the locator for this EID-prefix block is
10.1.1.1 and the traffic policy for this locator has a priority of 1 and a weight of 100.
switch# configure terminal
switch(config)# ip lisp map-cache 192.168.1.0/24 10.1.1.1 priority 1 weight 100
This example shows how to configure a destination EID-to-RLOC mapping and associated traffic
policy for the IPv4 EID-prefix block 192.168.2.0/24 to drop. No traffic is forwarded to this destination
as a result.
switch# configure terminal
switch(config)# ip lisp map-cache 192.168.2.0/24 drop
Related Commands Command
ip lisp
database-mapping
ip lisp itr
ip lisp map-cache-limit Configures the maximum number of IPv4 LISP map-cache entries allowed
Cisco Nexus 7000 Series NX-OS LISP Command Reference
LSP-54
drop—Packets that match the destination IPv4 EID-prefix are dropped. For example, this action
may be useful when administrative policies define that packets should be prevented from reaching
a site.
native-forward—Packets that match the destination IPv4 EID-prefix are natively forwarded
without LISP encapsulation. Use this action when the destination site is known to always be
reachable natively and LISP encapsulation should never be used.
map-request—Packets that match the destination IPv4 EID-prefix cause a Map-Request to be sent.
It is implied that the Map-Reply returned by this request will allow subsequent packets that match
this EID-prefix to be Locator/ID Separation Protocol (LISP)-encapsulated. Use this action
troubleshooting map-request activities and other diagnostic actions.
Description
Configures an IPv4 EID-to-RLOC mapping relationship and its associated
traffic policy.
Configures the Cisco NX-OS device to act as an IPv4 LISP Ingress Tunnel
Router (ITR).
to be stored by the Cisco NX-OS device.
Cisco Nexus 7000 Series LISP Commands