There are two ways to view your ports and connections. On the home page, your desired metro should be listed and will display your number of ports, your Layer 2 and Layer 3 connections. Click on the metro or your port number to take you to the other screen.
Buyers can view the Buy-side connections tab to see the services to which they are connected.
- By clicking the “Set Port Bandwidth Threshold Alert” link, you can set the percentage limit of bandwidth that will trigger an alert when it is met or exceeded. You can also enter the email addresses of the recipients for this alert. Once the threshold has been established, this link will change to “Edit Port Bandwidth Threshold Alert.” Clicking it will allow you to change the threshold percentage and list of email alert recipients
- Sellers can view the Seller-side Connections tab to see all of the virtual connections to their services
The following information is displayed on the Connections page for the buyer (A-side). This information was assigned when the Port and Connections were created and the information was returned by Equinix and the seller (e.g., the CSP). Please note that monitoring information unique to whichever service connection is used appears in the Connections tab when the VC is expanded.
- IBX location of this port on the Equinix Cloud Exchange Platform: This may be different than the IBX data center where your cage is located, as our platforms are connected within the metro
- Ports: The total number of ports which have been turned up for your company
- Connections: The total number of Layer 2 Connections and Layer 3 Connections provisioned in the IBX data center
Note: The Pending tab applies to sellers only. It displays connection requests from buyers to add or delete services awaiting the seller’s action to “approve and connect” or “reject” with an explanation.” Sellers can use this tab to complete any pending requests.
- Ports: the name of the Equinix Cloud Exchange Port on the platform
- Cable ID: this ID uniquely identifies the cross connect from your company’s cage to the Equinix Cloud Exchange Port. If the port includes more than one physical port which has been aggregated through link aggregation (LAG), the physical ports will be under one port name, and the cross connect ID will show all the cross connects for each of the physical ports (e.g., 1G).1G indicates two 1G ports were aggregated with LAG under the same logical port name
- Port Encapsulation: the encapsulation of the port. Options are Dot1Q and QinQ
- Port Speed: physical port speed of 1G or 10G
- Layer 2 Connections: the number of L2 connections on this Initially it will be zero
- Layer 3 Connections: the number of L3 connections on this Initially it will be zero
Note: An A-side buyer is not required to have ports in the same IBX as Z-side sellers. They should be in the same metro. Equinix will connect buyers to sellers transparently.
Buyer-side connections by metro (view with filters)
Connections by metro and destination metro (local and remote)
Add filter views by using the drop-down menus on the top row
Expand the details of the port by clicking on the grey arrow button before the port’s name. This extended view will show Layer 2 connection details.
- Connection ID: unique service ID to identify the L2 Cloud This can be used when creating a ticket to Equinix support to troubleshoot issues with your L2 Cloud Connection
- Seller-side VLAN ID: the VLAN ID assigned and returned by Azure ExpressRoute. This is the Outer Tag (also known as sTag) on the Z-side, (i.e. Azure ExpressRoute-side)
- Seller-side Port: the port assigned and returned by Azure ExpressRoute for which the buyer’s connection is provisioned