For Network Connectivity Use Cases, Customers ask for direct Server VLAN to Server VLAN L2 Remote Connections via Fabric on Metal billed Ports. Dedicated Ports are commercially prohibitive. Can we enable Metal to Metal L2 VCs on Fabric?

Enable connectivity from Metal VRFs to a Fabric Cloud Router via BGP

Enable connectivity from Metal Server to a Fabric Cloud Router using a Static IP Address

Currently BGP sessions for Layer 3 management networks are limited to the primary / first IP of the network. If a user deploys a server with a larger subnet size such as /29 it's not possible to have BGP sessions from the other IPs inside the same subnet. It has to be the first available host IP. This is useful for certain situations such as deploying a virtual network functions appliance or Google Anthos Layer 3 bundled load balancers with BGP.

Cloud-inspired load balancer service for distributing traffic to Metal servers and appliances. At launch, Equinix Metal's Load Balancers will support users deploying a fully managed L3/L4 network load balancing from the Metal portal interface. Load Balancers will initially support public traffic on the ingress virtual IP (VIP). No private NAT or network traffic for real servers will be supported at launch.

Currently only dedicated fabric ports can participate EVP-LAN. Being service token based, Metal VCs are not able to participate EVP-LAN. It'd provide great benefits for Metal customers to enable metal fabric VCs to join EVP-LAN

Some use cases require dozens or even hundreds of VLANs. Currently, projects are limited to 5 VLANs , with no formal path for buying or unlocking more (support can increase the limit modestly). Provide a service tier or a way for users to safely deploy and manage up to ~100 and then up to max (~4k) VLANs.

Would like to be able to setup a bgp session from a virtual machine running on an ESX instance, without having to use the ip of the physical instance.