Start networking and exchanging professional insights

Register now or log in to join your professional community.

Follow

What could be the reason while Troubleshooting LAN Connectivity where Serial is UP, Line protocol is Down ?

List all the possible conditions for such an issue ..

user-image
Question added by Mohammed Imtiaz Ali Ahsan , IT Resident Engineer , DXC Technology - P&G Account
Date Posted: 2016/03/21
Muhammad Usman
by Muhammad Usman , Production Support Engineer , UDHC

For LAN connectivity one should use Ethernet E interface. Instead of Serial S interface.

Anyhow there are many reasons among them are:

 

1-Protocol mismatch at both ends

2-Configurations are incomplete/incorrect

The reasons can be 

Other side of the interface is shutdown

Encapsulation mismatch

Bandwidth or MTU mismatch

Clock rate not set in DCE end

 

sham Ratan
by sham Ratan , Network Engineer , DWP

shut or no shut both interfaces and other problem is  Encapsulation  mismatch!!

Inam Sofi
by Inam Sofi , Technical Associate , Concentrix - India

Encapsulation mismatch, interface is up as mentioned in the question.

nandan singh
by nandan singh , Network Admin , Networkers Home Pvt Ltd

the serial is up line protocol is down ...check  the neighbor interface shutdown (interface is not up )   and other problem is encapsulation  mismatch .

Mudassir Mubin Baig
by Mudassir Mubin Baig , Network Engineer , Saima Packaging Pvt. Ltd.

Check Clock Rate, and Bandwidth settings

wali saeed
by wali saeed , Manger , Farabi Medical Clinics

The encapsulation that is configured on  Router A does not match the

encapsulation that is configured on Router B

Muhammad adnan Qumar
by Muhammad adnan Qumar , IT engineer , Synopsis Solutions Ltd

My understanding is the first state is physical OSI Layer1. If its down then look for an issue such as cabling.

The line protocol state is L2 issues, most commonly encapsulation mismatch (HDLC vs PPP)

 

So for Serial0/1 (on both router interfaces)  displaying Serial0/1 is up, line protocol down...

 

1. I verify the encapsulation type is set for the same type.

2. I verify both interfaces have a unique IP address in the same subnet.

3. Check that bandwidth setting is the same. And MTU value is the same.

4. Understand this is not being caused by a admin shutdown condition (otherwise L1 state would not be up)

5. Assume this would not be a cable problem (wrong cable type, cable not plugged in, cable not seated fully).

 

CLOCK RATE. This needs to be set on the DCE side of a back to back configuration and it is a favorite of Cisco when it comes to troubleshooting serial interfaces.

ARSHAD GAFOOR
by ARSHAD GAFOOR , Network Implementation Engineer , Wipro

The reason is basically;

1. Other end interface might be down.

2. Encapsulation mismatch.

3. MTU miss match.

4. Protocol mismatch.

 

Ahsan Badar
by Ahsan Badar , Network Engineer , Dynamic Security (Atlas Telecom)

Line protocol is Down: indicates L2 (ethernet, frame relay, ATM etc) problem

Sajid Ibrahim
by Sajid Ibrahim , Network Engineer , Insight school of Engineering and Management

Both serial interface Baud rate must match then only it will communicate each other

More Questions Like This

Do you need help in adding the right keywords to your CV? Let our CV writing experts help you.