Prerequisites for LISP Instance-ID Support
Figure 4: LISP Deployment Environment
When you plan the deployment of a LISP virtualized network environment, you must plan for virtualization
at both the device level and the path level.
For path level virtualization: LISP binds virtual routing and forwarding (VRFs) to instance IDs (IIDs). These
IIDs are included in the LISP header to provide data plane (traffic flow) separation.
For device level virtualization: Both the EID and the RLOC namespaces can be virtualized. The EID can be
virtualized by binding a LISP instance ID to an EID VRF; the RLOC by tying locator addresses and associated
mapping services to the specific VRF within which they are reachable.
Prerequisites for LISP Instance-ID Support
• Allow the use of instance-id 0's within a virtual routing and forwarding (VRF) instance.
Guidelines and Limitations for LISP Instance-ID Support
The LISP Instance-ID Support feature has the following configuration guidelines and restrictions:
• If you enable LISP, nondisruptive upgrade (ISSU) and nondisruptive downgrade (ISSD) paths are not
Device Level Virtualization
Virtualization at the device level uses virtual routing and forwarding (VRF) to create multiple instances of
Layer 3 routing tables, as shown in the figure below. VRFs provide segmentation across IP addresses, allowing
for overlapped address space and traffic separation. Separate routing, quality of service (QoS), security, and
management policies can be applied to each VRF instance. An interior gateway protocol (IGP) or exterior
gateway protocol (EGP) routing process is typically enabled within a VRF, just as it would be in the global
(default) routing table. LISP binds VRFs to instance IDs for similar purposes.
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
34
supported. Disable LISP prior to any upgrade. This restriction applies only to releases before 6.2(2), not
to 6.2(2) or subsequent LISP releases.
LISP Instance-ID Support