Forum Discussion

brnetworkguy's avatar
2 months ago
Solved

FCR is not doing ECMP

I have an FCR connected to one OCI connection and two AWS connections.

From AWS to OCI, passing through FCR, I see that AWS is implementing ECMP towards OCI prefixes, as evidenced by the RX traffic on the FCR coming from these two connections.

In FCR active routes, I am seeing the same prefixes learned from these two AWS connections.

If I look at the contrary (TX) from FCR to AWS (from traffic that originated in OCI), I always see TX to AWS using only one AWS connection, never the other one.

Support says that it is not working because OCI has only one connection to FCR.

As far as I know, ECMP is implemented hop by hop, and it is a local decision implemented independently at each router (hop) in the network, that is why I do not agree with this statement.

For me is the function of FCR implement ECMP in this case for these packets coming from OCI to AWS.

 

  • Thank you for bringing this to our attention. We have a number of customers using ECMP via BGP Multipath on FCR. For some reason you are having an issue our support team can help to identify and remediate if necessary.

    We do see you have opened a service ticket with Equinix support so we ask that you continue working with them until we validate, identify and rectify any operational issues that you may be experiencing related to ECMP with FCR.

2 Replies

  • Shannon's avatar
    Shannon
    Community Manager

    Thank you for bringing this to our attention. We have a number of customers using ECMP via BGP Multipath on FCR. For some reason you are having an issue our support team can help to identify and remediate if necessary.

    We do see you have opened a service ticket with Equinix support so we ask that you continue working with them until we validate, identify and rectify any operational issues that you may be experiencing related to ECMP with FCR.

  • Just complementing ...

    OCI connection is deployed in the primary fabric zone, and I am seeing traffic from OCI going to AWS connection deployed in the primary zone, but never to the AWS connection deployed in the secondary zone. My guess is Equinix Fabric is not treating prefixes from different fabric zones (primary and secondary) with the same BGP attributes as equals. If I need another connection in OCI using a secondary fabric zone to make this work, this is not true ECMP implemented on FCR.

Featured Places

  • Node avatar for Discussions

    Discussions

    Engage with industry experts, share insights, ask questions, and grow your network.
  • Node avatar for Ideas

    Ideas

    We're listening! Submit your ideas to shape the future of Equinix!
  • Node avatar for Groups

    Groups

    Ready to collaborate? Join a Group or upcoming beta program.
  • Node avatar for What's New

    What's New

    Stay ahead with the latest from Equinix. Discover new product announcements, insightful tutorials, and practical use cases.
  • Node avatar for Events

    Events

    Your Guide to Upcoming Events - Online, Hybrid, and In-Person!