mirror of
https://github.com/xcat2/xcat-core.git
synced 2025-05-21 19:22:05 +00:00
Add reventlog to hw management list
This commit is contained in:
Mark Gurevich
parent
833f33c820
commit
f72c4f088a
@ -8,3 +8,4 @@ Advanced Operations
|
||||
rvitals.rst
|
||||
rflash/index.rst
|
||||
rspconfig.rst
|
||||
reventlog.rst
|
||||
|
||||
@ -0,0 +1,14 @@
|
||||
``reventlog`` - Remote Event Log of Service Processors
|
||||
======================================================
|
||||
|
||||
See :doc:`reventlog manpage </guides/admin-guides/references/man1/reventlog.1>` for more information.
|
||||
|
||||
The ``reventlog`` command can be used to display and clear event log information on the service processor, or Baseboard Management Controller (BMC), of a physical machine.
|
||||
|
||||
For example, to display all event log entries for node ``cn5``: ::
|
||||
|
||||
reventlog cn5
|
||||
|
||||
To clear all event log entries for node ``cn5``: ::
|
||||
|
||||
reventlog cn5 clear
|
||||
@ -5,4 +5,3 @@ Known Issues
|
||||
:maxdepth: 2
|
||||
|
||||
genesis_base.rst
|
||||
openbmc/index.rst
|
||||
|
||||
@ -1,7 +0,0 @@
|
||||
#4264 - rpower command intermittently reports 503: Service Unavailable Error
|
||||
============================================================================
|
||||
|
||||
Issue `#4264 <https://github.com/xcat2/xcat-core/issues/4264>`_
|
||||
|
||||
In attempt to improve the performance of the REST calls to OpenBMC and reduce the time spent in a timeout, we fail too soon here before the BMC has a chance to respond.
|
||||
|
||||
@ -1,17 +0,0 @@
|
||||
SW402273 - Unable to tell the firmware level that is actually running on the node via REST
|
||||
==========================================================================================
|
||||
|
||||
* **Issue:** `SW402273 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW402273>`_
|
||||
* **Reported:** 1738B (ibm-v1.99.10-0-r7)
|
||||
* **Fixed:** 1740B (ibm-v1.99.10-0-r13)
|
||||
|
||||
**Issue:**
|
||||
|
||||
Until 1740B firmware (> ibm-v1.99.10-0-r13), there's no method provided by OpenBMC to indicate the active running firmware on the node. Until the BMC is rebooted or the HOST is rebooted, the Active firmware may or may not really be running.
|
||||
|
||||
If you are running a version that prints the following message from ``rflash``: ::
|
||||
|
||||
cn01: WARNING, The current firmware is unable to detect running firmware version.
|
||||
|
||||
Please update the BMC to a version higher than ibm-v1.99.10-0-r13.
|
||||
|
||||
@ -1,26 +0,0 @@
|
||||
SW404161 - Firmware do not self extract tar, causing rflash cannot find ID to activate
|
||||
======================================================================================
|
||||
|
||||
* **Issue:** `SW404161 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW404161>`_
|
||||
* **Reported:** 1738A (ibm-v1.99.10-0-r7)
|
||||
* **Fixed:** 1742D (ibm-v1.99.10-0-113-r10)
|
||||
|
||||
**Issue:**
|
||||
|
||||
Firmware is not extracted and could not be found by rflash to activate ::
|
||||
|
||||
[root@c650mnp03 ~]# rflash c650f07p27 obmc-phosphor-image-witherspoon.ubi.mtd.tar -a
|
||||
c650f07p27: Uploading /root/obmc-phosphor-image-witherspoon.ubi.mtd.tar ...
|
||||
c650f07p27: Firmware upload successful. Attempting to activate firmware: ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Could not find ID for firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d to activate, waiting 10 seconds and retry...
|
||||
c650f07p27: Error: Could not find firmware ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d after waiting 60 seconds.
|
||||
|
||||
**Work-around:** Use one of the following methods:
|
||||
|
||||
* Reboot the BMC before flashing firmware: ``rpower <> bmcreboot``
|
||||
* ssh into bmc and run: ``systemctl restart xyz.openbmc_project.Software.Version.service``
|
||||
@ -1,84 +0,0 @@
|
||||
SW406771 - Duplicate FW ID or 2 BMC firmware active at the same time
|
||||
====================================================================
|
||||
|
||||
* **Issue:** `SW407037 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW407037>`_
|
||||
* **Reported:** 1740A (ibm-v1.99.10-0-r11-0-g9c65260)
|
||||
* **Fixed:** 1742 or higher
|
||||
|
||||
**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.
|
||||
|
||||
|
||||
**Work-around**
|
||||
|
||||
Upgrade from 1740A
|
||||
------------------
|
||||
|
||||
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.
|
||||
|
||||
#. Identify the issue where the IDs are not using the correct hash ::
|
||||
|
||||
mid05tor12cn13: ID Purpose State Version
|
||||
mid05tor12cn13: -------------------------------------------------------
|
||||
mid05tor12cn13: 9e55358e BMC Active(*) ibm-v1.99.10-0-r11-0-g9c65260
|
||||
mid05tor12cn13: 6e71e1af BMC Ready ibm-v1.99.10-113-g65edf7d-r10-0-gcdf7635 <--- bad hash for 1742D
|
||||
|
||||
mid05tor12cn16: ID Purpose State Version
|
||||
mid05tor12cn16: -------------------------------------------------------
|
||||
mid05tor12cn16: efc8a851 BMC Ready ibm-v1.99.10-113-g65edf7d-r10-0-gcdf7635 <--- correct hash for 1742D
|
||||
mid05tor12cn16: b48d27e1 BMC Active(*) ibm-v1.99.10-113-g65edf7d-r3-0-g9e4f715
|
||||
|
||||
#. Flash up to 1742D, activate and reboot: ::
|
||||
|
||||
mid05tor12cn13: ID Purpose State Version
|
||||
mid05tor12cn13: -------------------------------------------------------
|
||||
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 <--- bad hash, active
|
||||
mid05tor12cn13:
|
||||
|
||||
#. Flash down to 1742C, activate and reboot: ::
|
||||
|
||||
mid05tor12cn13: ID Purpose State Version
|
||||
mid05tor12cn13: -------------------------------------------------------
|
||||
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:
|
||||
|
||||
#. Delete the bad hash firmware: ``rflash <node> -d 6e71e1af``
|
||||
|
||||
**Note:** This is optional because the BMC only allows 2 firmware max, so it would get pushed out.
|
||||
|
||||
#. Flash back up to 1742D (with correct hash), activate and reboot: ::
|
||||
|
||||
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: f6590ce0 BMC Active ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
mid05tor12cn13:
|
||||
|
||||
Two active BMCs
|
||||
---------------
|
||||
|
||||
If you have two active BMCs::
|
||||
|
||||
[root@mgt03 ~]# rflash f7n02 -l
|
||||
f7n02: ID Purpose State Version
|
||||
f7n02: -------------------------------------------------------
|
||||
f7n02: b5273d71 BMC Active(*) ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
f7n02: 30ee1c48 Host Active(*) IBM-witherspoon-ibm-OP9_v1.19_1.112
|
||||
f7n02: 4f33e0f4 Host Failed(+) IBM-witherspoon-ibm-OP9_v1.19_1.109
|
||||
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:
|
||||
|
||||
#. 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.
|
||||
@ -1,38 +0,0 @@
|
||||
SW407037 - bmcsetup does not successfully configure the IP (Sev1)
|
||||
=================================================================
|
||||
|
||||
* **Issue:** `SW407037 <https://w3.rchland.ibm.com/projects/bestquest/?defect=SW407037>`_
|
||||
* **Reported:** 1742C (ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d)
|
||||
* **Fixed:** Fixed in xCAT after 11/07/17 `#4242 <https://github.com/xcat2/xcat-core/issues/4242>`_
|
||||
|
||||
**Issue:**
|
||||
|
||||
OpenBMC firmware has problems with ipmi inband support of the ``access on`` comamnd and the work around is to use the ``raw 0x06 0x40`` instead. In early Sept, we switched to using ``access on`` because the implementation looked like it was working, since then we have found some issues with it and recommendation is to revert back to the raw command.
|
||||
|
||||
See related issues describing potential problems:
|
||||
* https://github.com/openbmc/openbmc/issues/2493
|
||||
* https://github.com/openbmc/openbmc/issues/2492
|
||||
|
||||
This problem is very severe because if the network is not configured correctly, the access to the BMC is lost.
|
||||
|
||||
**Work-around**
|
||||
|
||||
Use one of the following work arounds:
|
||||
|
||||
#. Install a version of xCAT built after November, 07, 2017 which includes the fix. (**Recommended**)
|
||||
|
||||
#. Manually patch bmcsetup using changes in PR: https://github.com/xcat2/xcat-core/pull/4247, then run ``mknb ppc64``
|
||||
|
||||
#. Patch the system with provided patch:
|
||||
|
||||
#. Download patch file: https://github.com/xcat2/xcat-core/files/1451181/bmcsetup.4242.patch.txt
|
||||
|
||||
#. If file name is ``/tmp/bmcsetup.4242.patch.txt``
|
||||
|
||||
#. ``cd /opt/xcat/share/xcat/netboot/genesis/ppc64/fs/usr/bin``
|
||||
|
||||
#. ``patch -p0 < /tmp/bmcsetup.4242.patch.txt``
|
||||
|
||||
#. ``mknb ppc64``
|
||||
|
||||
|
||||
@ -1,47 +0,0 @@
|
||||
OpenBMC Management Issues
|
||||
=========================
|
||||
|
||||
xCAT
|
||||
----
|
||||
|
||||
2.13.8
|
||||
``````
|
||||
|
||||
Please see the `2.13.8 Release Notes <https://github.com/xcat2/xcat-core/wiki/XCAT_2.13.8_Release_Notes>`_ for the full list of known issues.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
2_13_8.rst
|
||||
|
||||
Firmware
|
||||
--------
|
||||
|
||||
The following versions indicate the level of firmware the issue was reported.
|
||||
|
||||
|
||||
1742C - ibm-v1.99.10-113-g65edf7d-r8-0-g713d86d
|
||||
```````````````````````````````````````````````
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
SW407037.rst
|
||||
|
||||
1740A - ibm-v1.99.10-0-r11
|
||||
``````````````````````````
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
SW406771.rst
|
||||
|
||||
|
||||
1738A - ibm-v1.99.10-0-r7
|
||||
``````````````````````````
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
SW404161.rst
|
||||
SW402273.rst
|
||||
Loading…
x
Reference in New Issue
Block a user