PeerASN validation failed

Question

The child tag for this is wrong, but there is no child tag for the Internet Peering question I need to ask.

Does anyone have any tips or tricks for interacting with Microsoft Azure for the purpose of setting up peering over an Internet exchange (IX)?

Six months ago, I tried to create a Peer ASN Record, but it "failed validation." There was zero information as to what, exactly, failed. The Microsoft peering team was also unable to tell me what failed.

I just now tried to create it again, but I still have the same problem. I've engaged the peering team again to help. But I feel like I'm about to get the same runaround, if I get any response at all.

I have read the document at https://learn.microsoft.com/en-us/azure/internet-peering/howto-subscription-association-portal. I have created the Azure account with an active subscription, registered the peering provider, and I am stuck at step 3, create Peer ASN.

Azure support will not talk to me because I do not have a support contract. I do not need any paid services; I just need to arrange direct peering across several IXes.

Answer 1

Hello Brian Knight

I understand that you're experiencing a frustrating issue with Azure's Internet Peering setup, especially at the Peer ASN creation step.

• The ASN you provide must be a publicly registered Autonomous System Number. Private ASNs will not pass validation.
• The Peer Name must closely match your PeeringDB entry. Even small discrepancies can cause silent validation failures Check the document: https://learn.microsoft.com/en-us/azure/internet-peering/howto-subscription-association-portal
• Double-check your PeeringDB profile and ensure all details match those you are entering in Azure. And wait for 12 hours and see. check the reference doc:https://learn.microsoft.com/en-us/azure/internet-peering/howto-subscription-association-portal
• Make sure your provider is advertising routes for the prefix you're trying to validate. Remember, routes must be advertised with the Peering Service community string 8075:8007. If this isn’t included, the validation might fail.
• Ensure you have the correct number of sessions configured in both your primary and backup locations. Azure requires a minimum of two sessions for the primary peering location and one session for the backup location.
• Please review the technical requirements for Azure Peering Service detailed in the documentation and ensure that all necessary steps are followed. Reference doc: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager

Please share the below information:

1. Can you confirm the specific ASN values and prefixes you're trying to use, and if they meet the necessary criteria?
2. Are you able to check with your networking team if the routes are being advertised correctly and if the string 8075:8007 is being used?
3. Have you encountered any other error messages or validation errors previously, or is this the first time?
4. Could you provide details about the current networking setup, specifically any configuration for BGP sessions?

---

Hope the above answer helps! Please let us know do you have any further queries.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.