Good news everyone, Cisco re-examined the bug and concluded this particular problem was not a hardware issue after all but can be remedied with a software update: http://mailman.nanog.org/pipermail/nanog/2016-December/08941...