Cisco Nexus 7000 Series User manual

Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
First Published: 2016-12-23
Last Modified: 2018-07-05
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright ©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1721R)
©2016–2018 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface ix
Audience ix
Document Conventions ix
Related Documentation x
Documentation Feedback xi
Obtaining Documentation and Submitting a Service Request xi
New and Changed Information 1
CHAPTER 1
New and Changed Information 1
Configuring Locator ID Separation Protocol 3
CHAPTER 2
Information About Locator/ID Separation Protocol 3
Information About LISP 3
LISP Devices Overview 4
LISP Site Devices 5
LISP Infrastructure 5
LISP Internetworking Devices 5
Licensing Requirements for LISP 6
LISP Guidelines and Limitations 6
Default Settings for LISP 6
Configuring Locator/ID Separation Protocol 7
Enabling the LISP Feature 7
Configuring LISP ITR/ETR (xTR) Functionality 7
Configuring LISP ITR/ETR (xTR) 7
Configuring Optional LISP ITR/ETR (xTR) Functionality 9
Configuring LISP-ALT Functionality 11
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
iii

Configuring Required LISP Map-Resolver Functionality 12
Configuring LISP Map-Server Functionality 12
Configuring Required LISP Map-Server Functionality 12
Configuring Optional LISP Map-Server Functionality 14
Configuring Required LISP Proxy-ITR Functionality 15
Configuring Required LISP Proxy-ETR Functionality 16
Additional References 16
Related Documents 16
Standards 17
MIBs 17
RFCs 17
Feature History for LISP 17
Configuring LISP ESM Multihop Mobility 19
CHAPTER 3
Finding Feature Information 19
Information About LISP ESM Multihop Mobility 20
Licensing Requirements for LISP 20
Guidelines and Limitations for LISP ESM Multihop Mobility 20
Default Settings for LISP 20
Configuring LISP ESM Multihop Mobility 21
Configuring the First-Hop Device 21
Configuring the Site Gateway xTR 23
Configuring xTR 24
Configuring the Map Server 25
Configuration Examples for LISP ESM Multihop Mobility 27
Example: First-Hop Router Configuration 28
Example: Site Gateway xTR Configuration 30
Example: xTR Configuration 30
Example: MSMR Configuration 31
Example: Multi-Hop Mobility Interworking with Routing Protocols Configuration 31
Additional References 31
Feature Information for LISP ESM Multihop Mobility 32
LISP Instance-ID Support 33
CHAPTER 4
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
iv
Contents

Information about LISP Instance-ID Support 33
Overview of LISP Instance ID 33
Prerequisites for LISP Instance-ID Support 34
Guidelines and Limitations for LISP Instance-ID Support 34
Device Level Virtualization 34
Path Level Virtualization 35
LISP Virtualization at the Device Level 35
Default (Non-Virtualized) LISP Model 36
LISP Shared Model Virtualization 36
LISP Shared Model Virtualization Architecture 37
LISP Shared Model Virtualization Implementation Considerations and Caveats 38
LISP Parallel Model Virtualization 38
LISP Parallel Model Virtualization Architecture 39
LISP Parallel Model Virtualization Implementation Considerations and Caveats 40
How to Configure LISP Instance-ID Support 41
Configuring Simple LISP Shared Model Virtualization 41
Configuring a Private LISP Mapping System for LISP Shared Model Virtualization 47
Configuring Large-Scale LISP Shared Model Virtualization 50
Configuring a Remote Site for Large-Scale LISP Shared Model Virtualization 57
Configuring Simple LISP Parallel Model Virtualization 63
Configuring a Private LISP Mapping System for LISP Parallel Model Virtualization 69
Configuration Examples for LISP Instance-ID Support 72
Example: Configuring Simple LISP Shared Model Virtualization 72
Example: Configuring a Private LISP Mapping System for LISP Shared Model Virtualization 74
Example: Configuring Large-Scale LISP Shared Model Virtualization 75
Example: Configuring a Remote Site for Large-Scale LISP Shared Model Virtualization 77
Example: Configuring Simple LISP Parallel Model Virtualization 78
Example: Configuring a Private LISP Mapping System for LISP Parallel Model Virtualization 80
Feature_History_for_Configuring LISP_Instance_ID 81
Configuring LISP Delegate Database Tree (DDT) 83
CHAPTER 5
LISP Delegate Database Tree (DDT) 83
Overview of DDT 83
Restrictions for LISP Delegate Database Tree (DDT) 83
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
v
Contents

