Installation
Colocation Cross-Connects: Patching and Tenant Cabling
A cross-connect order, panel-to-equipment patch and virtual-service attachment can describe different pieces of a colocation connection. Identify the actual provider product and its ordered endpoints, then establish whether equipment patching is included. Give the tenant installation team only the remaining authorized physical work, with the final equipment ports and customer-supplied materials identified.
Name the connection product before assigning a cable task
A request to connect two cabinets can refer to cabling inside the tenant’s permitted space, an operator-provided physical connection between locations or a service carried over an existing provider attachment. Those descriptions do not identify the same deliverable. Ask which product is ordered and where its responsibility ends before estimating field work.
Equinix’s public documentation distinguishes Standard Cross Connects from Intra-Customer Cross Connects. The latter connects a customer’s non-contiguous equipment within the same IBX, including separate cages or cabinets. That is an operator product category, not permission for a tenant contractor to install an unrestricted cable between any two spaces.
The comparison below separates named provider descriptions from the buyer’s remaining question. Product eligibility, actual delivery boundaries and commercial conditions must be confirmed with the relevant provider. This article offers no provisioning SLA, price, general availability or interpretation of a customer agreement.
References: [E1]
Scroll the table horizontally on smaller screens.
| Published example | What the source distinguishes | What the tenant still needs to establish | Source |
|---|---|---|---|
| Equinix Standard Cross Connect | A provider interconnection product for connectivity to networks, cloud providers and enterprises | The actual ordered A-side/Z-side termination and any equipment patching | [E1] |
| Equinix Intra-Customer Cross Connect | Connection between the same customer’s non-contiguous equipment within one IBX | Provider eligibility/order scope and the physical work permitted to the tenant | [E1] |
| Digital Realty ServiceFabric documentation | Port creation includes a cross-connect request; link creation describes virtual connections | Which physical attachment exists and which requested service is virtual | [D1] |
Source-qualified product distinctions and original buyer questions. No provider account, eligibility, service order, installed circuit or logical configuration is verified here.
Check equipment patching as its own line
Equinix’s published ordering flow separately offers panel-to-equipment patching, with a device cabinet, connector type and port. It also separately offers Light Link Verification. These are examples of selectable provider scope, not proof that either option is included in a particular customer order.
Read the ordered endpoints and options together. If the provider is already responsible for the extension to the tenant’s switch, another installation task covering the same endpoints may overlap it. If the provider stops at a panel, an internal cable schedule that begins only at the switch may omit the extension entirely. Neither problem is resolved by saying that the cross-connect is complete.
Agree which party supplies the extension materials, may work at each endpoint and records its completion. If a provider verification option is present, identify its actual stated output and limits; do not rename it full network or application acceptance. This article does not prescribe a light measurement, require that option or claim Leviathan performs the provider’s test.
References: [E2]
Compare a missing extension with a duplicated task
Consider a fictional GPU installation that needs connectivity from a provider handoff to tenant switch EX-SW1. The same request reaches both a provider service desk and a tenant installation contractor. Their descriptions use the word patching but do not yet establish whether they cover different segments or the same segment twice.
The useful comparison is the actual work boundary. Keep the provider’s circuit reference separate from the tenant’s cable identity, then relate them through the confirmed endpoints. Do not manufacture a successful connection from matching filenames or a pair of completed tickets. These examples contain no real order, facility layout or customer identifiers.
Scroll the table horizontally on smaller screens.
| Supplied information | Unresolved physical question | Focused clarification | Source |
|---|---|---|---|
| Provider order EX-CC10 ends at panel EX-P1; tenant list starts at EX-SW1 | Who owns the missing panel-to-switch extension? | Confirm the provider demarcation and obtain an authorized endpoint/material package for the extension owner. | Planning analysis |
| Provider order EX-CC11 includes EX-P1 to EX-SW1; the contractor is quoted for the same endpoints | Are two parties being assigned the same physical task? | Reconcile the actual included patching before scheduling or changing either package. | Planning analysis |
| A virtual service is shown as active; the field brief says install its cross-connect | Is new physical work required, or does the service use an existing attachment? | Have the provider/customer network owner identify the attachment and any genuinely outstanding physical task. | Planning analysis |
Original buyer analysis only. No authorization letter, operating sequence, network design, service test or acceptance result is represented.
Separate a physical attachment from a virtual service
Digital Realty’s public ServiceFabric documentation page presents port creation and link creation separately. Its port tutorial description mentions a cross-connect request for setup; its link tutorial describes virtual connections between ports, customers and cloud services. Those published descriptions illustrate two different tasks, without establishing any customer’s actual port or service state.
For the installation brief, ask whether the physical attachment already exists and what endpoint it presents to the tenant. For the network team, ask which service is being provisioned over that attachment and what its own completion evidence is. A change to a virtual connection does not, by itself, identify a cable that a technician should move.
Keep provider service identifiers and local equipment-port references distinguishable. The platform team should resolve any missing logical association; the physical team should receive an approved connection package for the work it is actually asked to perform. No VLAN, BGP, service-key, portal or API configuration is supplied here.
References: [D1]
Record the boundary as a segment, not a project label
Give each scoped physical segment its own record. A project title such as cross-connect delivery can otherwise hide the difference between the provider's termination and the continuation to tenant equipment. Relate those records through confirmed endpoints; do not collapse the provider order, the local cable identity and a network service identifier into one interchangeable number.
Equinix's cited order page identifies cage, cabinet, panel and port information, and separately asks for equipment details when equipment patching is selected. That supports asking for a precise returned boundary. It does not establish what another provider or a particular customer order includes.
Use the following original field map to compare the actual returned order and the tenant package. A blank scope or material-supply field is a clarification still owed. It is not an instruction for the tenant contractor to take over the missing work.
References: [E2]
Scroll the table horizontally on smaller screens.
| Record field | Keep explicit | Decision it supports | Source |
|---|---|---|---|
| Record and order identity | Local segment reference, provider product/order reference and the customer package revision that relates them. | Which ordered segment is being compared, without renaming the provider's record as a tenant cable ID. | Planning analysis |
| Both physical ends | Actual termination references and the source that defines each; distinguish the provider handoff from the final equipment endpoint. | Whether a continuation is missing or two packages cover the same endpoints. | Planning analysis |
| Task and material ownership | Included patching, named work owner and the appointed supplier/delivery responsibility for the agreed assembly. | Who must confirm the remaining package before it is priced or released. | Planning analysis |
| Applicable issue and dependency | Order/package revision, unresolved endpoint questions and the owner of the next clarification or release. | Whether a later document still refers to the same authorized scope. | Planning analysis |
| Reported output and receiving decision | The available provider or tenant completion record, its scope and the person who must review the required result. | What the record actually closes and what remains unobserved or awaiting a decision. | Planning analysis |
Original documentary field map, not a provider order form, adopted standard, material specification or authorization to work at an endpoint. Real order and asset details remain in authorized project channels.
Work an endpoint discrepancy through the boundary record
In fictional request EX-B08, the provider segment is recorded as ending at panel reference EX-P1/04. The tenant intends a continuation to equipment reference EX-SW1/P01, but its draft names EX-P1/03. These are invented comparison keys, not allocated ports, a compatible connection design or a physical routing plan.
The disagreement is small in text but consequential to scope: the two documents do not yet describe the same handoff. Retain both references and send the question to the nominated customer/provider contacts. Do not silently correct a provider order from the tenant spreadsheet or treat an old draft as a released instruction.
For the next row in the example, assume the nominated customer owner obtains confirmation that EX-P1/04 is the applicable handoff and that equipment patching is absent from the provider scope. The tenant package is reissued as TP28/R1 against those confirmed inputs. This closes the documentary endpoint question in the example; it does not represent installation, a measurement or permission to disturb equipment.
Scroll the table horizontally on smaller screens.
| Record presented | What it establishes in the example | What remains separate | Source |
|---|---|---|---|
| Provider record EX-CC28 reports its segment complete at EX-P1/04 | A completion report exists for the provider's stated segment and endpoint. | The tenant extension and its required output are not included merely because this report is complete. | Planning analysis |
| Tenant draft TP28/R0 names EX-P1/03 to EX-SW1/P01 | The draft disagrees with the provider handoff reference. | The discrepancy remains assigned for clarification; no field correction follows from this table. | Planning analysis |
| Issued tenant package TP28/R1 uses the confirmed EX-P1/04 reference and names its task/material owners | The example's documentary scope now identifies the intended continuation and who must deliver it. | An issued package is not the continuation's physical completion record or customer acceptance. | Planning analysis |
| Logical service record EX-V28 is reported active | A separate service-state statement is available. | It does not close the tenant patch record or prove which physical work was performed. | Planning analysis |
The rows are a provider report, two tenant document issues and a logical-service record. They are not four cables, four orders or a complete topology. No real provider, customer, installation result or technical acceptance is represented.
Close each segment against its own output
At handoff, compare the requested physical result with the record returned for that segment. Keep the provider's reported termination, the tenant's applicable connection package and the tenant installation record distinguishable. If the required tenant record is absent, identify the missing output and its owner rather than borrowing a completed status from the provider order.
A changed endpoint also needs an applicability decision. Retain the old issue and show which newer order or package supersedes it for the affected segment. The authorized parties must resolve any impact on actual provider orders or field work; changing a row in the boundary register does not change either one automatically.
The customer can then see three different conclusions: which physical work is reported complete, which documentary discrepancies remain, and which network-service decisions belong to another owner. This is a useful handoff even when some items remain open, provided the unresolved state is explicit. It is not a substitute for the agreed physical checks or logical-service acceptance.
Scope the remaining tenant work from the confirmed boundary
A useful installation inquiry identifies the facility, confirmed provider handoff, final equipment endpoint, accessible work area and requested physical result. Include the relevant approved route and customer-supplied assembly references when available. Say which provider dependencies remain open and who can clarify them. A detailed list of generic rack tasks cannot substitute for a missing demarcation.
Leviathan can discuss agreed tenant-side mounting, cabling, routing, dressing, labeling, inspection, remediation and physical documentation at authorized customer facilities. The facility controls its provider infrastructure and access process. Provider orders, connectivity subscriptions and their service acceptance remain with the customer and provider; Leviathan does not sell the provider’s cross-connect or colocation product.
Agree the physical checks and record format for the actual engagement. Formal optical or copper measurements require confirmed equipment, personnel, method and acceptance criteria. Physical completion does not establish carrier activation, configured network behavior or workload readiness. Identify the appointed equipment/material supplier, approved configuration, quantities and delivery responsibilities before agreeing the physical work. Liquid-side work and facility electrical installation are excluded; full system/software commissioning is not a standard service.
Tell us about the project, and our team will follow up to discuss scope, requirements and availability. The goal of the initial discussion is to identify the real remaining customer-side work, rather than schedule another generic patching task against an ambiguous service description.
References: [L1]
Common planning questions
Does a prepared LOA mean the cross-connect is installed?
No. The cited Equinix documentation treats the authorization information and the order that uses it as different things. Confirm the actual provider order and its installed endpoints rather than using the document alone as completion evidence.
Is panel-to-equipment patching always part of the provider order?
Do not assume it. The cited Equinix flow offers it separately. Check the actual ordered endpoint and option, then assign only the remaining authorized tenant work.
Does a virtual connection require a new physical cable?
Not merely because it is called a connection. Identify the existing attachment and the specific service change with the provider and network owner. The ServiceFabric example distinguishes physical setup from virtual-link creation; no actual customer configuration is verified here.
Can Leviathan take over the facility’s cross-connect service?
Leviathan can discuss the defined customer-side physical installation and documentation package. The provider and customer retain their orders, restricted-area authorization, connectivity service and logical acceptance. Any proposed interface work must be explicitly scoped; no provider partnership or service entitlement is implied.
Can the provider's completed order close the tenant extension too?
Only the actual included endpoints and output can answer that. A provider segment reported complete at a panel does not close a separately scoped continuation to equipment. Relate each completion record to its own segment and keep missing tenant evidence open.
What if the panel or port in the tenant package differs from the provider record?
Keep both references and their document issues, assign the discrepancy to the nominated customer/provider contacts, and obtain the applicable confirmed input before reissuing the tenant scope. Do not infer that editing the local record updates a provider order or authorizes a physical change.
Who should supply the material for a remaining tenant patch?
Name the appointed supplier and delivery responsibility in the agreed package, separately from the work owner. An omitted provider patching option does not establish who supplies the extension, which assembly is suitable or which party may work at its ends.
Primary sources
- [E1] Equinix: Cross Connect product typesChecked 2026-10-15. Standard versus Intra-Customer product descriptions only. No SLA, fees, bundle minimums, eligibility determination or customer contract interpretation.
- [E2] Equinix: ordering with an LOA and optional equipment patchingChecked 2026-10-15. Named provider’s connection fields and separate equipment-patching/verification options only; no account operation, test procedure or included-order assumption.
- [E3] Equinix: Digital LOA roles and connection assetsChecked 2026-10-15. Published A-side/Z-side asset/authorization distinction only. No actual authorization, account entitlement, access right or legal disposition verified.
- [D1] Digital Realty: ServiceFabric product documentationChecked 2026-10-15. Public tutorial descriptions distinguish port/cross-connect setup from virtual links; no video procedure, account state or availability verified.
- [L1] Leviathan Colocation InstallationChecked 2026-10-15. Actual conditional tenant-side physical scope; provider services, access and logical acceptance remain separate. No hosting, materials or commissioning offer.