nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

0
More-specific EID-prefix: 172.20.40.102/32, instance-id:
Currently registered: yes
First registered: 14:49:08
Last registered: 00:00:25
Who last registered: 10.2.2.2
Routing table tag:
0x00000000
Proxy Replying:
no
Wants Map-Notifications: yes
Registered TTL:
1440 minutes
Registered locators:
10.1.1.1 (up), priority: 1, weight: 50
10.1.1.2 (up), priority: 1, weight: 50
Registration errors:
Authentication failures: 0
Allowed locators mismatch: 0
LISP Deployment Best Practices
LISP Host Mobility with Extended Subnet is deployed at the L2/L3 boundary at the data
center aggregation layer on the Nexus 7000. The data center aggregation layer enables the
LISP xTR functionality to be deployed at the first Layer 3 gateway for the LISP Mobility
Extended Subnet. Some of the best practices for deploying LISP follows:
• Deploy the MS with redundancy, each having its own IP address.
• Deploy the MR with redundancy leveraging Anycast IP; this would provide for
redundancy and allow each ITR to reach the closest MR via the L3 IGP/BGP routing
domain.
• Deploy the MS/MR functions colocated on the same device; this allows each xTR to
register with both Map-Servers’ LISP EID namespace.
• OTV must run in a separate VDC to support SVIs for IP routing on extended VLANs.
• Enable LISP in the Aggregation VDC, separate from OTV, just like any other IP
routing service.
• The prefix length of the dynamic-eid mappings must always be larger (more specific)
than the prefix length of the global mappings defined on a given xTR.
• Only add to the mobility configuration those prefixes that require mobility.
• For LISP MR, use Anycast, iTRs Anycast Map Request.
• All services such as FWs, LBs, and DPI should be deployed south of the LISP xTRs;
services must receive nonencapsulated traffic.
• Design the core with symmetric ECMPs that allow fast failover convergence of the
RLOC space.
• The recommendation is to define a loopback interface on each device as the RLOC so
that communication to that IP address remains successful as long as a valid L3 path