Verifying Lisp Support For Disjointed Rloc Domains - Cisco Nexus 7000 Series Configuration Manual

LISP Support for Disjointed RLOC Domains
Step 4 The configurations are relevant for RTR or PxTR 1. Similarly, configure the RTR or PxTR 2
device too.
Map-Server Configuration
Note
• The Map-Server disjointed RLOC logic is triggered by the existence of locator scope sets. Locator scope
• A device with IOS XE software is used for the role of Map-Server, and not a Cisco Nexus 7000 Series
Map-Server configuration on a device with IOS XE software (not Cisco Nexus 7000 Series device):
(config)# router lisp

Verifying LISP Support for Disjointed RLOC Domains

Testing Reachability from xTR 1 in Site A to the xTR in Site B
In the following example, locator information for both sites (192.0.2.1 in site A and 203.0.113.15 in site B)
are displayed. xTR 1 in site A is connected to the xTR in site B.
siteA-xTR1# lig 198.51.100.10 instance-id 5000
Mapping information for EID 198.51.100.10 from 192.0.2.9/32 with RTT 2 msecs
198.51.100.10/32, uptime: 00:07:06, expires: 00:14:59, via map-reply, complete
Locator
192.0.2.1
203.0.113.15
sets should be configured for the Map-Server to consider disjointed RLOCs in its Map-Request handling
logic.
device. The Map-Server configuration is documented for reference and completeness. For information,
see IP Routing: LISP Configuration Guide, Cisco IOS XE Release 3S.
locator-table vrf core
locator-set SITEAB
192.0.2.1 priority 1 weight 50
203.0.113.15 priority 1 weight 50
exit
locator-scope site-B
rtr-locator-set SITEAB
rloc-prefix 203.0.113.40/32
rloc-prefix 192.0.2.21/32
rloc-prefix 203.0.113.25/32
exit
locator-scope site-A
rtr-locator-set SITEAB
rloc-prefix 192.0.2.5/32
rloc-prefix 192.0.2.6/32
rloc-prefix 203.0.113.17/32
rloc-prefix 192.0.2.10/32
Uptime State
00:07:06 up
00:07:06 up
Pri/Wgt
1/50
1/50
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
Map-Server Configuration
99