Accepted Solutions
Hi Walt,
The reason you are getting these errors is because, Downgrading board controller is not supported. and It gets failed at activation, because either the package version set on the host FW policy doesn’t have this board controller image on it, or the UCSM doesn’t have any image of the current board controller version in its image inventory.
The work around for this would to do the following;
Workaround:
1. Customer can upgrade their Infrastructure & Blade FW to the latest one (2.2.4b or 2.2.5c), in order to match with the FW version of the new B200 M4 blades. But if it’s a big environment, most customers will not want to do that immediately.
2. If the customer using Host FW policy and the Service Profiles are bind to a template. You need to unbind the service profile from the template, and then set the host FW policy to default. But make sure Default Host FW policy is set to none.
If the default FW policy is set to some package version, and some of the Service profiles are already using it, then create a new host FW policy, set it to none, and attach it to the b200 m4 service profiles.
After the service profile of the B200 M4’s get associated or updated with the new Host FW policy (not set to anything) it will still show FAILED status.
Now go to cisco.com and download the UCS FW B bundle, whichever the blade came with (2.2.4b or 2.2.5c).
Upload it to your UCSM.
Once the uploading and unpacking of the FW bundle is done, go to Equipment and select your blade, go to installed firmware tab on the right side of the window.
Select board controller, right click and select Activate Firmware.
Now on the pop up window, select the right board controller image, check FORCE and click Apply/OK.
Give it a few minutes, or you can check the FSM status, the status will soon show Ready.
Once this done, customer cannot bind the Service profile back to the template, as it will change the host FW policy and the board controller will fail again.
If the customer doesn’t want to unbind the service profile from the template, they can create a new template for the new B200 M4 blades without using a Host FW policy and downgrade the blades manually.
3. If customer doesn’t want to do any of this, he can just simply ignore the fault, as this will not affect his production.
As you can tell by step 3 this is not impactable to production it is just because the board controller can not be downgraded. If you want me to give you detailed steps on how to solve this I can attach a guide on how to do this.
Hi Walt,
The reason you are getting these errors is because, Downgrading board controller is not supported. and It gets failed at activation, because either the package version set on the host FW policy doesn’t have this board controller image on it, or the UCSM doesn’t have any image of the current board controller version in its image inventory.
The work around for this would to do the following;
Workaround:
1. Customer can upgrade their Infrastructure & Blade FW to the latest one (2.2.4b or 2.2.5c), in order to match with the FW version of the new B200 M4 blades. But if it’s a big environment, most customers will not want to do that immediately.
2. If the customer using Host FW policy and the Service Profiles are bind to a template. You need to unbind the service profile from the template, and then set the host FW policy to default. But make sure Default Host FW policy is set to none.
If the default FW policy is set to some package version, and some of the Service profiles are already using it, then create a new host FW policy, set it to none, and attach it to the b200 m4 service profiles.
After the service profile of the B200 M4’s get associated or updated with the new Host FW policy (not set to anything) it will still show FAILED status.
Now go to cisco.com and download the UCS FW B bundle, whichever the blade came with (2.2.4b or 2.2.5c).
Upload it to your UCSM.
Once the uploading and unpacking of the FW bundle is done, go to Equipment and select your blade, go to installed firmware tab on the right side of the window.
Select board controller, right click and select Activate Firmware.
Now on the pop up window, select the right board controller image, check FORCE and click Apply/OK.
Give it a few minutes, or you can check the FSM status, the status will soon show Ready.
Once this done, customer cannot bind the Service profile back to the template, as it will change the host FW policy and the board controller will fail again.
If the customer doesn’t want to unbind the service profile from the template, they can create a new template for the new B200 M4 blades without using a Host FW policy and downgrade the blades manually.
3. If customer doesn’t want to do any of this, he can just simply ignore the fault, as this will not affect his production.
As you can tell by step 3 this is not impactable to production it is just because the board controller can not be downgraded. If you want me to give you detailed steps on how to solve this I can attach a guide on how to do this.
