COMMAND LINE
Copy to clipboard
Metros¶
Equinix Metal™ Metros are facilities that are grouped together geographically and share capacity and networking features.
Provisioning within a Metro¶
When you provision a server you select the Metro where you want your server to live. We then determine which specific facility within the Metro your server physically resides in based on a variety of factors including the capacity of the Metro and the entitlements of your account or organization. Metro-based provisioning is supported through all the deployment options: On-Demand, the Spot Market, Reserved Hardware, and Batch Deployments.
It is still possible to provision in specific facilities if you need to. More information is on the Facilities page.
Metro-level Networking¶
The facilities in a Metro are interconnected by high-speed links with typical latency within less than 5 milliseconds in a Metro and there is no billing of traffic between facilities within a Metro. Additionally, many of our Networking features are designed to take advantage of this.
- VLANs - When you provision a VLAN in a Metro, all servers in that Metro are able to connect to it.
- Elastic Public IPv4 Addresses - When you request an Elastic Public IPv4 address, you will be able to assign it to any server in the Metro where you requested it.
- Private IPv4 Addresses - While the blocks of private IPv4 addresses are facility-based, all there servers within a project in the same Metro can use them to connect to each other. If you need to set up connections between servers in different Metros, you can use Backend Transfer.
Metros Quick Reference¶
Core¶
Core metros have servers available for provisioning On-Demand, through the Spot Market, and through ordering Reserved Hardware.
Region | Metro | Code | Facilities |
---|---|---|---|
AMER | Washington DC | DC | dc13, iad1, iad2 |
AMER | Dallas | DA | da11, dfw2, dfw1 |
AMER | Silicon Valley | SV | sv15, sjc1 |
EMEA | Amsterdam | AM | am6, ams1 |
EMEA | Frankfurt | FR | fr2, fra2 |
APAC | Singapore | SG | sg1, sin2, sin3, sin1 |
APAC | Sydney | SY | sy4, syd2 |
Expansion¶
Expansion metros have servers that are only available through a Hardware Reservation.
Region | Metro | Code | Facilities |
---|---|---|---|
AMER | Chicago | CH | ch3, ord1, ord4 |
AMER | New York | NY | ny5, ny7, ewr1 |
AMER | Los Angeles | LA | la4, lax1, lax2 |
AMER | Toronto | TR | tr2, yyz1 |
APAC | Hong Kong | HK | hk2, hkg2 |
APAC | Seoul | SL | sl1 |
APAC | Tokyo | TY | ty11, nrt1 |
API Endpoints¶
Information about individual facilities is available from the /locations/metros
endpoint.
Sending a GET
request to the /locations/metros
endpoint will return a list of data centers where your user account is able to provision with lots of information about each, including name, code, ID.
curl -X GET -H 'X-Auth-Token: <API_TOKEN>' https://api.equinix.com/metal/v1/locations/metros
Capacity¶
To check capacity at all Metros, make a GET
request to the /capacity/metros
endpoint.
curl -X GET -H 'X-Auth-Token: <API_TOKEN>' https://api.equinix.com/metal/v1/capacity/metros
Capacity responses are one of the following:
- Normal - There are plenty of servers available.
- Limited - There are servers available, but the stock is limited.
- Unavailable - Servers of a particular type and data center combination are not available.
You can also check quantity of what is available in a specific Metro by sending a POST
request to /capacity/metros
endpoint, with the Metro and plan set in the body of the request.
curl -X POST \
-H "Content-Type: application/json" \
-H "X-Auth-Token: <API_TOKEN>" \
"https://api.equinix.com/metal/v1/capacity/metros" \
-d '{
"servers": [
{
"metro": "<metro_code>",
"plan": "<server_type>",
"quantity": <integer>
}
]
}'
If the request will succeed, the servers
object will contain an additional field "available":true
in the response. If the request will fail, the the servers
object will contain an additional field "available":false
in the response.