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

Layer-2 Point-to-Point Design Tips for VXCs

· 1 min read · Peer1IX Team

Layer-2 Point-to-Point Design Tips for VXCs

VXCs are simple, but a few design details — MTU, VLAN tags and routing — make the difference between smooth and painful.

MTU

Agree on the MTU with the other side. If one end sends larger frames than the path supports, some traffic will fail in ways that are hard to diagnose. Test with large pings after activation.

VLAN tags

On the fabric, each party’s VLAN tag only matters on its own port. You and your partner can use different VLAN IDs for the same VXC.

Addressing

Use small point-to-point subnets: /31 for IPv4 and /127 for IPv6 where supported, or /30 and /64 if not.

Routing

Run BGP over the VXC for dynamic routing and failover. Filter what you accept.

Failure detection

BFD speeds up detection of path problems.

Documentation

Record the circuit ID, VLANs, addresses, bandwidth and contacts for both sides. It saves time during incidents.

layer 2point-to-pointMTUdesign