Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Your software release might not support all the features documented in this module. For the latest caveats and feature information,
see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. To find information about the features documented in this module, and to
see a list of the releases in which each feature is supported, see the "New and Changed Information"chapter or the Feature
History table in this chapter.
Feature History for Redistribution of RIB Routes into LISP
Table 1. Feature History for Redistribution of RIB Routes into LISP
Feature Name
Releases
Feature
Information
Redistribution of RIB Routes into LISP
8.3(1)
This feature is supported on Cisco Nexus 7000 Series switches.
Information About Redistribution of RIB Routes into LISP
Starting with Cisco NX-OS 8.3(1), the Locator ID Separation Protocol (LISP) supports the redistribution of RIB routes into
LISP feature. This feature allows LISP to import Layer 3 RIB routes in use for internal applications. Importing information
from the RIBs allows for proactive learning of LISP prefixes in the control plane. This eliminates the need to statically
specify prefixes to be used for map-caches or databases in LISP.
The redistribution of RIB routes into LISP is enabled under the VRF Context and supports both IPV4 and IPV6 address families.
The following RIB sources are supported for LISP redistribution:
Configuring Database Application for Redistribution of RIB Routes into LISP
Locator ID Separation Protocol (LISP) egress tunnel routers (ETR) import prefixes with a local RIB route into the LISP EID
database and register it with the Mapping System. Perform the following steps on a xTR device in a LISP topology.
Before you begin
Enable the LISP feature.
Procedure
Command or Action
Purpose
Step 1
configure terminal
Example:
switch# configure terminal
Enters global configuration mode.
Step 2
vrf contextvrf-name
Example:
switch(config)# vrf context VRF1
Creates a new VRF and enters VRF configuration mode.
The value of the vrf-name is any case-sensitive, alphanumeric string of up to 32 characters.
Step 3
{ip | ipv6}lisp etr
Example:
switch(config-vrf)# ip lisp etr
Configures LISP ETR functionality for the VRF.
Step 4
lisp instance-idiid
Example:
switch(config-vrf)# lisp instance-id 100
Configures an instance ID to be associated with endpoint identifier (EID)-prefixes for LISP. The range is from 1 to 16777215.
Step 5
ip lisp locator-vrf {locator-vrf | default}
Example:
switch(config-vrf)# ip lisp locator-vrf default
Configures a non-default VRF table to be referenced by any IPv4 locators.
switch(config-vrf)# ip lisp etr map-server 10.10.10.10 key 3 1c27564ab12121212
Configures the IPv4 or IPv6 locator address of the LISP map server to be used by the egress tunnel router (ETR) when registering
for IPv4 endpoint identifier (EIDs).
Configures the import of routes from the RIB to define endpoint identifier EID space on an ETR.
The route-map keyword specifies that the imported IPv4 prefixes should be filtered according to the specified route-map name.
Step 8
(Optional) ip lisp route-import database maximum-prefix prefix-number
(Optional)
Configures the maximum number of prefixes that can be imported. The valid range is from 1 to 1000. The default value is 1000.
Step 9
(Optional) show [ip | ipv6] lisp route-importdatabase
(Optional)
Displays the EID instance address family for route-import database.
Step 10
(Optional) show [ip | ipv6] lisp database vrf vrf-name
(Optional)
Displays LISP ETR configured local IPv4 EID prefixes and associated locator sets.
Configuring Map-cache Application for Redistribution of RIB Routes into LISP
The LISP Ingress Tunnel Routers (ITRs) import the remote EID map caches and program them into the platform.
Note
LISP database-mappings have higher priority than map-caches. If the same prefix is imported for both database and map-cache
applications, the database route imports will take precedence over map-cache imports. In map-cache, the prefix is visible,
but with the keyword (self) in the show output of the show ip lisp map-cache vrf vrf-name command. Even though the prefixes are present in the map-cache, they will not be present in the routing table as LISP installed
routes.
switch# show ip lisp map-cache vrf VRF1
LISP IP Mapping Cache for VRF ”VRF1" (iid 100), 1 entries
* = Locator data counters are cumulative across all EID-prefixes
192.168.1.0/24, uptime: 00:02:48, expires: 0.000000, via route-import, self
Producer Set: 0004 route-import
Negative cache entry, action: send-map-request
Before you begin
Enable the LISP feature.
Procedure
Command or Action
Purpose
Step 1
configure terminal
Example:
switch# configure terminal
Enters global configuration mode.
Step 2
vrf contextvrf-name
Example:
switch(config)# vrf context VRF1
Creates a new VRF and enters VRF configuration mode.
The value of the vrf-name is any case-sensitive, alphanumeric string of up to 32 characters.
Step 3
Use one of the following commands:
{ip | ipv6}lisp itr
{ip | ipv6}lisp proxy-itrlocator-address
Example:
switch(config-vrf)# ip lisp itr
Configures LISP ITR functionality for the VRF.
Configures LISP Proxy-ITR functionality on the device. The locator address is used as a source address for encapsulating data packets or Map-Request messages. Optionally, you can provide an
address for the other address family (for example, IPv6 for the ip proxy-itr command.
Step 4
lisp instance-idiid
Example:
switch(config-vrf)# lisp instance-id 100
Configures an instance ID to be associated with endpoint identifier (EID)-prefixes for LISP. The range is from 1 to 16777215.
Step 5
ip lisp locator-vrf {locator-vrf | default}
Example:
switch(config-vrf)# ip lisp locator-vrf default
Configures a non-default VRF table to be referenced by any IPv4 locators.
Displays LISP ITR configured local IPv4 EID prefixes.
Example: Redistribution of RIB Routes in LISP
The following example shows the redistribution of RIB routes in database and map-cache applications in a LISP topology.
In the above image, xTR1 is provides global access to a local OSPF stub network and xTR2 connects to an external BGP cloud.
The following example shows a combined use of the two available route-import applications (database and map-cache) in a LISP
overlay fabric network. It first describes how prefixes from the OSPF cloud are imported in xTR1 as database-mappings, and
registered with the LISP mapping system, and then shows how the same prefixes are imported as map-caches on xTR2 so that data
traffic follows the optimized LISP overlay path.
Configuring Route Import with the Database Application
This section describes the database application configurations and commands to verify the configurations. In this case, xTR1
redistributes prefixes from the OSPF network as database-mappings that are then registered with the Mapping System. The figure
Redistribute RIB Routes into Database Topology shows the devices for configuring the LISP route import feature for the database application.
xTR1 Configuration for RIB Route Redistribution into Database
The following example shows how to configure the xTR1 in the sample topology for the LISP route redistribution database application:
switch# configure terminal
switch(config)# vrf context VRF1
switch(config-vrf)# ip lisp itr
switch(config-vrf)# ip lisp etr
switch(config-vrf)# instance-id 100
switch(config-vrf)# ip lisp locator-vrf default
switch(config-vrf)# ip lisp etr map-server 10.10.10.10 key lisp
switch(config-vrf)# ip lisp itr map-resolver 10.10.10.10
! Register database mappings imported from OSPF with the MS/MR with these locators!
switch(config-vrf)# lisp locator-set RLOCSET
switch(config-vrf-lisp)# 10.10.10.1 priority 1 weight 100
! Import fabric prefixes into LISP database based from OSPF!
switch(config-vrf)# ip lisp route-import database ospf 100 route-map RM_OSPF_to_LISP locator-set RLOCSET
Verifying Database-mappings with RIB Route Redistribution
The following example displays the sample show command outputs for the database-mapping configurations:
Verify that the OSPF has programmed the target prefix in the routing table.
xTR1# show ip route 192.168.1.1 vrf VRF1
IP Route Table for VRF “VRF1”
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
192.168.1.0/24, ubest/mbest: 1/0
*via 172.27.1.1, Eth1/27, [110/10], 05:10:39, ospf-100, intra
Verify that LISP has included the prefix in the database-mapping table.
xTR1# show ip lisp database vrf VRF1
LISP ETR IP Mapping Database for VRF "VRF1" (iid 100), global LSBs: 0x000000ff
Local Database: 12
EID-prefix: 192.168.1.0/24, instance-id: 5001, LSBs: 0x000000ff
Producer: route_import , locator_set: RLOCSET, uptime: 00:19:48
Locator: 10.10.10.1, priority: 1, weight: 100
Verify that the database-mapping is registered with the mapping system.
MS# show lisp site
LISP Site Registration Information
* = Some locators are down or unreachable
# = Some registrations are sourced by reliable transport
Site Name Last Up Who Last Inst EID Prefix
Register Registered ID
SITE_ALL_v4 never no -- 100 0.0.0.0/0
00:00:05 yes 10.10.10.1:65292 100 192.168.1.0/24
Verify the EID instance address family configurations for the route redistribution database application.
switch# show ip lisp route-import vrf VRF1 database
IP LISP Route Import for VRF “VRF1"
DATABASE
Specificatons : 1
Maximum Import : 1000
Threshold pct : 75%
Warn only : F
Withdraw : F
Routes Imported : 0
Rejected by limit : 0
Warned : 0
protocol : ospf-100
policy : RM_OSPF_to_LISP
bind_pending : F
type : Route Import Policy
locator_set : RLOCSET
Configuring RIB Route Redistribution with the Map-cache Application
This section describes the map-cache application configurations and commands to verify the configurations. In this section,
the Map Server redistributes the registration table to BGP that propagates the prefixes as routes to xTR2, and finally to
external networks. On xTR2, prefixes coming from the Map Server are imported into LISP as map-caches that can be resolved
using LISP to optimize the path to destination device. The figure Redistribute RIB Routes into Map-cache Topology shows the devices configured for the LISP RIB route redistribution for the map-cache application.
xTR2 Configuration for RIB Route Redistribution into Map-cache
The following example shows how to configure the xTR2 in the sample topology for the LISP route map-cache application:
switch# configure terminal
switch(config)# vrf context VRF1
switch(config-vrf)# ip lisp itr
switch(config-vrf)# ip lisp etr
switch(config-vrf)# instance-id 100
switch(config-vrf)# ip lisp locator-vrf default
switch(config-vrf)# ip lisp etr map-server 10.10.10.10 key lisp
switch(config-vrf)# ip lisp itr map-resolver 10.10.10.10
! Import fabric prefixes into lisp map-cache from BGP!
switch(config-vrf)# ip lisp route-import map-cache bgp 65536 route-map RM_BGP_to_LISP
Verifying Map-cache with RIB Route Redistribution
The following example displays the sample show command outputs for the map-cache route import configurations:
xTR2# show ip lisp map-cache vrf VRF1
LISP IP Mapping Cache for VRF ”VRF1" (iid 100), 1 entries
* = Locator data counters are cumulative across all EID-prefixes
192.168.1.0/24, uptime: 00:09:42, expires: 0.000000, via route-import
Producer Set: 0004 route_import
Negative cache entry, action: send-map-request
Once a prefix is imported as a map-cache, the routing table shows how LISP takes over the prefix to ensure an optimized path
through the LISP overlay to the destination device.
xTR2# show ip route 192.168.2.2 vrf VRF1
IP Route Table for VRF ”VRF1"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>
192.168.1.0/24, ubest/mbest: 2/0 time
**via Null0, [10/1], 02:08:42, lisp, eid
via 10.10.10.3%default, [200/0], 01:06:55, bgp-65536, internal, tag 65536 (mpls-vpn)
Verify the EID instance address family configurations for the route-import map-cache application.
switch# show ip lisp route-import vrf VRF1 map-cache
IP LISP Route Import for VRF “VRF1"
MAP-CACHE
Specificatons : 1
Maximum Import : 1000
Threshold pct : 75%
Warn only : F
Withdraw : F
Routes Imported : 0
Rejected by limit : 0
Warned : 0
protocol : bgp-65536
policy : RM_BGP_to_LISP
bind_pending : F
type : Route Import Policy