360 Networks BGP Customer Information
This document will define the BGP policy and configurations as they pertain to customers. Customers must already have an Autonomous System Number (ASN) assigned by ARIN.
This configuration will send the full internet routing table to the customer router. This is the standard configuration for BGP customers, but will require a router with enough memory. The current table is about 190k routes, which depending on the router will usually require at least 512M of RAM.
This configuration sends the customer only routes of other 360 customers. The number of routes this includes is based on the number of advertisements received from all our customers, so it can vary by quite a bit.
Default Route Only
This is the simplest configuration. The customer router will only receive on route representing the entire internet. While it requires the smallest horsepower needed to run BGP, it is also the most inflexible configuration.
Default Plus 360Networks Routes
This configuration is a combination of the two above. Both a default route and all 360 customer routes are sent to the customer router.
360Networks assigned IP space
360 can assign the customer a block depending on the needs of the customer. While a BGP customer can be assigned a block as small as /28, 360 will not advertise a route smaller than a /24. Because of this we suggest any BGP customer should use at least a /24 IP block.
Customer owned IP space
If a customer has obtained IP space directly from ARIN, or any other Internet Registry, we will listen to and re-advertise that IP space.
Customer IP space obtained from another provider
As with IP space obtained from 360, we will accept any routes the customer requests, but will only re-advertise at least a /24 route. Keep in mind some providers will not listen to their own IP space advertised back to them. It is the customer’s responsibility to inform their other provider that they wish to have that IP space advertised by 360.
Inbound from a customer to 360Networks:
We require all customers to tell us what routes they will be advertising, as we use a prefix-list to make sure no incorrect routes are received. This includes BGP customers of our customers; we must know all the routes that will be advertised.
We also filter based on AS number, therefore we require customers to tell us any AS number besides their own they wish to advertise.
Outbound to a customer
We filter routes based on the configuration the customer has requested (see above). In addition, we do not advertise private IP space or routes smaller than a /24 to customers.
Inbound and outbound to peers
We will not advertise or listen to private IP space or routes smaller than a /24. We only allow 360 customer routes to be advertised to peers.
Updates for new ASNs or routes to be added to filters should be sent to email@example.com. The turnaround time to get additions to the customer filters is generally same day, and filters usually get updated on our transit providers within 24 hours of notification.
Local-Preference and Customer set BGP Communities:
Local Preference is a BGP metric that is used to determine which of two similar routes are preferred on the 360Networks network. For example, customers have the highest preference, which is 100, while peers are assigned a preference of 80. A BGP customer can send 360 communities, which will affect the preference set on their routes on the 360 network. Below are the communities the customer can set on each route advertised to 360Networks.
|19092:90||This community will set the local-preference on the 360 network to 90.|
This allows a customer with more than one connection to 360 to use one of the connections as a backup, as it is lower than the default of 100. This also sets the equivalent community on our transit providers.
|19092:80||This community will set the local-preference on the 360 network to 80.|
This causes the customer route to be equal to a similar route learned from a peer. It can also be used to configure a tertiary backup with the above community. This also sets the equivalent community on our transit providers.
|19092:70||This community will set the local-preference on the 360 network to 70.|
This causes the customer route to be the least preferred on the 360 network. This also sets the equivalent community on our transit providers.
|19092:(6539|2828||3356)||These communities allow customers to tell us not to advertise routes to the appropriate peers on our network.|
For example, if a customer would not wish a route advertised to Level3, they would set the community of 19092:3356 on that route.
360Networks set BGP Communities:
360 also sets communities on routes inside our network, and the customer can request to have these communities sent to them. Following are communities that a customer might see on routes sent to them, and what they mean.
|19092:100||This community is present on all 360 customer routes. |
This includes both BGP customer routes, and 360 owned IP blocks from which static customers are allocated.
|19092:300||This community is present on all routes obtained from transit providers of 360.|
|19092:310||This community is present on all routes obtained from private peers of 360.|
|19092:320||This community is present on all routes obtained from public peers of 360.|
Customers can prepend their AS to any routes they send us as many times as they like. The only requirement is that we know what the ASN is, as mentioned above.
Multiple Exit Discriminators (MEDs):
360Networks listens to and advertises MEDs on all routes more than one AS hop away. For example, if a customer is AS 33333, we will NOT listen to MEDs on routes with an AS-PATH of 33333, but we WILL listen to MEDs on routes with an AS-PATH of 33333 44444 ( a bgp customer of AS 33333) or 33333 33333 (as-prepend of an AS 33333 route).