Hi, It seems the migration of campus networks to VxLAN fabric is promising. Looks like troubleshooting the data plane between endpoints across the fabric is much needed. I haven't gone through the earlier work on OAM for NVOs. I have some basic questions, 1) Why cant we use the legacy IP router alert option in a ping packet to the overlay destination at the VTEP. The ingress VTEP needs to copy the Router alert option in the outer tunnel header. When the destination VTEP is not reachable at a transit hop, the transit hop can send a destination unreachable. Using this information we can see which node is dropping. 2) In the case where the ping request reaches the egress VTEP, normal VxLAN header is decapsulated and original ping packet is given the local gateway. If the gateway doesn't find the destination as it maybe down, they can send a destination host unreachable with the gateway IP. Apologize if i overlooked anything.
-Prabhu
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
