Troubleshooting Interfaces and Cabling

Question 1

Excessive Noise

Answer 1

• Results in transmission errors
• Is caused by Damaged cables/improper cable types
• Can be verified using show interfaces command
  
  • will see #### CRC and ## collision errors

Question 2

Collisions

Answer 2

• Result in network congestion and could result in dropped packets
• are caused by:
  
  • Too many nodes on a network segment
  • Malfunctioning NIC’s in host computers
  • Duplex mismatch errors
• Can be verified by issuing the show interfaces command.

Question 3

Late Collisions

Answer 3

• Result in network congestion because frames have to be re-sent
• Caused by Duplex mismatch errors | Network segment is too long
• Can be verified by issuing the show interfaces command.

Question 4

Duplex Mismatch

Answer 4

• Results in connectivity and performance problems
• indicated by a high number of collisions and late collisions
• Can be verified by using the show interface status command

Question 5

Autonegotiation

Answer 5

• is a method for automatic configuration of speed and duplex settings between network interfaces.
• Cisco recommends enabling autonegotiation on both sides of a link if supported.
• When one side is statically configured, the autonegotiation-enabled side will operate at the fastest supported speed by the remote side.
• Setting autonegotiation on only one side can lead to configuration issues, such as mismatched duplex settings.

Question 6

Speed Mismatch

Answer 6

• Occurs when one end of a network link has a different configured speed than the other end.
• Example: One end transmits at 10 Mbps, while the other end transmits at 100 Mbps.
• Result: The link remains down; no traffic can be sent or received.
• to Prevent: Ensure at least one end of the link is set to autonegotiate speed settings.
• use show interfaces status to check interface speed settings