Cisco Nexus 7000 Series Command Reference Manual page 32

Cisco Nexus 7000 Series LISP Commands
eid-prefix
S e n d d o c u m e n t c o m m e n t s t o n e x u s 7 k - d o c f e e d b a c k @ c i s c o . c o m .
is accepted and the ETR registration is completed. If the EID-prefixes in the Map Register message do
not match those configured on the Map Server, the Map-Register message is not accepted and the ETR
is not registered.
A Map-Register message sent by an ETR contains all of the EID prefixes that the ETR is authoritative
Note
for. All of these EID prefixes must be listed on the Map Server within the lisp site configuration for the
Map-Register message sent by the ETR to be accepted. If the list in the Map-Register does not match
the one configured on the Map Server, the Map-Register message is not accepted and the ETR is not
registered.
When a LISP site successfully completes the Map-Registration process, you can display its attributes by
using the show lisp site command. If the Map-Registration process is unsuccessful, the site does not
display.
When you use the route-tag keyword, a tag value is associated with the EID-prefix that is being
configured. This tag value is useful for simplifying processes that populate the URIB or U6RIB alt-vrf.
For example, you can define a route-map policy to match this tag for Border Gateway Protocol (BGP)
redistribution of these EID-prefixes into the virtual routing and forwarding (VRF) used by the
LISP-ALT.
When you use the accept-more-specifics keyword, any EID-prefix that is more specific then the
EID-prefix configured is accepted and tracked. The accept-more-specifics keyword is intended for
LISP VM Mobility (dynamic-EID roaming). When a dynamic-EID moves from one LISP-VM switch to
another, the registration of the dynamic-EID to a new locator is performed to the Map Server. Using this
keyword avoids the need to configure an EID-prefix for each dynamic-EID that is capable of roaming.
This command does not require a license.
This example shows how to configure the IPv4 EID-prefix 192.168.1.0/24 and the IPv6 EID-prefix
Examples
2001:db8:aa::/48, each with the route-tag 123, for the LISP site Customer-1:
switch# configuration terminal
switch(config)# lisp site Customer-1
switch(config-lisp-site)# eid-prefix 192.168.1.0/24 route-tag 123
switch(config-lisp-site)# eid-prefix 2001:db8:aa::/48 route-tag 123
This example shows how to configure the IPv4 EID-prefix 192.168.2.0/24 for the LISP site Roamer-1
and adds the accept-more-specific keyword. In this case, the host-prefix 192.68.2.12/32, could register
according to this configuration:
switch# configuration terminal
switch(config)# lisp site Roamer-1
switch(config-lisp-site)# eid-prefix 192.168.2.0/24 accept-more-specifics
This example shows how to configure the IPv4 EID-prefix 192.168.1.0/24 with the instance ID of 123
for the LISP site Customer-2:
switch# configuration terminal
switch(config)# lisp site Customer-2
switch(config-lisp-site)# eid-prefix instance-id 123 192.168.1.0/24 route-tag 123
Cisco Nexus 7000 Series NX-OS LISP Command Reference
LSP-22