Hello Jerome,
our local dealer resolved the problem.
Between our sites we do static routing. From our Site 129.2 (which is connected via SDA Transit to 129.1, Main Site, with IP-Transit to external world) we have a default route 0.0.0.0 0.0.0.0 x.x.128.1
128.1 is on the same device which has the loopback address 129.1 (Main Site).
128.1 is the ip address of the interface who is connected to Site wich has the loopback 129.2.
The Device 129.2 has a physical address 128.2 which is connected do Main site 128.1.
On the Site with 129.2 we ca do a ping wich is successful to 129.1
The 129.2 Site has a default route to 128.1
The IP bindings via lisp from Site 129.2 to the TransitCP are all fine for default VN. But not for user created VN.
I do a few monitor sessions and saw that a ping from a user createt VN (Endpoint, PC) never leave the Edge Switch who the device is connected to.
I did a ping from another PC in the same VN which is connected via Main Site to Site connected via SD Transit. I saw packets came into Edge switch but never get back.
Solution:
The Edge Switch with loopback 129.2 need a dedicated host route to neighbour 129.1 like this:
#ip route x.x.129.1 255.255.255.255 x.x.128.1
[Remember, 128.1 has loopback0 with 129.1]
Thats all, the Client can communicate with each other and can leave via IP-Transit from Main Site the SDA Cloud.
Thanks for your help and have a nice weekend!
Output changed as expected:
#show lisp remote-locator-set default-etrs
Codes:
ETR = ETR Type (Default = Default-ETR, Service = Service-ETR)
SI = Service Insertion Type
ID = Service Insertion ID
- = No service insertion config type defined
DS = Default-ETR Firewall Service Insertion
SS = Service-ETR Firewall Service Insertion
P = Primary/Direct in use, Backup not available
PB = Primary/Direct in use, Backup available
B = Backup in use, Primary/Direct not available
BP = Backup in use, Primary/Direct available
MT = Multisite Service Insertion
* = This locator has multiple service EID configured.
LISP remote-locator-set default-etr-locator-set-ipv4 Information
RLOC Pri/Wgt/Metric Inst Domain-ID/MH-ID ETR SI/ID
x.x.129.2 10/10 /- 4100 2212154865/53350 Default B /-
#sh lisp instance-id 4100 ipv4 database 0.0.0.0/0
LISP ETR IPv4 Mapping Database for LISP 0 EID-table vrf VN (IID 4100), LSBs: 0x1
Entries total 1, no-route 1, inactive 0, do-not-register 5
0.0.0.0/0, locator-set DEFAULT_ETR_LOCATOR *** NO ROUTE TO EID PREFIX ***, default-ETR
Uptime: 20:12:16, Last-change: 03:29:53
Domain-ID: 2212154865
Metric: -
Service-Insertion: N/A
Locator Pri/Wgt Source State
x.x.129.2 10/10 cfg-intf site-self, reachable
Map-server Uptime ACK Domain-ID
x.x.129.2 03:29:53 Yes 495636582
#sh lisp instance-id * ipv4 map-cache 0.0.0.0/0
=================================================
Output for router lisp 0 instance-id 4100
=================================================
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf VN (IID 4100), 1 entries
0.0.0.0/0, uptime: 00:00:18, expires: 00:00:42, via pub-sub, unknown-eid-forward, remote-to-site
Sources: pub-sub
State: unknown-eid-forward, last modified: 03:30:24, map-source: local
Exempt, Packets out: 89(67824 bytes), counters are not accurate (~ 00:18:13 ago)
Configured as EID address space
PETR Uptime State Pri/Wgt Encap-IID Domain-ID/MH-ID Metric
x.x.129.1 03:30:24 up 10/10 - 2212154865/52721 0
