Slashdot Mirror


New Data Center Standard

mstansberry writes to tell us that the Telecommunications Industry Association (the people who brought you the CAT standards for unshielded twisted pair cabling) recently published a 148 page document meant to standardize the design considerations for every single aspect of a data center. The standard covers everything from site selection to rack mounting methods.

22 of 196 comments (clear)

  1. twisting by seanadams.com · · Score: 4, Interesting

    Speaking of CAT standards, has anyone else had a good look at the differences between CAT3, CAT5, etc?

    CAT5 just seems to be twisted a little tighter, but CAT6 actually modifies the twist gradually, in a cycle that repeats every few feet, with each pair 90 degrees "out of phase" from the next. Plus theres (sometimes) a plastic "spine" in there to maintain spacing and/or bend radius. It's not obvious to me how varying the twists-per-foot along the cable should help - anyone know?

    1. Re:twisting by Mr.+Flibble · · Score: 4, Informative

      because of the extra twisting there is less crosstalk. The less crosstalk, the more information you can pump down the wire, thus the difference between Cat 3,5 and 6.

      (FYI, crosstalk is interference from a parralell channel in the wire)

      --
      Try to hack my 31337 firewall!
    2. Re:twisting by rusty0101 · · Score: 4, Informative

      Not sure entirely myself, however as a thought, having a constant twist (different from one pair to the next, but the same for the length of the cable) could set up a situation where two cables are in phase at several points alog the cable run, and some signal transfer may hapen.

      Varying the twist rate along the run of a pair, as well as doing what you can to keep it out of phase with other pairs by braiding, or other means would make it possible to set up a longer cable run without viable phase transfer points that could cause signal bleed between pairs.

      However that's just conjecture on my part. I am sure someone will come along who can give us the math to show that my conjecture is entirely wrong.

      -Rusty

      --
      You never know...
    3. Re:twisting by SoloFlyer2 · · Score: 4, Informative

      Varying the twist rate only helps when u have several cables together ( Think 4 or 5 cables in a conduit ). Basically it just reduces the chance that 2 cables next to each other are going to have exactly the same twist rate.

      In other words it reduces cross-talk between cables :)

      --
      "I reject your reality, and substitute my own" - Adam Savage
    4. Re:twisting by DaEMoN128 · · Score: 4, Informative

      I am BICC certified. There is a difference between CAT3 and CAT 5. The twists are much more pronounced on CAT 5. It may not look like it, but there is a big differnece. There is also different amounts of twists per pair. CAT 6 is something I havent had much hands on with (we use mostly fiber for that stuff). CAT 3 has much lower frequency response per pair than CAT 5. A good cable tester can actually verify that for me if you can get your hands on one (see network analyser). Just from looking online, CAT 6 has a minimum 250MHz bandwith while CAT 5 has a minimum 100 MHz bandwith per pair. http://www.lanshack.com/cat5e-tutorial.asp check here. It says CAT 5e is the same as CAT 6 but CAT 6 is manufactured to a higher standard. I guess that the fab tolerances are tighter for Cat 6.

      --
      Stop signs are only Suggestions
    5. Re:twisting by william_w_bush · · Score: 3, Informative

      also yes and no, the added twisting makes the crosstalk elimination better at different freqencies. at 1ghz a single turn is enough to cause the antenna effect, while at 10mhz (original spec) you need like half a meter or something.

      --
      The first rule of USENET is you do not talk about USENET.
    6. Re:twisting by ajs318 · · Score: 3, Informative

      When you pull a bell-rope, it stretches slightly. Then the stretched bit shrinks back to how it was and a higher-up bit of the rope is stretched. The stretched bit works its way up the rope to the wheel, which only moves when the last bit of rope snaps back. All this happens far too fast for you to see, but it does happen. {You might be able to see it in a Slinky spring loosely stretched out, especially if you have a camcorder that can do slow motion playback}. Due to the physical properties of the rope and the mechanism at the bell end, there is a small but finite delay between pulling the rope and the bell ringing.

      The same thing happens with electrical signals. They do not travel along wires instantaneously. There is an entire subdiscipline of electrical engineering dedicated to the study of transmission lines, but here are some of the points relevant to this discussion.

      Every conductor carrying a current radiates a magnetic field. If you could have two wires absolutely coincident and carrying the same current in opposite directions, then the fields they radiate will cancel out exactly and thus not interfere with anything. Obviously you can't get them absolutely coincident, because real matter takes up space. But it turns out that intimate proximity is good enough for real world applications. So, we twist the wires to keep them together ..... this way we don't have to have a huge bulky insulation jacket forcing them together, and can fit more wires into the same space. We can help matters by ensuring that the load on the far end is perfectly resistive: i.e. that every bit of energy put into it actually does work {or just gets turned into heat} rather than getting stored and released.

      Now, any wire that is not absolutely straight looks like a coil. Electrons travelling along a coil behave as though they have inertia {due to energy being stored as a magnetic field and then released} and the faster they are moving, the harder it is to persuade them to change direction. If you have a coil with many turns and a socking great lump of steel up the middle, it takes awhile to build up a current from a battery because energy is being stored in magnetising the steel. {Water flow analogy: imagine a turbine in the pipe with a heavy flywheel. It takes an effort to get it up to speed, and it wants to keep turning -- and trying to shove water along -- even after the water stops.} When there are no more molecules to line up with the field, the core is saturated and the coil behaves as a simple resistor until the current changes. Disconnect the battery, and the electrons will actually take some time to come to a halt. That's why you often see a diode -- and maybe a resistor in series with the diode, if it's a really monstrously inductive load like a railway train motor* -- across a relay or motor switched by a transistor. The diode gives the current a path to flow through without having to arc across {a pure current source without a resistor in parallel with itself behaves as an infinite voltage source; most things become good conductors if you apply a high enough voltage}. Air obviously cannot store as much energy in the form of magnetism as steel; but at a high enough frequency, the current will have changed direction before magnetic saturation occurs. Which is why VHF inductances usually have only a few turns on a piddly little ferrite core, and UHF inductances often are literally just bent bits of wire. {Of course, these can even be printed}.

      Twisting two wires together actually forms a transformer. It's not a brilliant one, but it will work as one at high frequencies. Each wire induces a current in the other. The induced currents should cancel one another out perfectly. But of course two wires twisted together also form a capacitor. So your twisted pair cable is actually this huge inductive, capacitive, resistive nightmare of a thing.

      A cable also has a characteristic impedance. When you put a battery to one end, a pulse current flow

      --
      Je fume. Tu fumes. Nous fûmes!
  2. Doomed to failure? by Toby+The+Economist · · Score: 4, Insightful

    Be interesting to see if it's useful.

    When you specify something like a cable, it's straightfoward to get it right, because the job the cable does and the way it's used is very well understood and doesn't vary between users.

    With something complex like a data center, there's so much variance in how they're operated, exactly what they do, where they are, etc...having a standard may well *not* fit everyone's needs, either because their needs were not perceived or understood at the time or because their needs simply cannot be met by the standard.

    --
    Toby

    1. Re:Doomed to failure? by JanneM · · Score: 4, Insightful

      With something complex like a data center, there's so much variance in how they're operated, exactly what they do, where they are, etc...having a standard may well *not* fit everyone's needs, either because their needs were not perceived or understood at the time or because their needs simply cannot be met by the standard.

      True.

      But when you have a formal standard, you have something to measure against. Every aspect of the data center design is not only standardized, but the how's, why's and therefore's are spelled out. If you suspect the standard doesn't meet your needs in some respect (a clear lack of surround sound for late-night fps tournaments, say), it makes it clear exactly how your criteria changes the requirements, and it makes it much easier to see how it could impact the rest of the design.

      So even if you use not one single recommendation (we need the disco ball, damnit!), you have something reasonable and well documented to compare against, which makes your job easier.

      --
      Trust the Computer. The Computer is your friend.
  3. Pity it's $250 for a peek by darnok · · Score: 4, Interesting

    I'm curious to see what this document contains: whether it's an ITIL-like view of the world (e.g. a data centre runs on change management, capacity management, problem management, ...), a hardware based view (e.g. a data centre needs a raised floor to duct cables, air conditioning, secure access, racks, ...) or something else.

    Just not curious enough to pay the price to find out

  4. Steal the F*ing Manual by fyoder · · Score: 5, Funny
    Just not curious enough to pay the price to find out

    Seriously. If all manuals were that expensive there would have been no 'RTFM'. It would have been 'STFM'.

    --
    Loose lips lose spit.
  5. Cheap datacentres by lamasquerade · · Score: 3, Funny

    I welcome this standard with open arms. I look forward to the not-too-distant day when I will be able to buy 100m(sq) of Standard Data Centre on eBay for $25. No more un-backed-up un-RAIDed hard drives for my mp3s!

    --

    // It had been Fat's delusion for years that he could help people. --Philip K. Dick, Valis

  6. Re:Hum? by Samari711 · · Score: 4, Funny

    [this post intentionally left blank]

    --

    I never said I was smart, I just said I was smarter than you

  7. Re:Link to the document by Anonymous+Crowhead · · Score: 3, Insightful

    Does anybody have a link to the document yet, since $1.6 per page of bs is a bit too much.

    Slashdot moral concept #7: If item is perceived to suck, stealing - oops sorry, forgot Slashdot moral concept #6 - infringing it is allowed.

    Example: "If $band would put out better songs, maybe I'd buy their album. Until then, I will continue to use BitTorrent to get their material."

  8. Re:Not this again ... by drsmithy · · Score: 4, Insightful
    I don't imagine this would be an especially effective means of encouraging compliance either... "we'll tell you what to do for the low, low price of $250!!"

    Out of the costs involved in setting up a data centre, $250 wouldn't even qualify as a rounding error.

  9. Alternatives to THIS book by xmundt · · Score: 5, Interesting

    Greetings and Salutations.
              Interestingly enough, a quick google search for "data center design" comes up with more hits than one can shake a stick at, ranging from free to fairly inexpensive (under $100.00). I have to admit that I wonder if THIS magnum opus has anything in it that these OTHER resources do not cover.

              It never ceases to amaze me at the number of books out there that are supposed to be useful learning tools that are nothing more than a slightly changed rehash of the man pages for a given program.

              Regards
              Dave Mundt

    --
    YAB - http://blog.beemandave.com/
  10. Re:Raised Floors? by DaEMoN128 · · Score: 3, Informative

    After making my living as an installer... raised floors are a GOD SEND!! They are a pain, but they look 1000 times better than cable tray or ladder rack with 2000 cables in them. They make routing cables easier. It is no fun setting up some rig in order to hang cable tray 20 ft. off the ground. You dont want ladder rack the whole way... nothing wrong with it, but why when you can use a cable trough with a cover that allows the use of a pull tape. Raised floors help with cooling (forced air from under the cabnet). Also, they dont have to get nasty under there.... just make sure your standards for presentation are clearly stated in the contracts and enforce them.

    --
    Stop signs are only Suggestions
  11. This is a really bad idea, sort of by DaEMoN128 · · Score: 5, Insightful

    From TFA, this is a "checklist" for CIO's. Last thing I need is my PHB having a list to check off and thinking they are requirements instead of suggestions. You never give a PHB this much info. They dont know what you are doing a good part of the time anyways... and a little info is more dangerous than none.

    It can be a good idea if the techs get a hold of it though and stop giving my 2 inches of slack on these fiber runs and give be a proper service loop with good cable dressing instead of the rats nests I've had to fix recently.

    --
    Stop signs are only Suggestions
  12. Re:Raised Floors? by wirefarm · · Score: 3, Funny

    Did they later convert that space to a cubicle farm?
    I think I worked there.

    --
    -- My Weblog.
  13. Re:Raised Floors? by marquis-cablewitch · · Score: 5, Funny

    But without raised floors where am I supposed to hide the bodies?

  14. Purpose of the Datacenter by PhYrE2k2 · · Score: 3, Informative
    But when you have a formal standard, you have something to measure against. Every aspect of the data center design is not only standardized, but the how's, why's and therefore's are spelled out.


    But not all datacenters are equal for a reason. I've seen maybe 20-30 datacenters in the past few years for various clients and they all have different features, different offerings, and different goals.

    I'll list a few of the big differences I've seen in my experiences:

    Some want to be in the downtown core, close to many businesses, but charging a premium for the space. Others claim that being in the outskirts of the city provide security in the event of any problems (mainly hyped due to 'terrorist attacks').

    Some feel the need for N+2 generators, others more. Some feel that a fallback to city power if their PDUs ever fail is good, and others feel there should be a whole other protected power distribution system (at an extremely high cost for something rarely used).

    Some like cooling each rack from the top, others blow it up every other isle and suck air down on the opposite. Some cool the whole room, claiming lots and lots of cooling units around the outside does the trick.

    Some like the datacenter two stories underground. Others claim that they're a first target for flooding and other problems stereotypically associated with a basement. Others say that the datacenter on the 10th floor of a tower is inaccessable and subject to other security feats of the building.

    Some like dedicated buildings, others like quietly slotting themselves in office towers.

    A few I went to were monitored from 3000+km's away, and others had 24/7 onsite staff. Some had technical electronic keys, and others a simple mailbox key. Some had biometrics, others just a key.

    One I went to even had outter walls capable of withstanding most missiles. Others had windows with only paper over them for security reasons.

    Some let you roam freely by a security personelle and simply log equipment, others weigh you on the way out to make sure that you didn't take anything you didn't show up with without signing it out.

    The point is each of these serves a very different purpose. If you are going to have lots of untrusted people working on equipment, it's important to make sure nobody takes anything. Each one has its advantage and disadvantage, and I don't think any one of them is 'right'- it's just trying to find a solution to problems that experience has provided.

    Is there a right answer with anything? Who is to say that any answer is right or wrong? They're just different solutions to the problem. If power stays up, systems are secure, systems get cooled, and the network is available, who is to say the solution is wrong?

    -M
    --

    when you see the word 'Linux', drink!
  15. Re:But of course by dtfinch · · Score: 3, Funny

    To me, that does not imply buying a cheap rack, getting a T1 and a router, and sticking 5 servers in whatever closet is available in your office space.

    You just described our setup almost exactly.