Just curious if anyone has heard anything from Cisco Engineering about whether the recommended release for 9300 series switches is impacted by this bug? The known affected release happens to be the next minor release after the recommended. I can confirm we've hit it in 16.8.1a as well.
I've already been through a TAC case, they closed it with no good info on when to expect a fix. Just curious if anybody else had experienced and possibly found a version of code that wasn't impacted.
@Christopher Bell wrote:
I've already been through a TAC case, they closed it with no good info on when to expect a fix.
1. Raise another TAC Case. Maybe the TAC engineered "reached out" to the developers the wrong way.
2. Talk to your AM/SE about the new TAC Case.
Old bug - but just found one of my switches as affected, C9300 with 16.9.3
Bug Description "known fixed versions" is obvious not correct, my 16.9.3 is listet there as fixed....