Welcome to the Microsoft Q&A forum.
I understand you re facing issues while configuring private peering for your express route circuit. where you are encountering an issue with incomplete ARP entries and unable to successfully ping the Azure resources.
Not sure if you have already referred to this troubleshooting documentation here
If a problem with the on-premises or connectivity provider occurs, the ARP table shows one of two things. You see the on-premises MAC address show incomplete or only see the Microsoft entry in the ARP table. As shown below
The recommended solution here is to open a support request with your connectivity provider to debug such issues. If the ARP table does not have IP addresses of the interfaces mapped to MAC addresses, review the following information:
- If the first IP address of the /30 subnet assigned for the link between the MSEE-PR and MSEE is used on the interface of MSEE-PR. Azure always uses the second IP address for MSEEs.
- Verify if the customer (C-Tag) and service (S-Tag) VLAN tags match both on MSEE-PR and MSEE pair.
You don't see an ARP table shown for a peering if there are issues on the Microsoft side. If this is the issue it is recommended to open a support request. Please let me know if you do not have a support plan, I can help in that regard.
Regarding the sample configuration for the router's side, you can refer to these configuration samples for Cisco IOS-XE based routers and Juniper MX series routers. You can also reach out to device vendor's sales/technical team to find appropriate configurations to meet your needs.
Hope this answers your query. Please let me know if you have any additional questions. Thank you!
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.