T1 lines go mad

I have two Cisco 1760 routers connect to each other by two T1 lines.

Recently they experience a strange problem : most of the time, only one line goes up, the other line goes down. And they "take turn" to go down.

And when one line go down, sometimes the CSU on the first router shows DCD/CTS down, other time the CSU on the second router shows those signals down.

In other word, one of the four CSUs on the two routers will take turn to show the DCD/CTS down.

I re-ran all the cables from the Smartjacks to the routers and replaced the CSUs on one router ( have not done for the other, but even on the router with replaced CSUs, sometimes it still shows the DCD/CTS down ).

I call the phone company and they confirmed that the loopback from smartjack to smartjack shows no problem, and from their site to each smartjack shows no problem.

Any advice is greatly appreciated.

DT

Reply to
dt1649651
Loading thread data ...

My guess is timing. One end needs to provide the time, the other needs to get it from the network.

Reply to
Scooby

Hi Scooby, I tried "service-module T1 clock source line" on one end but it doesn't help. Is that command alone enough or do I need some more commands ?

Thanks,

DT

Reply to
dt1649651

That's good for one end. The other should be 'service-module T1 clock source internal'.

Hope that helps,

Jim

Reply to
Scooby

[...]

Oops, I typed it wrong. I did add 'service-module T1 clock source internal' on one site, and the other does have the default value to be "source line". It does not solve the problem.

In fact, I have something strange on these T1 lines. The phone company told me they are point-to-point lines and I should provide the clock on one router. But when I turned the clock on, no line was up. When I turned the clock off all those two lines were working until recently when they take turn to go up and down.

DT

Reply to
dt1649651

Can you post the interface configs as well as a show interface for each end?

Reply to
Scooby

[...]

( Currently I have to not provide the internal clock to make the lines up, but they are not stable now. One of them can go down at any time ).

Here is the settings of the 4 CSUs on two routers R-1 and R-2 R-1#sh run int se 0/0 Building configuration...

Current configuration : 137 bytes ! interface Serial0/0 description First T1 to Sun ip address 192.168.245.1 255.255.255.252 service-module t1 remote-alarm-enable end

R-1#sh run int se 1/0 Building configuration...

Current configuration : 138 bytes ! interface Serial1/0 description Second T1 to Sun ip address 192.168.245.5 255.255.255.252 service-module t1 remote-alarm-enable end

R-2#sh run int se 0/0 Building configuration...

Current configuration : 108 bytes ! interface Serial0/0 ip address 192.168.245.2 255.255.255.252 service-module t1 remote-alarm-enable end

R-2#sh run int se 1/0 Building configuration...

Current configuration : 108 bytes ! interface Serial1/0 ip address 192.168.245.6 255.255.255.252 service-module t1 remote-alarm-enable end

R-1#sh int se 0/0 Serial0/0 is up, line protocol is up Hardware is PQUICC with Fractional T1 CSU/DSU Description: First T1 to Sun Internet address is 192.168.245.1/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input 00:00:05, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 8 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/4/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 2000 bits/sec, 3 packets/sec 5 minute output rate 1000 bits/sec, 2 packets/sec 154228 packets input, 20582094 bytes, 0 no buffer Received 4685 broadcasts, 0 runts, 1 giants, 0 throttles 19694 input errors, 877 CRC, 18394 frame, 0 overrun, 0 ignored,

423 abort 164247 packets output, 35509807 bytes, 0 underruns 0 output errors, 0 collisions, 2181 interface resets 0 output buffer failures, 0 output buffers swapped out 5 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

R-1#sh int se 1/0 Serial1/0 is up, line protocol is up Hardware is PQUICC with Fractional T1 CSU/DSU Description: Second T1 to Sun Internet address is 192.168.245.5/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input 00:00:00, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 1/75/0/0 (size/max/drops/flushes); Total output drops:

13 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/6/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 1000 bits/sec, 1 packets/sec 5 minute output rate 3000 bits/sec, 3 packets/sec 638414 packets input, 76236347 bytes, 0 no buffer Received 12249 broadcasts, 0 runts, 10 giants, 0 throttles 16380 input errors, 2768 CRC, 13478 frame, 0 overrun, 0 ignored, 134 abort 763786 packets output, 478240193 bytes, 0 underruns 0 output errors, 0 collisions, 9 interface resets 0 output buffer failures, 0 output buffers swapped out 7 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

R-2#sh int se 0/0 Serial0/0 is up, line protocol is up Hardware is PQUICC with Fractional T1 CSU/DSU Internet address is 192.168.245.2/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input 00:00:06, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 4000 bits/sec, 5 packets/sec 5 minute output rate 2000 bits/sec, 6 packets/sec 3689 packets input, 379966 bytes, 0 no buffer Received 166 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 5930 packets output, 474583 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 output buffer failures, 0 output buffers swapped out 1 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

R-2#sh int se 1/0 Serial1/0 is up, line protocol is up Hardware is PQUICC with Fractional T1 CSU/DSU Internet address is 192.168.245.6/30 MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Keepalive set (10 sec) Last input 00:00:08, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 1158 kilobits/sec 5 minute input rate 1000 bits/sec, 1 packets/sec 5 minute output rate 1000 bits/sec, 1 packets/sec 3218 packets input, 675731 bytes, 0 no buffer Received 164 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 2378 packets output, 244655 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 output buffer failures, 0 output buffers swapped out 1 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up

Thanks,

DT

Reply to
dt1649651

DT,

Well, first, I don't see the 'clock source internal' anywhere. I know you said you typed it, but I don't see it here. If this is in fact a P2P line, then one side must have it. I've seen places that work for a long time without it, then all of a sudden, there is a problem. Also, I notice a lot of CRC errors - this is the key. It could be caused by the timing, or maybe not. If you set the timing properly and still have the problem (clear the stats and then watch them), then next step would be to replace the cable from the T1 card to the smartjack. If you still have the problems, I would have the telco get involved again. It would keep you down for a while, but they could put a monitor on over night from site to site (something like a T-bird) that will give some good hard testing to the line. The loop backs they run from their office are only so good.

Could you, perhaps, have been getting a lot of rain lately? I've found that can often affect telco lines quite a bit.

Jim

Reply to
Scooby

Hi Jim, as I said in my previous post, I have to get that command out otherwise the line will go down immediately.

All the cables from the 4 CSUs to the 4 smartjacks have been replaced.

2 CSUs were replaced last week, the other two were replaced this noon.

I think you are right that I have to call the telco. They confirm the lines are point-to-point but both lines are down when one router provides the clock. Will post back the result.

Thanks, Jim.

DT

Reply to
dt1649651

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.