Actually GNS set clock-rate for both ends and this is not cause problems, at least not under back2back serial link. Move your mouse over serial link in GNS workplace and see if it show you the same link like the one you configured. GNS has some weird bugs and should take into account that sometimes can be that and not your configs. Change your serial module and see if it works
On Fri, May 14, 2010 at 11:15 AM, Patrice Ngassam <[email protected]>wrote: > Hi folks, > I've been tried to work on VOL2 Lab1 using GNS3 for a couple of days. I am > having serious trouble with Serial interfaces. > To keep it short, R2 is connected to R5 using S0/1 and vice-versa, no > matter what I try the line protocol on that serial interface is always down. > My original config on R2 and R5: > > R2 > ---- > *username R5R2 password brayden > ! > interface Serial0/1 > description R5 s0/1 > ip address 150.50.9.2 255.255.255.192 > encapsulation ppp > clock rate 2000000 > ppp reliable-link > ppp authentication pap > ppp pap sent-username R2R5 password 0 brayden > !* > > R5 > ------ > *username R2R5 password brayden > ! > interface Serial0/1 > description R5 s0/1 > ip address 150.50.9.2 255.255.255.192 > encapsulation ppp > clock rate 2000000 > ppp reliable-link > ppp authentication pap > ppp pap sent-username R5R2 password 0 brayden > !* > > > line protocol down on R2 and R5 > debug ppp authentication did not help as I was supecting some issue with > PPP authentication. I then removed all the ppp section on both R2 and R5 and > change clock rate on R2 : > > R2 > ---- > *interface Serial0/1 > description R5 s0/1 > ip address 150.50.9.2 255.255.255.192 > clock rate 64000* > ! > > R5 > ------ > > *interface Serial0/1 > description to R2 s0/1 > ip address 150.50.9.5 255.255.255.192 > clock rate 2000000* > ! > > Same result: this f... line protocol is still down > > *R5(config-if)#do sh int s0/1 > Serial0/1 is up, line protocol is down > Hardware is GT96K Serial > Description: to R2 s0/1 > Internet address is 150.50.9.5/26 > 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:07, output hang never > Last clearing of "show interface" counters 00:04: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/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 > 32 packets output, 1693 bytes, 0 underruns > 0 output errors, 0 collisions, 10 interface resets > 0 output buffer failures, 0 output buffers swapped out > 0 carrier transitions > DCD=up DSR=up DTR=up RTS=up CTS=up* > > > > > I tried all applicable troubleshooting step the cisco Output Interpreter > suggested me to do with success. I am coming to you as you are my "Gateway > of last resort". > > Please help. > > > > *Patrice Ngassam > CEO NEN NET Inc.* > > > > > ------------------------------ > De nouvelles Emoticones sur Messenger ? Téléchargez les Emoticones pâte à > modeler > !<http://www.ilovemessenger.fr/emoticones/emoticones-pate-a-modeler.aspx> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
