xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-22 11:42:05 +00:00
Code Issues Releases Wiki Activity

Convert pod to rst for rflash and addkitcomp

Browse Source 
Upload rflash.rst and addkitcomp.rst which are converted from pod
by create_man_page.py.
This commit is contained in:
chenglch 2015-12-10 02:34:27 -05:00
parent e64a5017c6
commit 6d3c230907
2 changed files with 39 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/guides/admin-guides/references/man1/addkitcomp.1.rst
View File

@ -78,7 +78,9 @@ OPTIONS
\ **-n|--noupgrade**\
Allow multiple versions of kitcomponent to be installed into the osimage, instead of kitcomponent upgrade
1. Allow multiple versions of kitcomponent to be installed into the osimage, instead of kitcomponent upgrade.
2. Kit components added by addkitcomp -n will be installed separately behind all other ones which have been added.

40
docs/source/guides/admin-guides/references/man1/rflash.1.rst
View File

@ -46,6 +46,13 @@ NeXtScale FPC specific:
\ **rflash**\ \ *noderange*\ \ *http directory*\
OpenPOWER BMC specific:
=======================
\ **rflash**\ \ *noderange*\ \ *hpm file path*\ [\ **-c**\ |\ **--check**\ ]
*******************
\ **Description**\
@ -93,17 +100,17 @@ PPC (using Direct FSP Management) specific:
In currently Direct FSP/BPA Management, our \ **rflash**\ doesn't support \ **concurrent**\ value of \ **--activate**\ flag, and supports \ **disruptive**\ and \ **deferred**\ . The \ **disruptive**\ option will cause any affected systems that are powered on to be powered down before installing and activating the update. So we require that the systems should be powered off before do the firmware update.
The \ **deferred**\ option will load the new firmware into the T (temp) side, but will not activate it like the disruptive firmware. The customer will continue to run the Frames and CECs working with the P (perm) side and can wait for a maintenance window where they can activate and boot the Frame/CECs with new firmware levels. Refer to the doc to get more details:
The \ **deferred**\ option will load the new firmware into the T (temp) side, but will not activate it like the disruptive firmware. The customer will continue to run the Frames and CECs working with the P (perm) side and can wait for a maintenance window where they can activate and boot the Frame/CECs with new firmware levels. Refer to the doc to get more details:
XCAT_Power_775_Hardware_Management
In Direct FSP/BPA Management, there is -d <data_directory> option. The default value is /tmp. When do firmware update, rflash will put some related data from rpm packages in <data_directory> directory, so the execution of rflash will require available disk space in <data_directory> for the command to properly execute:
For one GFW rpm package and one power code rpm package , if the GFW rpm package size is gfw_rpmsize, and the Power code rpm package size is power_rpmsize, it requires that the available disk space should be more than:
For one GFW rpm package and one power code rpm package , if the GFW rpm package size is gfw_rpmsize, and the Power code rpm package size is power_rpmsize, it requires that the available disk space should be more than:
1.5\*gfw_rpmsize + 1.5\*power_rpmsize
For Power 775, the rflash command takes effect on the primary and secondary FSPs or BPAs almost in parallel.
For more details about the Firmware Update using Direct FSP/BPA Management, refer to:
For more details about the Firmware Update using Direct FSP/BPA Management, refer to:
XCAT_Power_775_Hardware_Management#Updating_the_BPA_and_FSP_firmware_using_xCAT_DFM
@ -111,10 +118,17 @@ NeXtScale FPC specific:
=======================
The command will update firmware for NeXtScale FPC when given an FPC node and the http information needed to access the firmware. The http imformation required includes both the MN IP address as well as the directory containing the firmware. It is recommended that the firmware be downloaded and placed in the /install directory structure as the xCAT MN /install directory is configured with the correct permissions for http. Refer to the doc to get more details:
The command will update firmware for NeXtScale FPC when given an FPC node and the http information needed to access the firmware. The http imformation required includes both the MN IP address as well as the directory containing the firmware. It is recommended that the firmware be downloaded and placed in the /install directory structure as the xCAT MN /install directory is configured with the correct permissions for http. Refer to the doc to get more details:
XCAT_NeXtScale_Clusters
OpenPOWER specific:
===================
The command will update firmware for OpenPOWER BMC when given an OpenPOWER node and the hpm1 formatted file path.
***************
\ **Options**\
@ -128,6 +142,12 @@ The command will update firmware for NeXtScale FPC when given an FPC node and th
\ **-c|--check**\
Chech the firmware version of BMC and HPM file.
\ **-p directory**\
Specifies the directory where the packages are located.
@ -235,6 +255,18 @@ The command will update firmware for NeXtScale FPC when given an FPC node and th
5
To update the firmware on OpenPOWER machine specify the node name and the file path of the HPM firmware file as follows:
.. code-block:: perl
rflash fs3 /firmware/8335_810.1543.20151021b_update.hpm
****************
\ **Location**\