Cisco Nexus 7000 Series Configuration Manual page 79

LISP Instance-ID Support
Step 15
Command or Action
ipv6 route vrf rloc-vrf-name ipv6-prefix
next-hop
Example:
switch(config)# ipv6 route vrf BLUE ::/0
Null0
Configuring Simple LISP Parallel Model Virtualization
Purpose
• natively forwarded when traffic is
LISP-to-non-LISP
Packets are deemed to be a candidate for LISP
encapsulation when they are sourced from a
LISP EID and the destination matches one of
the following entries:
• a current map-cache entry
• a default route with a legitimate next-hop
• a static route to Null0
• no route at all
In this configuration example, because the xTR
has IPv4 RLOC connectivity, a default route
to the upstream SP is used for all IPv4 packets
to support LISP processing.
Configures a default route to the upstream next
hop for all IPv6 destinations, reachable within
the specified RLOC VRF.
All IPv6 EID-sourced packets destined for both
LISP and non-LISP sites require LISP support
for forwarding in the following two ways:
• LISP-encapsulated to a LISP site when
traffic is LISP-to-LISP
• natively forwarded when traffic is
LISP-to-non-LISP
Packets are deemed to be a candidate for LISP
encapsulation when they are sourced from a
LISP EID and the destination matches one of
the following entries:
• a current map-cache entry
• a default route with a legitimate next-hop
• a static route to Null0
• no route at all
In this configuration example, because the xTR
has only IPv4 RLOC connectivity, adding an
IPv6 default route to Null0 ensures that all
IPv6 packets are handled by LISP processing.
If the destination is another LISP site, packets
are LISP-encapsulated (using IPv4 RLOCs)
to the remote site. If the destination is
non-LISP, all IPv6 EIDs are
LISP-encapsulated to a Proxy ETR (PETR)
–assuming one is configured.
Cisco Nexus 7000 Series NX-OS LISP Configuration Guide
67