How to Troubleshoot Cisco Fastethernet or Gigabitethernet Interface

Basic Fastethernet and Gigabitethernet Interface Troubleshooting Steps:

Follow  below steps to troubleshoot the Ethernet, Fastethernet, GigabitEthernet or Tengigabitethernet on Cisco Router or Switch. Enter the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command.

1)       Verify that the interface is up.

2)       Verify that the line protocol is up.

3)       Verify that the interface duplex mode matches the remote interface configuration.

4)       Verify that the interface speed matches the speed on the remote interface

5)       Observe the output hang status on the interface.

6)       Observe the CRC counter.

7)       Observe the late collision counter.

8)       Observe the carrier signal counters.

Troubleshoot and correct the detected problems on Fastethernet/Gigabitethernet Interface:  

1) Verify that the interface is up:

In the output got from the show interfaces fastethernet, show interfaces gigabitethernet or showinterfaces tengigabitethernet command, verify that the interface is up. If the interface is down, perform the following corrective actions:

  • If the interface is administratively down, use the no shutdown interface configuration command to enable the interface.
  • Be sure that the cable is fully connected.
  • Verify that the cable is not bent or damaged. If the cable is bent or damaged, the signal will be degraded.
  • Verify that a hardware failure has not occurred. Observe the LEDs to confirm the failure

2) Verifying the Line Protocol Is Up:

In the output from the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command, verify that the line protocol is up. If the line protocol is down, the line protocol software processes have determined that the line is unusable. Perform the following corrective actions:

     •     Replace the cable.

     •     Check the local and remote interface for misconfiguration.

     •     Verify that a hardware failure has not occurred. Observe the LEDs to confirm the failure.

3) Verifying Output Hang Status:

In the output for the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command, observe the value of the output hang field.

  • The output hang provides the number of hours, minutes, and seconds since the last reset caused by a

lengthy transmission. When the number of hours in the field exceeds 24 hours, the number of days and hours is shown. If the field overflows, asterisks are printed. The field shows a value of never if no output hangs have occurred.

4) Verifying the CRC Counter:

In the output from the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command, observe the value of the CRC counter. Excessive noise will cause high CRC errors accompanied by a low number of collisions. Perform the following corrective actions if you encounter high CRC errors:

Check the cables for damage.

Verify that the correct cables are being used for the SPA interface

5) Verifying Late Collisions:

In the output from the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command, observe the value of the late collision counter. Perform the following corrective actions if you encounter late collisions on the interface:

Verify the duplex mode on the local and remote interface match. Late collisions occur when there is a duplex mode mismatch.

Verify the length of the Ethernet cables. Late collisions result from cables that are too long.

6) Verifying the Carrier Signal:

In the output from the show interfaces fastethernet, show interfaces gigabitethernet or show interfaces tengigabitethernet command, observe the value of the carrier signal counters. The lost carrier counter shows the number of times that the carrier was lost during transmission. The no carrier counter shows the number of times that the carrier was not present during transmission. Carrier signal resets can occur when an interface is in loopback mode or shut down. Perform the following corrective actions if you observe the carrier signal counter incrementing outside of these conditions:

Check the interface for a malfunction.

Check for a cable problem.

 

Filed Under: Troubleshooting

Tags:

About the Author:

RSSComments (2)

Leave a Reply | Trackback URL

  1. John says:

    I just wanted to thank you for writing this article on Fastethernet and Gigabitethernet interface. I liked reading it. Best wishes, John 🙂

Leave a Reply




If you want a picture to show with your comment, go get a Gravatar.