A Private Interconnect (PI) enables direct traffic exchange between two networks over a dedicated VLAN on the AMS-IX infrastructure. The Private Interconnect VLAN can be implemented either on a dedicated port or on an existing port with (802.1) Q-tagging.
PI service description & features
A PI connection has two parties:
- Initiator - The Initiator is the AMS-IX contact point for the VLAN. The “ownership” of the VLAN lies with the Initiator.
- Participant - The other party is termed the Participant.
Both Initiator and Participant must be AMS-IX connected networks.
- See ISP Unicast service description.
- AMS-IX will assign a private VLAN, in the form of a VPLS instance.
- AMS-IX will configure a port in the PI VLAN and assign it to the Initiator.
- AMS-IX will configure a port in the PI VLAN and assign it to the Participant.
- AMS-IX does not assign IP addresses in the PI LANs. This is up to the participating parties.
- Customers may connect to a PI using a dedicated port, or using an existing port with a chosen 802.1Q tag.
- Both parties have access to the AMS-IX NOC in case of problems.
- In case of problems the following information should be supplied to the NOC:
- Names of both parties involved.
- PI VLAN identification.
- See the ISP Unicast service description.
Applying for the Private Interconnect service
If you are not AMS-IX connected yet you need to apply for a connection first.
AMS-IX customers can apply for a PI connection by ordering a PI form on the my.ams-ix.net environment.