Can anybody explain why the Black Hole Mitigation feature changes the default 100kmicrosec beacon interval to a "slightly lower value" (usually 99 or 98 kmicrosec) ? I am rather baffled by this very slight change - where is the advantage to black hole mitigation ?
Check if these values were the same before you enabled black hole mitigaton, could be a possibility they were tweaked even before you configured this feature. If the answer is no better check if it is a known bug.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.