Configuring BGP
Fabric Cloud Router uses BGP routing protocol, and supports several features that enable users to manage how traffic is routed to support complex topologies.
Once you have created a connection on your Fabric Cloud Router, you can configure its routing from your Connections Inventory. Select the connection you want to configure.
On its Routing Details tab, click Configure Routing.
If you are updating or editing a previous configuration, on the Routing Details tab, click Edit in either the Direct or BGP Routing Details sections.
Routing Details - Direct
Select the type of subnet to provide: Enter my own IPv4 address.
Enter an Equinix-side IPv4 address using CIDR notation. /30 is sufficient, but /28 and /29 also are permitted. If you're using IPv6, also enter the the IPv6 address using CIDR notation.
Routing Details - BGP
To enable management of additional BGP routing, select Enable Border Gateway Protocol (BGP).
IPv4 and IPv6 Peer Addressing
Fabric Cloud Router (FCR) supports IPv4 and IPv6 addressing. Each address type can be configured independently or concurrently (dual-stack). Each virtual connection created from the FCR requires configuration of a local (FCR) and remote peer IP address for each IP protocol version used on the connection. In most cases, you can define the BGP peering subnet to use, unless the remote peer, such as Google Cloud, requires specific addressing.
Enter a Peer IPv4 host address and optionally, a Peer IPv6 host address.
MD5 Authentication
Cloud Router supports the use of MD5 authentication as specified by RFC2385, which provides an additional layer of security for BGP by requiring participating BGP peers to have matching MD5 authentication keys.
Fabric Cloud Router MD5 authentication supports up to 80 ASCII characters, unhashed.
If you are using BGP Authentication, enter the shared secret. Make sure that the secret matches on both the Fabric Cloud Router side and the remote side of the connection.
Maximum Routes Received for IPv4/v6 (Max Prefix Limit)
Cloud Router supports the ability to configure the maximum routes to receive from a particular peer. This allows you to configure a maximum number of routes to allow a peer to advertise to the Cloud Router before resetting BGP sessions.
If a peer advertises more than the configured limit for the connection, the Cloud Router resets the BGP session for 5 minutes before re-establishing the session. Also, configuring or updating a maximum limit after the session has been established triggers a reset of the BGP session.
Enter the Max Prefix Limit(s).
Allowed Values - between 1 and the Cloud Router package IPv4/v6 route quota.
Default – Cloud Router package route quota limit. If the you do not configure this value, it defaults to the IPv4/6 quota for the Cloud Router. For more information about the Cloud Router packages, see Service Packages.
Peer ASNs
The peer Autonomous System Number (ASN) for the remote BGP peer provides Layer 3 connectivity. Cloud Router supports both registered (public) ASN and private ASN ranges. Cloud Router uses unique Equinix-registered ASNs in each Fabric metro to avoid potential conflicts with private ASNs. Cloud Routers within a given metro always use the same registered ASN, and do not currently support user-configured ASNs.
Cloud Router allows use of 2-byte or 4-byte ASNs (1-4294967294), except for the numbers listed below.
| ASN | Purpose |
|---|---|
| Special purpose numbers: | |
| 0 | Reserved by RFC7607 |
| 112 | Used by the AS112 project RFC7534 |
| 23456 | AS_TRANS; reserved by RFC6793 |
| 64496–64511 | Reserved for documentation by RFC5398 |
| 65535 | Reserved by RFC7300 |
| 65536–65551 | Reserved for documentation by RFC5398 |
| 4294967295 | Reserved by RFC7300 |
| Equinix-reserved numbers: | |
| 64600, 4200000000–42000000002 |
Enter your Peer ASN.
AS Path Prepend
Cloud Router supports outbound AS path prepend, which allows you to set the number of prepends to the AS path. With values set larger than 0, the Cloud Router adds its own ASN to the AS path based on the value of the prepend that you select. When using prepending, this increases the length of the AS path. This indicates to the BGP peer that a particular connection might be less preferred, because one of the parameters that BGP relies on for route preference is the number of Autonomous Systems (AS) between BGP peers. A longer AS path is typically less preferred, unless another BGP operation has a higher priority over the AS path length.
Supported FCR AS-Path Values: Disabled, 1, 3, 5
Default: Disabled (no prepending will occur)
To enable, select the AS-path value from the drop-down.
AS Override
Cloud Router supports user-enabled AS override, which overwrites one or more instances of the BGP peer ASN found within the AS path advertised by FCR.
When one or more Fabric Cloud Routers (multiple Cloud Routers connected to an IP-WAN network) are used to interconnect networks using the same Autonomous System Number (ASN), AS override can be used to disable the default eBGP loop prevention mechanism.
Example: AS override on FCR might be desired when a user has Cloud Routers in multiple metros such as Dallas and Ashburn (Washington D.C.) interconnected via IP-WAN. The user also has connections to a cloud provider (such as Oracle, Azure, or Google) that uses a single global ASN for all cloud regions in both locations. The user might prefer that their inter-region traffic between cloud regions be routed through Cloud Router and IP-WAN rather than the cloud provider’s network. In this case, AS override can be enabled on each cloud provider FCR connection, and traffic between the cloud regions will be permitted, because the AS-Path of advertised prefixes will not include the cloud provider’s originating ASN in the AS-Path.
Supported AS Override Settings: Disabled, Enabled
Default: Disabled
To enable, select Enable AS Overide.
Multi-Exit Discriminator
Cloud Router supports user-configured Inbound and Outbound Multi-Exit Discriminator (MED) for each connection. Default use of the MED parameter requires more than one connection between neighboring ASes.
MED parameters are optional, allowing you to suggest to a peer the preferred connection that the peer should use to send traffic to the originating AS. MEDs can also be applied locally to received (inbound) prefixes to influence which connection could be used to send traffic to the neighboring AS. When configuring a MED, values with a lower number are preferred over those with a higher number.
- Inbound – The MED value that the user applies to a connection to influence the local routing decision to prefer this connection over another for traffic sent to the neighboring AS.
- Outbound – The MED value that is advertised to a neighboring AS to suggest a preferred connection for traffic sent to this AS.
Cloud Router-supported MED values: 1 – 4294967295
Enter your Inbound and Outbound MED values.
Bidirectional Forwarding Detection (BFD)
Cloud Router supports user-enabled BFD for each virtual connection, which can assist with the amount of time required to detect and propagate any changes with BGP routes as part of reconvergence, including minimizing interruptions due to fail-over events. You can configure the BFD TX interval at which the Cloud Router will announce to the BGP peer.
Cloud Router-supported BFD TX intervals: 100 – 999 (in milliseconds)
Default: BFD Enabled = False
BFD Multiplier: 3x (This value is not user configurable.)
If you would like to use Bidirectional Forwarding Detection (BFD), select Enable BFD and set the appropriate interval in milliseconds. The BFD interval must match on both sides of the connection.
Applying Changes
Once you have updated the Routing Details, click Apply Changes. If the connection status was Pending Interface Configuration it is updated to Provisioned.
