What can you do to prevent this issue from happening again?

Refer to the exhibit.

While troubleshooting high CPU utilization on one of your Cisco Catalyst switches, you find that the
issue is due to excessive flooding that is caused by STP. What can you do to prevent this issue from
happening again?

Refer to the exhibit.

While troubleshooting high CPU utilization on one of your Cisco Catalyst switches, you find that the
issue is due to excessive flooding that is caused by STP. What can you do to prevent this issue from
happening again?

A.
Disable STP completely on the switch.

B.
Change the STP version to RSTP.

C.
Configure PortFast on port-channel 1.

D.
Configure UplinkFast on the switch.

E.
Configure PortFast on interface Gi0/15.



Leave a Reply 3

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


Ben

Ben

portfast will stop the information of topology changes

zaha

zaha

we don’t know if the port who generate TC or simply relay them to the root.both cases will increment the TC counters.
portfast stops generating TC, but when TC’s get to Gi0/15, the port will start generating its own.

can someone reply on this please’i’am confused here.

Thx

Bruno Silva

Bruno Silva

The correct anwser is “E” but let’s comment why other are wrongs.

“A” – It’s impossible to disable STP on switchs. And don’t make sense to disable this feature.

‘B” – First of all, this switch is running MST and not STP, but change to RSTP will not fix this issue, because in RSTP a non-edge port when move from discarting state to forwarding state will generate BPDU with TC bit flag. This BDPU will flood mac address table and CPU will increase.

“C” – Port-channel 1 is the root port and you can’t assigned portfast feature in a root port

“D” – MST already has uplinkfast feature build-in natively