| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| peering-toolbox:physical_connectivity [2022/08/01 14:47] – [Stage Three] philip | peering-toolbox:physical_connectivity [2022/08/19 20:51] – [Connectivity to another entity] philip |
|---|
| {{peering-toolbox/peeringtoolbox.png?400|}} | {{peering-toolbox/peeringtoolbox.png?400|}} |
| |
| ====== Connectivity to another entity ====== | ====== Connectivity to another Network ====== |
| |
| This section discusses some of the considerations for a newcomer to interconnection and peering. | This section discusses some of the considerations for a newcomer to interconnection and peering. |
| This router is normally dedicated only for peering connections, whether connecting to public peers at an IXP or private peers. If procuring a separate router is not a possibility, it is possible that an existing router could be used, so long as it meets the appropriate technical requirements for participating in a peering infrastructure (full support of BGP, sufficient controlplane memory and CPU capacity). | This router is normally dedicated only for peering connections, whether connecting to public peers at an IXP or private peers. If procuring a separate router is not a possibility, it is possible that an existing router could be used, so long as it meets the appropriate technical requirements for participating in a peering infrastructure (full support of BGP, sufficient controlplane memory and CPU capacity). |
| |
| If this router will be installed at the IXP location, appropriate arrangements need to made to procure it and have it delivered, installed, and configured, to coincide with the delivery and commissioning of the physical link back to the aspiring member's network infrastructure. If this IXP is in another country, then there may well be the issues with shipping, import duties, customs agents, and who would handle the import (it's highly likely that the IXP staff or volunteers would not be too willing to do this work for their aspiring member). | The diagram below shows the peering router in the aspiring member's network, and the remote connection to the IXP. |
| | |
| | {{:peering-toolbox:ixp-router1.png?400| }} |
| | |
| | If this router will be installed at the IXP location (as shown in the diagram below), appropriate arrangements need to made to procure it and have it delivered, installed, and configured, to coincide with the delivery and commissioning of the physical link back to the aspiring member's network infrastructure. If this IXP is in another country, then there may well be the issues with shipping, import duties, customs agents, and who would handle the import (it's highly likely that the IXP staff or volunteers would not be too willing to do this work for their aspiring member). |
| | |
| | {{:peering-toolbox:ixp-router2.png?400| }} |
| |
| ==== Stage Two ==== | ==== Stage Two ==== |
| Once the new member's router is in place and operational, a free port needs to be connected to the layer-2 infrastructure operator. The most common way is by ethernet whereby the remote IXP LAN is delivered over a particular identified VLAN. This method allows the layer-2 infrastructure operator to provide several different connectivity services to its customers, each allocated their own VLAN. | Once the new member's router is in place and operational, a free port needs to be connected to the layer-2 infrastructure operator. The most common way is by ethernet whereby the remote IXP LAN is delivered over a particular identified VLAN. This method allows the layer-2 infrastructure operator to provide several different connectivity services to its customers, each allocated their own VLAN. |
| |
| This could look something like this: | This could look something like this (using Cisco IOS CLI as an example): |
| |
| | {{:peering-toolbox:remote-peer-router.png?800| }} |
| |
| [[:peering-toolbox/next-steps| Back to 'Establishing Peering' page]] | [[:peering-toolbox/next-steps| Back to 'Establishing Peering' page]] |
