peering-toolbox:next-steps
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
peering-toolbox:next-steps [2022/05/13 16:36] – [Enabling the Peer] philip | peering-toolbox:next-steps [2023/03/24 17:15] (current) – [Establishing Peering] philip | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{peering-toolbox/ | {{peering-toolbox/ | ||
- | ====== | + | ====== |
- | This section | + | This section |
- | So far we have assumed that the dear reader is a newcomer | + | * [[physical_connectivity|Connectivity |
+ | * [[single_upstream|Single Upstream]] | ||
+ | * [[single_upstream_private_peer|Adding a Private Peer]] | ||
+ | * [[single_upstream_two_private_peer|Adding Two Private Peers]] | ||
+ | * [[single_upstream_ixp|Peering at an IXP]] | ||
- | This section is all about simple deployment | + | For other scenarios |
- | * [[next-steps# | + | [[: |
- | ===== Single Upstream & Private Peer ===== | + | |
- | + | ||
- | Most network operators first encounter with peering is when they have a simple connection to their upstream provider. This connection usually involves the operator having a static default route configured on the link to the upstream, with the upstream pointing a default route to their customer. | + | |
- | + | ||
- | There are two possible cases here: | + | |
- | + | ||
- | - Adding the peering, retaining static route to upstream | + | |
- | - Adding the peering, introducing BGP with the upstream | + | |
- | + | ||
- | ==== Enabling the Peer ==== | + | |
- | + | ||
- | === Deploying Address Space === | + | |
- | + | ||
- | If we are not already using our own address space, then we need to consider first how to go about deploying it. | + | |
- | + | ||
- | We already have obtained our own address space and ASN for the network. As noted elsewhere, most upstream providers forbid the use of their address space for connecting with any other operator. Renumbering a network is beyond the scope of the Toolbox, but there are many published documents and guides on how to do this. At a high level, the steps are: | + | |
- | - Create your Route Object for your address space, using your upstream provider' | + | |
- | - Create your ROA for your address space, using your upstream provider' | + | |
- | - Provide a Letter of Authority (LOA) to your upstream provider requesting their peers and transits accept and propagate your address space (some providers request this, so it is good to be prepared) | + | |
- | - Organise with the upstream (transit provider) for the address space to be announced globally and routed to you | + | |
- | - Renumber the network (change dynamic pools, and use secondary addressing if needed) | + | |
- | - Withdraw the old address space | + | |
- | - Return the old address space to the upstream | + | |
- | + | ||
- | === Deploying IBGP === | + | |
- | + | ||
- | Once our own address space is in use for the network, BGP needs to deployed internally (IBGP) across the network (at least for the devices in the core and border of the network). If the network is just of a single router, no IBGP is needed. | + | |
- | + | ||
- | There are many online guides on how to deploy IBGP so will not be covered here. The assumption is that an interior routing protocol like OSPF or ISIS is already operating - if it is not, then this will also need to be deployed before IBGP can be deployed. The AS number that BGP requires is the one already obtained from the Regional Internet Registry. | + | |
- | + | ||
- | === Deploying EBGP with Peer === | + | |
- | + | ||
- | The final step is to deploy EBGP with the brand new peer. With BGP already running on the border/ | + | |
- | + | ||
- | First we create our BGP policy: | + | |
- | * outbound we announce just our address block, so a prefix filter allowing our address block out to our peer is sufficient here | + | |
- | * inbound we accept just the prefixes our peer will send us, so another prefix filter allowing those in from our peer is sufficient here | + | |
- | + | ||
- | And then we set up the EBGP session with our direct peer. | + | |
- | + | ||
- | The prefixes learned will be propagated by the IBGP across the network, and all devices connected will now have a direct path to the peer. | + | |
- | + | ||
- | + | ||
- | ==== BGP with Upstream ==== | + | |
- | + | ||
- | Here we go one step further. | + | |
- | + | ||
- | The address space still needs to be deployed, IBGP needs to be set up across the backbone, and EBGP needs to be set up with the peer. These three steps were described in the [[next-steps# | + | |
- | + | ||
- | Enabling EBGP with the upstream will now make the network operator' | + | |
- | + | ||
- | First we need to discuss with the upstream provider about setting up the EBGP session. | + | |
- | + | ||
- | + | ||
- | ===== Single Upstream & IXP ===== | + | |
- | + | ||
- | ===== Two Upstreams & Private Peer ===== | + | |
- | + | ||
- | ===== Two Upstreams & IXP ===== | + | |
- | ===== To be done ===== | + | |
- | + | ||
- | ===== References ===== | + | |
- | + | ||
- | This content is sourced from many contributors, | + | |
- | * [[https:// | + | |
- | * Network Startup Resource Center | + | |
- | * Input from Mark Tinka, Kurt Erik Lindqvist, etc | + | |
- | + | ||
- | [[: | + |
peering-toolbox/next-steps.1652423802.txt.gz · Last modified: 2022/05/13 16:36 by philip