Hi Andrew Kelly
We understand you're experiencing connectivity issues with your ExpressRoute circuit, specifically with the secondary path showing a degraded status and the on-prem ARP entry missing.
If the ARP entry for on-prem is missing, it typically means no Layer 2 frames are being received from your edge router on that path.
Please review the following details to potentially resolve the issue:
- Please validate the L2 configuration, use the PowerShell cmdlets to validate the ARP tables for both the primary and secondary pathways. This will confirm if any entries show up for your setup.
- For private peering:
Get-AzureDedicatedCircuitPeeringArpInfo -ServiceKey <your Service Key> -AccessType Private -Path Secondary
- Ensure that you generate traffic from your on-prem environment to Microsoft services and verify if the ARP entries are populated thereafter.
- You can refresh the circuit configuration via the Azure portal, which might help if there's a routing issue.
- Sometimes, clearing the ARP cache on your on-prem router can help re-establish connectivity.
- Refer to the information in the following Microsoft documentation links to view ARP table troubleshooting:https://learn.microsoft.com/en-us/azure/expressroute/expressroute-troubleshooting-expressroute-overview#validate-arp
I hope this helps! If these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.
If the above is unclear or you are unsure about something, please add a comment below.