What the hell is wrong with this point to point??

P

Protoform-X

[H]ard|Gawd
Joined
Jan 30, 2002
Messages
1,203
Cisco 1721 on both sides. Yesterday users started reporting problems accessing servers over the point to point in either direction. There were some problems with the T1 line that the ISP claims have been repaired. Is there a problem with my equipment, or is there still a problem with the line? I see a mess of input errors report on the PHX router and they seem to be streaming in at a steady rate. Not really sure what they might indicate. :confused:

Code: 
PHX#show int s0/0/0
Serial0/0/0 is up, line protocol is up
  Hardware is GT96K with integrated T1 CSU/DSU
  Internet address is 10.0.0.1/30
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
     reliability 207/255, txload 1/255, rxload 5/255
  Encapsulation PPP, LCP Open
  Open: CDPCP, IPCP, 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 20:44:14
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 3
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/16/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1158 kilobits/sec
  5 minute input rate 32000 bits/sec, 4 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     260688 packets input, 59016507 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 4 giants, 0 throttles
     142445 input errors, 142445 CRC, 49173 frame, 24138 overrun, 0 ignored, 830
51 abort
     177939 packets output, 61160438 bytes, 0 underruns
     0 output errors, 0 collisions, 118 interface resets
     0 output buffer failures, 0 output buffers swapped out
     9 carrier transitions
     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up


Vegas#show int s0/0/0
Serial0/0/0 is up, line protocol is up
  Hardware is GT96K with integrated T1 CSU/DSU
  Internet address is 10.0.0.2/30
  MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
     reliability 255/255, txload 3/255, rxload 1/255
  Encapsulation PPP, LCP Open
  Open: CDPCP, IPCP, 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 19:01:50
  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/15/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, 3 packets/sec
  5 minute output rate 19000 bits/sec, 11 packets/sec
     161503 packets input, 54683791 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     297097 packets output, 124032257 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
 
You got 142445 errors in almost 21 hours... the line is not fixed. Call your ISP and yell. Be prepared for them to tell you its your router, or your smartjack, or your software, or maybe the color of your shoes. Don't accept those as answers; kindly remind them it wasn't seeing any errors before. Good luck.
 
Thanks for the reinforcement. The ISP is doing an "intrusive" test now. No idea why that wasn't done in the first place.
 
If no changes were made on your end, it is always the ISPs fault. No matter what they tell you, that is always the case. After it magically comes back, they'll say that they didn't change anything on their end. Thankfully, I don't have to deal with these assholes anymore.

I'm assuming you didn't clear the counters after they fixed the issue, so they may say that those errors are old. Do a "clear count s0/0/0" on PHX and tell them what the new error count is.

What is the output of "sh controllers T1" on both ends? Do you ever get alarms on those interfaces?

If you feel like wasting your time while the ISP fixes their issue, you could read through these:
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a0080104552.shtml
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801095a3.shtml
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801509d7.shtml
 
I actually did do a clear inherently by rebooting the router last night after the problem was "fixed." Turns out these morons were looking at the wrong T1 line. They fixed the bonded T1 data line. One of the T1 lines was down... What pisses me off is there's no telling how long it was down. They're still running tests on the PTP line, so I'm twiddling my thumbs. I finally got them failed over to a VPN, and they can work again. Everybody's happy for now. :)

Show controllers T1 comes back blank. I've administratively shutdown the serial interfaces so my VPN route could come up. Not sure if that makes a difference.
 
Fint said:
You got 142445 errors in almost 21 hours... the line is not fixed. Call your ISP and yell. Be prepared for them to tell you its your router, or your smartjack, or your software, or maybe the color of your shoes. Don't accept those as answers; kindly remind them it wasn't seeing any errors before. Good luck.
Click to expand...
You can't come to that conclusion just by looking at input errors of one device, could be any number of things(both layer 1 and layer 2).

Proto, the tell-tale sign is that you're not seeing any output errors on the other side of the T as well as the PHX side. If you were seeing output errors then you would know where the source of the problem was(vegas). Do everything that you can to prove its not your side of the demarc(on both sides), change the cable to the smartjack first. This can ALWAYS be a hard problem to spot and is generally the frist place people never look when dealing with copper.

Also, remind them that you're not seeing any other problems at the other end of the p2p circuit. Good luck.
 
Thanks, X.

I ended up going onsite and replacing the cable and T1 WIC to prove my point. After explaining to XO that all my equipment had been replaced, they sent an engineer out to replace their equipment. The point to point came back online in full force at about 12:30AM today.
 
You must log in or register to reply here.
Back
Top