Yes, the Equinix Internet Exchange provides an Ethernet switch fabric over which networks can exchange IP traffic.
Yes, all connections to the Equinix IX are over Ethernet. Our policies limit participants to a single MAC address per port and do not allow layer 2 protocols such as Spanning Tree to be shared between customer devices over the Equinix switching fabric.
Yes. Equinix filters all IX traffic on the MAC address each participant has registered. If you change the device connected to the IX, please email email@example.com with your new MAC address.
Equinix will assign an IP address from its allocated subnet for use on the IX. Equinix will also maintain the in-addr PTR record you provide for this IP address.
Yes, there are multiple peering discussion lists:
On a global level, firstname.lastname@example.org can be used to make announcements to your peers or to discuss related topics. To subscribe, please email email@example.com with a request to be added to the firstname.lastname@example.org mailing list.
Each of the AP Exchanges in Hong Kong, Tokyo, Singapore, and Sydney, have separate discussion and announcement lists as well. You can manage your subscriptions to these lists at http://lists.ap.equinix.com/mailman/listinfo.
Yes, when you peer with the Equinix Corporate network (AS14609) it includes the IBX Kiosk wireless network. When peering is established with AS14609 you will eliminate transit hops and latency between the IBX Kiosk wireless and your equipment in the IBX. To establish peering with AS14609 please email email@example.com.
Yes, participants can add capacity by using link aggregation groups to bind multiple ports into a single logical port.
Yes, Equinix supports remote connections to IX switch hardware from networks not physically present in our facilities. All Equinix IX policies apply as well as an additional Remote Connection policy.
Yes, Equinix calls this service the Multi-Lateral Peering Exchange (MLPE), and maintains a redundant pair of route servers at each IX for this purpose. We support IPv6 at all MLPE locations and BGP communities for route control at many. For full description of this service, and to request participation, please visit the MLPE Registration Page.
MLPE participants should configure 'no bgp enforce-first-as' and 'next-hop-self' (or similar commands for your implementation). We recommend a Max-Prefix setting of 50,000, which is roughly double the number of prefixes announced at our largest MLPE sites.
Equinix is a neutral player; while we encourage our participants to foster an open exchange environment, we do not exercise any control over the routing or peering policies of any participants. If there is a technical issue we can help you resolve, we are more than happy to help, but we cannot influence the peering policies of our customers.
Absolutely. Equinix supports assignment of IPv6 addresses and reverse DNS for dual-stack peering on the same peering port as IPv4. To be assigned an IPv6 address please email the request to firstname.lastname@example.org.
Please email email@example.com for your IPv6 address assignment.
Based on customer demand for redundant peering presences in those locations, we are keeping the fabrics in Silicon Valley and the Washington DC metro separate. If you have any questions about fabric reachability options, please email firstname.lastname@example.org.
In general, we do not provide connectivity options between sites in different regions, however we can assist in connecting to Palo Alto or San Jose from local Equinix sites and have options between Zurich and Geneva as well. For additional information on connectivity options, please email email@example.com.
Equinix Metro Abbreviations
|DC||Washington DC (Ashburn)|
|NY||New York Metro|
|SV||Silicon Valley (San Jose)|