When a LISP ETR registers with a map server, it sends a map-register message that contains, among other things, one or more EID prefixes that the ETR is configured to use. On the ETR, EID prefixes are configured using the
database-mapping command. To configure these EID prefixes on the map server, use the
eid-prefix command in LISP site configuration mode.
The same EID prefixes must be configured on the map server and the ETR in order for the ETR to be registered, and for these EID prefixes to be advertised by LISP. After verifying the authentication data, the map server compares the EID prefixes within the map-register message against those configured on the map server for the LISP site. If they agree, the map register 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 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, its attributes can be displayed by the
site command. If the map-registration process is unsuccessful, the site will not be displayed.
route-tag keyword is used, a tag value is associated with the EID prefix being configured. This tag value may be useful for simplifying processes that populate the routing information base (RIB). For example, a route-map policy can be defined 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 Alternative Logical Topology (ALT).