need help about rip....

zom

hi there, i was browsing through the techexams.net and found that there's a thread which teaches on how to configure the rip network so i give it a try. but i can't manage to ping my routers both way though. any 1 know wat's going on? i follow all the steps correctly except din set the password though. i type the sh ip interface brief it shows that the serial 0 is up but the protocol is down on both routers......is this be the problem? thx alot ^^

gojericho0

Double check to make sure you set clocking the the serial interface that acts as the DCE.

zom

yup i did recheck everything.......some 1 mind to help me pls? here's my list

interface IP-Address OK? Method Status Protocol
Ethernet0 unassigned YES NVRAM administratively down down

Serial0 192.168.22.5 YES manual up down

Serial1 unassigned YES NVRAM administratively down down

config list of my router a

hostname routerA
!
logging rate-limit console 10 except errors
enable secret 5 $1$pB3i$whW7UZ62CxwfZ/.Xx9B1y/
!
ip subnet-zero
no ip finger
no ip domain-lookup
!
no ip dhcp-client network-discovery
!
!
!
!
interface Ethernet0
no ip address
shutdown
!
interface Serial0
description connected to routerB
ip address 192.168.22.5 255.255.255.0
encapsulation ppp
!
interface Serial1
no ip address
shutdown
!
router rip
network 192.168.0.0
network 192.168.22.0
!
ip kerberos source-interface any
ip classless
ip http server
!
!
line con 0
transport input none
line aux 0
line vty 0 4
login
!
end

zom

Interface IP-Address OK? Method Status Protocol

Ethernet0 unassigned YES unset administratively down down

Ethernet1 unassigned YES unset administratively down down

Serial0 192.168.22.6 YES manual up down

Serial1 unassigned YES unset administratively down down

here's my router B config list

hostname routerB
!
ip subnet-zero
no ip domain-lookup
!
!
!
interface Ethernet0
no ip address
no ip directed-broadcast
shutdown
!
interface Ethernet1
no ip address
no ip directed-broadcast
shutdown
!
interface Serial0
description connected to routerA
ip address 192.168.22.6 255.255.255.0
no ip directed-broadcast
encapsulation ppp
no ip mroute-cache
clockrate 64000
!
interface Serial1
no ip address
no ip directed-broadcast
shutdown
!
router rip
network 192.168.0.0
network 192.168.22.0
!
ip classless
!
!
line con 0
transport input none
line aux 0
line vty 0 4
login
!
end


pls help me~~ thx alot ^^

EdTheLad

Why are you using PPP encapsulation on the serial ports?
Change the encapsulation on both ends to hdlc

config t
int s0
encapsulation hdlc

After you have done this check the interface status:

show int s0

You need to see Serial0 is up, line protocol is up

zom

ed_the_lad wrote:

Why are you using PPP encapsulation on the serial ports?
Change the encapsulation on both ends to hdlc

config t
int s0
encapsulation hdlc

After you have done this check the interface status:

show int s0

You need to see Serial0 is up, line protocol is up

nop still unable to see

this is my router B serial interface

routerB#sh int s0
Serial0 is up, line protocol is down
Hardware is HD64570
Description: connected to routerA
Internet address is 192.168.22.6/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation HDLC, loopback not set, keepalive set (10 sec)
Last input never, output 00:00:04, output hang never
Last clearing of "show interface" counters never
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/1/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
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
94 packets output, 1452 bytes, 0 underruns
0 output errors, 0 collisions, 29 interface resets
0 output buffer failures, 0 output buffers swapped out
42 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

zom

here's my router A int s0 list

routerA#sh int s0
Serial0 is up, line protocol is down
Hardware is HD64570
Description: connected to routerB
Internet address is 192.168.22.5/24
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 never, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:06:29
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 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
27 packets output, 594 bytes, 0 underruns
0 output errors, 0 collisions, 13 interface resets
0 output buffer failures, 0 output buffers swapped out
42 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

EdTheLad

Are you sure routerB is the DCE ?

On each router do the following

show controllers s 0

The router which has a DCE in the output should have the clock rate set.
Anyway just set the clock rate on RouterA and you should be good.

zom

ed_the_lad wrote:

Are you sure routerB is the DCE ?

On each router do the following

show controllers s 0

