Product Forums

 Following the successful launch in California, where SHRED expanded to San Jose, Santa Clara, and Palo Alto IBXs, we're excited to announce the next phase of our rollout across EMEA. This significantly increases our coverage and brings secure, sustainable e-waste disposal services to even more customers across the region.We are now launching SHRED (Smart Hands for Responsible Electronic Disposal) in the following IBXs:FR2, FR4, FR5, FR6, FR7, FR8, FR13, IL2, IL4, MU1, MU3, MU4, DU1, DX1, DX2, and AD1This expansion strengthens our global footprint and reflects the growing demand for responsible IT asset disposal solutions across our data centers.Simplify IT Asset Disposal While Supporting a Greener FutureWith SHRED, customers can securely and responsibly dispose of retired IT equipment while supporting their sustainability goals. SHRED ensures electronic waste is handled according to the highest standards of security and environmental responsibility.What is SHRED?SHRED is a Smart Hands

We are excited to announce a significant architectural evolution in our sovereignty controls. While geo-boundary enforcement has historically resided at the Fabric port level, we have successfully extended this capability down to the Network Edge virtual device itself. This upgrade empowers customers to define and enforce Geo Zones when the Network Edge is the originating endpoint of a Fabric connection. You can now provision and validate this constraint directly via the UI or API, ensuring compatibility checks run before provisioning commits. This proactive validation removes the risk of post-deployment configuration mismatches.  This feature is live today across GCP, AWS, and Oracle Quick Connect, supporting both VD-to-Port and VD-to-CSP provisioning paths. (A note for your integration specialists: The API layer for this specific implementation is delivered by the Fabric team.)   

We currently have a copper bandwidth connection at the data center (in a cabient) and are looking to increase the available bandwidth.Could you assist with the steps invovled in ordering?From reading past forums does it involve ordering a new connection?Thanks for your expertise.

I scavenged the terraform registry looking for a Equinix Internet Access Terraform module. ]I found an example of a connection to EIA.This is the only thing that comes up in the registry as EIA.  https://github.com/equinix/terraform-equinix-fabric/tree/v0.22.0/examples/virtual-device-2-eia-connectionBut none that creates the EIA itself. Can anyone answer if this may or may not be supported in terraform and if so, what would the resource name be for it? The GUI terminology doesn't always translate one for one, so maybe I'm missing something.  

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?

Hi! I’m working with a customer who is asking if our Equinix Internet Access supports rDNS/Reverse DNS? I can’t find any supporting documentation on the docs site, looking for product to confirm or deny. Thank you.

We have a great opportunity for you to share your experience with internet access. We need your input!  Your valuable insights will directly influence our planning for 2025 as we work towards enhancing your internet access experience. We want to make sure we address your pain points, cater to your needs, and improve the overall purchasing experience.      Interested in taking part in this 5-minute survey activity? Fill out survey below or click here to submit your feedback! Once you complete the activity, you’ll have the opportunity to sign up today for the Equinix Customer Insights Panel. Influence new ideas, processes, product releases, capabilities, and more through engaging research activities like this one!  Join, shape, influence, and innovate today! 

We have an exclusive opportunity where we are redesigning the Fabric experience within the Equinix Portal to make the navigation menu easier and more intuitive. Your feedback will have a direct impact to this redesign, ensuring a seamless, intuitive user experience within Fabric portal. Interested in taking part in this 5-minute survey activity? Fill out survey below or click here to submit your feedback! Once you complete the activity, you’ll have the opportunity to sign up today for the Equinix Customer Insights Panel. Influence new ideas, processes, product releases, capabilities, and more through engaging research activities like this one! Join, shape, influence, and innovate today!    

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.

How do you find your Account Manager on the Portal?Whats the procedure for moving a cross connect from one of our racks to the other?I know how I would do it. I don't want to set a date for it as thats what the portal wants me to do and I am not ready for that yet. Answers on a post card please or a phone call if possible.

Hi team,  Could someone explain the new BlueCat offering on Equinix Network Edge?

Is it possible to connect Network Edge devices to Fabric Cloud Router?

Hello everyone, We're using Virtual circuits between Fabric ports & Edge virtual devices, it works fine but still it's impossible to get the link usage statistics as for other circuits.Any news about that option that is missing? Thanks 🙂

 I saw that Equinix now offers subscription licenses for the Cisco 8KV on Equinix Network Edge.  Does this support 16 core/8G memory devices?

