Soru

Zorluk: ZorInterface and Cable Troubleshooting Issues

A network engineer is troubleshooting performance issues across several switch interfaces using Cisco IOS CLI outputs. Match each interface status or error counter symptom on the left to its corresponding Layer 1 or Layer 2 root cause on the right.

  • Interface shows incrementing 'late collisions' and FCS errors on a local interface set to half-duplex while experiencing poor throughput.Duplex mismatch resulting from the remote device operating in full-duplex mode while the local port operates in half-duplex mode.
  • Interface shows status 'GigabitEthernet0/1 is down, line protocol is down' when connecting two switch interfaces with Auto-MDIX disabled using a straight-through cable.Pinout misconfiguration between identical MDI-X interfaces requiring a crossover cable when auto-negotiation features are inactive.
  • Interface shows status 'GigabitEthernet0/2 is up, line protocol is down (disabled)' accompanied by encapsulation error messages.Layer 2 framing or keepalive mismatch between connected endpoints causing data-link failure while physical signaling remains active.
  • Interface shows incrementing 'giants' and CRC errors on an Ethernet port receiving traffic from a server.End-host network interface card (NIC) transmitting babbling/oversized frames exceeding the standard Maximum Transmission Unit (MTU).

Cevap

Each interface symptom matches its specific root cause based on Cisco IOS interface operation: Late collisions match a duplex mismatch; physical down/down with straight-through and disabled Auto-MDIX matches pinout misconfiguration requiring a crossover cable; up/down (disabled) matches Layer 2 framing or keepalive failure; incrementing giants with CRC errors matches oversized frame transmission exceeding MTU.
Each symptom accurately maps to its fundamental physical or data-link root cause: late collisions indicate duplex mismatch; down/down with straight-through cabling on switch-to-switch links without Auto-MDIX indicates incorrect pinout; up/down indicates Layer 2 framing/keepalive failure; and giants indicate frames received that exceed the allowable maximum frame size.

Adım Adım Çözüm

1
Analyze the late collisions symptom
Identified duplex mismatch as the root cause
Late collisions happen when one side sends frames mid-transmission because it is configured as full-duplex while the local side is half-duplex.
2
Analyze the line status down / line protocol down scenario with Auto-MDIX disabled
Identified pinout misconfiguration requiring a crossover cable
Switch-to-switch links connect MDI-X to MDI-X. Without Auto-MDIX, a straight-through cable causes Tx-to-Tx mapping, resulting in Layer 1 link failure.
3
Analyze the up / line protocol down (disabled) state
Identified Layer 2 framing or encapsulation mismatch
Layer 1 is active (up), but Layer 2 fails to establish framing or keepalive communication, causing line protocol to be down.
4
Analyze incrementing 'giants' and CRC counters
Identified oversized frame transmission exceeding MTU limits
'Giants' explicitly refer to frames received over 1518 bytes (or configured MTU), typically caused by jabbering NICs or MTU mismatch.

Anahtar Kavram

Cisco IOS Interface Counter Analysis and Physical/Data-Link Troubleshooting
Bu soruyu puanla