mchin345 Mon, 03/31/2008 - 13:21
User Badges:
  • Silver, 250 points or more

It seems there are line problems to the ASCU (the CRC error checks). As a result of the CRC errors, the ASCU is taken down. I think this is a physical layer issue. Please check that.


YeungKinSan Mon, 03/31/2008 - 19:25
User Badges:

Maybe is not physical layer issue. We have 30 ASCUs, normally is UP, but 3 to 4 days should get one DISABLE.


IOS:

(C3845-ENTBASEK9-M), Version 12.4(15)T1, RELEASE SOFTWARE (fc2)


DEBUG LOG:

Mar 22 12:36:49.027 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State= IDLE, Event= DATA_TO_SEND

Mar 22 12:36:49.027 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= TxData

Mar 22 12:36:49.027 CST: ALPS ASCU: Tx UTS DATA MSG (33 bytes + BCC) to ascu 23 on i/f Serial1/3

2E8A0EB0: 0123D070 029B0B37

2E8A0EC0: 208FD5D0 20C1C7C1 49CE2020 20202020

2E8A0ED0: 20202020 9BE58391 0000

Mar 22 12:36:49.027 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= TxGenPoll

Mar 22 12:36:49.027 CST: ALPS ASCU: Tx UTS POLL MSG (7 bytes + BCC) to ascu 23 on i/f Serial1/3

2DD03B90: 0123D070 83800000

2DD03BA0:

Mar 22 12:36:49.027 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State transition to DATA_GP_SENT

Mar 22 12:36:49.055 CST: ALPS ASCU: Rx UTS REPLY_REQ (7 bytes + BCC) from ascu 23 on i/f Serial1/3

2E8795F0: 01236770 10050322

2E879600:

Mar 22 12:36:49.055 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State= DATA_GP_SENT, Event= REPLY_REQ

Mar 22 12:36:49.055 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= TxRetxReq

Mar 22 12:36:49.055 CST: ALPS ASCU: Tx UTS POLL MSG (9 bytes + BCC) to ascu 23 on i/f Serial1/3

2DD03B90: 01236770 10158332

2DD03BA0: 0000

Mar 22 12:36:49.067 CST: ALPS ASCU: Rx UTS TRAFFIC (6 bytes + BCC) from ascu 23 on i/f Serial1/3

2E89CCD0: 01236770 370300

Mar 22 12:36:49.067 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State= DATA_GP_SENT, Event= TRAFFIC

Mar 22 12:36:49.067 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= FwdToCktMgr

Mar 22 12:36:49.067 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= TxGpAck

Mar 22 12:36:49.067 CST: ALPS ASCU: Tx UTS POLL MSG (9 bytes + BCC) to ascu 23 on i/f Serial1/3

2DD03B90: 0123D070 103183A1

2DD03BA0: 0000

Mar 22 12:36:49.079 CST: ALPS ASCU: Rx UTS TRAFFIC_ACK (6 bytes + BCC) from ascu 23 on i/f Serial1/3

2E8795F0: 01236770 370321

Mar 22 12:36:49.079 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State= DATA_GP_SENT, Event= TRAFFIC_ACK

Mar 22 12:36:49.079 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= FwdToCktMgr

Mar 22 12:36:49.079 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), Action= TxGpAck

Mar 22 12:36:49.079 CST: ALPS ASCU: Tx UTS POLL MSG (9 bytes + BCC) to ascu 23 on i/f Serial1/3

2DD03B90: 0123D070 103183A1

2DD03BA0: 0000

Mar 22 12:36:49.083 CST: ALPS ASCU: UTS FSM (rid= 23, Serial1/3), State transition to GP_ACK_SENT

Mar 22 12:36:49.091 CST: ALPS ASCU: Rx UTS TRAFFIC (6 bytes + BCC) from ascu 23 on i/f Serial1/3

2E7F4630: 01236770 370300

Mar 22 12:36:49.091 CST: ALPS ASCU: RX 4 consecutive UTS msgs from rid 23 sid 67 on i/f Serial1/3 - disabling ascu



Actions

This Discussion