xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-29 17:23:08 +00:00
Code Issues Releases Wiki Activity

Remove trailing spaces in file docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rflash/openbmc/openbmc_common.rst

Browse Source
This commit is contained in:
GONG Jie 2017-12-31 23:59:59 +00:00
parent 2152120521
commit c85b4eae0f
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rflash/openbmc/openbmc_common.rst
View File

@ -25,19 +25,19 @@ If there are errors encountered during the flash process, take a look at the man
The sequence of events that must happen to flash OpenBMC firmware is the following:
#. Power off the Host
#. Upload and Activate BMC
#. Power off the Host
#. Upload and Activate BMC
#. Reboot the BMC (applies BMC)
#. Upload and Activate Host
#. Power on the Host (applies Host)
#. Power on the Host (applies Host)
Power off Host
Power off Host
--------------
Use the rpower command to power off the host: ::
rpower <noderange> off
rpower <noderange> off
Upload and Activate BMC Firmware
--------------------------------
@ -48,18 +48,18 @@ Use the rflash command to upload and activate the Host firmware: ::
If running ``rflash`` in Hierarchy, the firmware files must be accessible on the Service Nodes.
**Note:** If a .tar file is provided, the ``-a`` option does an upload and activate in one step. If an ID is provided, the ``-a`` option just does activate the specified firmware. After firmware is activated, use the ``rflash <noderange> -l`` to view. The ``rflash`` command shows ``(*)`` as the active firmware and ``(+)`` on the firmware that requires reboot to become effective.
**Note:** If a .tar file is provided, the ``-a`` option does an upload and activate in one step. If an ID is provided, the ``-a`` option just does activate the specified firmware. After firmware is activated, use the ``rflash <noderange> -l`` to view. The ``rflash`` command shows ``(*)`` as the active firmware and ``(+)`` on the firmware that requires reboot to become effective.
Reboot the BMC
--------------
Use the ``rpower`` command to reboot the BMC: ::
rpower <noderange> bmcreboot
The BMC will take 2-5 minutes to reboot, check the status using: ``rpower <noderange> bmcstate`` and wait for ``BMCReady`` to be returned.
The BMC will take 2-5 minutes to reboot, check the status using: ``rpower <noderange> bmcstate`` and wait for ``BMCReady`` to be returned.
**Known Issue:** On reboot, the first call to the BMC after reboot, xCAT will return ``Error: BMC did not respond within 10 seconds, retry the command.``. Please retry.
**Known Issue:** On reboot, the first call to the BMC after reboot, xCAT will return ``Error: BMC did not respond within 10 seconds, retry the command.``. Please retry.
Upload and Activate Host Firmware
---------------------------------
@ -70,14 +70,14 @@ Use the rflash command to upload and activate the Host firmware: ::
If running ``rflash`` in Hierarchy, the firmware files must be accessible on the Service Nodes.
**Note:** The ``-a`` option does an upload and activate in one step, after firmware is activated, use the ``rflash <noderange> -l`` to view. The ``rflash`` command shows ``(*)`` as the active firmware and ``(+)`` on the firmware that requires reboot to become effective.
**Note:** The ``-a`` option does an upload and activate in one step, after firmware is activated, use the ``rflash <noderange> -l`` to view. The ``rflash`` command shows ``(*)`` as the active firmware and ``(+)`` on the firmware that requires reboot to become effective.
Power on Host
-------------
User the ``rpower`` command to power on the Host: ::
rpower <noderange> on
rpower <noderange> on
.. END_flashing_OpenBMC_Servers
@ -86,15 +86,15 @@ User the ``rpower`` command to power on the Host: ::
Validation
----------
Use one of the following commands to validate firmware levels are in sync:
Use one of the following commands to validate firmware levels are in sync:
* Use the ``rinv`` command to validate firmware level: ::
rinv <noderange> firm -V | grep -i ibm | grep "\*" | xcoll
rinv <noderange> firm -V | grep -i ibm | grep "\*" | xcoll
* Use the ``rflash`` command to validate the firmware level: ::
rflash <noderange> -l | grep "\*" | xcoll
rflash <noderange> -l | grep "\*" | xcoll
.. END_Validation_OpenBMC_firmware