View BGP Routes

Once BGP sessions are established on multiple connections, you can view the advertised and received routes for each connection. Go to the connection details page and select Routes:

screenshot of Routes page

The routes are oriented from the position of the Cloud Router:

  • Received: Routes from the attached cloud that are destined for other clouds. These must originate from IP addresses within the ranges listed under BGP Settings > Allowed Prefixes from Cloud.
  • Advertised: Routes from other cloud connections destined for the attached cloud. These must originate from IP addresses within the ranges listed under BGP Settings > Allowed Prefixes to Cloud.

illustration of routes coming in and going out

Routes table

  • Row

    • Field
    • Description
  • Row

    • Address
    • The IP address and prefix of the route.
  • Row

    • Metric
    • This field is currently empty, but will be populated when we implement static routing.
  • Row

    • Protocol

    • The protocol is one of the following:

      • BGP
      • Static (when implemented)
  • Row

    • Next Hop

    • The next hop in the route path.

      • When viewing recieved routes, this should be the IP address for the cloud-side router.
      • When viewing advertised routes, this should be Self (because the Cloud Router is the next hop from the cloud).
  • Row

    • Local preference
    • The local preference set for the route. Routes with the highest local preference value are preferred.
  • Row

    • MED

    • The MED for the route (if set).

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

  • Row

    • AS Path
    • A list of AS numbers that the route has traversed.
  • Row

    • Origin
    • I – IGP, or Interior Gateway Protocol
      E – EGP, or Exterior Gateway Protocol
      ? – Incomplete (typically because the route was redistributed or the AS path was aggregated)

Show hidden routes

If you select Show hidden routes, you see any routes that have been rejected and the reason why. The most common reason is because the route is disallowed by the import policy, meaning you may need to adjust your allowed prefixes lists.