1
l SOLUTION BRIEF l
S E C U R I T Y
PHYSICAL CROSS-CONNECT
CONNECTIONS (DIRECT
CONNECT) OVERVIEW
Physical cross-connects are available in the
following locations:
• Ashburn (DC6)
• San Jose (SV1)
• Amsterdam (AM7)
• Frankfurt (FR5)
• Sao Paulo (SP4) – Target availability
December 2019
Introduction
For larger clean network traffic rates, and for business-critical latency sensitive applications,
organizations require performance that can exceed the capabilities of Generic Routing
Encapsulation (GRE) tunnels.
Customers of Arbor Cloud achieve decreased latency and increased reliability in clean
traffic transportation back to their network through a direct connection from the Arbor
Cloud infrastructure. This direct connection functionality can help with an increase in both
performance and data integrity to the customers network during a mitigation event.
NETSCOUT's Arbor Cloud solution features two ways to directly connect into the platform for a
customer to receive clean traffic.
• Equinix Cloud Exchange (ECX) fabric
• Physical Cross-Connect (Direct Connect)
Equinix ECX Connections Overview
The Equinix Cloud Exchange is a multi-location, multi-national switching fabric that was set
up by Equinix to provide a mechanism for their customers to establish logical connections
between services located in different geographic locations serviced by Equinix. Customers that
contract a local connection to one of the Cloud Exchange datacenters are then able to contract
a logical circuit to another service that is connected to an Equinix Cloud Exchange datacenter.
The remote service could belong to the same customer, a partner, a cloud provider, or a service
vendor. More information is available about ECX at https://ecxfabric-documentation.equinix.
com/hc/en-us. Customers can use Equinix ECX connections to directly connect to Arbor Cloud
when they have existing Equinix access in an Equinix datacenter or it is convenient for them to
establish a connection in a local Equinix datacenter. This allows for a Layer 2 (L2) ECX port to
be built between the NETSCOUT
®
Arbor Cloud ECX instance and the customer. The customer is
responsible for creating the ECX connection and connecting into the Arbor Cloud service profile
built into the ECX provisioning portal.
The NETSCOUT Arbor Cloud platform can accept ECX connections into the following
Equinix facilities:
• Ashburn (DC2)
• San Jose (SV1)
• Amsterdam (AM7)
• Frankfurt (FR5)
• Sao Paulo (SP4) – Target availability December 2019
Customers connected to the ECX fabric in any ECX enabled Equinix facility can use the ECX
switching fabric to connect logically into the Arbor Cloud DDoS Protection Platform.
Direct Connections for Clean Traffic Return Post
Mitigation Event Can Increase Data Integrity
