Cisco 1720 point-to-point issue 1

[Midstream]

I'm trying to turn up a point-to-point and ping across it to another Cisco 1720. The serial interface 0 has been going up and down on me. I've figured out enough of the syntax to start the serial interface, but still can't ping across. AT&T says the circuit is up.

IP of the router is 192.168.2.244 pinging to 192.168.3.105

ideal-1720-MG(config-if)#no shut
ideal-1720-MG(config-if)#show interface serial 0
^
% Invalid input detected at '^' marker.

ideal-1720-MG(config-if)#exit
ideal-1720-MG(config)#exit
ideal-1720-MG#show interface seri 0
Serial0 is up, line protocol is up
Hardware is PQUICC with Fractional T1 CSU/DSU
Internet address is 10.40.30.1/30
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 11/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:01, 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: Class-based queueing
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/4/256 (active/max active/max total)
Reserved Conversations 1/1 (allocated/max allocated)
Available Bandwidth 649 kilobits/sec
5 minute input rate 71000 bits/sec, 141 packets/sec
5 minute output rate 2000 bits/sec, 1 packets/sec
122440 packets input, 7422647 bytes, 0 no buffer
Received 95 broadcasts, 0 runts, 3 giants, 0 throttles
349 input errors, 29 CRC, 275 frame, 0 overrun, 0 ignored, 44 abort
12510 packets output, 1509293 bytes, 0 underruns
0 output errors, 0 collisions, 72 interface resets
0 output buffer failures, 0 output buffers swapped out
7 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

ideal-1720-MG#ping 192.168.3.105

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.3.105, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
ideal-1720-MG#

When pinging from my laptop I get this:
Pinging 192.168.3.105 with 32 bytes of data:

Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Request timed out.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.244: TTL expired in transit.
Reply from 192.168.2.244: TTL expired in transit.

 

[unclerico]

the encapsulation is set to hdlc instead of ppp

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[Midstream]

This is what I see on the other end...

Serial0 is up, line protocol is down(looped)

no loop light on the WIC

both sides set to hdlc

 

[unclerico]

but the PE device is set to PPP. you need to change your serial interface encapsulation to match your provider. your line protocol is down because of L2 encapsulation mismatch, i.e. should be PPP as opposed to HDLC. change this on both of your devices

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[jeter]

IF both sides are hdlc it will work just fine.

Reset the card on the circuit (NIU) just pull it out and replace it.. This will clear a circuit loop.

Clear your counters and monitor the interface.

Go Army!
Tek-TIP Member 19,650

 

[Midstream]

Hoo-Ha! Go Army!

It was a bad card in the CO. They replaced it and it popped right back up!!

Thanks everyone for chiming in on a weekend.

 

[unclerico]

you should reward the man with a Star

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)