protocol down...down....down....

zenzen

I recently got a wic-2t for my 3640 router, I am connecting it to my 2501 router and I suspect s0/0 on the 3640 is just broken. Here is what I am doing maybe you can tell me for sure if I am right or if there's something I can try. btw .10.0 is 3640 and .0.1 is 2501

3640 s0/0 > 2501 s1

erased 3640s startup-config
only commands I entered are as follows

Router(config)#int s0/0
Router(config-if)#ip address 10.0.10.0 255.0.0.0
Router(config-if)#encap
Router(config-if)#encapsulation p
Router(config-if)#encapsulation ppp
Router(config-if)#no shut
Router(config-if)#no shutdown
Router(config-if)#
00:02:57: %LINK-3-UPDOWN: Interface Serial0/0, changed state to upRouter(config)#int s0/0

on 2501 I did a sh ip int br, here is what I got, notice the protocol down

Router#sh ip int br
Interface IP-Address OK? Method Status Protocol
Ethernet0 192.168.1.200 YES NVRAM up up
Serial0 unassigned YES manual administratively down down
Serial1 10.0.0.1 YES manual up down


now when I do same thing on 3640's s0/1 everything comes up and I can ping the 2501

3640 s0/1 > 2501 s1

Router(config)#int s0/1
Router(config-if)#ip address 10.0.20.0 255.0.0.0
Router(config-if)#enca
Router(config-if)#encapsulation p
Router(config-if)#encapsulation ppp
Router(config-if)#no shut
Router(config-if)#no shutdown
Router(config-if)#
00:01:58: %LINK-3-UPDOWN: Interface Serial0/1, changed state to up
00:01:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1, changed state to up


2501 sh ip int br

Router#sh ip int br
Interface IP-Address OK? Method Status Protocol
Ethernet0 192.168.1.200 YES NVRAM up up
Serial0 unassigned YES manual administratively down down
Serial1 10.0.0.1 YES manual up up



I got the process down to these few steps and got s0/1 working but s0/0 seems to not go protocol up. I am using a DCE to DTE cable, dte end on the 2501 and dce on the 3640. since like I said those were the only commands I didn't mess with clock rate. but before I did mess with clock rate, trying various ones and I couldn't get it to work


Here is a sh int s1 on the 2501, input errors and crc errors kept going up for a little while and then just stopped, not sure exactly what this is, I haven't learned how to use this information, in fact I just typed the command to see if it would do anything

Router#sh int s1
Serial1 is up, line protocol is down
Hardware is HD64570
Internet address is 10.0.0.1/8
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 232/255, load 1/255
Encapsulation PPP, loopback not set, keepalive set (10 sec)
LCP REQsent
Closed: IPCP, CDPCP
Last input 00:02:12, output 00:00:01, output hang never
Last clearing of "show interface" counters 00:00:30
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/2/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
3557 input errors, 3557 CRC, 1617 frame, 0 overrun, 0 ignored, 1825 abort
10 packets output, 140 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
4 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up


Please tell me there is some incredible way to get 3640's s0/0 protocol state to up

btw I erased startup-config on the 2501 again and once again the s0/1 on the 3640 brings both status and protocol up, s0/0 doesn't



I just wanted to add that after staying up til 5:15 am with this(I did learn a lot despite this problem) I gotta go to sleep so if I don't get back to ya a while, all info will be gone over the first chance I get and I'll post any other sort of info you guys need to see. Thanks.

lildeezul

Set the clock rate of the DCE port.

Also remember the encapuslation has to be the same. ( hdlc-hdlc)
and your keep alive set timer has to be right. ( default 10 secs), it has to be the same on both sides.

but try to set a clock rate and go from there.

zenzen

setting a clock rate isn't doing anything, anything else it could be. The interface is getting errors like crc and giants