11-06-2018 12:24 PM
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.
11-06-2018 03:05 PM
11-13-2018 07:16 AM
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.
12-07-2018 05:26 AM
bump
12-07-2018 02:29 PM
@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.
04-26-2021 03:14 AM
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....
11-23-2022 07:29 AM
Also having the issue in 16.12.5b which is listed under "known fixed versions"
11-23-2022 09:12 PM
Please stop using 16.12.X.
Either downgrade to latest 16.6.X or upgrade to the latest 17.6.X.
11-28-2022 01:17 AM
Care to share why 16.12.x should be avoided?
11-28-2022 01:38 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide