Re: [802.3BA] Longer OM3 Reach Objective
I am in line with your comment and plan to pitch that a longer OM3 reach objective than 100m is necessary with the following slides in the coming mtg.
What is important is no extra cost added by taking advantage of simple EDC-based host.
From: Jonathan Jew [mailto:email@example.com]
Sent: Friday, March 14, 2008 10:33 AM
Subject: [802.3BA] Longer OM3 Reach Objective
I am a consultant with over 25 years experience in data center
infrastructure design and data center relocations including in excess of 50
data centers totaling 2 million+ sq ft. I am currently engaged in data
center projects for one of the two top credit card processing firms and one
of the two top computer manufacturers.
I'm concerned about the 100m OM3 reach objective, as it does not cover an
adequate number (>95%) of backbone (access-to-distribution and
distribution-to-core switch) channels for most of my clients' data centers.
Based on a review of my current and past projects, I expect that a 150m or
larger reach objective would be more suitable. It appears that some of the
data presented by others to the task force, such as Alan Flatman's Data
Centre Link Survey supports my impression.
There is a pretty strong correlation between the size of my clients' data
centers and the early adoption of new technologies such as higher speed LAN
connectivity. It also stands to reason that larger data centers have
higher bandwidth needs, particularly at the network core.
I strongly encourage you to consider a longer OM3 reach objective than 100m.
J&M Consultants, Inc
co-chair BICSI data center standards committee
vice-chair TIA TR-42.6 telecom administration subcommittee
vice-chair TIA TR-42.1.1 data center working group (during development of
USTAG representative to ISO/IEC JTC 1 SC25 WG3 data center standard adhoc