Welcome to Francisco CC and be switched 201 15 Exam Prep series. My name is Philip Pension. Early on in the race, every sort we're gonna focus on Luke guard on road card
If a block import on unknown Road bridge no longer receives any bpd use from the other non would switch this was usually means some sort of uni directional failure between the links. It will wait on filaments. Each timer expires and then transition so far within state in two times the forward delay timer know this creates a loop
on you could enable look guard to protect against this type of uni directional failure. Once Luke guard is enable
the block import we transition into the loop inconsistent state.
You should only enable Luke guard on your route on non designated ports in your switches. It is advisable to configure. Look guard on apart into fierce pieces. So from the interfere stop configuration, would you would issue the command spun in tree yard, look to prevent any switches which is introduced their network from taking over the rude ritual. We can enable rude guard
on the non reports in the switches that are leading away from the rude words,
thus eliminating any bpd. You coming in with a better priority to take over the route braids role
would guard prevents the port receiving a superior bpd was from becoming the route port on it places the port in the root, inconsistent state. Once the port stops receiving superior bpd. Use rude guard. We enables the port and removes the route. Inconsistency State
the configure route guard. You would do it on a poor port basis from interferes up configuration. Would you? Would you see the command spine entry guard route? I'll bring up a lot knows we'll see how we would consider a Luger on route card.
No to set up Luke guard,
Let's say one of the set of Blue Guard on one of my ports.
The command, his spine entry
No, I would specify the word look,
and that's it. That's how we would set up Luke. GERD.
No. If I wanted to set up route guard,
the command is similar.
Instead of loop, I would say route,
but no, you can't run. Look guard on regarding the same port because one is gonna disable the auto,
as you will see when I press enter.
Now, if you look under the running conflict for the interferes, we're no longer seen spine entry guard loop. But instead we're seeing spine entry guard route. So they're mutually exclusive. You can only run one, but not both on the same interferes. All right, let's go back to the slides.
We have a post assessment question which command enables. Look, guard on an interface, a spine entry loop guard or be spun entry guard loop or a C spine entry loop.
The answer is B spine entry guard. Look,
And there is every sort We wrapped up spine entry by working with loved guard on route guard.
In the next episode, River in a switch gears to spun on our spun. This is Phillip. Mention Ali and I wanna thank you would choose in cyber