Fabric Cloud Router Policies cant be applied when peering is down
We cant able to apply the router filter policies(RFP) when the Peerings are down on FCR. By the time we apply the Filter policies, all routes learnt from peers are advertised to the other peers resulting in downtime due to loop(unwanted routing). Even if we are quick enough to apply the policies, Fabric backend can only able to process one Filter policy at a time. If you try to apply/save the other policies it gives you an error as FCR is in Transient state. As a best practice we need to have Filter policies enabled first and then turn on the BGP peering to avoid loops/sub optimal routing.Connecting Fabric Cloud Router to AWS and Azure
In this video, we'll show you how to Create a Fabric Cloud Router, create a connection to AWS, create a connection to Microsoft Azure, and then run a ping test between those two virtual machines running in the cloud environments. This step-by-step demo shows how quickly you can create a Fabric Cloud Router, and then with the help of Quick Connect for AWS and Azure, connect the router with Virtual Machines at Equinix. And finally, how to test the new connections. Create connections using Fabric Cloud Router in the Fabric portal: https://fabric.equinix.com/
Terraform-Provider-Equinix v1.16.0 Release
Equinix Terraform Provider v1.16.0 not only has the ability to create Fabric Cloud Router resources directly, but also layer 2 connections to AWS, GCP, and specific fabric ports in Equinix. Connections to Azure and Oracle via Terraform are coming soon! FCR is a great option for those who want to quickly route between clouds using BGP or static networks without worrying about specific OS, vendor requirements, or advanced configuration. For those who use Network Edge, this Terraform release allows you to disable the default internet connectivity before provisioning specific firewalls (Palo Alto Networks NGFW, Cisco FTDv, and Aviatrix FireNet) just like you can in the console.Is a Digital Services Agreement (DSA) required to order/use Fabric Cloud Router (FCR)?
Hey Community! We often get questions about Fabric Cloud Router and we’re here to help clarify for others who might have the same question in the future. If you’ve got additional questions about FCR, ask them in Community! What is a Digital Services Agreement (DSA)? The Digital Services Agreement is a document that is presented to users when setting up a Billing Account to order digital services like Fabric Cloud Router. If this is your first time ordering digital services with Equinix and you do not have an existing Billing Account (or sometimes called a Cloud Billing Account), you’ll be directed to digitally sign the DSA. If you're creating additional Billing Accounts, you will be asked whether you want to use an existing Digital Services Agreement or sign a new Digital Services Agreement. If you need guidance on either DSA option, please review this documentation. [Example only for reference and may not reflect latest version of DSA] I’m a new customer; do I need to sign a Fabric DSA? Yes, if you are a new customer and using Fabric for the first time, you’ll log into the Fabric Portal to order an FCR and be prompted to follow the click-through DSA. This is meant to allow and support our new customers who are looking to quickly onboard and use Fabric. What about if I'm an existing Equinix customer using Fabric for the first time, do I need to sign a DSA? Great question! If an existing Equinix customer clicks through Fabric for the first time they would also be prompted with the click-through DSA, however, if this customer already has an existing MCA/GTC Agreement with Equinix, these can be associated (by the Sales / Legal Ops) to a Billing Account for Fabric, and once that's correctly completed, the Billing Account should how as Active for the customer in the Portal and they will not be prompted to sign the click-through DSA. I already have a MCA/GTC agreement, but I’m getting prompted about a DSA. If an MCA/GTC agreement has been associated with the billing account for Fabric and the customer is still being prompted with the click-through DSA: The association of the MCA/GTC to the billing account may not be setup correctly and we recommend to contact support. The user logged into the Portal may not be associated with the correct Fabric Account/Project that has access to the active billing account.
