L1 and L2 Troubleshooting

Posted on August 20, 2009. Filed under: CCNA, ICND1 break down | Tags: , , , |


The most import troubleshooting command is “show interface fa0/0”.

R1#show interface serial0

In normal conditions, we will see:

“Serial0 is up, line protocal is up.”

The first part is the port’s physical status, the second part is the port’s logical status.

When we have problem at L1 and L2, we will see:

  • “Serial0 is administratively down, line protocal is down.” “administratively down” means the interface is shutdown by the adminstrator manually. Use “no shutdown” to open it.
  • “Serial0 is down, line protocol is down”. This time “down” means there are physical problem about the connection. The solution is to check the layer 1 devices such as port connection or wrong cable.
  • “fa 0/0 is down, line protocol is down (err-disabled)”. “err-disabled” means the port is shut down because of some security vialations. Check the port security for the trouble with command “show-port security interface”.
  • “Serial0 is up, line protocol is down”. In this case, the L1 physical layer is fine, but L2 or higher level protocol is wrong. Most possibly, either the clock rate is not set on the DCE or the encapsulation type don’t match on both ends of the link.
  • “Serial0 is up, line protocol is down (looped)”. In this case, the L1 physical layer is fine, but L2 or higher level protocol is wrong. “(looped)” means there is an active loopback on the router, on the line between the router and the local Frame Relay switch, or on the local Frame Relay switch itself. To fix it,  save your running-config and issue the encapsulation hdlc, keepalive 10 and unique ip address commands on the main interface. Check this cisco document for details.

Another useful IOS “show” commands are

Switch#show mac-address-table

Swtich#show vlan brief

Router#show version

Don’t forget the command “ping 1.0.0.0” and the extended ping command “ping“.

Sometimes, we need run-time informations, we use debug commands.

R1#debug ip packet

R1#debug ip protocols

R1#debug ip rip

To add a time stamp to a debug or log message, use command “service timestamps“.

If we want to see the output of our debugs during our session, use command “terminal monitor” in EXEC mode. All debug outputs and system error messages for the current terminal and session will be displayed.

Looking at log files can give us insight about during troubleshooting. To enable system messages to a local buffer use command “logging buffered [size]” in global configuration mode. The default size is 4096k and once this is full older messages will be overwritten with newer ones.

Don’t forget the house-keeping after trouble-shooting.

R1#show debug

R1#undebug all

Advertisements

Make a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

6 Responses to “L1 and L2 Troubleshooting”

RSS Feed for IT Certifications Comments RSS Feed

Excellent it is very useful to learn d troubleshooting of L1 and L2 switching and please add some more problems for learn troubleshooting and if it is possible please send any papers to my mail please.

Your articles are very helpful I just wanted to come and visit in your site every time I am online.

Perfectly explanation of topics level-wise.
It would be so nice of you if you can get the same for ICND-2 as well just like ICND-1.

Thanks a ton in advance !!

[…] Cisco Discovery protocol (CDP) * L1 and L2 Troubleshooting * Telnet and SSH Maintenance Commands * Administrative Distance * Extended Ping […]

[…] https://kl2217.wordpress.com/2009/08/20/l1-and-l2-troubleshooting/ xxxxx http//xyznetwork.blogspot.com/2009/08/l1-and-l2-troubleshooting_20.html […]


Where's The Comment Form?

Liked it here?
Why not try sites on the blogroll...

%d bloggers like this: