BGP Session Procedure

The following is a quick guide to help you understand the BGP session setup process on our network. This guide is intended for customers/clients only and not peers which will have a different procedure.

Step 1: Client orders a BGP session for a current service or as an addon during the order process. Note that not all VPS/Cloud plans support a BGP session, plans under $19/mo are ineligible for BGP sessions. 

Step 2: Client makes appropriate entries at their RIR for announcements including RPKI signing of the ROA (Route Origin Authorization) and aut-num sets as appropriate. At a minimum, an ROA should be made for each subnet you wish to announce via your ASN and an export entry in your aut-num authorizing AS32931 to announce your as-set.

Step 3: Client opens a ticket with the support department providing a LOA (Letter of Authorization) authorizing Mean Servers Limited to advertise the client's ASN. Client will inform us if they require a full BGP table, a limited BGP table (only peers, clients, and IXes plus default route), or solely a default route. Client will indicate if they wish for a complementary associate membership and BGP session with Denver IX.

Step 4: Mean Servers Limited will then verify the LOA authenticity utilizing RIR whois information. Note that if we are unable to verify the LOA authenticity we will not proceed with the BGP session setup without exception.

Step 5: Mean Servers will setup the appropriate policies to ensure only ROA space is accepted for propagation, the BGP session will be installed on our network and client sets their end point IP addresses under their BGP session services from the client area.

Step 6: Client configures their end of the BGP session and a BGP session is successfully establish. Client can then begin announcing their IP space.

Step 7: Should the client require specific traffic engineering, this can be performed with our BGP communities.

If you decide to also join the Denver IX:
(Mean Servers offers complementary associate membership to the Denver IX for all clients with a BGP session)

Step 1: We will forward your information to Denver IX so they can make the appropriate setup configurations on their end. Note that Denver IX makes use of ROAs for all routes announced to their route reflectors.

Step 2: We will extend an additional VLAN to your VPS, dedicated server, or colocation environment via your existing infrastructure. VPS/cloud clients will be provided this VLAN via an additional virtual interface installed on their services. Dedicated server/colocation clients will receive the VLAN tag on their port. This VLAN will enable you to connect to the Denver IX peering fabric where you can peer with the route servers or establish a BGP session with other peers directly. See the Denver IX website for details on the security procedures. This additional VLAN will be unmetered from your regular VLAN or uplink with Mean Servers.

Step 3: We will provide you with details for establishing a BGP session with Denver IX along with your IP address on the peering fabric. Additional configurations may be required on your end and will be appropriately provided for your environment.

Step 4: You can establish a BGP session with the route reflectors and/or willing peers on the fabric.

  • bgp, bgp session, internet exchange, ix, denver ix, roa, rkpi, letter of authorization, route origin authorization, loa, free internet exchange membership, traffic engineering, bgp community
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Maximum Prefixes

Mean Servers sets a maximum prefix limit on all downstream BGP sessions. These limits are hard...

Announcing New IP Space

If you have a BGP session with Mean Servers, we have previously verified your letter of...

BGP Communities

Mean Servers Assigned Communities RPKI Validation Statuses:32931:901 - RPKI Valid32931:902 -...