Data-center interconnection (DCI) starts with the communication the sites need, not a fiber-cable specification.
A hypothetical backup request shows how to separate the service, route, endpoint equipment and cable plant—and what remains unverified until the link is designed and tested.
Data center fundamentals series
What must be defined before choosing fiber?
A request to connect two data centers does not yet specify what the connection must carry. First identify the communication service and signals, where the connection will be built, the equipment at each end, the required speed and the distance to be covered.
Those answers inform the optical link and its cable plant; the cable alone does not provide the whole service. This is the sequence described in the Fiber Optic Association’s fiber-network design guidance.
The Fiber Optic Association — The FOA Reference For Fiber Optics - Fiber Optic Network Design
The Fiber Optic Association — The FOA Reference For Fiber Optics - Fiber Optic Data Links -
Worked example: Site A sends backups to site B
Hypothetical example: site A needs to send data to site B for remote backup. Neither site nor its connecting route represents an actual installation. A useful first request would keep the following decisions separate:
- Service: Identify what A must back up to B. Ask for the data volume, transfer schedule, completion deadline and required transfer rate; none has been specified. Ask separately whether B must take over operations if A fails. Storing a backup does not establish automatic failover or service continuity.
- Route: Identify the proposed connection points, then investigate possible paths, obstacles, existing conduits, permissions and any fiber available to lease. The actual path and its length are unknown.
- Endpoints: Identify the equipment that will handle the required communication at A and B, including suitable optical interfaces and transceivers. No port rate or optic has been selected.
- Cable plant and acceptance: Match the installed fiber, connections and terminations to the chosen route and interfaces. Define how its optical loss and the operation of the complete link will be checked; neither an allowable loss nor a test result is available yet.
Remote backup and transfer of operations to another region are distinct uses described by IBM. The second requirement cannot be inferred from the first in this example.
IBM — What Is a Data Center? | IBM
Does knowing the two locations settle the route?
No. The distance between points on a map is not an installed cable route or proof that a path is usable. Route planning must account for conditions on site, existing utilities and obstacles, and the permissions needed to use a path. The Fiber Optic Association also describes existing conduit and rentable fiber as possibilities in some areas.
They are options to investigate, not resources known to exist between hypothetical sites A and B.
How do the endpoint optics and cable plant fit together?
Equipment at each site must handle the requested communication. Its optical transceiver converts between the equipment’s electrical signal and the optical signal carried over fiber. Required bandwidth and the route’s actual length affect the selection of equipment, optical interfaces and fiber; these choices must be checked together.
The cable plant is the installed, protective cable plus its splices, terminations and other connection hardware. It is commonly connected to transceivers through short patch cords at outlets or patch panels. Its fiber and connector types, loss, bandwidth and suitability for the installation environment must match the selected link.
Fiber count cannot be set by saying that two sites need “one fiber”: a typical full-duplex fiber datalink uses one fiber in each direction, while some implementations use wavelength-division multiplexing for bidirectional transmission on a single fiber. Neither arrangement has been selected for A and B.
What would show that the chosen link works?
Once a route and components are specified, estimate cable-plant loss from fiber attenuation over the route plus connector and splice losses. Compare that estimate with the selected transceivers’ optical power budget. Receiver overload and dispersion-related bandwidth limits also need consideration: a claimed reach distance alone cannot establish that this particular link will work.
After installation, distinguish the cable plant’s optical-loss test from checks of transceiver operation over that plant and, where required, the complete communications link. Record the route, each fiber’s connections and the test results so later checks can identify the path they concern. A passing cable-plant test by itself is not a result for the backup service.
What is the next decision for A and B?
Complete the backup requirement and investigate a usable route before committing to a cable specification. Then check the endpoint equipment against the proposed cable plant and set test criteria for both the plant and the operating link. Termination space, power and route permissions belong in that planning too.
Until those inputs are known, the example supports no promise about speed, reachable distance or continued operation during a failure.
Sources
- IBM — What Is a Data Center? | IBM
- The Fiber Optic Association — The FOA Reference For Fiber Optics - Fiber Optic Data Links -
- The Fiber Optic Association — The FOA Reference For Fiber Optics - Fiber Optic Network Design
No comments:
Post a Comment