Multiple PRI Clocking Issues 2

[moCtech]

We have a customer with an IPO R8 that has been experiencing clocking issues on an AT&T Local PRI and an AT&T LD PRI for some time. I know it is preferred to only have one clock source but the clocking appears to be off because we get errors no matter which clock we choose. We also tried setting both circuits to Network and that worked for a day.

Equipment: IP500v2 with 2ea. Legacy Card Carrier T1/PRIs

Local PRI Settings:

5ESS
B8ZS
ESF
CRC: On
Clock: Network

LD PRI Settings:

ANI
B8ZS
ESF
CRC: Off
Clock: Unsustainable

Any suggestions, AT&T wants their own clocks on the local and LD side????

 

[NYSTECH]

You should have one set to network and the other as fallback or unsustainable...

What kind of errors are you seeing? have you has AT&T look at it?

 

[moCtech]

We have had at&t look at the line several times. We keep getting clock slips and the trunk never comes up.

Is there a certain trace I can run to help?

 

[amriddle01]

They are providing the clock source, so if you are having issues with clocking, it is their issue

http://www.ipoffice.tel

 

[NYSTECH]

You can use monitor to help- isolate the issue.. Has AT & T done and intrusive testing?

 

[moCtech]

We are receiving the following errors unders system status:

Error Seconds: 43
Severely Errored Seconds: 5
Clock Slips: 160
Missed Frames: 4477

 

[moCtech]

Here's a trace from Monitor. V5 is a local PRI V9 is an LD PRI


6176536mS ISDNL3Tx: v=9 peb=9
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0019(Remote)
Message Type = ConnectAck
6176536mS ISDNL2Tx: v=9 peb=9
0000 00 01 0c 10 08 02 00 19 0f .........
6176537mS ISDNL1Tx: v=9 peb=9
0000 00 01 0c 10 08 02 00 19 0f .........
6176547mS ISDNL1Rx: v=9 peb=9
0000 00 01 01 0e ....
6176547mS ISDNL2Rx: v=9 peb=9
0000 00 01 01 0e ....
6186579mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
6186579mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
6187729mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
6187729mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
6188879mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
6188879mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
6190029mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
6190029mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
6191179mS ISDNL3Evt: v=5 p1=5,p2=1001,p3=5,p4=0,s1=
6191929mS T1DSP: T1 DSP: Slot C: Channel 23 Received Digit: 1
6196629mS T1DSP: T1 DSP: Slot C: Channel 23 Received Digit: 1
6196693mS T1DSP: T1 DSP: Slot B: is alive, version 115
6196693mS T1DSP: T1 DSP: Slot C: is alive, version 115
6200690mS T1DSP: T1 DSP: Slot C: Channel 23 Received Digit: 3
6206547mS ISDNL2Tx: v=9 peb=9
0000 00 01 01 11 ....
6206547mS ISDNL1Tx: v=9 peb=9
0000 00 01 01 11 ....
6206556mS ISDNL1Rx: v=9 peb=9
0000 00 01 01 0f ....
6206556mS ISDNL2Rx: v=9 peb=9
0000 00 01 01 0f ....

 

[NYSTECH]

Do u have an external CSU befor the IPO?

 

[moCtech]

We did, we removed it before this monitor session was taken.

 

[NYSTECH]

If you have the what does the System status show you when no CSU in place.. The above trace isn't very good

 

[moCtech]

Here's another trace with no csu in front of the IPO.

