The world of network architecture is vast and complex. Equinix Metal offers a robust suite of networking solutions tailored to fit diverse needs and workloads. To ensure you’re composing the best “fit for purpose” architecture, there are a few key decision points and considerations. We’ve designed the following decision tree as a tool to help guide you through this decision-making process.
Select a specific IP range, deploy a VLAN and connect the devices to that VLAN
Provides each device with private and optional public IP address
Start overSome devices can connect directly to the internet and the rest connect to the internet via NAT Gateway
Start overDevices use private IPs allocated by you and not by Equinix Metal
Connected on different layer 2 VLANs, some utilizing Equinix Metal
Start overDevices use private Ips allocated to you by Equinix Metal single or multi metro
Start overDevices communicate a single, shared VLAN and use private Ips allocated by you in a single metro
Devices connect to a subnet in a VPC on your cloud provider and the subnet is in a different IP range than the VLAN
Start overThose devices can communicate privately with servers and services in a subnet in a network in your colocation cage
Start overProvides each device with private and optional public IP addresses
Each and every device receives a public IPv4 address and a private IPv4 address. Each device is on its own private subnet, to which just the device and its upstream router are connected.
Start overEvery device is connected to each other but not to the internet
Each and every device receives only a private IPv4 address and is on its own private subnet
Some devices are directly connected to the internet while all devices are interconnected
Each and every device receives a private IPv4 address and subnet, those that should be connected to the internet also receive a public address
Classic protected set of devices, where they all can communicate with each other, but do not have public IP addresses
Each normal devices receives only a private Ipv4 address. In addition, a few devices dedicated to routing traffic to and from the internet also receive a public address. Each device is on its own private subnet
Deploy the devices as is, and use the public IP addresses to communicate between them or set up a VPN and Backend Transfer. If no internet, Backend is the only option
Start over