Exhibit
R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is Gigabit Ethernet, address is aaaa.bbbb.cccc (bia aaaa.bbbb.cccc)
Internet address is 192.168.1.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, 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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
12345 packets input, 1234567 bytes
Received 123 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
1500 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
R1# show interfaces GigabitEthernet0/1
GigabitEthernet0/1 is up, line protocol is down
Hardware is Gigabit Ethernet, address is aaaa.bbbb.cccd (bia aaaa.bbbb.cccd)
Internet address is 192.168.1.5/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)
Auto-duplex, Auto-speed, 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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes
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
0 packets output, 0 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
R1# show running-config interface GigabitEthernet0/0
Building configuration...
Current configuration : 100 bytes
!
interface GigabitEthernet0/0
no shutdown
ip address 192.168.1.1 255.255.255.252
duplex full
speed 1000
end
R1# show running-config interface GigabitEthernet0/1
Building configuration...
Current configuration : 75 bytes
!
interface GigabitEthernet0/1
no shutdown
ip address 192.168.1.5 255.255.255.252
end- A
Configure 'no duplex' and 'no speed' under interface GigabitEthernet0/0 to enable auto-negotiation.
This is correct because the issue is a duplex mismatch on GigabitEthernet0/0. R1 is statically set to full duplex and 1000 Mbps, but the connected switch port likely uses auto-negotiation or half-duplex, causing input errors. Reverting to auto-negotiation with 'no duplex' and 'no speed' allows both sides to negotiate the best settings, resolving the mismatch.
- B
Change the duplex setting on GigabitEthernet0/0 to half-duplex using 'duplex half'.
Why wrong: This is incorrect because forcing half-duplex on R1's GigabitEthernet0/0 would likely cause a mismatch if the switch is set to full duplex or auto-negotiation, worsening the problem. The correct approach is to enable auto-negotiation on both sides.
- C
Apply 'speed 100' and 'duplex full' on GigabitEthernet0/0 to match a common switch configuration.
Why wrong: This is incorrect because the interface is GigabitEthernet, which typically requires 1000 Mbps. Forcing 100 Mbps and full duplex may not be supported or could cause a speed mismatch. Additionally, the root cause is duplex mismatch, not speed.
- D
Clear the interface counters on GigabitEthernet0/0 with 'clear counters gigabitethernet0/0' without changing any configuration.
Why wrong: This is incorrect because clearing counters only resets statistics; it does not fix the underlying duplex mismatch. The input errors will continue to accumulate after clearing.
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.