11-09-2016 01:55 AM - edited 03-20-2019 09:08 PM
We have the same problem like #CSCuy98373 with IOS-XE 3.17.02.S release (i.e. 15(6)1.S2).
Will it be fixed in the next versions of 3.17?
Solved! Go to Solution.
11-09-2016 11:33 AM
Hi there
The fix for CSCuy98373 seen in 3.17.02.S will be fixed in 3.17.03.S. Its ETA is early December.
While on this topic of CSCuy98373, same problem is fixed using CSCuy32345 for 16.2 and 16.3 release trains.
I hope this helps ... Palani
11-09-2016 11:33 AM
Hi there
The fix for CSCuy98373 seen in 3.17.02.S will be fixed in 3.17.03.S. Its ETA is early December.
While on this topic of CSCuy98373, same problem is fixed using CSCuy32345 for 16.2 and 16.3 release trains.
I hope this helps ... Palani
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