Configuring LISP Delegate Database Tree (DDT) 84
Configuration Examples for LISP Delegate Database Tree (DDT) 85
Examples: LISP Delegate Database Tree (DDT) 85
Feature History for LISP Delegate Database Tree 86
Configuring LISP Multicast 87
CHAPTER 6
LISP Multicast 87
Finding Feature Information 87
Restrictions for LISP Multicast 88
Configuring LISP Multicast 88
Configuration Example for LISP Multicast 90
Example: Configuring LISP Multicast 90
Feature History for LISP Multicast 91
LISP Support for Disjointed RLOC Domains 93
CHAPTER 7
LISP Support for Disjointed RLOC Domains 93
Overview of LISP Support for Disjointed RLOC Domains 93
Prerequisites for LISP Support for Disjointed RLOC Domains 93
Information About LISP Support for Disjointed RLOC Domains 93
How to Configure LISP Support for Disjointed RLOC Domains 96
Verifying LISP Support for Disjointed RLOC Domains 99
Feature History for LISP Support for Disjointed RLOC Domains 101
Configuring LISP Extranets 103
CHAPTER 8
Finding Feature Information 103
Feature History for LISP Extranets 103
Information About LISP Extranets 103
Use Case for LISP Extranets 104
Use Case for LISP Local Extranet Policies 106
Licensing Requirements for LISP 106
Guidelines and Limitations for LISP Extranets 106
Configuring LISP Extranets 107
Configuring LISP Map Server with Extranet Policies 107
Configuring LISP xTR functionality for Extranet Policies 109
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
vi
Contents

Verifying LISP Extranets 110
Configuring Local LISP Extranets 111
Verifying LISP Local Extranets 113
Redistribution of RIB Routes into LISP 115
CHAPTER 9
Finding Feature Information 115
Feature History for Redistribution of RIB Routes into LISP 115
Information About Redistribution of RIB Routes into LISP 115
Configuring Database Application for Redistribution of RIB Routes into LISP 116
Configuring Map-cache Application for Redistribution of RIB Routes into LISP 117
Example: Redistribution of RIB Routes in LISP 119
Configuration Limits for LISP 125
CHAPTER 10
Configuration Limits for LISP 125
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
vii
Contents

Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
viii
Contents

Preface
This preface describes the audience, organization, and conventions of the Book Title. It also provides
information on how to obtain related documentation.
This chapter includes the following topics:
Audience
This publication is for experienced network administrators who configure and maintain Cisco NX-OS on
Cisco Nexus 7000 Series Platform switches.
Document Conventions
• As part of our constant endeavor to remodel our documents to meet our customers' requirements, we
have modified the manner in which we document configuration tasks. As a result of this, you may find
a deviation in the style used to describe these tasks, with the newly included sections of the document
following the new format.
• The Guidelines and Limitations section contains general guidelines and limitations that are applicable
to all the features, and the feature-specific guidelines and limitations that are applicable only to the
corresponding feature.
Note
Command descriptions use the following conventions:
DescriptionConvention
Bold text indicates the commands and keywords that you enter literally
as shown.
bold
Italic text indicates arguments for which the user supplies the values.
Italic
Square brackets enclose an optional element (keyword or argument).[x]
Square brackets enclosing keywords or arguments separated by a vertical
bar indicate an optional choice.
[x | y]
Braces enclosing keywords or arguments separated by a vertical bar
indicate a required choice.
{x | y}
Nested set of square brackets or braces indicate optional or required
choices within optional or required elements. Braces and a vertical bar
within square brackets indicate a required choice within an optional
element.
[x {y | z}]
Indicates a variable for which you supply values, in context where italics
cannot be used.
variable
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
ix

DescriptionConvention
A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
string
Examples use the following conventions:
DescriptionConvention
Terminal sessions and information the switch displays are in screen font.screen font
Information you must enter is in boldface screen font.boldface screen font
Arguments for which you supply values are in italic screen font.
italic screen font
Nonprinting characters, such as passwords, are in angle brackets.< >
Default responses to system prompts are in square brackets.[ ]
An exclamation point (!) or a pound sign (#) at the beginning of a line
of code indicates a comment line.
!, #
This document uses the following conventions:
Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
Note
Means reader be careful. In this situation, you might do something that could result in equipment damage or
loss of data.
Caution
Related Documentation
Documentation for Cisco Nexus 7000 Series Switches is available at:
• Configuration Guides
http://www.cisco.com/c/en/us/support/switches/nexus-7000-series-switches/
products-installation-and-configuration-guides-list.html
• Command Reference Guides
http://www.cisco.com/c/en/us/support/switches/nexus-7000-series-switches/
products-command-reference-list.html
• Release Notes
http://www.cisco.com/c/en/us/support/switches/nexus-7000-series-switches/products-release-notes-list.html
• Install and Upgrade Guides
http://www.cisco.com/c/en/us/support/switches/nexus-7000-series-switches/
products-installation-guides-list.html
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
x
Preface
Related Documentation

• Licensing Guide
http://www.cisco.com/c/en/us/support/switches/nexus-7000-series-switches/
products-licensing-information-listing.html
Documentation for Cisco Nexus 7000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is
available at the following URL:
http://www.cisco.com/c/en/us/support/switches/nexus-2000-series-fabric-extenders/
products-installation-and-configuration-guides-list.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service
request, and gathering additional information, see What's New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the . RSS
feeds are a free service.
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
xi
Preface
Documentation Feedback

Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
xii
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
New and Changed Information
•New and Changed Information, on page 1
New and Changed Information
The table below summarizes the new and changed features for this document and shows the releases in which
each feature is supported. Your software release might not support all the features in this document. 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.
Table 1: New and Changed Information
Where DocumentedChanged in ReleaseDescriptionFeature
Configuring LISP
Extranets, on page 103
8.3(1)This feature was
introduced.
LISP Extranets
Redistribution of RIB
Routes into LISP, on page
115
8.3(1)This feature was
introduced.
Redistribution of RIB
Routes into LISP
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
1

Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
2
New and Changed Information
New and Changed Information

CHAPTER 2
Configuring Locator ID Separation Protocol
This chapter describes how to configure the basic Cisco NX-OS Locator/ID Separation Protocol (LISP)
functionality on all LISP-related devices, including the Ingress Tunnel Router (ITR), Egress Tunnel Router,
Proxy ITR (PITR), Proxy ETR (PETR), Map Resolver (MR), Map Server (MS), and LISP-ALT device.
This chapter contains the following sections:
•Information About Locator/ID Separation Protocol, on page 3
•Information About LISP, on page 3
•LISP Devices Overview, on page 4
•Licensing Requirements for LISP, on page 6
•LISP Guidelines and Limitations, on page 6
•Default Settings for LISP, on page 6
•Configuring Locator/ID Separation Protocol, on page 7
•Additional References, on page 16
•Feature History for LISP, on page 17
Information About Locator/ID Separation Protocol
The Locator/ID Separation Protocol (LISP) network architecture and protocol implements a new semantic
for IP addressing by creating two new namespaces: Endpoint Identifiers (EIDs), which are assigned to end
hosts, and Routing Locators (RLOCs), which are assigned to devices (primarily routers) that make up the
global routing system. Splitting EID and RLOC functions improves routing system scalability, multihoming
efficiency, and ingress traffic engineering. LISP end site support is configured on devices such as Cisco
routers.
Information About LISP
In the current Internet routing and addressing architecture, the IP address is used as a single namespace that
simultaneously expresses two functions about a device: its identity and how it is attached to the network. One
very visible and detrimental result of this single namespace is demonstrated by the rapid growth of the Internet's
default-free zone (DFZ) as a consequence of multi-homing, traffic engineering (TE), nonaggregatable address
allocations, and business events such as mergers and acquisitions.
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
3

LISP changes current IP address semantics by creating two new namespaces: Endpoint Identifiers (EIDs) that
are assigned to end-hosts and Routing Locators (RLOCs) that are assigned to devices (primarily routers) that
make up the global routing system. These two namespaces provide the following advantages:
• Improved routing system scalability by using topologically aggregated RLOCs
• Provider independence for devices numbered out of the EID space
• Multihoming of endsites with improved traffic engineering
• IPv6 transition functionality
LISP is deployed primarily in network edge devices. It requires no changes to host stacks, Domain Name
Service (DNS), or local network infrastructure, and little to no major changes to existing network infrastructures.
Figure 1: Cisco NX-OS LISP Deployment Environment
This figure shows a LISP deployment environment. Three essential environments exist in a LISP environment:
LISP sites (EID namespace), non-LISP sites (RLOC namespace), and LISP Mapping Service (infrastructure).
The LISP EID namespace represents customer end sites as they are defined today. The only difference is that
the IP addresses used within these LISP sites are not advertised within the non-LISP, Internet (RLOC
namespace). End customer LISP functionality is deployed exclusively on CE routers that function within
LISP as Ingress Tunnel Router (ITR) and Egress Tunnel Router (ETR) devices.
The ITR and ETR are abbreviated as xTR in the figure.
Note
To fully implement LISP with support for Mapping Services and Internet interworking, you might need to
deploy additional LISP infrastructure components such as Map Server (MS), Map Resolver (MR), Proxy
Ingress Tunnel Router (PITR), Proxy Egress Tunnel Router (PETR), and Alternative Topology (ALT).
LISP Devices Overview
The following devices are found in a full LISP deployment:
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
4
Configuring Locator ID Separation Protocol
LISP Devices Overview

LISP Site Devices
The LISP site devices are as follows:
Ingress Tunnel Router (ITR)—This device is deployed as a LISP site edge device. It receives packets from
site-facing interfaces (internal hosts) and either LISP encapsulates packets to remote LISP sites or the ITR
natively forwards packets to non-LISP sites.
Egress Tunnel Router (ETR)—This device is deployed as a LISP site edge device. It receives packets from
core-facing interfaces (the Internet) and either decapsulates LISP packets or delivers them to local EIDs at
the site.
Customer Edge (CE) devices can implement both ITR and ETR functions. This type of CE device is referred
to as an xTR. The LISP specification does not require a device to perform both ITR and ETR functions,
however.
For both devices, the EID namespace is used inside the sites for end-site addresses for hosts and routers. The
EIDs go in DNS records. The EID namespace is not globally routed in the underlying Internet. The RLOC
namespace is used in the (Internet) core. RLOCs are used as infrastructure addresses for LISP routers and ISP
routers and are globally routed in the underlying infrastructure. Hosts do not know about RLOCs, and RLOCs
do not know about hosts.
Note
LISP Infrastructure
The LISP infrastructure devices are as follows:
Map Server (MS)—This device is deployed as a LISP Infrastructure component. It must be configured to
permit a LISP site to register to it by specifying for each LISP site the EID prefixes for which registering
ETRs are authoritative. An authentication key must match the key that is configured on the ETR. An MS
receives Map-Register control packets from ETRs. When the MS is configured with a service interface to the
LISP ALT, it injects aggregates for the EID prefixes for registered ETRs into the ALT. The MS also receives
Map-Request control packets from the ALT, which it then encapsulates to the registered ETR that is authoritative
for the EID prefix being queried.
Map Resolver (MR)—This device is deployed as a LISP Infrastructure device. It receives Map-Requests
encapsulated to it from ITRs. When configured with a service interface to the LISP ALT, the MR forwards
Map Requests to the ALT. The MR also sends Negative Map-Replies to ITRs in response to queries for
non-LISP addresses.
Alternative Topology (ALT)—This is a logical topology and is deployed as part of the LISP Infrastructure
to provide scalable EID prefix aggregation. Because the ALT is deployed as a dual-stack (IPv4 and IPv6)
Border Gateway Protocol (BGP) over Generic Routing Encapsulation (GRE) tunnels, you can use ALT-only
devices with basic router hardware or other off-the-shelf devices that can support BGP and GRE.
LISP Internetworking Devices
The LISP internetworking devices are as follows:
Proxy ITR (PITR)—This device is a LISP infrastructure device that provides connectivity between non-LISP
sites and LISP sites. A PITR advertises coarse-aggregate prefixes for the LISP EID namespace into the Internet,
which attracts non-LISP traffic destined to LISP sites. The PITR then encapsulates and forwards this traffic
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
5
Configuring Locator ID Separation Protocol
LISP Site Devices

to LISP sites. This process not only facilitates LISP/non-LISP internetworking but also allows LISP sites to
see LISP ingress traffic engineering benefits from non-LISP traffic.
Proxy ETR (PETR)—This device is a LISP infrastructure device that allows IPv6 LISP sites without native
IPv6 RLOC connectivity to reach LISP sites that only have IPv6 RLOC connectivity. In addition, the PETR
can also be used to allow LISP sites with Unicast Reverse Path Forwarding (URPF) restrictions to reach
non-LISP sites.
Licensing Requirements for LISP
The following table shows the LISP licensing requirements:
License RequirementProduct
This feature requires the LAN_ENTERPRISE_SERVICES_PKG license. For a complete
explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.
Cisco NX-OS
LISP Guidelines and Limitations
LISP has the following configuration guidelines and limitations:
•LISP requires the Cisco Nexus 7000 Series 32-Port, 10 Gigabit Ethernet (M1) module (N7K-M132XP-12
or N7K-M132XP-12L), with Electronic Programmable Logic Device (EPLD) version 186.008 or later.
• Use an Overlay Transport Virtualization (OTV) or another LAN extension mechanism to filter the HSRP
hello messages across the data centers to create an active-active HSRP setup and provide egress path
optimization for the data center hosts.
• Make sure that the HSRP group and the HSRP Virtual IP address in all data centers in the extended LAN
are the same. Keeping the HSRP group number consistent across locations guarantees that the same
MAC address is always used for the virtual first-hop gateway.
• LISP VM mobility across subnets requires that the same MAC address is configured across all HSRP
groups that allow dynamic EIDs to roam. You must enable the Proxy Address Resolution Protocol (ARP)
for the interfaces that have VM mobility enabled across subnets.
• LISP is not supported for F2 Series modules.
• From Release 8.2(1), LISP is supported on F3 and M3 line cards.
Default Settings for LISP
This table lists the default settings for LISP parameters.
Table 2: LISP Default Settings
DefaultParameters
Disabledfeature lisp command
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
6
Configuring Locator ID Separation Protocol
Licensing Requirements for LISP

Configuring Locator/ID Separation Protocol
Enabling the LISP Feature
You can enable the LISP feature on the Cisco NX-OS device.
Procedure
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Step 1
switch# configure terminal
switch(config)#
Enables the LISP feature set if it is not already
configured.
feature lisp
Example:
Step 2
switch(config)# feature lisp
Configuring LISP ITR/ETR (xTR) Functionality
Configuring LISP ITR/ETR (xTR)
You can enable and configure a LISP xTR with a LISP Map-Server and Map-Resolver for mapping services
for both IPv4 and IPv6 address families.
Procedure
PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Step 1
switch# configure terminal
switch(config)#
Enables LISP ITR functionality.{ip |ipv6}lisp itr
Example:
Step 2
switch(config)# ip lisp itr
Example:
switch(config)# ipv6 lisp itr
Enables LISP ETR functionality.{ip |ipv6}lisp etr
Example:
Step 3
switch(config)# ip lisp etr
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
7
Configuring Locator ID Separation Protocol
Configuring Locator/ID Separation Protocol

PurposeCommand or Action
Example:
switch(config)# ipv6 lisp etr
Enables both the LISP ITR and the LISP ETR
functionality. When both ITR and ETR
(Optional) {ip |ipv6}lisp itr-etr
Example:
Step 4
functionality is being enabled on the same
switch(config)# ip lisp itr-etr device, the configuration can be simplified by
using this command instead of the {ip |
Example:
ipv6}lisp itr and {ip |ipv6}lisp etr
commands separately.
switch(config)# ipv6 lisp itr-etr
Configures the locator address of the
Map-Resolver to which this router sends
Map-Request messages for IPv4 or IPv6 EIDs.
{ip |ipv6}lisp itr map-resolver
map-resolver-address
Example:
Step 5
The locator address of the
Map-Resolver can be an IPv4 or
IPv6 address. See the Cisco Nexus
7000 Series NX-OS LISP Command
Reference for more details.
Note
switch(config)# ip lisp itr map-resolver
10.10.10.1
Example:
switch(config)# ipv6 lisp itr
map-resolver 10.10.10.1
Configures an EID-to-RLOC mapping
relationship and associated traffic policy for all
IPv4 or IPv6 EID prefix(es) for this LISP site.
{ip |ipv6}database-mapping
EID-prefix/prefixlength locator priority priority
weight weight
Step 6
Example: If the site has multiple locators
associated with the same EID-prefix
block, enter multiple ip lisp
database-mapping commands to
configure all of the locators for a
given EID-prefix block.
If the site is assigned multiple
EID-prefix blocks, enter the ip lisp
database-mapping command for
each EID-prefix block assigned to
the site and for each locator by
which the EID-prefix block is
reachable.
If the site has multiple ETRs, you
must configure all ETRs with the ip
lisp database-mapping and ipv6
lisp database-mapping commands
ensuring the options used are
consistent.
Note
switch(config)# ip lisp database-mapping
10.10.10.0/24
172.16.1.1 priority 1 weight 100
Example:
switch(config)# ipv6 lisp
database-mapping
2001:db8:bb::/48 172.16.1.1 priority 1
weight 100
Configures the locator address of the LISP
Map-Server to which this router, acting as an
IPv4 or IPv6 LISP ETR, registers.
{ip |ipv6}lisp etr map-server
map-server-address key key-type
authentication-key
Step 7
Example:
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
8
Configuring Locator ID Separation Protocol
Configuring LISP ITR/ETR (xTR)