Metal and Network Edge (Layer 2)
Users can implement a simple network design between Equinix Metal and Network Edge. Because Equinix Fabric (the underlying network service connecting both services together) is a Layer 2 VLAN between both endpoints, it is possible to have a single subnet spanning Network Edge and Equinix Metal. This is the most basic method to establish connectivity between NE and a small group of Metal instances.
Important: This is a single broadcast domain that might not be suitable for all situations. Consideration should be given to other designs as the Metal workloads expand.
For this scenario, we’ll use a basic Layer 2 connection between Network Edge and Equinix Metal. A single subnet, 172.16.0.1/24, will be configured on both the NE device and the Metal Server.
This configuration assumes the following steps are complete:
Metal instance created
Network option changed to Hybrid Bonded
Sub-interface on Metal instance created
Equinix Fabric connection requested
A new VLAN created in Metal Console
Fabric connection attached to VLAN in Metal Console
Network Edge instance created
Fabric connection created between Network Edge and Equinix Metal
Network Edge, Cisco CSR100v router (Equinix-Configured Device)
Equinix Fabric Virtual Connection
Equinix Metal c3.medium.x86 instance
Equinix Metal Configuration
Create the sub-interface on the Metal server with the IP address 172.16.0.100.
Make sure the Metal server is attached to the VLAN for the Fabric Virtual Connection.
Network Edge Configuration
Log in to the Equinix Fabric Portal and locate the Network Edge devices.
Identify the interface for the Fabric connection to Metal.
SSH to the Network Edge Cisco CSR1000v Virtual device and double check the interface assignment.
NE1>sh int des
Interface Status Protocol Description
Gi1 up up MGMT interface
Gi2 up up SSH Interface
Gi3 admin down down
Gi4 admin down down
Gi5 admin down down
Gi6 admin down down
Gi7 admin down down
Gi8 admin down down
Gi9 admin down down
Gi10 admin down down
Lo10 up up Public Access to VNF
Configure GigE10 on the Cisco router.
Enter configuration commands, one per line. End with CNTL/Z.
NE1(config-if)#vrf forwarding cloud
NE1(config-if)#ip address 172.16.0.50 255.255.255.0
Verify network connectivity to Metal Instance. Ping from NE to Metal.
NE1# ping vrf cloud 172.16.0.100
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.0.100, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Tip: For Equinix-configured devices, ensure the ping command includes vrf cloud.
Ping from Metal to NE.
[root@metal1 ~]# ping 172.16.0.50
PING 172.16.0.50 (172.16.0.50) 56(84) bytes of data.
64 bytes from 172.16.0.50: icmp_seq=1 ttl=255 time=0.766 ms
64 bytes from 172.16.0.50: icmp_seq=2 ttl=255 time=0.821 ms
64 bytes from 172.16.0.50: icmp_seq=3 ttl=255 time=0.811 ms
64 bytes from 172.16.0.50: icmp_seq=4 ttl=255 time=0.803 ms
--- 172.16.0.50 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.766/0.800/0.821/0.028 ms
Metal and Network Edge are now connected at Layer 2.