point to point magix issues

[Shermanchicken]

I have a client that is having issues with their T1. For whatever reason the T1 goes down( I think) I check the 100DCD slots status and it shows errors and in standbye mode. I have to reset the 100DCD cards at both locations then clear the errors then it works okay until the next time. If the LEC's T1 goes down will it cause my slots to go in standbye mode or is it something else? This problem has been happening off and on. They have had issues with the local LEC's T1 before but not this extent. Any ideas?

 

[SYQUEST]

When a DS1 goes down it can generate different alarms depending on the type of failure. Because this appears to be intermittent, I would first test the 100DCD in the Legend to see if there is hardware failure. Have you tried to "restore" the module to service or does it come back by itself? If that appears to be OK, I would check all the DS1 cabling and terminations and make sure all the connections are good to the MPOE or NIU.

If these tests are passed and you have another failure, I would open a trouble ticket with the service provider to fix it. They can put a monitor on the circuit to see what is happening. Also, it is a good idea to keep a log with date/time of all DS1 failures. You should also have the customer request an out-of-service credit once the DS1 is fixed from the service provider.

Don't take NO for an answer, if you don't get results at the first level escalate the ticket to a supervisor!

If you don't have documentation for the Legend, it can be downloaded from Avaya's web-site: support.avaya.com
The maintenance document has explanations for the tests or post more questions here.

It would be a good idea to post a printout of the errors so we can see just what you are getting.

Hope this helps!

....JIM....

 

[BigWill]

One thing that you can also do, this is pending how many T-1's you have in that carrier. If it is the only T-1, by default it is the primary loop clock source. If it is the second T-1 you will want to make sure it is in the secondary clocking source. What I am thinking is that if too many errors acru as a result of having no "master" and no "slave", it "could" cause these flakey results. Another test that you can do is to place a T-1 loopback plug into a cat-5 patchcord, do a CSU-Loopback test on each T-1 card. I also found out that you can turn the loopback towards the Point-to-point, and at the Merlin at the other end of the circuit do the same CSU-Loopback test, it should test. It is a good way to test the integrity of the Point-to-point. Good luck

 

[Shermanchicken]

Thanks for the input. Customer will inform me when it happens again and also will have service provider monitor their circuit. Will try these tests. thanks again.