newb question, connecting 2 routers. home CCNA lab

[wiimike]

I'm just trying to get two routers to the point where I can ping each other. This is new equipment, it could be user error (most likely), broken routers, broken serial cards, a messed up cord, who knows.

here's what I've done, I've assigned both interfaces different IP addresses (11.0.0.11 amd 3.0.0.3) both with 255.0.0.0 masks. I've given the DCE end a clock rate of 64000. I've set encapsulation to PPP on each end.

One side sees that it is the DCE with the show controllers s0/0 command, the other says "DTE Unknown (13) TX and RX clocks detected."

The side that sees it is DCE reads as up, line protocol down. The side that does not know is down, and it's line protocol is down.

I tried putting "bandwidth 64" on each, it didn't seem to do anything. I read to do it from some random internet site.

From my understanding this should be all that's needed to make them both up, and line protocol up, and they SHOULD be able to ping, no?

 

[burtsbees]

If they are connected to each other like that, they need to be on the same subnet. Everything else is okay. Don't forget the "no shut" command on the interfaces, too, which it looks like you have.

Burt

 

[wiimike]

ooooh, think that could be it? I thought routers are supposed to be on different subnets? What about this config makes it so it shouldnt be that?

gunna test it in a few, hockey game is on though, go ducks =)

 

[wiimike]

just set em,

198.0.0.11 255.255.255.0

and

198.0.0.3 255.255.255.0

still having the problem.

 

[wiimike]

2611#show int s0/0
Serial0/0 is down, line protocol is down
Hardware is PowerQUICC Serial
Internet address is 198.0.0.11/24
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Closed
Closed: IPCP, CDPCP
Last input never, output never, output hang never
Last clearing of "show interface" counters 00:07:57
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
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
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions







2503#show int s0
Serial0 is up, line protocol is down
Hardware is HD64570
Internet address is 198.0.0.3/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive set (10 sec)
LCP Listen
Closed: ipcp, cdp
Last input never, output 00:00:18, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
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 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
88 packets output, 1232 bytes, 0 underruns
0 output errors, 0 collisions, 32 interface resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

 

[xpsuser]

>Serial0/0 is down, line protocol is down

conf t
int serial 0/0
no shut
end

 

[burtsbees]

Ha ha---if it were the "no shut" command, then the interface would be administratively down, and the other side would be down---he did the no shut, because the interface is simply down---plus, the other side is up.
Mike, one thing that looks scary is the number of interface resets in the 2600 (one), and the interface resets in the 2503 (32)---this I believe points to a bad serial interface, and I would guess the one in the 2600...anyone else agree? Mike, I have an extra serial, and you know about that---let me know if you need it bro.

Burt

 

[wiimike]

woah good call burt, yeah that does seem kind of fishy, are serial resets a normal thing that this card just isn't doing? Didn't know about that.

Thanks for the offer man but have already ordered another.

 

[burtsbees]

Well, it looks like since the 2503 has like 32 resets, it is constantly trying to connect---the 2600 only reset once, so I suspect that it is no good. You should ideally have NO resets on either end. The 2600 recognizes the serial card, because it states what type of hardware it is (which means your IOS supports it).

Burt

 

[xpsuser]

>Ha ha---if it were the "no shut" command, then the interface
>would be administratively down, and the other side would
>be down-

Duh, dunno why I didn't get that. Good call, that'll teach me to reply in a hurry.

 

[burtsbees]

Don't feel bad, xp---it's actually something that's overlooked more than you might think. The good thing is that you did reply---seems some people just don't want to take the time to help for whatever reason, but I for one do really appreciate anyone that does take the time, even if it's not me who may need help.
Perhaps the "ha ha" I typed was unneccesary---for that I do apologize.

Burt

 

[wiimike]

Haha burt is my hero =). Nah it was funny, even if it's you that misses something obvious, you gotta admit it's funny.

Do your serial devices not reset? kinda curious.

I'll check on mine more tomorrow after I get home from work.