Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Redundant Private Links With Diverse VXCs

· 1 min read · Peer1IX Team

Redundant Private Links With Diverse VXCs

A single VXC depends on one port at each end. How to design redundant private connectivity on the fabric.

Where the risk is

A VXC depends on your port, the partner’s port and the fabric between them. If either port fails, the VXC goes down.

Design for redundancy

  • Each party connects with two ports, ideally on different devices or in different locations.
  • Create two VXCs, one between each pair of ports.
  • Run BGP over both, with one preferred or both active.

Location diversity

For critical relationships, terminate the two VXCs in different Peer1IX facilities.

Test

Disable one VXC during a planned window and confirm that traffic fails over within your expectations.

redundancydiverse pathsVXC