Exhibit
R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is CN Gigabit Ethernet, address is 0000.0c12.3456 (bia 0000.0c12.3456)
Internet address is 10.0.0.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, 100Mb/s, media type is RJ45
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:05, 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 1000 bits/sec, 2 packets/sec
5 minute output rate 2000 bits/sec, 3 packets/sec
1500 packets input, 120000 bytes, 0 no buffer
Received 50 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
100 input errors, 100 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1500 packets output, 130000 bytes, 0 underruns
0 output errors, 0 collisions, 1 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- A
Enter interface configuration mode for the problematic interface and issue the 'no speed' and 'no duplex' commands to revert to auto-negotiation.
This is correct because CRC errors and input errors often indicate a duplex mismatch. Manually setting speed and duplex on one side while the other uses auto-negotiation can cause such errors. Removing manual settings allows both sides to auto-negotiate, resolving the mismatch.
- B
Enter interface configuration mode and issue the 'speed 100' and 'duplex full' commands to ensure both sides are set to the same values.
Why wrong: This is incorrect because the interface is already manually set to speed 100 and duplex full, yet errors persist. Reapplying the same settings does not address the root cause; the problem is likely a mismatch with the remote side.
- C
Enter interface configuration mode and issue the 'no shutdown' command to bring the interface up.
Why wrong: This is incorrect because the interface is already up (as indicated by the show interface output showing line protocol is up). The issue is not administrative shutdown but physical layer errors.
- D
Enter interface configuration mode and issue the 'duplex half' command to match the remote side's duplex setting.
Why wrong: This is incorrect because setting duplex to half on R1 would create a mismatch if R2 is using full-duplex (which is typical for 100 Mb/s links). The correct approach is to auto-negotiate, not force half-duplex.
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.