pdu guard, portfast are configured at the access layer so that the interface transitions into the forwarding state immediately in order to
avoid unnecessary TCN changes. These ports should see only end-station traffic so we configure these features here.
The device which is configured as the root in the network, in order to ensure that it remains the root and is not affected by changes in the
network we can configure root guard, loop guard.
Loop guard should be enabled on ports at any layer where there is a chance of a loop happening. This
could be at access, distribution ,core layers.
Root guard is enabled on ports where you don't expect a superior BPDU to be recieved on . Lets say you have
A as the root , and so if someone connects a switch which has a lower pri than the current root, it is going
to advertise iteself as root , so lets say you have rootguard configured on the B-C link then it will put
the link into root-inconsistent state .
So again, it depends on your topology you have in place and what features you would like to implement.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...