Configuration

LISP routing is configured in LANconfig under Routing protocols > LISP. The switch Locator/ID separation protocol (LISP) activated is used to switch this routing protocol on or off.





Disable TTL propagation
When enabled, the ITR does not copy the Time-To-Live (TTL) from the outer to the inner header. As a result, a client running traceroute sees the LISP tunnel as a hop. If disabled, traceroute shows all of the hops between ITR and ETR.
Map-Cache-Limit
Defines the maximum number of map-cache entries across all LISP instances. After reaching the limit, new entries are rejected. Only after older entries in the map cache have become invalid will new entries be accepted. 0 means there is no restriction.

LISP instances

This table contains the global configuration of the LISP instances on the device.





Name
Specifies a unique name for a LISP instance. This name is referenced in other LISP tables.
Entry active
Activates or deactivates this LISP instance.
EID routing tag
Routing tag of the endpoint identifier (EID) of this instance.
RLOC routing tag
Routing tag of the routing locator (RLOC) of this instance.
Instance ID
LISP instance ID as a numeric tag from RFC 8060 (LISP Canonical Address Format (LCAF)) for the segmentation of networks with ARF.
Probing method
Specifies the method used to periodically check the accessibility of the RLOCs for map cache entries. Available methods:
  • Off: The availability of the RLOCs is not checked periodically.
  • RLOC probing: The availability of the RLOCs is periodically checked by LISP RLOC messages.
IPv6
Name of the IPv6 WAN profile from the IPv6 WAN interface table. An entry is required if IPv6 EIDs are used.
Administrative distance
The administrative distance of this LISP instance.

EID mapping

This table specifies the mapping of EIDs to RLOCs to be registered with the map server.





Name
References the name of the LISP instance.
Operating
Activates or deactivates this EID mapping.
EID address type
Protocol version of the EID prefix when referencing the EID prefix via an interface or network name. Possible values:
  • IPv4: Only the IPv4 prefix of the referenced interface is used.
  • IPv6: Only the IPv6 prefix of the referenced interface is used.
  • IPv4+IPv6: Both the IPv4 prefix and the IPv6 prefix of the referenced interface are used.
EID prefix
EID prefix of the EID mapping. Possible values are an IPv4 network name or an IPv6 interface, e.g. INTRANET, or a named loopback address.
Locator address type
Protocol version of the RLOC when referencing the EID prefix via an interface name. Possible values:
  • IPv4: Only the IPv4 address is used as the RLOC of the referenced interface.
  • IPv6: Only the IPv6 address is used as the RLOC of the referenced interface.
  • IPv4+IPv6: Both the IPv4 address and the IPv6 address are used as the RLOC of the referenced interface.
Locator
RLOC of the EID mapping. Possible values are named remote sites, IPv6 WAN interfaces, or loopback interfaces.
Priority
The priority of the EID mapping. Default: 1.
Weight
The weight of the EID mapping. Default: 100.
Comment
Enter a descriptive comment for this entry.

ETR settings

This table specifies the parameters for the role as Egress Tunnel Router (ETR).





Name
References the name of the LISP instance.
Operating
Activates or deactivates these ETR settings.
Map-Server
IPv4 or IPv6 address of the LISP map server
Map-Server-Backup
IPv4 or IPv6 address of the LISP backup map server. The LISP registration is sent in parallel both to the primary map server and to the backup map server.
Routing tag
Routing tag to be used to access the map server.
Source address (opt.)
Contains the sender address as the named interface that is used with the map server in LISP communication.
Map-Cache-TTL
Time-to-live of the EID mappings in minutes registered with the map server.
Map register interval
Registration interval in seconds in which map registrations are sent to the map server.
Key type
Algorithm used for authentication at the map server. Possible values:
  • None
  • HMAC-SHA-1-96
  • HMAC-SHA-256-128
Key
Key or password used to register the EID mapping on the map server.
Proxy-Reply
Determines whether the proxy reply bit is set in map registrations. In this case, the map server acts as a proxy and responds to map requests on behalf of the ETR.

ITR settings

This table specifies the parameters for the role as Ingress Tunnel Router (ITR).





Name
References the name of the LISP instance.
Operating
Activates or deactivates these ITR settings.
Map-Resolver
IPv4 or IPv6 address of the LISP map resolver.
Routing tag
Routing tag used to access the map resolver.
Source address (opt.)
Contains the sender address as the named interface that is used with the map resolver in LISP communication.
Map-Resolver-Retries
Number of retries for map requests to the map resolver. Default: 3
Map-Request-Route-IPv4
Specifies the IPv4 route or prefix for the LISP map requests.
Map-Request-Route-IPv6
Specifies the IPv6 route or prefix for the LISP map requests.

Route redistribution

The redistribution of routes allows routes from the routing table to be imported into the LISP map cache. Map requests are performed for these routes.

Route redistribution also allows routes to be imported from the routing table and dynamically registered to the map server as an EID prefix.





Name
References the name of the LISP instance.
Route redistribute
Specifies the route sources of the imported routes.
  • Static: The device imports static routes from the routing table into the LISP map cache or into the EID table as an EID prefix.
  • Connected: From directly connected networks, the device imports information from the routing table into the LISP map cache or into the EID table as an EID prefix.
  • OSPF: The device imports OSPF routes from the routing table into the LISP map cache or into the EID table as an EID prefix.
  • BGP: The device imports BGP routes from the routing table into the LISP map cache or into the EID table as an EID prefix.
Destination
Specifies the destination of routes imported to LISP. Possible values:
  • Map cache: Imports the routes into the map cache. LISP performs map requests for these routes.
  • EID table: Import the routes into the LISP EID table. These routes are registered with the map server as an EID prefix with the configured RLOC.
Locator address type
Protocol version of the RLOC when referencing the EID prefix via an interface name. Possible values:
  • IPv4: Only the IPv4 address is used as the RLOC of the referenced interface.
  • IPv6: Only the IPv6 address is used as the RLOC of the referenced interface.
  • IPv4+IPv6: Both the IPv4 address and the IPv6 address are used as the RLOC of the referenced interface.
Locator
Specifies the RLOC used to register the imported EID prefixes with the map server. Possible values are named remote sites, IPv6 WAN interfaces, or loopback interfaces.
Priority
The priority. Default: 1
Weight
The weight. Default: 100

Native forward

If LISP networks are to communicate with non-LISP networks, proxy routers can be used. These roles are referred to as proxy ingress tunnel routers (proxy ITRs) and proxy egress tunnel routers (proxy ETRs).

If a LISP router receives a negative response from the map resolver, i.e. there is no mapping between the requested EID and an RLOC, the LISP router can either send the associated packets to a proxy xTR (packet with LISP header) or send it via another local interface (packet without LISP header).

LCOS only supports scenarios where PITR and PETR functions are operated on the same router.





Name
References the name of the LISP instance.
Type
Defines how to send packets to non-LISP networks.
  • None: Packets to non-LISP networks are not forwarded but dropped
  • Proxy XTR: Packets to non-LISP networks are sent to a ProxyXTR
  • Interface: Packets to non-LISP networks are sent via a local interface
Proxy XTR
IPv4 or IPv6 address of the proxy XTR used to send packets to non-LISP networks.
Interface
Name of the interface used to send packets to non-LISP networks.

www.lancom-systems.com

LANCOM Systems GmbH | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E-Mail info@lancom.de

LANCOM Logo