Where to See this error :
1.CIMC ---> storage ---> Cisco Flexflash ---->controller info
2.If you are running ESXI server on this C series server you will be getting “Bootbank cannot be found at the path /bootbank” error
Cause for this issue: this is a known bug if you are running firmware version less than 1.5(3d) on c series server. The bug id is CSCuh33982. It is resolved in firmware version 1.5(3d).
https://tools.cisco.com/bugsearch/bug/CSCuh33982
Workaround to fix this issue:
1. Reboot CIMC --- this will not cause any disruptions to the esxi server or the vm’s running on it. The management page of CIMC page need to be reloaded. I would recommend to clear the cache and try to access the management page after CIMC restart.
How to restart the CIMC:
Goto Admin tab on CIMC and click reboot CIMC.
If you want to do that on CLI, ssh into the management ip address of CIMC and run the below commands.
Scope cimc
Reboot
2. If CIMC shows the controller is healthy now and ESXI still shows the same error then ssh into the ESXI server and restart the service by using the below command
Services.sh restart ( this will not affect your VM running on it but this will disconnect the esxi server and connect it back automatically when the service comes up).
1.CIMC ---> storage ---> Cisco Flexflash ---->controller info
2.If you are running ESXI server on this C series server you will be getting “Bootbank cannot be found at the path /bootbank” error
Cause for this issue: this is a known bug if you are running firmware version less than 1.5(3d) on c series server. The bug id is CSCuh33982. It is resolved in firmware version 1.5(3d).
https://tools.cisco.com/bugsearch/bug/CSCuh33982
Workaround to fix this issue:
1. Reboot CIMC --- this will not cause any disruptions to the esxi server or the vm’s running on it. The management page of CIMC page need to be reloaded. I would recommend to clear the cache and try to access the management page after CIMC restart.
How to restart the CIMC:
Goto Admin tab on CIMC and click reboot CIMC.
If you want to do that on CLI, ssh into the management ip address of CIMC and run the below commands.
Scope cimc
Reboot
2. If CIMC shows the controller is healthy now and ESXI still shows the same error then ssh into the ESXI server and restart the service by using the below command
Services.sh restart ( this will not affect your VM running on it but this will disconnect the esxi server and connect it back automatically when the service comes up).
No comments:
Post a Comment