You might look at that feature's title and think, What is really a BPDU Skew, and why do I want to find it? What we're really attempting to discover are BPDUs that aren't being relayed as easily as they should really be. Clicking www.free-leakdetection.com/ maybe provides cautions you might give to your father.
After the root bridge election, the root bridge transmits BPDUs, and the non-root turns communicate that BPDU down the STP tree. This should happen quickly all over, since the root bridge will soon be giving every two seconds to a automatically (hello time), and the buttons should exchange the BDPUs fast enough therefore every change is seeing a every two seconds.
That's in a perfect world, however, and there are lots of imperfect systems out there! You may have an active switch that can not spare the CPU to inform the BDPU easily, or even a BPDU may simply just be lost in transmission. That two-second hello time value doesn't provide the changes much flexibility, but we do not want the STP topology recalculated unnecessarily often.
BDPU Skew Detection is strictly a notification feature. Skew Detection will not act to avoid STP recalculation when BDPUs aren't being relayed easily enough by the changes, but a syslog message will be sent by it telling the system administrator of the problem. The quantity of time between if the BDPU should have arrived and when it did arrive is known as skew time or BPDU latency.
A active CPU can easily find itself overcome if it had to deliver a syslog message for every BPDU delivery that's skewed. The syslog messages will soon be limited to one every 60 seconds, unless the skew time is at a crucial level. If so, the message will undoubtedly be sent immediately with no one-per-minute control.
And what is critical, based on BDPU Skew Detection? Any value greater than 1/2 of the MaxAge value, making the important skew time degree 10 seconds or greater.. To check up additional info, consider taking a gander at: plumber orange county.