01-17-2018 07:10 AM
experts
In the ISE 2.2 Patch 5 release note, this bug is fixed. However, my customer still hit the same bug when trying out on patch 5 released on mid-Dec.
Checking on the bug note, I see that the bug was in version 2.2.0470, fixed in 2.2.0905. We are informed that these two are all the same patch 5 version: 2.2.0905 is 2.2 Patch 5. 2.2.0470 is the FCS build version.
I am really confused at this point.
Solved! Go to Solution.
01-17-2018 08:45 AM
Yes that’s correct
But you’re still running into the bug. Do you have a case to explore why that’s happening?
You should be looking through the tac to troubleshoot
01-17-2018 07:31 AM
Do they have a tac case to investigate and correct discrepancies
01-17-2018 08:00 AM
The TAC engineer is telling us the 470 and 905 are the same code for patch 5.
01-17-2018 08:45 AM
Yes that’s correct
But you’re still running into the bug. Do you have a case to explore why that’s happening?
You should be looking through the tac to troubleshoot
01-17-2018 09:25 AM
There are many builds culminating in final release. The FCS number of 470 is the last build used for FCS. After FCS, patches are flagged using 90#, where # is the Patch version.
Yes, be sure to work with TAC to determine if truly hitting same issue or new issue.
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