Exhibit
R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is ISR4331-2x1GE, address is aabb.cc00.0100 (bia aabb.cc00.0100)
Internet address is 192.0.2.1/30
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, link type is auto, media type is RJ45
output flow-control is unsupported, input 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 never
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
12034 packets input, 1234567 bytes, 0 no buffer
Received 12034 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
150 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
45678 packets output, 4567890 bytes, 0 underruns
0 output errors, 0 collisions, 2 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
R1#- A
Configure 'duplex auto' and 'speed auto' on interface G0/0 of R1.
This is correct because the symptoms (input errors with zero CRC/frame errors, full-duplex manually set) indicate a duplex mismatch. Enabling auto-negotiation on both ends allows the devices to agree on duplex and speed, resolving the mismatch and eliminating collisions that cause input errors.
- B
Replace the faulty cable between R1 and R2.
Why wrong: This is incorrect because the interface is up/up and there are no CRC or frame errors, which would typically indicate a physical layer issue like a faulty cable. The input errors without CRC suggest a duplex mismatch, not a cabling problem.
- C
Increase the MTU size on interface G0/0 of R1.
Why wrong: This is incorrect because increasing MTU would not resolve duplex mismatch issues. MTU affects the maximum packet size, and changing it could cause fragmentation problems or mismatches with the neighbor, worsening connectivity.
- D
Disable CDP on interface G0/0 of R1.
Why wrong: This is incorrect because CDP (Cisco Discovery Protocol) is a Layer 2 protocol used for neighbor discovery and does not affect duplex or speed settings. Disabling CDP would not fix the duplex mismatch causing input errors.
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.