BGP Reference

A BGP session requires the following:

  • 2 ASNs: A cloud-side ASN and a PacketFabric-side ASN
  • 2 router IP addresses: A cloud-side router and a PacketFabric-side router
  • 2 sets of allowed IP prefixes: IP addresses going into the cloud and those originating in the cloud

Supported ASNs

Cloud-side ASN

The cloud-side ASN is either set by the cloud service provider (CSP) on your behalf (Microsoft Azure, IBM Cloud), or you manually select it when creating a VPC gateway (AWS, Google Cloud).

NOTE: In some cases, the cloud service provider (CSP) allows a wider range of ASN values, such as 4-byte ASNs. The tables below reflect what is supported by both PacketFabric and the CSP.
  • Row
    • Cloud
    • ASN
    • Notes
  • Row
    • Amazon

    • 7224

      64512 to 65534

    • You specify the Amazon-side ASN when you create the AWS Direct Connect Gateway or AWS Virtual Private Gateway. Public virtual interfaces use the Amazon public ASN 7224.

      The Amazon-side ASN is also listed on the VIF details page.

  • Row
    • Google

    • 16550**

    • You specify the Google-side ASN when you create the Google Cloud Router.

      Google requires that you use ASN 16550 on all Google Cloud Routers associated with Partner Interconnect VLAN attachments.

      ** If you are using the PacketFabric Cloud Router to connect two separate Google Cloud environments, then only one of those Google connections can use the 16550 ASN. In this case, you must configure a private ASN on the Google Cloud Router after associating it with the VLAN attachment. See Google-side ASN workaround.

  • Row
    • Microsoft
    • 12076
    • Microsoft sets this ASN for all ExpressRoute peerings on your behalf. It cannot be changed.
  • Row
    • IBM
    • 13884
    • IBM sets this ASN for all Direct Link peerings on your behalf. It cannot be changed.

PacketFabric-side ASN

You set the ASN when you create the PacketFabric Cloud Router. It can be our public ASN 4556 or a private ASN of your choice.

After you add a connection to the Cloud Router, you must supply this ASN when configuring peering on the cloud side. Where you supply the ASN varies depending on the cloud service provider (CSP).

  • Row

    • Cloud
    • ASN
    • Notes
  • Row

    • Amazon
    • 4556
      64512 to 65534
    • Enter the ASN into the BGP ASN field when creating a virtual interface in the AWS console.
  • Row

    • Google
    • 4556
      64512 to 65534
    • Enter the ASN into the Peer ASN field when configuring BGP in the Google Cloud console.
  • Row

    • Microsoft

    • 4556
      64512 to 65514
      65521 to 65534

    • Enter the ASN into the ASN field when configuring peering in the Azure console.

      Microsoft reserves ASNs 65515 to 65520 (inclusive) for internal use.

  • Row

    • IBM

    • 4556
      64514 to 65099
      65101 to 65200
      65235 to 65401
      65434 to 65499
      65501 to 65534

    • PacketFabric automatically sends the Cloud Router ASN to IBM on your behalf.

      IBM reserves the following ASNs: 64512, 64513, 65100, 65201-65234, 65402-65433, and 65500.

For example, if you intend to route traffic between Google Cloud, IBM, and AWS, you can set your PacketFabric Cloud Router to 65515. But this means you cannot add an Azure connection to that Cloud Router, as 65515 is reserved by Microsoft.

Router IP addresses

In every case except for Microsoft Azure, the CSP generates both router IP addresses on your behalf. All that is left for you to do is copy and paste those addresses when configuring BGP on the PacketFabric side.

  • Row

    • Cloud
    • Notes
  • Row

    • Amazon

    • By default, the router IPs are automatically generated when you create the AWS virtual interface (VIF).

      If necessary, you can specify your own IP addresses under the Advanced settings section of the virtual interface form. However, we recommend that you allow AWS to provide them on your behalf.

      PacketFabric fields:

      • Amazon Router Peer IP: Enter the Amazon router peer IP provided with the VIF.
      • PacketFabric Router Peer IP: Enter Your router peer IP provided with the VIF.
  • Row

    • Google

    • The router IPs are automatically generated when you accept the connection from the Google side. They cannot be modified.

      PacketFabric fields:

      • Google Router Peer IP: Enter the Cloud Router IP provided for the VLAN attachment.
      • PacketFabric Router Peer IP: Enter the On-premises router IP provided for the VLAN attachment.
  • Row

    • Microsoft

    • Azure is the only CSP that requires you to select IP ranges instead of automatically generating them on your behalf.

      Regardless of whether you intend to use both primary and secondary connections, you must supply a subnet range for each when configuring peering on the Azure side.

      From there, the router IPs are derived from the subnet ranges you provide. The first usable IP is allocated to the PacketFabric Cloud Router, and the second is allocated to the Microsoft edge router.

      For example, if you enter 192.168.100.128/30, the PacketFabric Cloud Router peer IP address is 192.168.100.129 and the Microsoft peer is 192.168.100.130.

      PacketFabric fields:

      • IPv4 primry subnet: Enter the same value you provided in the IPv4 Primary subnet field when configuring private peering in the Azure portal.
      • IPv4 secondary subnet: Enter the same value you provided in the IPv4 Secondary subnet field when configuring private peering in the Azure portal.

      PacketFabric will programmatically select one from which to assign the peer IP addresses.

      NOTE: At this time, Cloud Router does not support the Microsoft public peering option.
  • Row

    • IBM

    • The router IPs are automatically generated and configured on your beahalf when you create the Direct Link connection.

      PacketFabric fields:

      • IBM Router Peer IP: This corresponds to the IBM CIDR value in the IBM Cloud Console.
      • PacketFabric Router Peer IP: This corresponds to the User CIDR value in the IBM Cloud Console.

BGP statuses

The following statuses appear when viewing connections in the portal:

  • Row
    • State
    • Meaning
  • Row
    • Not configured
    • The BGP settings have not been entered yet.
  • Row
    • Configuring
    • The BGP settings have been sent to the device, and a session is being established. This can take up to 10 minutes.
  • Row
    • Fetching
    • Fetching BGP session. This can take a up to 10 minutes, depending on the cloud service provider.
  • Row
    • Established
    • BGP session is configured and can pass traffic.

Annotated screenshots

Google Cloud Platform