Exhibit
R1# show interfaces gigabitEthernet 0/0
GigabitEthernet0/0 is up, line protocol is down
Hardware is ISR4331, address is aabb.cc00.0100 (bia aabb.cc00.0100)
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)
Auto-duplex, Auto-speed, 1000BaseTX/FX
input errors 0, CRC 0, frame 0, overrun 0, ignored 0
output errors 0, collisions 0, interface resets 0
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 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 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 gigabitEthernet 0/0
Building configuration...
Current configuration : 114 bytes
!
interface GigabitEthernet0/0
ip address 10.0.0.1 255.255.255.252
shutdown
end- A
Enter interface configuration mode for the down interface and issue the 'no shutdown' command.
The 'shutdown' command administratively disables an interface. Issuing 'no shutdown' re-enables it, bringing the interface up and allowing the line protocol to come up if the other end is properly configured.
- B
Enter global configuration mode and issue the 'interface reset' command to reset the interface counters.
Why wrong: This is incorrect because 'interface reset' is not a valid Cisco IOS command. Resetting counters does not bring an administratively down interface up.
- C
Enter interface configuration mode and issue the 'speed' command to set the interface speed to match the connected device.
Why wrong: This is incorrect because the interface is administratively down due to the 'shutdown' command, not due to a speed mismatch. Changing speed does not bring an administratively down interface up.
- D
Enter interface configuration mode and issue the 'no keepalive' command to disable keepalives.
Why wrong: This is incorrect because disabling keepalives does not bring an administratively down interface up. Keepalives are used to detect remote failures, not to enable an interface.
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.