Exhibit
SwitchA# show interfaces gigabitethernet 0/1
GigabitEthernet0/1 is down, line protocol is down (err-disabled)
Hardware is Gigabit Ethernet, address is 0011.2233.4455 (bia 0011.2233.4455)
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, 1000BaseTX/FX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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, 0 no buffer
Received 0 broadcasts (0 multicast)
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, 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
SwitchA# show errdisable detect
ErrDisable Reason Detection Status
------------------ -----------------
udld Enabled
bpduguard Enabled
security-violation Enabled
SwitchA# show interfaces gigabitethernet 0/1 status
Port Name Status Vlan Duplex Speed Type
Gi0/1 err-disabled 1 auto auto 10/100/1000BaseTX- A
Replace the Category 5e cable with a Category 6 cable to support Gigabit Ethernet.
Why wrong: Category 5e cable is fully capable of supporting 1000BASE-T (Gigabit Ethernet) up to 100 meters, so a cable upgrade is not necessary.
- B
Configure the interface as a trunk port and disable spanning-tree BPDU guard.
The port is in err-disabled because bpduguard is enabled. Since this is a connection between two switches, the port should be configured as a trunk (or at least not as an access port with portfast) and bpduguard should be disabled to prevent the errdisable state.
- C
Replace the copper SFP with a fiber SFP to increase the distance.
Why wrong: The interface diagnostics show the port type is 10/100/1000BaseTX (copper RJ-45), not an SFP slot. The problem is not related to distance or transceiver type.
- D
Manually set the speed and duplex to 1000 Mbps and full duplex on both switches.
Why wrong: While speed/duplex mismatch can cause interface issues, the err-disabled state with bpduguard enabled indicates a BPDU guard violation, not a mismatch. The interface shows auto-negotiation is enabled.
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.