User Tools

Site Tools


peering-toolbox:single_upstream_two_private_peer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
peering-toolbox:single_upstream_two_private_peer [2022/08/01 17:34] – [Single Upstream with Two Private Peers] philippeering-toolbox:single_upstream_two_private_peer [2022/08/26 19:56] (current) – [Route Object & ROAs] philip
Line 7: Line 7:
 To add the second peering, we build on what we learned in the previous section, noting that we have already deployed our address space, set up IBGP, created Route Objects and ROAs, and created policies for our EBGP sessions. To add the second peering, we build on what we learned in the previous section, noting that we have already deployed our address space, set up IBGP, created Route Objects and ROAs, and created policies for our EBGP sessions.
  
-The diagram below shows the scenario being discussed.+diagram showing the typical physical layout of this scenario is shown below: 
  
 {{:peering-toolbox:2-private-peers.png?400|}} {{:peering-toolbox:2-private-peers.png?400|}}
Line 34: Line 34:
 ==== Route Object & ROAs ==== ==== Route Object & ROAs ====
  
-No change is needed in the Route Object in the IRR, or the ROAs created for the address space. Both indicate the ASN originating the prefix and this does not change when a new peering is established.+No change is needed in the [[[[peering-toolbox/the_internet_routing_registry#route_object|Route Object]] in the IRR, or the [[peering-toolbox/route_origin_authorisation|ROA]]s created for the address space. Both indicate the ASN originating the prefix and this does not change when a new peering is established.
  
 ==== Scaling ==== ==== Scaling ====
peering-toolbox/single_upstream_two_private_peer.1659339247.txt.gz · Last modified: 2022/08/01 17:34 by philip