Archive for December, 2010

Fiber Optic Cabling 101

December 20, 2010

I thought I’d create a quick and dirty little cheat sheet for dealing with fiber optic cabling and the different connector types we usually have to deal with.  For the most part, when dealing with fiber cables there are really 3 things you need to know:

–          Length needed

–          Connector types

–          Cable type/size

Now if you don’t know how to determine what length you need – well then you probably should click HERE to link to a site that won’t strain your brain quite so much or run to your local hardware store for a quick lesson on how to use a tape measure.  The rest of you please read on.

There are lots of connector options for fiber cables but I’ll concentrate on the ones we run into most often – LC – SC and ST.  When specing out cabling these connectors are usually designated as a combination such as LC/LC or LC/SC each designating which type of connector is on each end.  Here is what these connectors look like:



















ST cables were one of the first widely used fiber cable connections.  ST stands for “Straight Tip” and while it was widely used for many years it has been slowly replaces by smaller and more dense connections. These connectors have a twist on/off type connector.

SC connectors are similar to the ST type connections but use a push-on/pull-off type connector which is easier to use that the ST type cable connector.

LC connectors are probably the more reconizable and current type of connector.  These were developed by Lucent Technologies – hence the “LC” designation.  These connectors work similar to an RJ45/RJ11 plug and simply clip in.

The type of connectors you use will obviously be determined by the equipment you are trying connect together and the type of SFP’s at each end.  For example if we are connecting a Fiber Channel EMC Clariion SAN to a Cisco MDS switch we usually use LC/LC cables with LC connectors on both ends.

So now we know what how long of a cable we need and what connections we need so we should be good to go right?  Well, yes and no.  There is one other detail we need to take into consideration and that is cable width.  Generally speaking there are 2 options – 62.5 micron and 50 micron which will usually be designated 50/125 micron and 62.5/125 micron.

In the past, fiber core diameter were extremely important details in fiber optic transmission but improvements in fiber technology have reduced that importance.  Newer 850nm lasers offer increased transmission rates and smaller spot size requirements in the fiber’s core. These new lasers and the low cost and high-bandwidth capacity of 50-micron fiber allow both gigabit and 10-gigabit data transfer rates at an affordable price point.  62.5-micron fiber is also capable of gigabit and 10-gigabit data transfer rates but 50-micron fiber offers better reliability and increased distances.  50-micron fiber has three times or more the bandwidth capacity of 62.5-micron fiber and this enables it to achieve longer distances when new lasers are used.

Deciding between 62.5-micron and 50-micron fiber may seem like a given but it will depend on whether you are installing a new network  an upgrading/replacing an existing network.  62.5 and 50 micro cables can be joined but there are plenty of gotchas to watch out for so you’ll want to consult a networking professional to avoid data loss and connection issues.

Remove the Client from Your Thin-Client (Sort of)

December 12, 2010

Virtual Desktop Infrastructure (VDI) is certainly nothing new but it is becoming more and more common in the market place.  There are very good solutions from all the major technology players like Microsoft, Citrix and VMware.  With VDI you are essentially moving your “desktop” to the datacenter and basically controlling your desktop as a remote session.  To do this you still need some sort of “client” to enable you to connect to that session.  There are lots of options out there but most have traditionally been small, dumb, “Thin Clients” with very little memory, no hard drive and keyboard, mouse and monitor connections.  There are other options like converting your desktop to a thin client or using something like an iPad but for the most part the dumb little thin client box is the most common.  The thin client has little or no moving parts and draws very little energy compared to a traditional desktop.  I would say they’re “cheap” but that could be argued either way with the falling costs of desktops and laptops.  Lets just say they are, for the most part, “more cost effective”.

Looking at the biggest players in the thin client market you’ll probably come up with Wyse and HP as the largest and then serveral other smaller companies like ChipPC, Pano Logic and several others.  One you probably wouldn’t think of is Samsung.  For awesome flat screen tv’s, absolutely, but thin clients?  Samsung came up with a very attactive option for thin computing – just a monitor.  I’d heard of these a few months back but really never had any first hand feed back on how well they worked until recently. The idea is simple, build the thin client right into the monitor itself.  Let’s face it the monitor is the one thing you just can’t get rid of no matter what your solution.  So I talked to one of our clients last week that recently implemented a few of these new thin client and they have been real happy with it.  It is a very clean solution.  No little boxes with cables coming out all over the place – just a monitor with a keyboard and mouse hooked up and one power cord.

The TC240 is a  24” LCD monitor with full feature thin-client.  It is capable of at least 1280 x 1024 resolution, have 256MB of RAM a 1Gb ethernet connection and a USB hub built in.  The thin client OS is Windows XPe to give you great flexibility and power.  You can find full specs for the TC240 here:

Looking for a PCoIP solution in a smaller monitor – they have that too.  Take a look at the 19” NC190 here:

I really like these Samsung monitor/thin clients as a VDI option just due to their pure simplicity.  Slap a monitor on the desk and hook it into your Citrix XenDesktop or VMware View environment and your good to go.  The only downside I have noted is there isn’t a model with built in wireless available.