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/
