Issues deploying Equinix Connections
I have managed to use several terraform modules without problem. I have used the palo alto cloudgenix vm modules, palo alto firewalls modules, device link modules, and fabric cloud router module. All work okay on the lastest version of equinix/equinix. However as I dive into other connections I get a lot version issues. For example. Leveraging the cloud-router-port connection. https://registry.terraform.io/modules/equinix/fabric/equinix/latest/examples/cloud-router-2-port-connection This would be used to connect the cloud router to the pa firewall mgmt interface. Documentation covers the following version. required_providers { equinix = { source = "equinix/equinix" version = ">= 2.9.0" } } } But code doesnt work without this version terraform { required_providers { equinix = { source = "equinix/equinix" version = "~> 1.26.0" } } } When using new versions error occurs. Failure. Ive redone this several times in my code base. ephemeral.aws_secretsmanager_secret_version.equinix_iac_credentials: Opening... ephemeral.aws_secretsmanager_secret_version.equinix_iac_credentials: Opening complete after 0s module.equinix_deployment.module.fw-mgmt-to-fcr-connection-ch-1a.equinix_fabric_connection.this: Creating... ╷ │ Error: 400 Bad Request Code: EQ-3142558, Message: Json syntax error, please check request body, Details: Unknown json property : aSide.accessPoint.router.package.code. Unexpected value '' │ │ with module.equinix_deployment.module.fw-mgmt-to-fcr-connection-ch-1a.equinix_fabric_connection.this, │ on ..\..\modules\cloud-router-2-port-connection\main.tf line 1, in resource "equinix_fabric_connection" "this": │ 1: resource "equinix_fabric_connection" "this" { I can get past this error and deploy the connection with an older version but then run into version issues when attempting to leverage the virtual-device-2-eia-connection https://registry.terraform.io/modules/equinix/fabric/equinix/latest/examples/virtual-device-2-eia-connection here the primary problem is that on older versions. there is no resource virtual-device-connection. only fabric-device-connection. One thought is to completely separate the fabric cloud router to port module Here is the original cloud router to port module main.tf resource "equinix_fabric_connection" "this" { name = var.connection_name type = var.connection_type bandwidth = var.bandwidth notifications { type = var.notifications_type emails = var.notifications_emails } a_side { access_point { type = "CLOUD_ROUTER" router { uuid = var.aside_fcr_uuid } } } z_side { access_point { type = var.zside_ap_type virtual_device { type = var.zside_vd_type uuid = var.zside_vd_uuid } interface { type = var.zside_interface_type id = var.zside_interface_id } location { metro_code = var.zside_location } } } order { purchase_order_number = var.purchase_order_number } } variables variable "connection_name" { type = string description = "Name of the Fabric connection" } variable "connection_type" { type = string description = "Type of the Fabric connection (e.g., IP_VC)" } variable "bandwidth" { type = number description = "Connection bandwidth in Mbps" } variable "notifications_type" { type = string default = "ALL" description = "Notification type" } variable "notifications_emails" { type = list(string) description = "Emails for notifications" } variable "purchase_order_number" { type = string default = "" } variable "aside_fcr_uuid" { type = string description = "UUID of the FCR device" } variable "zside_ap_type" { type = string default = "VD" } variable "zside_vd_type" { type = string default = "EDGE" } variable "zside_vd_uuid" { type = string } variable "zside_interface_type" { type = string default = "NETWORK" } variable "zside_interface_id" { type = number } variable "zside_location" { type = string } versions.tf terraform { required_providers { equinix = { source = "equinix/equinix" version = "~> 1.26.0" } } } module module "fw-mgmt-to-fcr-connection-ch-1a" { #FCR Router to FW Management Interface Connection source = "../../modules/cloud-router-2-port-connection" connection_name = "fcr-2-fw-mgmt-ch" connection_type = "IP_VC" bandwidth = 50 notifications_type = "ALL" notifications_emails = var.notifications purchase_order_number = "mgmt-connection" #aside Fabric Cloud Router aside_fcr_uuid = module.fcr_ch.id #zside Palo aAlto Firewall zside_ap_type = "VD" #Virtual Device zside_vd_type = "EDGE" zside_vd_uuid = module.pa_vm_ch.id zside_interface_type = "NETWORK" zside_interface_id = 1 # Palo Alto Firewall Management Port zside_location = "CH" #metro code }Boost Your Multicloud Strategy with High-Performance Connectivity
Experts from Equinix and Oracle are going to show you how to boost your multicloud strategy with high-performance connectivity. Discover how Oracle Cloud Infrastructure (OCI) via FastConnect enables essential private, dedicated, high-bandwidth connectivity. Key Topics: Predictions and trends for multicloud Oracle Cloud Infrastructure (OCI) distributed cloud Multicloud use cases and challenges How to connect to multiple clouds High-performance cloud-to-cloud connectivity solution Multicloud data integration architecture Fabric Cloud Router Learn more about Equinix and Oracle solution
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.Simplify multicloud networking and be AI-ready with AWS
Join us to discover how Equinix and AWS can help you efficiently manage workloads across cloud environments and locations. One of our key offerings, the Equinix Fabric Cloud Router with AWS Direct Connect, simplifies the complexities of owning and operating your own routers. By leveraging this solution, you can enhance application performance and reduce cloud egress charges. RSVP to the Tech Talk During this webinar, we will address specific challenges and provide solutions for: Moving data from one public cloud to another with GPU availability, ensuring efficient utilization of resources. How Equinix FCR with AWS Direct Connect, provides businesses with robust, low-latency, and cost-effective networking options between AWS and their other public clouds. Establishing cloud-to-cloud private connectivity to integrate systems following mergers and acquisitions, enabling seamless collaboration. Conducting large-scale cloud-to-cloud migrations to minimize egress charges associated with data transfer. Join hosts, Gene McColm Principal Solutions Architect, Equinix, and Nathan Spitler, Senior Product Manager, AWS Networking as they delve into these topics.Create a Fabric Cloud Router on AWS Marketplace
Learn how to set up an Equinix Fabric Cloud Router (FCR) on AWS from start to finish, even if you’re new to the platform. Katie guides you step-by-step, starting with signing up for the FCR trial on the AWS Marketplace, where she shows how to locate the listing, complete a brief form, and finalize your account setup using the information provided by AWS and Equinix. Once signed in, she demonstrates how to create a cloud router by selecting a location, entering the subscription key, and configuring the router with the standard trial package. Finally, she walks through creating a secure, dedicated connection between FCR and AWS, showing you how to set up and manage a Direct Connect link seamlessly. By the end, you’ll have the knowledge and confidence to establish a robust connection between your Equinix Fabric Cloud Router and AWS. Learn more about Fabric Cloud Router. 🤝 Join the Conversation: We value your feedback! Drop a comment below with your thoughts, questions, or suggestions for future video topics.
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.
