Configure BGP for Port Connections

Before you begin, ensure you have completed the steps outlined in Add a Connection from a Port to the Cloud Router.

Add BGP information to the Cloud Router connection

  1. After completing the steps above, return to the Cloud Routers page in the PacketFabric portal.

  2. Click the connection to open its side panel.

  3. Under BGP Sessions, click Create New Session.

    Screenshot of the Create New Session action

Complete the following fields and then click Submit.

BGP Settings
  • Header row
    • Field
    • Description
  • Row 1
    • PacketFabric ASN
    • This is the ASN you specified when creating your PacketFabric Cloud Router. You cannot edit this field.
  • Row 1
    • ASN
    • This is the ASN for your on-premises environment. If you have one, you can use your public ASN. Otherwise, you can select a private ASN from 64512 to 65534.
  • Row 1
    • PacketFabric Router Peer IP

    • Enter a private IP prefix of your choice.

      If you are connecting to an AWS public VIF, you must enter a public IP prefix owned by you.

  • Row 1
    • Customer On-Premises Router Peer IP
    • Enter an IP address for the router connected to PacketFabric via cross connect.
  • Row 1
    • Allow longer prefixes

    • This applies to the allowed incoming and outgoing prefixes that you list below.

      For example, say you list as an allowed incoming prefix. You have three other cloud connections with the following outgoing prefixes:

      Connection A:
      Connection B:
      Connection C:

      If you do not select this option, only routes from Connection A are allowed.

      If you select this option, routes from Connection A and Connection C are allowed.

BFD settings

Select Enable BFD to enable Bidirectional Forwarding Detection (BFD) for this connection.

When BFD is enabled, test packets are periodically sent to BGP peers. If a peer fails to reply after a specified interval and number of attempts, the BGP session shuts down.

On its own, BGP will take about 90 seconds to detect a failure and shut down. With BFD, you can detect failures significantly faster.

The interval (in milliseconds) at which to send test packets to peers. The default is 300 ms, and you can enter a value from 3 to 30000 ms.
The multiplier is the number of consecutive packets that can be lost before BFD considers a peer down and shuts down BGP. The default is 3, and you can enter a value from 2 to 16.
NAT settings

This option appears if you opted for NAT capability when creating the connection.

Prefixes to NAT

The prefixes from your on-premises environment that you want to associate with the NAT pool.

NAT Pool Prefixes

This is autofilled with the PacketFabric router CIDR. All prefixes that are NATed on this connection will be translated to the pool prefix address.

Allowed prefixes to cloud

This is a list of addresses that you want to allow into your on-premises router. These can be addresses from other cloud environments or from a different router.

  • Row
    • Field
    • Description
  • Row
    • ASN prepend

    • Number of additional times to add the ASN to the BGP path, resulting in a higher path length.

      Routes with higher path length (a higher ASN prepend value) have a lower priority.

  • Row
    • MED

    • The multi-exit discriminator (MED) value.

      When the same route is advertised in multiple locations, those with a lower MED are preferred by the peer AS.

  • Row
    • Prefix/Mask
    • Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.
Allowed prefixes from cloud

This is a list of addresses from within the on-premises environment that you want to advertise to other connections.

  • Row
    • Field
    • Description
  • Row
    • Local preference
    • When the same route is received in multiple locations, those with a higher local preference value are preferred by the PacketFabric Cloud Router.
  • Row
    • Prefix/Mask
    • Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.

Multiple BGP sessions

You can configure multiple BGP sessions for a dedicated port connection.

After you configure your first session, a Create BGP Session action appears on the BGP Sessions page.

Keep in mind that if you are going to have multiple BGP sessions on a connection, all sessions will use the same PacketFabric Router Peer IP address that you configured for your initial session. Since the on-premises router IP must be in the same range, you will want to use an appropriate network mask that allows for a larger range (e.g. do not use /31). If you find your range is not large enough, you can go back and edit the initial BGP session.