diff --git a/docs/source/guides/admin-guides/references/man1/rflash.1.rst b/docs/source/guides/admin-guides/references/man1/rflash.1.rst index abc48f8d7..4eb48fa80 100644 --- a/docs/source/guides/admin-guides/references/man1/rflash.1.rst +++ b/docs/source/guides/admin-guides/references/man1/rflash.1.rst @@ -150,31 +150,19 @@ The command will update firmware for OpenPOWER BMC when given an OpenPOWER node \ **-l|-**\ **-list**\ : +The list option will list out available firmware on the BMC. It provides an interface to display the ID of the various firmware levels. -.. code-block:: perl - - The list option will list out available firmware on the BMC. It provides an interface to display the ID of the various firmware levels. - - The (*) symbol indicates the active running firmware on the server. - - The (+) symbol indicates the firmware that is pending and a reboot is required to set it to be the active running firmware level. +The (\*) symbol indicates the active running firmware on the server. +The (+) symbol indicates the firmware that is pending and a reboot is required to set it to be the active running firmware level. \ **-u|-**\ **-upload**\ : - -.. code-block:: perl - - The upload option expects a .tar file as the input and will upload the file to the BMC. Use the list option to view the result. - +The upload option expects a .tar file as the input and will upload the file to the BMC. Use the list option to view the result. \ **-a|-**\ **-activate**\ : - -.. code-block:: perl - - The activate option expects either a .tar file or an ID as the input. If a .tar file is provided, it will upload and activate the firmware in a single step - +The activate option expects either a .tar file or an ID as the input. If a .tar file is provided, it will upload and activate the firmware in a single step To apply the firmware level, a reboot is required to BMC and HOST. @@ -182,37 +170,14 @@ To apply the firmware level, a reboot is required to BMC and HOST. \ **-d**\ : - -.. code-block:: perl - - This option steamlines the update, activate, reboot BMC and reboot HOST procedure. It expects a directory containing both BMC and PNOR .tar files. When BMC and PNOR tar files are provided, the command will upload and activate firmware. After BMC becomes activate, it will reboot BMC. If BMC state is Ready, the command will reboot the HOST. If BMC state is NotReady, the command will exit. - +This option steamlines the update, activate, reboot BMC and reboot HOST procedure. It expects a directory containing both BMC and PNOR .tar files. When BMC and PNOR tar files are provided, the command will upload and activate firmware. After BMC becomes activate, it will reboot BMC. If BMC state is Ready, the command will reboot the HOST. If BMC state is NotReady, the command will exit. \ **Note:**\ When using \ **-**\ **-no-host-reboot**\ , it will not reboot the host after BMC is reboot. \ **-**\ **-delete**\ : +This delete option will delete update image from BMC. It expects an ID as the input. -.. code-block:: perl - - This delete option will delete update image from BMC. It expects an ID as the input. - - - -\ **-d**\ : - -.. code-block:: perl - - This option steamlines the update, activate, reboot BMC and reboot HOST procedure. It expects a directory containing both BMC and PNOR .tar files. When BMC and PNOR tar files are provided, the command will upload and activate firmware. After BMC becomes activate, it will reboot BMC. If BMC state is Ready, the command will reboot the HOST. If BMC state is NotReady, the command will exit. - -\ **Note:**\ When using \ **--no-host-reboot**\, it will not reboot the host after BMC is reboot. - - -\ **-**\ **-delete**\ : - -.. code-block:: perl - - The delete option will delete update image from BMC. It expects an ID as the input. *************** diff --git a/docs/source/guides/admin-guides/references/man1/rvitals.1.rst b/docs/source/guides/admin-guides/references/man1/rvitals.1.rst index 7fa7e62d6..f67fe481d 100644 --- a/docs/source/guides/admin-guides/references/man1/rvitals.1.rst +++ b/docs/source/guides/admin-guides/references/man1/rvitals.1.rst @@ -67,7 +67,7 @@ OpenPOWER (OpenBMC) specific: ============================= -\ **rvitals**\ \ *noderange*\ [\ **temp | voltage | wattage | fanspeed | power | altitude | all**\ ] +\ **rvitals**\ \ *noderange*\ [\ **temp | voltage | wattage | fanspeed | power | leds | altitude | all**\ ] diff --git a/perl-xCAT/xCAT/Usage.pm b/perl-xCAT/xCAT/Usage.pm index 454f8cbc1..9d0ecbf38 100755 --- a/perl-xCAT/xCAT/Usage.pm +++ b/perl-xCAT/xCAT/Usage.pm @@ -83,7 +83,7 @@ my %usage = ( OpenPOWER (IPMI) specific: rvitals noderange [temp|voltage|wattage|fanspeed|power|leds|chassis|all] OpenPOWER (OpenBMC) specific: - rvitals noderange [temp|voltage|wattage|fanspeed|power|altitude|all] + rvitals noderange [temp|voltage|wattage|fanspeed|power|leds|altitude|all] MIC specific: rvitals noderange {thermal|all} pdu specific: diff --git a/xCAT-client/pods/man1/rflash.1.pod b/xCAT-client/pods/man1/rflash.1.pod index 447bdc332..f6985b970 100644 --- a/xCAT-client/pods/man1/rflash.1.pod +++ b/xCAT-client/pods/man1/rflash.1.pod @@ -103,19 +103,19 @@ The command will update firmware for OpenPOWER BMC when given an OpenPOWER node B<-l|--list>: - The list option will list out available firmware on the BMC. It provides an interface to display the ID of the various firmware levels. +The list option will list out available firmware on the BMC. It provides an interface to display the ID of the various firmware levels. - The (*) symbol indicates the active running firmware on the server. +The (*) symbol indicates the active running firmware on the server. - The (+) symbol indicates the firmware that is pending and a reboot is required to set it to be the active running firmware level. +The (+) symbol indicates the firmware that is pending and a reboot is required to set it to be the active running firmware level. B<-u|--upload>: - The upload option expects a .tar file as the input and will upload the file to the BMC. Use the list option to view the result. +The upload option expects a .tar file as the input and will upload the file to the BMC. Use the list option to view the result. B<-a|--activate>: - The activate option expects either a .tar file or an ID as the input. If a .tar file is provided, it will upload and activate the firmware in a single step +The activate option expects either a .tar file or an ID as the input. If a .tar file is provided, it will upload and activate the firmware in a single step To apply the firmware level, a reboot is required to BMC and HOST. @@ -123,13 +123,13 @@ B When using B in hierarchical environment, the .tar file must be B<-d>: - This option steamlines the update, activate, reboot BMC and reboot HOST procedure. It expects a directory containing both BMC and PNOR .tar files. When BMC and PNOR tar files are provided, the command will upload and activate firmware. After BMC becomes activate, it will reboot BMC. If BMC state is Ready, the command will reboot the HOST. If BMC state is NotReady, the command will exit. +This option steamlines the update, activate, reboot BMC and reboot HOST procedure. It expects a directory containing both BMC and PNOR .tar files. When BMC and PNOR tar files are provided, the command will upload and activate firmware. After BMC becomes activate, it will reboot BMC. If BMC state is Ready, the command will reboot the HOST. If BMC state is NotReady, the command will exit. B When using B<--no-host-reboot>, it will not reboot the host after BMC is reboot. B<--delete>: - This delete option will delete update image from BMC. It expects an ID as the input. +This delete option will delete update image from BMC. It expects an ID as the input. =head1 B diff --git a/xCAT-client/pods/man1/rvitals.1.pod b/xCAT-client/pods/man1/rvitals.1.pod index fb246eb40..e588434f3 100644 --- a/xCAT-client/pods/man1/rvitals.1.pod +++ b/xCAT-client/pods/man1/rvitals.1.pod @@ -32,7 +32,7 @@ B I [B|B|B|B|B|B I [B|B|B|B|B|B|B] +B I [B|B|B|B|B|B|B|B] =head1 B