Skip to main content

Devices on Multiple VLANs with Full IP Control and Connected to multiple Cloud Providers' VPC Subnets

Networking Architecture (Scenario 13) - Creating a network where devices are linked on a shared layer 2 VLAN with full IP control, directly connected to subnet in multiple VPCs on multiple cloud provider.

Devices on Multiple VLANs with Full IP Control and Connected to multiple Cloud Providers' VPC Subnets

In this scenario:

  • No devices are connected directly to the Internet; there are no Internet connections at all
  • No devices are connected directly to Equinix Metal's private network
  • Devices communicate with each other shared Layer 2 VLANs
  • Devices use private IPs allocated by you and not by Equinix Metal
  • Devices connect to subnets in multiple VPCs on your cloud providers
  • Each subnet, whether in cloud provider VPCs or in Metal VLANs, is in unique IP range

You have one or more isolated VLAN. All of your devices are on those VLANs, and can communicate at Layer 2 with other devices on the same VLAN. Those devices can communicate privately with servers and services in subnets in multiple VPC on your cloud providers, and on the other VLAN. The VPCs and subnets have address ranges distinct from each other, as well as from the VLANs, and therefore communication happens over layer 3, i.e. routing.

Devices receive no private or public IP addresses from Equinix Metal.

General Layout

As you have multiple networks - VPCs in cloud providers, VLANs in Equinix Metal - you need two things to be able to send traffic between them:

  • connectivity - actual networking connectivity between the networks: Equinix Fabric
  • routing - knowledge of how to route traffic between the networks: Virtual Routing and Forwarding

Equinix Fabric is the connectivity between the cloud providers and Metal VLANs. You deploy a Virtual Connection (VC) to link each pair of one of the VLANs, via a Metal Gateway, with each cloud provider. Virtual Routing and Forwarding (VRF) provides the routing functionality between the pairs of networks over the Fabric VC. You deploy a single VRF that handles all of the connections.

  1. Select a unique IP range for each VLAN, distinct from the IP ranges in use in your VPCs or other VLANs.
  2. Deploy Equinix Metal VRF. Ensure that your allowed_ips ranges cover the IP ranges that you will use on all of your VLANs.
  3. Reserve the IP ranges for each of your VLANs from inside the VRF configuration, using ip_reservations.
  4. For each VLAN:
    1. Create the VLANs.
    2. Create a Metal Gateway, attached to the VLAN and the single VRF.
    3. Create as many devices as you desire, without a public or private IP address but connected to the VLAN. For each device:
      1. Retrieve the port ID for the network port, using the Equinix Metal console or API.
      2. Assign that network port to the VLAN, using the Equinix Metal console or API.
      3. ssh into the device, assign an IP address of your choosing, and set the default route of the device to the previously retrieved "gateway" address for the IP reservation.
  5. For each cloud provider VPC:
    1. Deploy an Equinix Fabric Virtual Connection (VC) between the VRF and the VPC subnet.

Comms

Last updated

15 May, 2024

Category

Tagged

Article
Subscribe to our newsletter

A monthly digest of the latest news, articles, and resources.