269
82. A. The interface has been administratively down, which means that the interface has
been placed into a shutdown state. To resolve the problem, a
no shutdown command
must be configured on the interface. There is no evidence in the exhibit that the interface
has negotiated at half-duplex. The exhibit does not show any evidence that the duplex is
mismatched on the interface, because the interface states it is administratively disabled.
The exhibit also shows no evidence that the cable is shorted on the interface.
83. C. In order to clear the counters for a single interface, you would use the command
clear counters interface fast 0/1. After it’s entered, you will need to confirm
clearing of the counters. Then you can monitor the solution provided on the interface.
The command
reset counters interface fast 0/1 is incorrect. The command
clear interface fast 0/1 is incorrect. The command clear statistics
interface fast 0/1 is incorrect.
84. D. The counters on this interface are all nominal, but the interface and line protocol are
down/down. This most likely suggests that the cable is disconnected. If the interface was
shut down, it would state in the exhibit that the interface was administratively shut down.
There is no evidence in the exhibit that the interface is negotiated at half-duplex. The
interface is not operating nominally because it is in a down state.
85. A. It is recommended to set all servers and networking hardware statically for speed and
duplex. If a network interface flaps (transitions between up and down), auto-negotiation of
speed and duplex will be performed again, which could create a service outage. Changing
the VLAN to another VLAN will not have any effect on interface resets and disconnects.
Changing the switchport mode to a trunk is only applicable if the other side of the link
is another switch that is configured as a trunk. Setting the switchport to auto-negotiate
will turn on the Dynamic Trunking Protocol (DTP) and allow the switchport to become a
trunk if plugged into another switch with DTP.
86. D. The txload and rxload counters are extremely high. This depicts that the interface
is not fast enough for the data being transferred. The speed and duplex currently are
10 Mb/s and full-duplex. However, the interface on the switch is capable of 100 Mb/s. It is
recommended to upgrade the node’s NIC. Although there are no major problems with the
interface, the counters depict congestion on the interface. The exhibit shows no evidence
that the interface is auto-negotiating speed and duplex. Although there are a large number
of broadcasts, this is not a problem compared to the load on the interface.
87. A. The commands to set the port back to auto-negotiation are
speed auto and
duplex auto. You can also negate the command with no speed and no duplex
commands. Both methods will set auto-negotiation back on the port. The commands
speed autonegotiate and duplex autonegotiate are incorrect. The command
switchport autonegotiate is incorrect. The command interface autonegotiate is
incorrect.
88. B. Cisco switches can auto-detect speed, so the speed sensed will be 100 Mb/s. However,
if the switch cannot detect the speed, then it will fall back to 10 Mb/s. Duplex is decided
upon by bandwidth when IEEE auto-negotiation is turned off. If the speed is 10 Mb/s or
100 Mb/s, then the duplex will be half-duplex; otherwise it will be full-duplex on 1000
Mb/s links.
Do'stlaringiz bilan baham: |