We have a very simple SDA setup. One fabric edge node which clients connect too, and one Border/Control Plane Node that connects out to the rest of our Non-Fabric environment, specifically a N7K Fusion Router. Our DHCP server is out in the Non-Fabric environment.
When our client sends a DHCP request, it hits the edge node (confirmed by packet capture) and then sets the Option 82/GIaddr. I checked the circuit and remote circuit ids through ip dhcp debugs and confirmed that it is setting the correct RLOC, VLANs, etc (confirmed by embedded packet capture).
However, after this... the process seems to stop. No more debugs appear. Embedded packet capture does not find any packets leaving the interfaces to our Border/PETR node, and no packets are captured inbound on the Border/PETR node that have to do with DHCP/UDP 67+68. I'm thinking it might have something to do with our LISP table?
DHCP server is 172.20.100.110.
#sh ip cef vrf DEV_VN 172.20.0.0 det
172.20.0.0/16, epoch 0, flags [check lisp eligibility]
LISP remote EID: 48 packets 15266 bytes fwd action fwd native
LISP fwd-native source
Dependent covered prefix type LISP-FWD, cover 0.0.0.0/0
1 IPL source [no flags]
attached to LISP0.4099
#sh ip lisp map-cache 172.20.100.0 instance-id 4099
LISP IPv4 Mapping Cache for LISP 0 EID-table vrf DEV_VN (IID 4099), 1 entries
172.20.0.0/16, uptime: 00:29:58, expires: 00:14:38, via map-reply, forward-native
Sources: map-reply
State: forward-native, last modified: 00:29:58, map-source: 172.21.255.1
Active, Packets out: 48(15266 bytes), counters are not accurate (~ 00:00:22 ago)
Encapsulating to proxy ETR
Not sure which steps to take or where to go from here.
I can ping the DHCP server from fusion router.
I can ping DHCP server from global routing table and from the DEV_VN VRF on the border node (as long as it is sourced from the Loopback DNA center created on the border).
I can ping the DHCP server from the global routing table but NOT from the DEV_VN VRF on the fabric edge.
Should I be able to ping the PETR RLOC address from the DEV_VN VRF on the fabric edge? Is it possible that it doesn't know how to reach the PETR from the VRF and that is the issue? I can ping PETR RLOC from global routing table on fabric edge but not from the VN VRF.
DHCP snooping is enabled with correct vlans attached, fabric edge is configured as PITR, option 82 originate is on... not sure where I'm going wrong. Thanks.
More info:
Fabric Edge LISP -
Information applicable to all EID instances:
Router-lisp ID: 0
Locator table: default
Ingress Tunnel Router (ITR): disabled
Egress Tunnel Router (ETR): enabled
Proxy-ITR Router (PITR): enabled RLOCs: 172.21.255.2
Proxy-ETR Router (PETR): disabled
NAT-traversal Router (NAT-RTR): disabled
Mobility First-Hop Router: disabled
Map Server (MS): disabled
Map Resolver (MR): disabled
Mr-use-petr: disabled
First-Packet pETR: disabled
Multiple IP per MAC support: disabled
Delegated Database Tree (DDT): disabled
Multicast Flood Access-Tunnel: disabled
Publication-Subscription: enabled
Publisher(s): *** NOT FOUND ***
ITR Map-Resolver(s): 172.21.255.1
ETR Map-Server(s): 172.21.255.1
xTR-ID: 0x570C1D3C-0x75B2B221-0x8FB89F16-0x428F42C4
site-ID: unspecified
ITR local RLOC (last resort): *** NOT FOUND ***
ITR use proxy ETR RLOC(Encap IID): 172.21.255.1
Border Node LISP -
Information applicable to all EID instances:
Router-lisp ID: 0
Locator table: default
Ingress Tunnel Router (ITR): disabled
Egress Tunnel Router (ETR): enabled
Proxy-ITR Router (PITR): enabled RLOCs: 172.21.255.1
Proxy-ETR Router (PETR): enabled
NAT-traversal Router (NAT-RTR): disabled
Mobility First-Hop Router: disabled
Map Server (MS): enabled
Map Resolver (MR): enabled
Mr-use-petr: enabled
Mr-use-petr locator set name: default-etr-locator-set-ipv4
First-Packet pETR: disabled
Multiple IP per MAC support: disabled
Delegated Database Tree (DDT): disabled
Multicast Flood Access-Tunnel: disabled
Publication-Subscription: enabled
Publisher(s): *** NOT FOUND ***
ITR Map-Resolver(s): 172.21.255.1
ETR Map-Server(s): 172.21.255.1
