I have a concern,
if we have upgraded to 4.2.1 and effected with bug. what is the best practice.
do we need to follow the work around? or upgrade to version 4.2.1i/4.2.2a - since cisco released the bug fixed version.
Workaround:
Downgrade to lower version of UCSM
Confirmed workaround works with 4.1(3b) and 4.1(2b)