Accepted Solutions
Walter,
What happens is that the downgrade is not supported... if you try yo do it manually through a SSH session, the system will tell you "downgrade is not supported"
Try the commands (for future users, you may know them already 
):
# scope server X/Y (chassis X blade Y)
# scope boardcontroller
# show image (this will list all of the firmware versions)
# activate firmware version.0 force (Select a lower version than the one already running)
# commit-buffer <<<<< Here you will see that message I mentioned
HTH
-Kenny
Walter,
What happens is that the downgrade is not supported... if you try yo do it manually through a SSH session, the system will tell you "downgrade is not supported"
Try the commands (for future users, you may know them already ):
# scope server X/Y (chassis X blade Y)
# scope boardcontroller
# show image (this will list all of the firmware versions)
# activate firmware version.0 force (Select a lower version than the one already running)
# commit-buffer <<<<< Here you will see that message I mentioned
HTH
-Kenny
My pleasure Walter... I'd say that if the SP associated properly and the famous "WILL_BOOT_FAULT" did not come up, he can safely ignore the "non-compliant" message but he may need to consider a window for the upgrade to avoid possible unexpected behaviors caused by a mismatch.
If you see something else besides the "non-compliant", let me know... you know where to find me 
-Kenny
