Error message 103.77.108.12 already in use with different ASN when registering a direct peering request with Microsoft Peering

Question

Dear Microsoft Team,

We are trying to register a bilateral BGP session using your portal.

However we receive bellow error and we are unable to complete the process.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"BadArgument","message":"103.77.108.12 already in use with different ASN."}]}

Our details are:

ASN: 135814

Extreme IPv4 address: 103.77.108.12

Extreme IPv4 address: 2001:df2:1900:2::12

Location: Extreme IX Mumbai

Here is our peering DB record:

https://www.peeringdb.com/net/12573

103.77.108.12 cannot be in use with a different ASN, this IP address is part of a subnet of our own and not provided to any other member (active one or terminated one).

Please check what it could be the issue and inform us as soon as possible since we are trying to register the request for many days. You already confirmed that you do not have active BGP sessions between mentioned IP address and your end.

I was advised in support chat with your team using Azure portal to ask here someone from your experts to assist us. This is taking a month already. We are the largest local Internet exchange in India, we have /23 network so once we terminate a member, we will reuse their IP address for another new one in some time. Please explain why this is taking so much time and what process we need to follow in future?

Answer 1

Your team has assisted in related ticket at our end and we were able to request the peering sessions. Thank you, I am closing this topic.

Answer 2

Hi,

Welcome to the Microsoft Q&A platform!

Microsoft Exchange is mainly focused on the technical questions about administration, monitoring, and performance for Exchange Server.

According to your description, your question is not in our support scope. So we will remove Exchange related tag from your thread.

Thanks for your understanding and patience!