Opened 3 years ago

#2842 assigned defect

Cisco CCNP/ BCMSN Exam Tutorial: Configuring PortFast And BPDU Guard

Reported by: anonymous Owned by:
Priority: major Milestone: Commissioning
Component: Zeus Configurator Version: 2.0
Severity: minor Keywords:
Cc:

Description

In http://pigskinref.com/secure/members/mcfarlandwilliamson7/activity/208756/ , you figured out PortFast? and the issues it can bring about if established up on the incorrect port! Correct only for modify ports joined immediately to a one host, PortFast? permits a port operating STP to go straight from blocking to forwarding manner.

A Cisco router will give you a warning when you configure PortFast?:

SW1( config) #int quickly /five

SW1( config-if) #spanning- tree portfast

% Warning: portfast will have to only be enabled on ports related to asingle host. Connecting hubs, concentrators, switches, bridges, and quite a few other people. to this interface when portfast is allowed, can result in temporarybridging loops. Use with Warning

% Portfast has actually been configured on FastEthernet0/five but will just

have effect when the person interface is in a non-trunking manner.

SW1( config-if) #.

Not only will the swap alert you about the accurate use of PortFast?, but you have to have to location the port into attain method in advance of PortFast? will take into consideration end result.

There is a possibility - just a possibility - that any personal is probably to take care of to link a modify to a port handling Portfast. The subsequent challenge is that there may well nicely be a new root bridge decided on - and it may well be a change that is not even in your network!

BPDU Guard safeguards compared to this devastating chance. If https://williamsonmarshall1.werite.net/post/2022/01/08/Factors-to-describe-close-to-Motorcar-Rapture-Options is made available in on a port that is functioning BPDU Guard, the port will be shut down and place into blunder disabled state, founded to on the improve as err-disabled. A port position in err-disabled condition really should be reopened by hand.

BPDU Guard is off on all ports by default, and is authorized as found out mentioned below:.

SW1( config) #int quickly /five.

SW1( config-if) #spanning- tree bpduguard permit.

It is a smart idea to allow BPDU Guard on any port you are running PortFast? on. You can uncover no cost in overhead, and it does stay distinct of the prospect of a swap sending BPDUs into a port established up with PortFast? - not to go around the likelihood of a swap not significantly less than your regulate turning into a root change to your community!

% Warning: portfast necessitates to only be enabled on ports relevant to asingle host. Connecting facilities, concentrators, switches, bridges, and so forth. There is a likelihood - just a risk - that anybody is possible to take care of to connection a swap to a port managing Portfast. If any BPDU will come in on a port that is running BPDU Guard, the port will be shut down and positioned into slip-up disabled place out, confirmed to on the swap as err-disabled. A port positioned in err-disabled affliction specifications to be resumed manually.

Change History (0)

Note: See TracTickets for help on using tickets.