LISP Delegated Database Tree (DDT) defines a large-scale distributed database of LISP Endpoint Identifier (EID) space using
a DDT node. A DDT node is configured to be authoritative for some specified portion of an overall LISP EID space, as well
as the set of more specific subprefixes that are delegated to other DDT nodes. It is also
configured with the set of more-specific sub-prefixes that are
further delegated to other DDT nodes. To delegate a sub-prefix, the
“parent” DDT node is configured with the Routing Locators (RLOCs) of each child DDT
node that is authoritative for the sub-prefix. Each RLOC either
points to a map server (sometimes termed a “terminal DDT node”) to
which an egress tunnel routers (ETRs) registers that sub-prefix or
points to another.
Restrictions for LISP Delegate Database Tree (DDT)
The following restriction applies to the LISP Delegate Database Tree (DDT) feature:
If LISP is enabled, nondisruptive upgrade (ISSU) and nondisruptive downgrade (ISSD) paths are not supported. Disable LISP
prior to any upgrade. This restriction only applies to releases before 6.2(2) but not to this release or to future LISP releases.
Configuring LISP Delegate Database Tree (DDT)
Command or Action
Switch# configure terminal
Enters global configuration mode.
Switch(config)# lisp ddt
Configures a switch to perform LISP DDT functionality.
Switch(config)# lisp ddt root 10.1.1.1
Configures an IPv4 or IPv6 locator for a DDT root node within the delegation hierarchy on a DDT-enabled map resolver.
In this example, a DDT-enabled map resolver is configured to refer to the DDT root node locator: 2001:db8:1::1111.
Displays the DDT referral cache stored in
map-resolvers. When the eid-address variable is specified each cache entry that is less
specific than the eid-address variable will be displayed.
Configuration Examples for LISP Delegate Database Tree (DDT)
Examples: LISP Delegate Database Tree (DDT)
The following is an example of parent and child DDT nodes, where
the parent has all of 10.0.0.0/8 and delegates two sub-prefixes,
10.0.0.0/12 and 10.0.16.0/12 to two child DDT nodes. All of these
prefixes are within the DDT sub-tree Key-ID=0, IID=223, and AFI=1
The following example defines the delegation of the EID-prefix 10.0.0.0/12
to a DDT Map Server with RLOC 192.168.1.100 and delegation of the
EID-prefix 10.16.0.0/12 to a DDT Map-Server with RLOC
192.168.1.200. The child DDT Map-Server for 10.16.0.0/12 is further
configured to allow ETRs to register the sub-prefixes 10.18.0.0/16