mirror of
https://github.com/xcat2/xcat-core.git
synced 2025-05-22 03:32:04 +00:00
Remove trailing spaces in file docs/source/references/coral/known_issues/openbmc/SW406771.rst
This commit is contained in:
parent
b70a164641
commit
1d8fc9df1c
@ -5,7 +5,7 @@ SW406771 - Duplicate FW ID or 2 BMC firmware active at the same time
|
||||
* **Reported:** 1740A (ibm-v1.99.10-0-r11-0-g9c65260)
|
||||
* **Fixed:** 1742 or higher
|
||||
|
||||
**Issue:**
|
||||
**Issue:**
|
||||
|
||||
At some point after 1740A firmware, ``ibm-v1.99.10-0-r11-0-g9c65260``, the hashing algorithm to create the ID on the BMC was chagned by the Firmware team. This allows for the same firmware to potentially have two different IDs resulting in two active running BMC firmware.
|
||||
|
||||
@ -15,7 +15,7 @@ At some point after 1740A firmware, ``ibm-v1.99.10-0-r11-0-g9c65260``, the hashi
|
||||
Upgrade from 1740A
|
||||
------------------
|
||||
|
||||
If you are running 1740A, you will need to get two BMC firmware levels from your IBM representative.
|
||||
If you are running 1740A, you will need to get two BMC firmware levels from your IBM representative.
|
||||
|
||||
This example will cover flashing from 1740A to 1742D, using 1742C as the recovery flash level.
|
||||
|
||||
@ -47,7 +47,7 @@ This example will cover flashing from 1740A to 1742D, using 1742C as the recover
|
||||
mid05tor12cn13: 9e55358e BMC Active ibm-v1.99.10-0-r11-0-g9c65260
|
||||
mid05tor12cn13: 221d9020 Host Active(*) IBM-witherspoon-redbud-ibm-OP9_v1.19_1.33
|
||||
mid05tor12cn13: 6e71e1af BMC Active(*) ibm-v1.99.10-113-g65edf7d-r10-0-gcdf7635
|
||||
mid05tor12cn13: f6590ce0 BMC Active(+) ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d <--- 1742C
|
||||
mid05tor12cn13: f6590ce0 BMC Active(+) ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d <--- 1742C
|
||||
mid05tor12cn13:
|
||||
|
||||
#. Delete the bad hash firmware: ``rflash <node> -d 6e71e1af``
|
||||
@ -59,7 +59,7 @@ This example will cover flashing from 1740A to 1742D, using 1742C as the recover
|
||||
mid05tor12cn13: ID Purpose State Version
|
||||
mid05tor12cn13: -------------------------------------------------------
|
||||
mid05tor12cn13: 221d9020 Host Active(*) IBM-witherspoon-redbud-ibm-OP9_v1.19_1.33
|
||||
mid05tor12cn13: efc8a851 BMC Active(*) ibm-v1.99.10-113-g65edf7d-r10-0-gcdf7635 <--- good hash
|
||||
mid05tor12cn13: efc8a851 BMC Active(*) ibm-v1.99.10-113-g65edf7d-r10-0-gcdf7635 <--- good hash
|
||||
mid05tor12cn13: f6590ce0 BMC Active ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
mid05tor12cn13:
|
||||
|
||||
@ -77,8 +77,8 @@ If you have two active BMCs::
|
||||
f7n02: f6590ce0 BMC Active(*) ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
f7n02:
|
||||
|
||||
There's no way to de-activate one manually, recover by doing the following:
|
||||
There's no way to de-activate one manually, recover by doing the following:
|
||||
|
||||
#. Flash the BMC to the previous level of the firmware and reboot BMC
|
||||
#. Delete the duplicate firmware using ``rflash <node> -d <ID>``
|
||||
#. Re-flash the BMC to the target level and reboot the BMC.
|
||||
#. Re-flash the BMC to the target level and reboot the BMC.
|
||||
|
Loading…
x
Reference in New Issue
Block a user