Exhibit
Switch#show interfaces gigabitEthernet 1/0/24
GigabitEthernet1/0/24 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is aabb.cc01.1824 (bia aabb.cc01.1824)
Description: Server-01
Internet address is 192.168.1.10/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:02:34
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 12000 bits/sec, 12 packets/sec
5 minute output rate 8000 bits/sec, 8 packets/sec
12345 packets input, 1234567 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
12345 packets output, 1234567 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Switch#show controllers gigabitEthernet 1/0/24
Interface GigabitEthernet1/0/24
Hardware is Gigabit Ethernet
Media Type: 10/100/1000BaseTX
PHY: Marvell 88E1111
MASTER: internal
Auto-negotiation: enabled
Link Partner Capabilities: 10/100/1000BaseT, Full-duplex
Local Capabilities: 10/100/1000BaseT, Full-duplex
Advertised Capabilities: 10/100/1000BaseT, Full-duplex
Operational: 1000BaseT, Full-duplex
Flow Control: off (both sides)
MDIX: off (crossover cable not detected)
Cable length: 100 meters
Speed: 1000 Mb/s
Duplex: Full
Errors:
CRC errors: 0
Alignment errors: 0
Symbol errors: 0
False carrier: 0
Runts: 0
Giants: 0
Transceiver: internal
DTE status: up
Loopback: none
Last link flapped: 00:00:05 ago- A
Duplex mismatch between the switch port and the server NIC
Why wrong: Duplex mismatch typically causes CRC errors and late collisions, not runts and giants. The 'show controllers' shows both sides are Full-duplex, so duplex mismatch is unlikely.
- B
Faulty cable or connector causing physical layer errors
Runts and giants without CRC errors often indicate physical layer issues like a bad cable, connector, or excessive noise. The cable length at maximum (100 meters) and MDIX off suggest potential signal degradation, leading to intermittent flapping and err-disabled state.
- C
Incorrect VLAN configuration on the switch port
Why wrong: VLAN mismatch causes connectivity issues but does not produce runts or giants. It would result in packets being dropped at Layer 2, not physical layer errors.
- D
Speed mismatch between the switch port and the server NIC
Why wrong: Speed mismatch would cause the port to not come up or to flap with errors like CRC errors. The 'show controllers' shows both sides are operating at 1000 Mb/s Full-duplex, so speed mismatch is not present.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.