EDGROUTER X RUN A PING CONSOLE HOW TO

I'm not sure how to interpret Gateway '0.0.0.0' here. The last three rows in the routing table are the internal networks in which the VMs that I try to ping are.

So, it seems to me that the problem is that the DLR cannot complete ARP requests for his own OS - not the routing part (as it would affect communications between networks, which is not the case).Д¬an anybody help identify the problem here?ДЇrom the commands you advised it seems everything is OK. When I run 'show apr' on DLR control VM, the result is empty - there are no ARP entries.ДЇirewalls are disabled for now. DLR cannot participate is OSPF with EDGE router.ДҐ. DLR cannot ping its default gateway (EDGE router).Д¤. Separate interface on EDGE router, created for testing purposes only, connected to one of the intenal networks can ping VMs in corresponding Logical Switch.ДЎ. EDGE router, that is a default gateway for the affected DLR,can ping DLR's IP on the interface in the Interconnect network (separate Logical Switch).Д¤.

VMs can ping affected router's interface IPs.ДЈ. Routing between internal networks: VMs from one Logical Switch can ping VMs in other Logical Switch, with gateway interfaces for each network being on the affected DLR.Дў. Long story short, although it operates as router and routes packets between internal networks with no issues detected, it seems to be unable to complete ARP requests for himself.ДЎ. I've stumbled upon strange behavior of a DLR router on one installation (NSX v.6.3).

Edgrouter x run a ping console