No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Due to missing internal fiber cross connections bidirectional Backbone trails are not showing as bidirectional in Transmission Media Layer Route

Publication Date:  2012-07-25 Views:  184 Downloads:  1
Issue Description
Actually, The concern is raised by our customer, XYZ Provider that:

There are some old Bidirectional Backbone trails in XYZ network which are not showing as bidirectional in Transmission Media Layer Route (TMLR) (as shown below)

(Note: I am taking only one trail as example, but there are around 20-25 trails)

Alarm Information

Handling Process
Then, we’ve started checking the entire optical cross connections at each node in between for particular trail & find out that there are several internal cross connections are missing that means not created at the time long back when the trail got live. So we've created the missing ones, and after searching again for that particular trail we get the results as required & accepted  by the customer.

Now our customer is delighted with our service.  

Root Cause
Now,  we’ve to take corrective actions as per the customer requirement.

No alarms are reported, power levels, trace are fine & also the trails are working fine.

Although this is an easy task, but still we need to take care while creating the trails & properly check the internal fiber cross connections, to avoid the unnecessary complaints.