I have an ExpressRoute circuit set up with a partner (Equinix). I am able to create the circuit, eventually get the service key, give it to Equinix, and it all looks right. Eventually it says "Provider Status: Provisioned". So I go to "peerings -> Azure private" to try and set up peering information (peer ASN, primary and secondary IP ranges, BGP shared key). When I hit save, it says that it failed because prior PUT call failed, and circuit is in a failed state. The "overview" now shows "circuit status: failed". I suspect it may be related to BGP failure, but of course, I cannot edit the peering information, because... circuit is in a failed state! It might be something different as well. The circuit shows in valid state on the Equinix side, except for "Pending BGP", of course, which I want to fix. How do I figure out why the circuit is in a failed state and fix it. Conversely, if this "failed state" is primarily because of BGP, how do I get it so that I can enable the peering settings and thus fix it? I have created and destroyed a circuit 3 times in a row, so it isn't something transient. Thanks in advance for all who help.

@avi , Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well. When you say, "I have created and destroyed a circuit 3 times in a row", Did you also share the service key to your service provider 3 times? Generally, Circuit status being in a failed state indicates a Control plane operation failure (CRUD). To fix this, we can try getting and setting the Circuit. Use the below Powershell command to get the Circuit Then Set "Allow Classic Operations" to TRUE and Update the Circuit For update operation, we should make some change This is just for the testing purpose and you can set this value to "FALSE" later $ckt = Get-AzExpressRouteCircuit -Name "<NAMEOFCIRCUIT>" -ResourceGroupName " <NAMEOFRESOURCEGROUP>" $ckt.AllowClassicOperations = $true Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt Let me know how this goes. Cheers, Kapil

How to fix ExpressRoute circuit in failed state?

Accepted answer

KapilAnanth-MSFT 46,776 Reputation points Microsoft Employee

2024-07-03T11:46:59.8766667+00:00
@avi ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

When you say, "I have created and destroyed a circuit 3 times in a row",

Did you also share the service key to your service provider 3 times?

Generally, Circuit status being in a failed state indicates a Control plane operation failure (CRUD).

To fix this, we can try getting and setting the Circuit.

Use the below Powershell command to get the Circuit

Then Set "Allow Classic Operations" to TRUE and Update the Circuit

For update operation, we should make some change

This is just for the testing purpose and you can set this value to "FALSE" later

$ckt = Get-AzExpressRouteCircuit -Name "<NAMEOFCIRCUIT>" -ResourceGroupName " <NAMEOFRESOURCEGROUP>" $ckt.AllowClassicOperations = $true Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt

Let me know how this goes.

Cheers,

Kapil
Please sign in to rate this answer.

1 person found this answer helpful.
avi 20 Reputation points

2024-07-03T12:48:02.4666667+00:00

Hi Kapil, thanks for the warm welcome, and especial thanks for hopping to try and assist.

Yes, each time I tore the whole thing down and set it up anew: new circuit on Azure side, new connection on Equinix side, etc. I wanted to be sure it wasn't some transient error.

I will give it a shot via PowerShell. I will have to do it locally, as clicking on CloudShell in the console just gives me a blank pull up on bottom. Going to try it and post here shortly.

avi 20 Reputation points

2024-07-03T13:02:49.8966667+00:00

Tried it:

PS /Users/adeitcher> Get-AzExpressRouteCircuit -Name "Azure-VRF" -ResourceGroupName "Equinix" ResourceGroupName Name Location AllowClassicOperations CircuitProvisioningState ServiceProviderProvisioningState Service Provide rNotes ----------------- ---- -------- ---------------------- ------------------------ -------------------------------- ------- Equinix Azure-VRF eastus False Enabled Provisioned PS /Users/adeitcher> $ckt = Get-AzExpressRouteCircuit -Name "Azure-VRF" -ResourceGroupName "Equinix" PS /Users/adeitcher> $ckt.AllowClassicOperations = $true PS /Users/adeitcher> Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt ResourceGroupName Name Location AllowClassicOperations CircuitProvisioningState ServiceProviderProvisioningState Service Provide rNotes ----------------- ---- -------- ---------------------- ------------------------ -------------------------------- ------- Equinix Azure-VRF eastus True Enabled Provisioned

Now it says "enabled":

I will check if I can set the peering info now.

That looks pretty good. Now I check on the console:

avi 20 Reputation points

2024-07-03T13:07:45.97+00:00

OK, that worked. Now I am unsure what it all means.

KapilAnanth-MSFT 46,776 Reputation points Microsoft Employee

2024-07-03T13:33:08.27+00:00

@avi ,

You are most welcome and the pleasure is ours.

When Circuit status becomes failed, it indicates that some configuration of the ExpressRoute in the backend did not reach the end "Goal State"

For e.g. some mandatory field being NULL or some special fields not having a accepted value.

Or the "PUT" operation failed for some other reason

This happens mostly with IaaC (Bicep, Terraform) deployments.

What we did is,

We get the Circuit with the "Get-AzExpressRouteCircuit" command

We make some minimal changes

Then we update the circuit with the command

This update, fixes the issues from the previous "PUT" Operation.

Hope this clarifies.

I would highly appreciate if you could Accept the answer and close this thread

Original posters help the community find answers faster by identifying the correct answer.

Thanks,

Kapil

avi 20 Reputation points

2024-07-03T13:35:49.95+00:00

Sure, I will accept.

Since it happened 3 distinct times, how do I find the problem to prevent it from happening again?

KapilAnanth-MSFT 46,776 Reputation points Microsoft Employee

2024-07-05T14:53:50.4766667+00:00

@avi ,

Are you by any chance using a IaaC Deployment?

If so, please make sure you are following the correct documentation

If you are using the portal and you are able to repo this issue at will, I would suggest you please file a support ticket so that a support engineer can have a screen share session to pinpoint the issue

Cheers,

Kapil
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix ExpressRoute circuit in failed state?

0 additional answers

Your answer