Exhibit
R1# show interfaces gigabitEthernet 0/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 10.0.0.1/30
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 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
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 00:10:00
Input queue: 0/375/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 1000 bits/sec, 2 packets/sec
120 packets input, 9600 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
120 packets output, 9600 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
R1# show interfaces gigabitEthernet 0/1
GigabitEthernet0/1 is up, line protocol is down
Hardware is ISR4331-2x1GE, address is aabb.cc00.0101 (bia aabb.cc00.0101)
Internet address is 10.0.0.5/30
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 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 00:10:00
Input queue: 0/375/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 1000 bits/sec, 2 packets/sec
120 packets input, 9600 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
150 input errors, 150 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
120 packets output, 9600 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
Configure the interface with the 'duplex full' command.
This is correct because the show interface output indicates a duplex mismatch: R1 is set to half-duplex while the remote side is likely full-duplex, causing CRC errors and flapping. Setting duplex to full on R1 resolves the mismatch and stabilizes the link.
- B
Configure the interface with the 'speed 100' command.
Why wrong: This is incorrect because the issue is a duplex mismatch, not a speed mismatch. While speed should match on both ends, the primary problem is duplex; setting speed alone does not fix the duplex mismatch.
- C
Configure the interface with the 'no shutdown' command.
Why wrong: This is incorrect because the interface is administratively up (not shutdown). The problem is a duplex mismatch, not an administrative shutdown.
- D
Configure the interface with the 'duplex auto' command.
Why wrong: This is incorrect because setting duplex to auto on a manually configured full-duplex link can cause a mismatch. The remote side is likely set to full-duplex, so R1 must also be set to full-duplex manually to match.
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.