IP VPN On‑Demand support

Aggregate and advertise my RFC 1918 routes ‑ Option 1 (default)

Ideal for cloud service providers (CSPs) with restrictive BGP prefix limits like AWS and Google and if most of your prefixes are RFC 1918.

Lumen automatically aggregates network prefixes according to RFC 1918 standards to reduce the number of prefixes sent to the CSP.

Lumen only advertises network RFC 1918 prefixes: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. 

Note: Aggregates are not injected into your routing tables.

Advertise all routes except those specified ‑ Option 2

Allows you to control which routes are advertised to the CSP. Check with your CSP to verify any BGP maximum prefix limits before selecting this option, as it could cause issues with your connection.

The provider edge (PE) router advertises all your network prefixes EXCEPT those you append the block community to by default. To deny specific prefixes, mark them in your routing table with the appropriate BGP community.

Blocking communities are assigned per CSP.

• AWS: 6745:8601
  
• Azure: 6745:8600
  
• Google: 6745:8604
  
• Oracle: 6745:8606

Deny all routes except those specified ‑ Option 3

Optimal for CSPs with maximum prefix limits that require reducing advertised prefixes and your prefixes don’t fall under RFC 1918 ranges.

You can select prefixes to allow by specifying the aggregates below. You can also advertise your network prefixes to the CSP by appending BGP cloud‑allow community 6745:8610 to the prefix in your routing table.

Note: Aggregates are NOT injected into your routing tables.