Which action can the engineer take to resolve this issue?

Refer to the exhibit.

Users of PC-1 experience slow connection when a webpage is requested from the server. To increase bandwidth, the network engineer configured an
EtherChannel on interfaces Fa1/0 and Fa0/1 of the server farm switch, as shown here:
Server_Switch#sh etherchannel load-balance
EtherChannel Load-Balancing Operational State (src-mac):
Non-IP: Source MAC address
IPv4: Source MAC address

IPv6: Source IP address
Server_Switch#
HoweIer, traffic is still slow. Which action can the engineer take to resolve this issue?

Refer to the exhibit.

Users of PC-1 experience slow connection when a webpage is requested from the server. To increase bandwidth, the network engineer configured an
EtherChannel on interfaces Fa1/0 and Fa0/1 of the server farm switch, as shown here:
Server_Switch#sh etherchannel load-balance
EtherChannel Load-Balancing Operational State (src-mac):
Non-IP: Source MAC address
IPv4: Source MAC address

IPv6: Source IP address
Server_Switch#
HoweIer, traffic is still slow. Which action can the engineer take to resolve this issue?

A.
Disable EtherChannel load balancing.

B.
Upgrade the switch IOS to IP services image.

C.
Change the load-balance method to dst-mac.

D.
Contact Cisco TAC to report a bug on the switch.

Explanation:
Since this traffic is coming from PC-1, the source MAC address will always be that of PC-1, and since the load balancing method is source MAC, traffic will only be
using one of the port channel links. The load balancing method should be changed to destination MAC, since the web server has two NICs traffic will be load
balanced across both MAC addresses.



Leave a Reply 0

Your email address will not be published. Required fields are marked *