Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya IP Office E1 Loopback Tester 1

Status
Not open for further replies.

Jhon88

Technical User
Nov 29, 2015
75
ID
Hi All Master,

I face E1 cut off suddenly when talking, it happen random. When I ask provider they said work fine in their network and system.
To test E1 card status I try to make E1/Pri Loopback cable using rj-48C Pin out ( Pin 1 to 4 and pin 2 to 5) in Avaya Ip office 500v2.when it tested using cable meter that pin out is fine and work normal. but when I insert it to E1 port and see system status, the current state is out of service. while the led light is solid green and blink 5 second like normal (IPO heart beat) on e1 port.
rj48_loop_zamayv.gif


how to check physical e1 card problem ?
some e1 log in sysmon still capture to more data analysis.

thank so much to any appreciate.
 
You cannot just loop back a PRI, it needs special configuration which is not available in IP Office.
Use a PRI tester to check the provider line or use monitor to see what happens.
IP Office provides very goor info in the monitor tool, very similar to waht a PRI tester delivers apart from the harware layer testing.
 
Loopback the PRI channels using system status.

loopback_ttidte.jpg


A madman with a taste for speed.
 
Hi All,

We want to separate problem. is my e1 problem or my provider problem. so i want to test with loopback test to locally problem. but it doest not work as what i tell above.

someday we tested line's provider to my e1 system and got log below from sysmon:
when get this log, I see E1 status is out of service for 15 minutes and when i see in system status, i see yellow alarm log increase and e-bit error continously increase. see the picture for detail:
e-bit_error_sruane.jpg


then I revoke e1 cable from provider to my e1 then plugging the cable to my e1 then E1 system status become idle..

========================================

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:14:30 839560029mS ERR: CDRServer discarding - framecount=500
2018-07-25T11:14:49 839579754mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:14:50 839580255mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:14:55 839585255mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=4,p4=127,s1=
2018-07-25T11:14:55 839585256mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:14:58 839589865mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:15:34 839624465mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:15:46 839636243mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:15:46 839636263mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:16:09 839659065mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:16:43 839693665mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:16:54 839704102mS ERR: CDRServer discarding - framecount=500

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:17:18 839728265mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:17:52 839762865mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:18:07 839778093mS ERR: CDRServer discarding - framecount=500

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:18:26 839797465mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:19:01 839832066mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:19:05 839835634mS ERR: CDRServer discarding - framecount=500

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:19:35 839866666mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:20:11 839901269mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:20:11 839901791mS ERR: CDRServer discarding - framecount=500

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:20:45 839935869mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:20:49 839939759mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:20:49 839939810mS ISDNL1Evt: v=13 peb=13,PHAI
2018-07-25T11:20:51 839941565mS ISDNL3Evt: v=13 p1=13,p2=1000,p3=0,p4=0,s1=
2018-07-25T11:20:57 839947760mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:20:58 839948260mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:21:02 839953260mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=4,p4=127,s1=
2018-07-25T11:21:02 839953260mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:21:06 839957868mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:21:09 839959760mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:21:09 839959810mS ISDNL1Evt: v=13 peb=13,PHAI
2018-07-25T11:21:11 839961566mS ISDNL3Evt: v=13 p1=13,p2=1000,p3=0,p4=0,s1=
2018-07-25T11:21:17 839967760mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:21:18 839968260mS ISDNL1Evt: v=13 peb=13,PHDI

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:21:23 839973260mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=4,p4=127,s1=
2018-07-25T11:21:23 839973260mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:21:27 839977867mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:21:28 839979760mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:21:28 839979810mS ISDNL1Evt: v=13 peb=13,PHAI
2018-07-25T11:21:30 839981566mS ISDNL3Evt: v=13 p1=13,p2=1000,p3=0,p4=0,s1=
2018-07-25T11:21:44 839995760mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:21:45 839996260mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:21:49 839999760mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:21:49 839999810mS ISDNL1Evt: v=13 peb=13,PHAI
2018-07-25T11:22:04 840015760mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:22:05 840016261mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:22:10 840021264mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=4,p4=127,s1=
2018-07-25T11:22:10 840021264mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:22:14 840025871mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:22:39 840050618mS ERR: CDRServer discarding - framecount=500
2018-07-25T11:22:50 840060471mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:23:16 840086315mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:23:16 840086315mS ISDNL1Evt: v=13 peb=13,F3 F1
2018-07-25T11:23:16 840086322mS ISDNL1Evt: v=13 peb=13,UnLocked
2018-07-25T11:23:16 840086325mS ISDNL1Evt: v=13 peb=13,F5 F3

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:23:23 840093023mS ISDNL1Evt: v=13 peb=13,F2 F5
2018-07-25T11:23:25 840095071mS ISDNL3Evt: v=13 p1=13,p2=1001,p3=5,p4=0,s1=
2018-07-25T11:23:33 840103024mS ISDNL1Evt: v=13 peb=13,Locked
2018-07-25T11:23:48 840119762mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:23:48 840119812mS ISDNL1Evt: v=13 peb=13,PHAI
2018-07-25T11:23:50 840121568mS ISDNL3Evt: v=13 p1=13,p2=1000,p3=0,p4=0,s1=
2018-07-25T11:24:05 840135762mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:24:06 840136262mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:24:08 840139762mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:24:08 840139812mS ISDNL1Evt: v=13 peb=13,PHAI

********** SysMonitor v9.0.1.0 build 845 [connected to 10.1.21.2 ] **********
2018-07-25T11:24:24 840155762mS ISDNL1Evt: v=13 peb=13,F2 F1
2018-07-25T11:24:25 840156262mS ISDNL1Evt: v=13 peb=13,PHDI
2018-07-25T11:24:28 840159762mS ISDNL1Evt: v=13 peb=13,F1 F2
2018-07-25T11:24:28 840159813mS ISDNL1Evt: v=13 peb=13,PHAI

********** Warning: Logging to Screen Stopped **********

what's wrong with my e1 link
 
@HoldMusic : That isonly available on a US PRI trunk, not for a E1 trunk.
F1 & F2 messages are Layer 1 error messages (link down and link up)
F3 & F4 messages are layer 2 error messages (channels down / up)
F4 & F5 messqges are layer 3 error messages (sync down / up)

Either your PRI card is defect or the providers modem is defect or the in between cable is bad or the IPO chassis is defect.
 
Hi Intrigrant,

Thanks for your explanations.
yes we know either my PRI card or provider modem problem or line cable because the provider using Gpon (ONU to transmit Pri signal) and we void to debate about who has defect device.
any some article say, If any Yellow alarm in IPO, and provider side will be red alarm. and red alarm indicate wiring problems, loss of connectifity or framming mismatch.

[URL unfurl="true"]https://www.tek-tips.com/viewthread.cfm?qid=1731368

[/url]
[URL unfurl="true"]http://www.cyber-cottage.eu/?p=124
[/url]
 
From experience
this is almost certainly a line provider issue
In 20 years working on IPO (& Network alchemy) with over 4000 systems on maintenance the number of genuinely faulty PRI cards I have seen can be counted on the fingerers of one hand (with change).

from your sys mon trace - PHDI = Physical Hardware Disconnet Indicator. The ISDN 30 Circuit is dropping, 99% certain to be the NTE & Not the IPO.


Do things on the cheap & it will cost you dear
 
Hi @Holdmusic34,

you are right,
Now i am trying to to set loopback test to state out of service and inservice mode, and test with provider line.
it will be monitor from now.

Hi @IPGuru,
I'm agree with you. I think it may be D-Channel Problem in Pri line provider ?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top