Cross-connect / Equinix FR5
Templass scrubs in Equinix FR5 (Frankfurt). If you already have space, a partner cage, or a network presence there, you can take clean traffic over a cross-connect instead of GRE.
Order it with support; Equinix and Templass both process the circuit.
When a cross-connect is the right path
- You colocate in FR5 or can order a connection into FR5
- You want a dedicated physical handoff
- Tunnel overhead or a public GRE endpoint is a problem
- The plan is Custom, or sales has already scoped a cross-connect
If you only have a server on another network, use GRE.
What you receive
Cage numbers, patch-panel IDs, and LOAs are issued after the order is accepted.
You should receive, in writing:
| Item | Source |
|---|---|
| LOA / CFA for the Equinix order | Templass |
| Z-side identification for FR5 | Templass |
| Agreed port speed and interface type | You and Templass |
| Your side (A-side) details Equinix already knows | You / your colo provider |
| Inner addressing or VLAN, if the handoff is not a simple L2 cable | Templass |
If a reseller or remote-hand provider is ordering on your behalf, they need the same LOA. Do not reuse an LOA from another customer or from a screenshot on the internet.
Order flow
- Email [email protected] with your Equinix account name, FR5 presence, desired speed, and who should be on the ticket.
- Complete the commercial step (Custom quote or an agreed add-on). Access dates stay unconfirmed until payment and admin review. See Access and Panel unlock.
- Templass issues the LOA and Z-side data.
- You (or your DC operator) submit the Equinix cross-connect order that points at those Z-side details.
- Equinix completes the physical path. Lead time is Equinix's, not Panel's.
- Templass and you bring up the interface, then apply routing for
<PROTECTED_PREFIX>.
Bring-up checks
- Optics or copper match what was ordered
- Link light on both sides
- Agreed VLAN (only if Templass specified one)
- No GRE required on this path unless you were told to layer a tunnel on top (uncommon)
Then probe <PROTECTED_PREFIX> from outside, the same way you would after a GRE cutover.
During an attack
A cross-connect does not change how you use Panel. Watch Attacks and follow Under attack. The circuit is the clean handoff. Mitigation still happens on the Templass side in FR5.
If Equinix rejects the order
Most rejections are a mismatched Z-side, a wrong IBX, or an account that cannot order in FR5. Send the Equinix error to [email protected] with the LOA reference. Do not open a second cross-connect at a guessed location.