11 Replies Latest reply on May 10, 2018 4:07 PM by jayh

    TA 900 with CRC errors on a PRI customer also have another T1 in a different TA900 on same PBX

    jlvega New Member

      Customer want to have redundancy and wanted to have 2 different Adtrans, but one of the T1 keeps dropping with CRC ES errors.  Could it be the clock settings? 

      t1 0/3 is UP
        Description: A9161495
        Receiver has no alarms
        T1 coding is B8ZS, framing is ESF
        Clock source is system, FDL type is ANSI
        Line length is 10 feet
        No remote loopbacks, No network loopbacks
        Acceptance of remote loopback requests enabled
        Tx Alarm Enable: rai
        Last clearing of counters 4d 19:14:08
          loss of frame  : 7, last occurred 20:35:12
          loss of signal : 9, last occurred 20:32:35
          AIS alarm      : 0
          Remote alarm   : 725, last occurred 00:06:51

        DS0 Status: 123456789012345678901234
                    XXXXXXXXXXXXXXXXXXXXXXXX
        Status Legend: '-' = DS0 is not allocated
                       'X' = DS0 is allocated (nailed)

        Signaling Bit Status: 123456789012345678901234
                         RxA: 000000000000000000000000
                         RxB: 000000000000000000000000

                         TxA: 000000000000000000000000
                         TxB: 000000000000000000000000
                              123456789012345678901234

        Line Status: -- No Alarms --

        5 minute input rate 24 bits/sec, 0 packets/sec
        5 minute output rate 24 bits/sec, 0 packets/sec
        Current Performance Statistics:
          47 Errored Seconds, 0 Bursty Errored Seconds
          0 Severely Errored Seconds, 0 Severely Errored Frame Seconds
          0 Unavailable Seconds, 0 Path Code Violations
          0 Line Code Violations, 47 Controlled Slip Seconds
          0 Line Errored Seconds, 0 Degraded Minutes

        TDM group 1, line protocol is not set
          Encapsulation is not set

       

       

      sh event history

       

       

       

       

      2018.05.01 11:15:17 T1.t1 0/3 CSS 15 min threshold exceeded
      2018.05.01 11:17:48 T1.t1 0/3 Yellow
      2018.05.01 11:17:48 INTERFACE_STATUS.t1 0/3 changed state to down
      2018.05.01 11:17:48 ISDN.EP     PRI  1  D channel is DOWN
      2018.05.01 11:17:48 ISDN.EP     PRI  1  D channel is DOWN
      2018.05.01 11:17:48 TM.T02 23 IsdnTmStateInboundConnected - rcvd unexpected CallRelease
      2018.05.01 11:17:48 TM.T02 23 IsdnTmStateIdling - clear trunk appearance
      2018.05.01 11:17:48 TM.T02 21 IsdnTmStateInboundConnected - rcvd unexpected CallRelease
      2018.05.01 11:17:48 TM.T02 21 IsdnTmStateIdling - clear trunk appearance
      2018.05.01 11:17:48 TM.T02 0 Taking 23 b-channels out-of-service

      2018.05.01 11:17:48 TM.T02 23 tachgClearing processed by IsdnTmState base
      2018.05.01 11:17:48 TM.T02 21 tachgClearing processed by IsdnTmState base
      2018.05.01 11:17:49 INTERFACE_STATUS.pri 1 changed state to down