The router which has a DCE in the output should have the clock rate set.
Anyway just set the clock rate on RouterA and you should be good.

yes i am pretty sure that the router A is on DTE
routerA#sh controllers s 0
HD unit 0, idb = 0x29A4E4, driver structure at 0x2A1AA8
buffer size 1524 HD unit 0, V.35 DTE cable

and while i try to set the clock rate on router a it said that only DCE ables to set the clock rate....

zom

this is my routerB

routerB#sh controllers s 0
HD unit 0, idb = 0xE23C8, driver structure at 0xE7860
buffer size 1524 HD unit 0, RS-232 DCE cable, clockrate 64000
cpb = 0xE2, eda = 0x2940, cda = 0x2800

EdTheLad

The config is good, try toggle the interfaces
i.e. shutdown, no shutdown on both serial 0's
Change cable, power on and off each router, get another router

rossonieri#1

zom

can some 1 pls help me pls?? i dunno izzit my router fault or IOS or the cable fault.....pls help thx ^^ i am using 2501 and 2514. i tried to shutdown the int s0 and no shut it the line protocol seems to up for like few seconds and then changed back to down again....

Fouve

It sounds to me like you have a bad cable. I've had that happen with a few cables of my own. Also, make sure your hello timers are equal and not set to different times. That would cause them not to communicate as well. As far as I see, you have the right setup. Most of the time the problem is physical rather than any of the network settings, so try changing the cables with a set that you know works.

zom

Fouve wrote:

It sounds to me like you have a bad cable. I've had that happen with a few cables of my own. Also, make sure your hello timers are equal and not set to different times. That would cause them not to communicate as well. As far as I see, you have the right setup. Most of the time the problem is physical rather than any of the network settings, so try changing the cables with a set that you know works.

i tried changing the DTE cable and it still doesn't work....guess i should change the DCE cable as well....btw i am using a DCE cable which has 1 serial interface with 2 DCE female output interface that have DCE 1 and DCE 2....i tried to plug it into DCE 2 and then the router just shows that my serial0 is down and protocol down so i guess that the DCE 2 is not usable.
wonder if that's the DCE cable problem....this cable is given by my friend and he said that it can be use as crossover too....izzit because of the cable?

he-man

Might be worth buying a new cable, they're not that expensive, at least that way you can rule out cable problems with any future issue on other equipment.

ps get a DTE/DTC crossover, it cuts the chances of cable problems by 50% over 2 separate cables (DCE and DTE)

zom

thx alot for the helps guys ^^ really appreciate it problem solved!

he-man

What was it in the end :

zom

it happens to be the cable fault....which the 2 DEC interface cable was not suitable in doing crossover connection. after changing the cable the routers worked wonderfully ^^

KGhaleon

3 years back I had a cisco test where my instructor paired students in groups of twos and had them configure a rack of routers. Our test that day involved setting up RIP and getting our 5 routers communicating back and forth.

Just at the time of the test, one of our DCE/DTE cables went bad and we were unable to ping across it. After locating the problem, we quickly swapping it out for another and completed the test at 15-20 minutes.

If you don't mind, I have another question to add in:
How far can you ping in a network consisting of multiple routers connected by serial interfaces. Will you only be able to pick across 15?
I was doing a RIP lab earlier today in the Boson netSim with Four routers, and I noticed they were unable to ping devices 2 or 3 hops away. The clocking, addresses and everything seemed correct and there was no one point of failure. I just thought it was strange.

KG

EdTheLad

KGhaleon wrote:

How far can you ping in a network consisting of multiple routers connected by serial interfaces. Will you only be able to pick across 15?
I was doing a RIP lab earlier today in the Boson netSim with Four routers, and I noticed they were unable to ping devices 2 or 3 hops away. The clocking, addresses and everything seemed correct and there was no one point of failure. I just thought it was strange.
KG

How far you can ping depends on the value of ping timeout and also the TTL.
Rip will propagate routes a maximum of 15 hops,this has nothing to do with a ping.Once the route is available and the ping time out and TTL are greater than zero the ping will be propagated.
Use your Boson sim to learn commands only, this sim will not help when trying to learn network behaviour.My advice for your problem is to track the packet as it transverses your network checking the routing table as u go.

darkuser

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcprt2/1cfrip.htm