********** Warning: Logging to Screen Started **********
14055019mS PRN: FalcLockedChecks FPGA_FIFO_CTRL: 4; FIFO_CTRL: 4
14055020mS PRN: Falc 5 slip
14055020mS PRN: WARNING:
14055020mS PRN: ****Reset Slip Store Falc 5 0 0
14055020mS PRN:
14055020mS PRN: WARNING:
14055020mS PRN: 20:08:57
14055021mS PRN:
14064680mS PRN: FalcLockedChecks FPGA_FIFO_CTRL: 4; FIFO_CTRL: 4
14064680mS PRN: Falc 5 slip
14064681mS PRN: WARNING:
14064681mS PRN: ****Reset Slip Store Falc 5 0 0
14064681mS PRN:
14064681mS PRN: WARNING:
14064681mS PRN: 20:09:07
14064681mS PRN:
14066170mS T1DSP: T1 DSP: Slot B: is alive, version 115
14066171mS T1DSP: T1 DSP: Slot C: is alive, version 115
14073931mS PRN: FalcLockedChecks FPGA_FIFO_CTRL: 4; FIFO_CTRL: 4
14073931mS PRN: Falc 5 slip
14073931mS PRN: WARNING:
14073931mS PRN: ****Reset Slip Store Falc 5 0 0
14073931mS PRN:
14073931mS PRN: WARNING:
14073931mS PRN: 20:09:15
14073931mS PRN:
14074573mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 81 .....
14074573mS ISDNL2Tx: v=5 peb=5
0000 00 01 d2 06 03 01 80 0f 01 01 c0 18 03 a9 83 81 ................
14074573mS ISDNL1Tx: v=5 peb=5
0000 00 01 d2 06 03 01 80 0f 01 01 c0 18 03 a9 83 81 ................
14074574mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 82 .....
14074574mS ISDNL2Tx: v=5 peb=5
0000 00 01 d4 06 03 01 80 0f 01 01 c0 18 03 a9 83 82 ................
14074574mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 83 .....
14074574mS ISDNL2Tx: v=5 peb=5
0000 00 01 d6 06 03 01 80 0f 01 01 c0 18 03 a9 83 83 ................
14074574mS ISDNL1Tx: v=5 peb=5
0000 00 01 d4 06 03 01 80 0f 01 01 c0 18 03 a9 83 82 ................
14074575mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 84 .....
14074575mS ISDNL2Tx: v=5 peb=5
0000 00 01 d8 06 03 01 80 0f 01 01 c0 18 03 a9 83 84 ................
14074575mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 85 .....
14074575mS ISDNL2Tx: v=5 peb=5
0000 00 01 da 06 03 01 80 0f 01 01 c0 18 03 a9 83 85 ................
14074575mS ISDNL1Tx: v=5 peb=5
0000 00 01 d6 06 03 01 80 0f 01 01 c0 18 03 a9 83 83 ................
14074576mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)
0000 01 01 c0 ...
InformationElement = CHI
0000 18 03 a9 83 86 .....
14074576mS ISDNL2Tx: v=5 peb=5
0000 00 01 dc 06 03 01 80 0f 01 01 c0 18 03 a9 83 86 ................
14074576mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=03(Maintenance) Reflen=1 ref=00(Local)
Message Type = Service
InformationElement = Change Status (IN SERVICE)

 

[moCtech]

We currently have the switch set to 5ESS, I was thinking of trying NI2? It's an AT&T circuit and I know they like NI2....

Any thoughts?

 

[NYSTECH]

Was the ANI just a typo? Are both PRIs 5ESS or NI2?

LD PRI Settings:

ANI
B8ZS
ESF
CRC: Off
Clock: Unsustainable

What does At&T say the ckts are to be provisioned for?
Have they done an extended tests to the SJ with different patterns?

 

[moCtech]

We upgraded an existing system on Thursday night. (Changed an IP 406 R3 to an IP500 V2 and used legacy two legacy T1/PRIs)

The previous settings were 5ESS, B8ZS, ESF, CRC On.

The telco has performed intrusion testing and replaced the smart jack.

The LD carrier has stated we should be NI2.

The Local says we should be 5ESS.

Both Local and LD are AT&T so it is really weird we are having clocking issues unless there is some type of protocol mismatch.

 

[NYSTECH]

Try NI2.. See what happens..

 

[moCtech]

NI2 seems to be working. I have the clocking set to: Local "Network" and LD "Unsustainable"

The LD was logging some clock slips but they are decreasing. We've been running for about a half an hour with 0 clock slips.