peering-toolbox:single_upstream_two_private_peer
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
peering-toolbox:single_upstream_two_private_peer [2022/05/14 16:48] – [Route Object & ROAs] philip | peering-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. | ||
+ | A diagram showing the typical physical layout of this scenario is shown below: | ||
+ | |||
+ | {{: | ||
===== Enabling the second Peer ===== | ===== Enabling the second Peer ===== | ||
Line 31: | 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/ |
==== Scaling ==== | ==== Scaling ==== |
peering-toolbox/single_upstream_two_private_peer.1652510930.txt.gz · Last modified: 2022/05/14 16:48 by philip