LISP catch-all entry

Andrii Oliinyk — Tue, 19 Dec 2023 10:53:11 GMT

yeah... i have 2 sites each with 2 BNs & certain number of ENs. lisp configurations are mainly identical (obviously RLOC data is different). Now when i'm looking on the Subject on each Site i can see different output (not sure what inherits what there). Anyone can explain to me this difference?

SITE1EN0002#sho lisp instance-id 4099 ipv4 map-cache detail
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf OFFICE_VN (IID 4099), 7 entries
0.0.0.0/0, uptime: 15:21:15, expires: 00:11:29, via map-reply, unknown-eid-forward
Sources: map-reply, static-send-map-request
State: unknown-eid-forward, last modified: 15:21:15, map-source: 10.200.120.242
Exempt, Packets out: 1143(451439 bytes), counters are not accurate (~ 00:24:33 ago)
Configured as EID address space
action: send-map-request + Encapsulating to proxy ETR
PETR Uptime State Pri/Wgt Encap-IID Domain-ID/MH-ID Metric
10.200.120.241 15:21:15 up 10/10 - 2128425366/12694 0
10.200.120.242 15:21:15 up 10/10 - 2128425366/12694 0

SITE2EN0002#sho lisp instance-id 4099 ipv4 map de
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf OFFICE_VN (IID 4099), 21 entries
0.0.0.0/0, uptime: 00:00:57, expires: 00:00:02, via static-send-map-request
Sources: static-send-map-request
State: send-map-request, last modified: 10w4d, map-source: local
Exempt, Packets out: 28139(15246720 bytes), counters are not accurate (~ 00:07:25 ago)
Configured as EID address space
Negative cache entry, action: send-map-request

SITE1EN0002#show ip cef vrf OFFICE_VN 0.0.0.0/0 detail
0.0.0.0/0, epoch 1, flags [cover dependents, subtree context, check lisp eligibility, default route], per-destination sharing
SC owned,sourced: LISP remote EID - locator status bits 0x00000000
LISP remote EID: 1143 packets 451439 bytes fwd action signal-fwd, cfg as EID space
LISP source path list
nexthop 10.200.120.241 LISP0.4099
nexthop 10.200.120.242 LISP0.4099
Covered dependent prefixes: 6
notify cover updated: 6
2 IPL sources [no flags]
nexthop 10.200.120.241 LISP0.4099
nexthop 10.200.120.242 LISP0.4099

SITE2EN0002#show ip cef vrf OFFICE_VN 0.0.0.0/0 detail
0.0.0.0/0, epoch 0, flags [cover dependents, check lisp eligibility, default route]
LISP remote EID: 28139 packets 15246720 bytes fwd action signal, cfg as EID space
LISP source path list
attached to LISP0.4099
Covered dependent prefixes: 17
notify cover updated: 17
1 IPL source [no flags]
attached to LISP0.4099

Re: LISP catch-all entry

jalejand — Thu, 04 Jan 2024 08:40:36 GMT

The 1st entry already triggered resolution, the second one hasn't.

A resolved 0.0.0.0/0 map cache in pubsub:

Edge2#show lisp ins 4099 ipv4 map 0.0.0.0/0
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf Campus (IID 4099), 1 entries

0.0.0.0/0, uptime: 02:36:59, expires: 00:06:05, via map-reply, unknown-eid-forward
Sources: map-reply, static-send-map-request
State: unknown-eid-forward, last modified: 02:36:59, map-source: 172.12.1.66
Exempt, Packets out: 4(2304 bytes), counters are not accurate (~ 21:33:58 ago)
Configured as EID address space
action: send-map-request + Encapsulating to proxy ETR
PETR Uptime State Pri/Wgt Encap-IID Domain-ID/MH-ID Metric
172.12.1.65 02:36:59 up 10/10 - 2088152724/44692 0
172.12.1.66 02:36:59 up 10/10 - 2088152724/44692 0

After clearing:

Edge2#clear lisp ins 4099 ipv4 map 0.0.0.0/0
Edge2#show lisp ins 4099 ipv4 map 0.0.0.0/0
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf Campus (IID 4099), 1 entries

0.0.0.0/0, uptime: 00:00:01, expires: 00:00:12, via static-send-map-request
Sources: static-send-map-request
State: send-map-request, last modified: 00:00:01, map-source: local
Exempt, Packets out: 0(0 bytes), counters are not accurate
Configured as EID address space
Negative cache entry, action: send-map-request

Reasons for an unresolved map-cache:

No traffic triggered resolution on this instance-id/VRF

Connectivity to the CP is impacted (no map-reply has been received in the FE)

Map-requests are not going out to the CP (map-supression, reachability to CP, blocked by CTS, some defect?? 🙂 ).

topic LISP catch-all entry in Software-Defined Access (SD-Access)

LISP catch-all entry

Re: LISP catch-all entry