- July 19, 2021
- July 1, 2021
- June 17, 2021
- June 1, 2021
- April 30, 2021
- April 8, 2021
- March 25, 2021
- March 15, 2021
- February 25, 2021
- February 8, 2021
- January 28, 2021
- January 21, 2021
- January 13, 2021
- 2020 Releases
- Getting Started
- Cross Connects
- Virtual Circuits
- Cloud Connectivity Overview
- Hosted vs. Dedicated Connections
- Amazon Web Services
Google Cloud Platform
- Google Cloud Interconnect Overview
- Pricing Examples
- High Availability and Redundancy
- Microsoft Azure
- IBM Cloud
- Oracle Cloud Infrastructure
- Cloud Router Overview
- Requirements and Feature Support
- Create and Manage Cloud Routers
- Add Connections
- Manage Connections
- BGP Sessions
- Resources and FAQ
- Marketplace & IX
- Troubleshooting & FAQ
- Technical Reference
- Reseller Admin Portal
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:
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.
- The IP address and prefix of the route.
- This field is currently empty, but will be populated when we implement static routing.
The protocol is one of the following:
- Static (when implemented)
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).
- Local preference
- The local preference set for the route. Routes with the highest local preference value are preferred.
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.
- AS Path
- A list of AS numbers that the route has traversed.
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.