10Gbps over 62.5µm Multimode Fiber


I first wrote about the potential issues with 10Gbps connectivity across a legacy fiber cable plant back in 2009 in an article titled, 10GBase-SR and Fiber Cable Plants. I just recently had another run into this same issue while working a consulting engagement. The customer had a legacy 62.5µm multimode fiber network that was currently running 1Gbps via 1000BaseSX GBIC transceivers. The customer was replacing their aging Cisco switches with HPE Aruba 2920 switches trying to use 10GBaseSR SFP+ transceivers. I was contracted to configure the HPE Aruba switches but when things didn’t work I had to dig through what the pre-sales team had assembled for the reseller and quickly found that someone had made some major mistakes in the design.

The customer believed that their fiber cable plant had 62.5µm multimode fiber and a spot check of the cable sheathing in a few locations confirmed as much. Unfortunately the fiber runs were believed to be between 200ft and 400ft in distance. With a 1000BaseSX transceiver you can reach 220m (721ft) over 62.5µm (OM1) fiber plant. With a 10GBaseSR transceiver you can only achieve 33m (108ft) over 62.5µm (OM1) fiber plant. That’s a pretty big difference and the primary reason why this initial upgrade attempt failed.

There is good news though for those with a legacy 62.5µm fiber cable plant, there’s no need to go tearing out that legacy fiber. The industry and the IEEE has provided a solution in 10GBaseLRM. The 10GBaseLRM transceiver can potentially reach 220m (721ft) over 62.5µm (OM1) fiber plant when combined with a special mode conditioning fiber patch cable. What’s a mode conditioning patch cable (MCPC)? It’s a special patch cable that has a small piece of singlemode fiber fusion spliced onto a multimode fiber.


Image Credit: LANshack.com

Since singlemode fiber is usually only 9µm and multimode fiber can be either 50µm or 62.5µm the center of each fiber doesn’t match up when paired together, hence the mode conditioning fiber patch is required to help align the signal as it leaves the transceiver and hits the fiber cable plant.

The moral of this story, make sure you do the proper research and always verify that your fiber cable plant will be in spec for the transceiver you’re going to be using in your solution.



Discussion with Roger Lapuh from Avaya


Over the weekend Dominik and myself had a great conversation with Roger Lapuh, Product Line Manager and Architect at Avaya. We recorded the conversation and posted it up to the Network Broadcast Storm podcast. If your interested in some of the back story behind SMLT you might find the conversation interesting. Cheers […] Read More


Audible – Audiobook List


I've been an Audible user for quite a few years but it's only been in the past 12 to 18 months that I've added a number of titles to my library. I spend more than 8 hours a week commuting to and from work and while I enjoy a number of podcasts I also enjoy a good book every now and then. Let me know what you think of my list, It's currently a combination of Tom Clancy and Sci-Fi based. I'm happy to accept recommendations. Ghost in the Wires: My Adventures as the World’s Most Wanted Hacker In the […] Read More


Infoblox REST API with Perl


I recently had the need to add a couple of thousand host objects to our Infoblox IPAM solution since we were missing almost all our store routers, switches, wireless switches, APC UPS, printers, etc. With over 500+ stores and not having any interns available I wasn't looking forward to the challenge of navigating the WEB UI within Infoblox to create over 2,500+ objects. Instead I decided to let the computer do the work and I wrote a quick and dirty little Perl script that could essentially loop over the subnets in a /16 network and create the host objects for […] Read More


DNS Loops – how to not configure DNS forwarding


I'm continually amazed by how much I don't know and by all the little issues and problems that I encounter in my day to day tasks.  You never know what's going to pop-up. I recently stumbled over a very poorly configured DNS environment and thought I would share how to not configuring DNS forwarding. There was a standalone Microsoft domain which had four domain controllers which were set to forward their requests to another pair of Microsoft DNS servers which eventually forwarded those requests to a fairly new Infoblox DNS environment. Upon looking at the Infoblox reports I noticed a number […] Read More