C-LIGHT telephone TEL:+86 132 6656 7067    
Language
C-LIGHT search

EoR vs MoR: Data Center Switch Placement, Cabling Distance and Network Design

By C-LIGHT Marketing 丨 Jul 8, 2025
Table of Contents

    Centralized access switching is an established approach to organizing data center network infrastructure. Instead of installing an access switch in every server rack, multiple server cabinets connect to shared switching equipment in a dedicated network location. End-of-Row (EoR) and Middle-of-Row (MoR) are two deployment models built around this principle.

    Both architectures consolidate access switches and use structured cabling to connect servers across a row. Their main difference is the position of the network cabinet. EoR places the switching equipment at one end of the row, while MoR positions it closer to the center. This affects the maximum horizontal cable distance, cable distribution, equipment space, and the way network maintenance is organized.

    For data center designers, the decision involves more than choosing a convenient cabinet location. Row dimensions, server density, cable pathways, port capacity, power distribution, cooling, and redundancy all influence the final layout.

    1. What Is EoR (End-of-Row) Switching?

    End-of-Row switching places access switches in a dedicated network rack at one end of a row of server cabinets. Servers in multiple racks connect to these centralized switches through horizontal copper or fiber-optic cabling.

    Rather than installing a separate access switch in every server cabinet, EoR consolidates network ports into one or more shared switching platforms. Patch panels are commonly used to organize permanent cable runs and provide cross-connect points between server racks and network equipment.

    Typical EoR characteristics include:

    • End-positioned switching: Network cabinets are installed at one end of the server row.

    • Centralized access ports: One or more switches can serve multiple server cabinets.

    • Horizontal cabling: Server connections travel from individual racks to the EoR switching location.

    • Shared port capacity: Ports can be allocated across several racks according to server requirements.

    • Centralized maintenance: Access-switch equipment and associated connections are concentrated in a designated area.

    EoR can be suitable for facilities with established structured cabling and centralized network operations. It can also reduce the number of individual access switches installed throughout the server area.

    2. What Is MoR (Middle-of-Row) Switching?

    Middle-of-Row switching uses a similar centralized access model, but places the network cabinet near the middle of the server row. Server racks on both sides connect to the shared switching equipment through horizontal cable routes.

    The central position changes the distribution of cable distances. Instead of routing connections from every server rack toward one end of the row, MoR allows cables to branch toward racks on both sides of the network cabinet.

    Typical MoR characteristics include:

    • Central-positioned switching: Network cabinets are located near the middle of a server row.

    • Bidirectional cable distribution: Horizontal cable routes extend toward server racks on both sides.

    • Shorter maximum cable runs: In comparable row layouts, the farthest racks are generally closer to the switching location than in EoR.

    • Centralized port allocation: Access-switch capacity is shared across nearby server cabinets.

    • Dedicated network space: The central location must accommodate switches, patch panels, cable pathways, power, and cooling.

    MoR is often considered when a data center wants the centralized management benefits of EoR while reducing the longest horizontal cable routes. Depending on the facility layout, multiple MoR switching locations may be used to serve different groups of racks.

    3. EoR vs MoR: Key Differences

    The two architectures share centralized access switching, but their physical arrangements create different cabling and infrastructure requirements.

    FeatureEoR (End-of-Row)MoR (Middle-of-Row)
    Switch locationAt one end of the server rowNear the center of the server row
    Switch distributionCentralized at the row endCentralized near the row center
    Cable directionConnections generally run toward one endConnections branch toward both sides
    Maximum cable distanceCan be relatively long for distant racksGenerally shorter in a comparable row layout
    Switch quantityShared switches serve multiple racksShared switches serve multiple nearby racks
    Port utilizationCan improve through centralized allocationCan improve through centralized allocation
    Patch-panel arrangementOften requires structured cross-connects between server and network racksCan use shorter cable routes and a simpler patching arrangement
    Network cabinet spaceRequires space at the row endRequires space near the row center
    Power and coolingConcentrated in the network cabinet at the row endConcentrated in the network cabinet near the row center
    MaintenanceCentralized access to network equipmentCentralized access to network equipment
    Primary design concernLonger cable routes from distant racksCentral cabinet placement and available space
    Key distinction: EoR and MoR use the same general centralized switching principle. Moving the network cabinet from the row end to the center changes cable distances and physical layout, but does not automatically change the Ethernet switching or routing architecture.

    4. EoR and MoR Physical Network Layouts

    The most visible difference between the two models is the direction and distance of the horizontal cabling.

    EoR layout

    End-of-Row Switching Architecture
    Server Rack 1
    Server 1
    Server 2
    Server 3
    Server Rack 2
    Server 1
    Server 2
    Server 3
    Server Rack 3
    Server 1
    Server 2
    Server 3
    EoR Network Rack
    Access Switches
    Patch Panels
    Uplink Ports

    Multiple server racks connect to access switches positioned at one end of the row.

    Upstream Network / Spine Layer

    In this layout, cable routes from racks farther away must travel a greater distance to reach the EoR cabinet. The design can require larger horizontal cable bundles and careful planning of cable trays, patch panels, and cable identification.

    MoR layout

    Middle-of-Row Switching Architecture
    Server Rack 1
    Server 1
    Server 2
    Server 3
    Server Rack 2
    Server 1
    Server 2
    Server 3
    MoR Network Rack
    Access Switches
    Patch Panels
    Uplink Ports
    Server Rack 4
    Server 1
    Server 2
    Server 3
    Server Rack 5
    Server 1
    Server 2
    Server 3

    The central network cabinet serves server racks on both sides of the row.

    Upstream Network / Spine Layer

    MoR distributes the cable routes in both directions. This can reduce the longest connection distance and make the cable plant easier to organize in some layouts. The network cabinet, however, occupies a central position that must be included in the original floor plan.

    5. Cable Distance and Structured Cabling

    Cable distance is one of the main reasons data center designers consider MoR instead of EoR. In an EoR layout, the switching cabinet is at one end of the row, so the most distant server cabinets require the longest horizontal connections. Moving the switching cabinet toward the center can shorten those routes.

    Consider an illustrative row with eight equally spaced server-rack positions and a centralized network cabinet:

    LayoutSwitching PositionLongest Rack-to-Switch RouteCable Distribution
    EoRAt one end of the rowApproximately the full row length, excluding cabinet and pathway detailsPrimarily toward one end
    MoRNear the center of the rowApproximately half the row length in a symmetrical layoutToward both sides

    This is a simplified geometric illustration, not a guaranteed installation measurement. Actual cable routes depend on the number of cabinets, rack spacing, vertical routing, overhead trays, underfloor pathways, patch-panel locations, and service loops.

    MoR's shorter runs can create additional media choices. Depending on the distance and interface, some links that would require optical fiber in a longer EoR route may be feasible with copper cabling. The final choice must still follow the supported Ethernet channel length and cabling specifications.

    Both architectures benefit from structured cabling practices:

    • Use clearly identified permanent cable routes and patch-panel ports.

    • Keep cable bundles organized and avoid unnecessary cable crossings.

    • Plan sufficient tray and conduit capacity for future expansion.

    • Maintain appropriate bend radius and cable separation.

    • Document redundant paths and avoid common physical failure points.

    • Test installed links against the relevant performance requirements.

    6. Patch Panels and Cable Management

    EoR and MoR commonly use structured cabling to connect server cabinets with centralized access switches. Patch panels provide a convenient point for terminating permanent cables and connecting equipment through shorter patch cords.

    In EoR, a server rack may connect to a local patch panel, with a permanent cable run extending to another patch panel in the network cabinet. A short patch cord then connects the network-side panel to the access switch. This cross-connect arrangement provides flexibility, but can increase the number of patching points and total connection components.

    MoR can reduce the distance between the server-side and network-side patching locations. Depending on the chosen design, shorter routes may allow a more direct patching arrangement and fewer intermediate connection fields.

    ConsiderationEoRMoR
    Patch-panel locationConcentrated at the row-end network cabinet and server racksConcentrated around the central network cabinet and server racks
    Horizontal cable lengthGenerally longer for distant cabinetsGenerally shorter in a comparable row
    Cross-connect arrangementMay require additional patching fieldsMay support a simpler patching arrangement
    Maintenance accessCentralized at the row endCentralized near the row center
    Expansion planningRequires spare ports and cable capacity at the row endRequires spare ports and cable capacity near the center

    Reducing the number of patching points can simplify the physical channel, but it should not come at the expense of maintainability. The appropriate arrangement depends on the cabling standard, connection density, testing requirements, and operational procedures.

    7. Switch Port Utilization and Equipment Costs

    Both EoR and MoR can improve access-switch port utilization compared with installing a separate switch in every server rack. A shared switching platform can allocate available ports across multiple cabinets rather than reserving a fixed number of ports for each rack.

    For example, a server row may contain several racks with different server populations. Centralized switching allows the network team to allocate ports according to actual demand, provided cable routes and switch capacity are available.

    However, EoR and MoR do not necessarily require the same amount of equipment. The number of switches depends on port density, server count, required redundancy, uplink capacity, and the size of the switching platform.

    Cost FactorEoRMoR
    Switch hardwareShared access switches at the row endShared access switches near the row center
    Port utilizationCan be high when server demand is well distributedCan be high when several nearby racks share capacity
    Horizontal cablingLonger cable routes may increase material and installation costsShorter routes may reduce cable quantities and pathway requirements
    Network cabinet spaceRequires space at the end of the rowRequires space near the center of the row
    Power and coolingConcentrated in the EoR locationConcentrated in the MoR location
    Maintenance costsCentralized equipment can simplify accessCentralized equipment can simplify access
    Future expansionRequires spare capacity at the row endRequires spare capacity at the central location

    MoR may reduce cable-related costs when shorter routes allow simpler media and patching arrangements. However, it may require a different floor layout or consume space that could otherwise accommodate server cabinets. A complete cost model should include switching equipment, transceivers, cabling, patch panels, installation labor, network cabinet space, power, cooling, and future upgrades.

    8. Power, Cooling and Physical Space

    Both EoR and MoR move access-switch power consumption and heat away from individual server racks and into dedicated network cabinets. This can help keep server racks focused on computing equipment, but it creates a separate infrastructure requirement for the centralized switching area.

    The difference is where that additional power and cooling demand is concentrated.

    • EoR: Switches, power distribution, and cooling requirements are concentrated at the end of the row.

    • MoR: The same equipment requirements are concentrated near the center of the row.

    MoR may create a more balanced cable layout, but the central cabinet must not obstruct planned airflow, aisle access, or equipment movement. It also needs sufficient clearance for maintenance and cable entry.

    Important planning considerations include:

    • Available network-cabinet floor space and rack capacity.

    • Switch power consumption and redundant power-supply requirements.

    • Cooling capacity and airflow around centralized switching equipment.

    • Access to cable trays, conduits, and patch panels.

    • Physical separation of redundant equipment and cable routes.

    • Future growth in server count and network port density.

    9. Network Performance and Redundancy

    EoR and MoR are physical access-switch deployment models. They do not inherently define the routing protocol, switching capacity, or forwarding performance of the network. Actual performance depends on the selected switches, interface speeds, oversubscription, traffic patterns, and upstream topology.

    For servers connected to the same centralized access switch, traffic may be forwarded directly between local ports without traversing the upstream network. Traffic destined for other access switches must follow the configured network paths.

    Redundancy is especially important because a centralized switching platform can serve several server racks. A failure in a shared access switch may affect a larger group of servers than a failure involving a single rack-level switch.

    Common design measures include:

    • Dual access switches: Use independent switching devices where availability requirements justify redundant connections.

    • Dual-homed servers: Connect server interfaces to separate access devices using supported multihoming or link-aggregation designs.

    • Independent uplinks: Connect access switches to separate upstream devices or paths.

    • Physical cable diversity: Route redundant connections through separate pathways where practical.

    • Power redundancy: Use independent power feeds and suitable backup arrangements.

    MoR can make redundant cabling more balanced because connections can be routed in both directions. EoR can also provide redundancy through dual switching systems or separate network cabinets. The actual resilience depends on whether the design avoids shared failure points in equipment, power, cable pathways, and upstream connectivity.

    10. Optical Connectivity in EoR and MoR Networks

    Optical connectivity is important in centralized access architectures, particularly when server rows require high-speed links to upstream switching equipment or when copper cable reach becomes a limitation.

    In EoR deployments, longer horizontal routes may increase the importance of fiber-optic cabling, especially when the row is large or the required data rate exceeds the practical reach of the selected copper channel.

    MoR can shorten these horizontal routes. Depending on the actual distance and Ethernet interface, designers may have more flexibility to use copper or optical media. Shorter cable distance does not automatically mean that copper is suitable: the complete channel must still meet the applicable Ethernet reach and performance requirements.

    Connectivity OptionTypical ApplicationSelection Factors
    DACShort connections between nearby equipmentSupported reach, interface compatibility, and cable routing
    AOCShort-to-medium optical connections between compatible devicesData rate, cable length, power, and endpoint support
    100G Optical TransceiverHigh-speed access and upstream linksWavelength, fiber type, connector, reach, and link budget
    400G Optical TransceiverHigh-capacity data center switching connectionsForm factor, Ethernet standard, lane configuration, and optical interface
    800G Optical TransceiverHigh-bandwidth data center and AI network fabricsSwitch compatibility, module power, cooling, fiber layout, and reach

    For high-speed data center links, C-LIGHT provides a range of optical transceiver solutions. Module selection should be based on the exact switch model, supported port speed, Ethernet standard, wavelength, fiber type, connector, transmission distance, and optical link budget.

    Centralized EoR and MoR designs should also account for optical patch-panel insertion loss, connector cleanliness, fiber polarity, and the number of intermediate connections. These factors become particularly important when the network is upgraded to higher-speed interfaces or when multiple fiber distribution points are introduced.

    11. When Should You Choose EoR or MoR?

    The right choice depends on the physical layout of the data center and the way network equipment is operated. EoR may be more convenient when the row-end network area is already available, while MoR may be attractive when shorter cable distances and balanced distribution are priorities.

    EoR may be suitable when:

    • Dedicated network space is already available at the end of each row.

    • Centralized access-switch management is a major operational priority.

    • Existing structured cabling supports the required cable distances and data rates.

    • Server racks are arranged around a centralized row-end switching location.

    • Network equipment should remain outside the server-rack area.

    MoR may be suitable when:

    • Long horizontal cable runs from one end of the row are difficult to manage.

    • Server racks are distributed fairly evenly along the row.

    • Shorter cable distances may allow more flexible media choices.

    • A central network cabinet can be accommodated without affecting airflow or access.

    • Centralized access switching is preferred but cable distance needs to be controlled.

    Design RequirementPotentially Suitable ModelReason
    Existing network cabinet at row endEoRCan reuse the existing physical layout and cable infrastructure.
    Long server rowMoRCentral placement can reduce the maximum horizontal cable distance.
    Balanced cable distributionMoRConnections can branch toward both sides of the row.
    Dedicated space at row endEoRUses an established network-equipment location.
    Reduced horizontal cable lengthMoRSwitches are positioned closer to racks on both sides.
    Centralized access-switch maintenanceBothBoth models consolidate network equipment outside server racks.
    High-density server deploymentDepends on facility layoutPower, cooling, cabling, and port density determine suitability.

    12. Conclusion

    EoR and MoR both centralize access switching for multiple server racks, but they position the network equipment differently. EoR places switches at one end of the row, while MoR places them near the center. This simple change can significantly affect horizontal cable distances, cable distribution, patching requirements, and the use of available floor space.

    EoR can be effective when centralized network equipment is already planned for the row end and the cable infrastructure can support the required connections. MoR can provide shorter and more balanced cable routes, particularly in long server rows, while retaining the centralized management characteristics of EoR.

    Neither architecture is universally superior. A successful design must account for the actual row dimensions, server density, switch capacity, cabling standards, power, cooling, redundancy, and future bandwidth requirements. The best choice is the one that delivers a manageable cable plant and sufficient network capacity throughout the data center's operating life.

    For high-speed Ethernet and data center optical connectivity requirements, visit C-LIGHT Optical Transceivers or Contact C-LIGHT.

    For any questions, please contact us by email or WhatsApp.

    Email: sales@c-light.com

    WhatsApp: +86 132 6656 7067

    Related Articles

    Call
    Top