Can anyone explain what kind of support is available for the Cisco Catalyst 8000V?

This is first part of a series of posts highlighting the best practices for customers who desire highly resilient networks in Network Edge. This entry will focus on the foundational architecture of Plane A and Plane B in Network Edge and how these building blocks should be utilized for resiliency.For more information on Network Edge and device plane resiliency please refer to the Equinix Docs page here.Dual Plane ArchitectureNetwork Edge is built upon a standard data center redundancy architecture with multiple pods that have dedicated power supplies and a dedicated Top of Rack (ToR) switch. It consists of multiple compute planes commonly referred to as Plane A and Plane B for design simplicity Plane A connects to the Primary Fabric network and Plane B connects to the Secondary Fabric networkThe most important concept for understanding Network Edge resiliency: the device plane determines which Fabric switch is used for device connections. Future posts will dive much deeper in the vario

I've heard about the new Zscaler offering -- what is it?

..

This is the second part of a series of posts highlighting the best practices for customers who require highly resilient networks in Network Edge. This entry highlights how to build resilient Device Link Group (DLG) connections. For more information on Device Link Resiliency please refer to the Equinix docs page here.Device Link Groups are used to connect Network Edge device interfaces to other Network Edge device interfaces​ They can be local (same metro) or remote and are a shared broadcast domain​ A single DLG, like a single Ethernet cable, provides no resiliency​ Local DLGs do not traverse the Equinix Fabric and aren’t susceptible to Fabric switch outages ​ Hybrid DLGs have some devices connected to the Primary Fabric plane and other to the Secondary​ Customers that require maximum resiliency should deploy additional DLGs that connect to both the Primary and Secondary Fabric networks​ Redundant Devices can have one or both devices connect to the DLG​ Clustered devices act as one log

This is the fourth and final part of a series of posts highlighting the best practices for customers who require highly resilient networks in Network Edge. This entry highlights how to build resilient Fabric Virtual Connections.Virtual connections allow NE devices to connect to CSPs, NSPs and ISPs as well as co-location​ The same logic still applies: the NE device plane determines which Fabric switch is used​ The VC connection workflow is very similar to the EVP-LAN workflow with some differences​ Customers that require VC link resiliency should create two or more VCs to their NE devices with each connection traversing the Primary and Secondary fabric switch​ Some CSPs like Azure require resiliency but most do not​ The Fabric portal allows connections to be created as redundant or single-legged​ The workflow is highlighted in the next few slides for both Redundant and Clustered devicesRedundant Devices Clustered Devices This concludes a four part series on building Highly Resilient Net

This is the third part of a series of posts highlighting the best practices for customers who require highly resilient networks in Network Edge. This entry highlights how to build resilient EVP-LAN connections in Network Edge.EVP-LAN is another method to connection Network Edge devices EVP-LANs differ from DLGs in that they connect to Network Edge devices and Fabric ports​ All EVP-LAN connections go to the Fabric, even for devices in the same metro--this is in contrast to DLGs which can be local or remote.​ As of November 2023, multiple NE devices in the same metro can be part of the same EVP-LAN network, removing the previous restriction of a single NE device per metro.​ Customers that require maximum resiliency should deploy additional EVP-LANs that span both the Primary and Secondary Fabric networks The same logic applies for EVP-LANs such that they should spread across Primary and Secondary Fabric planes​ The current maximum bandwidth for all EVP-LAN connections in the same metro i

To help you connect, we have added "connectToCloudVision," "cvpType," "cvpFqdn," "cvpIpAddress," "cvaasPort," "cvpPort," and "cvpToken" fields. Check out the following pages for details: Launch Self-Configured Device Get Virtual Devices Get Virtual Device {uuid}  

Now you can monitor your Network Edge device utilization traffic by accessing your device details. In your Virtual Device Inventory, click on the device you want to monitor. In the Device Details, click the Interfaces tab. Expand the arrow next to the port you want to monitor and a graph will display showing Inbound and Outbound traffic for the last 7 days. Refresh the graph by clicking Refresh.Change the duration using the drop-down. Choose Last 7 days or Last 24 hours.

This spotlight video covers a few new features/functionalities in Network Edge 2023.10 release: General availability of Prosimo Connector in the Network Edge Marketplace Virtual Devices supporting DLG's between primary and secondary Fabric switches Virtual Device Re-Sizing Include/exclude components of a Solution Builder quote

Appreciate your help - How can I convert my CSR1000V Equinix-configured device to a C8000V self-configured device?