
OPERATIONAL DEFECT DATABASE
...

...
If the relayed dhcp packet is supposed to be forwarded through the l3vni, it is failing to forward. From debug ip packet we see: Jun 20 11:50:08.348: IP: s=0.0.0.0 (Vlan100), d=255.255.255.255, len 343, input feature, MCI Check(109), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE *Jun 20 11:50:08.349: IP: s=0.0.0.0 (Vlan100), d=255.255.255.255, len 343, rcvd 2 *Jun 20 11:50:08.349: IP: s=0.0.0.0 (Vlan100), d=255.255.255.255, len 343, stop process pak for forus packet *Jun 20 11:50:08.349: IP: tableid=2, s=10.0.100.1 (local), d=10.0.200.2 (Vlan123), routed via FIB *Jun 20 11:50:08.349: IP: s=10.0.100.1 (local), d=10.0.200.2 (Vlan123), len 343, sending *Jun 20 11:50:08.349: IP: s=10.0.100.1 (local), d=10.0.200.2 (Vlan123), len 343, encapsulation failed
- SVI configured as dhcp relay - dhcp server reachable via the vxlan l3vni
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.