Line Protocol Down - Very Basic Lab Setup

Mar 19, 2006 14 Replies
Line Protocol Down - Very Basic Lab Setup open original image

I cannot ping the Serial0 interfaces on either of the two 2501's in my lab, and the line protocol shows down for both.



Here are the configs:


Router2, DCE



--------------



version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Router2 ! enable password pasword ! ip subnet-zero ! ! ! ! interface Ethernet0 ip address 192.168.1.102 255.255.255.0 ! interface Serial0 ip address 192.168.2.2 255.255.255.0 encapsulation x25 clockrate 56000 ! interface Serial1 no ip address shutdown ! router rip network 192.168.2.0 ! no ip classless no ip http server ! ! line con 0 line aux 0 line vty 0 password password login line vty 1 4 login ! end


------------------



Router1, DTE:


--------------------- hostname Router1 ! enable password password ! ip subnet-zero ! ! ! ! interface Ethernet0 ip address 192.168.1.108 255.255.255.0 ! interface Serial0 ip address 192.168.2.1 255.255.255.0 encapsulation x25 ! interface Serial1 no ip address shutdown ! router rip network 192.168.2.0 ! no ip classless no ip http server ! ! line con 0 line aux 0 line vty 0 password password login line vty 1 4 login ! end



-------------



What am I doing wrong? I've tried different encapsulations, but with same results.



Thanks


-tom



Also, in light of a post earlier today, I did a show controllers, and it looks correct:

Router2#show controllers s 0 HD unit 0, idb = 0x256374, driver structure at 0x25DE98 buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 56000

Router1#show controllers s 0 HD unit 0, idb = 0x256374, driver structure at 0x25DE98 buffer size 1524 HD unit 0, V.35 DTE cable

Thanks

-tom

You have set both ends for X.25 encapsulation. Was that the intent? Do you really want to run X.25 encaps on this serial interface? If not, just type in "encap hdlc" under the serial interface config to set the default HDLC encap and you should be able to ping fine.

OTOH if you really wanted X.25 encaps on the serial line, then you need to do more config like an X.25 address, X.25 map etc. Take a look at

formatting link
for how to set up back-to-back X.25 connections.

Cisco da Gama

formatting link

I changed the encap to hdlc, but the problem persists.

I cannot ping the local serial0 interface on either router, from that router.

Thanks

-tom

Could you try a "show int" on the two serial0 interfaces, instead of the "show controller"?

The first step to a serial port ping is a "show interface" that shows "up up".

Hi Tom, Can you do a (sh ip int brief) on both routers. Show the output you get. Peter.

Router2#sh ip int brief Interface IP-Address OK? Method Status Prot ocol Ethernet0 192.168.1.102 YES NVRAM up up

Serial0 192.168.2.2 YES NVRAM up down

Serial1 unassigned YES NVRAM administratively down down

Router1#sh ip int brief Interface IP-Address OK? Method Status Prot ocol Ethernet0 192.168.1.108 YES NVRAM up up

Serial0 192.168.2.1 YES NVRAM up down

Serial1 unassigned YES NVRAM administratively down down

Thanks

-tom

Now do a (sh run int ser 0) on both routers. Peter.

Router2#sh run int ser 0 Building configuration...

Current configuration : 119 bytes ! interface Serial0 ip address 192.168.2.2 255.255.255.0 no ip route-cache no ip mroute-cache clockrate 56000 end

-----------------------

Router1#sh run int ser 0 Building configuration...

Current configuration : 102 bytes ! interface Serial0 ip address 192.168.2.1 255.255.255.0 no ip route-cache no ip mroute-cache end

---------------

-tom

Sometime routers or interfaces lock up. Try conf t int ser 0 shutdown no shutdown

or

copy run start reload or power reset

Peter.

Thanks, but no go. If there is a hardware issue, how would I narrow that down?

Thanks

-tom

V.35 loopback plug into DCE cable,router sould see loopback on serial. Peter.

Excellent - I'll come up with the cable.

Thanks for your help.

-tom

Change to encapsulation ppp.

formatting link
Peter.

For all who are interested - it turns out to be a bad interface - s0 - on RouterB.

Thanks for everyone's help.

-tom

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required