A connector brings two other components together. In the context of a basic Layer 3 service, this is between a port and an RI, though it can and will have other functions in the future. If the port is a tagged interface, the connector does this with a VLAN. The nature or setup of both the port and RI are generally not relevant and do not affect how the connector is configured, except as noted below in limitations.
Connecting a port and an RI together allows a user to peer with Equinix using eBGP at either end of the below diagram:
A connector has the following required parameters to create:
- Select RI: to which RI will this connector be attached
- Select Port: to which port will this connector be attached
- Connector name: this will default to “[port name] to [RI name]” but the user may enter any value they want, as long as it is unique to their account and that metro
- Conditional (C-Tag): if the selected port is a Dot1Q or a Q-in-Q port, user enters a valid VLAN value (if the port is untagged no VLAN is entered)
- Conditional (S-Tag): if the selected port is a Q-in-Q port, user enters a valid VLAN value (if the port is untagged, no VLAN is entered)
- Notifications: user indicates any email addresses to receive notifications about this component
The following optional services are available on the Connector component:
- Policer: User can add a policer to any connector that will set a traffic rate limit; at or below the capacity of the port it is connected to, using the VLAN as the sub-interface. All traffic to and from the RI from all subscriptions that are not dedicated, will be limited to this speed. It is also the speed from which the billing tier is derived on a connector. Some notes:
- In the absence of a Policer, the speed tier is assumed to be the same as the port to which it is attached
- The user may select any speed from the default settings at each speed tier, or enter a custom speed on their own
- If a service mandates a speed, the Policer becomes mandatory
- Bi-directional forwarding detection: This enables a specific protocol that the connector uses when associated to an RI. The BFD protocol allows detection of a BGP signal and is generally used as a monitoring feature to determine if peering is active on a particular link.
At this time, the connector component is limited to connecting one port and one RI together. As the connector is a generic component, however, users should be aware it will not always be limited to this and will apply in many other scenarios.
Once provisioned, assigned IP addresses will appear on the connector details for a user to create their own configurations, but do not appear until orchestration is complete.
Although users can create multiple connectors from the same or multiple ports to the same RI, the system will not allow connectors from more than one chassis group to the same RI.