Issue link: https://www.e-digitaleditions.com/i/1066130
January/February 2019 I 47 It is essential to inspect both sides of the connection. Figure 10 depicts an entire array of fibers on an MPO connector being inspected inside of a microscope that allows the technician to go through all fibers. Inspect them all to make sure that they are in pristine condition. When inspecting MPO connectors behind a bulkhead, use a probe that can inspect all 8, 12, or 24 fibers independently. Make sure both sides are clean; otherwise, one already cleaned could potentially be plugged into a connector that is dirty, causing cross contamination. When testing, make sure to document results. Dirty fiber end faces are the leading cause of problems within fiber systems, so being able to show that the network was installed correctly can help with system warranties and to show customers that work was correctly performed. POLARITY TESTING If connecting MPO connectors into active equipment (i.e., that is the QSFP to QSFP type connections), end- to-end polarity must be B polarity so the transmitters hit receivers, rather than transmitters. For existing installations, the end-to-end polarity is often not known. Having the ability to do a fiber map, much like doing a wire map in copper, is a very useful tool because it will determine what needs to be done to get the right end-to- end polarity, whether it is duplex or MPO. It is also useful when setting up an MPO tester to do pass/fail analysis, since the technician has to tell it what polarity to expect FIGURE 10: Inspect all fibers in a multi-fiber connector and both sides of every connection. Dirty fiber end faces are the # 1 cause of problems in fiber systems. Easily create automated quotes and customized proposals Revolutionize your business with the best PSA in the Information and Communications Technology industry. Put your business on the right track with Tigerpaw. Get started by visiting tigerpaw.com/righttrack Manage projects and track and control materials Generate, manage and deliver invoices using service tickets