arif/xcat-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

modified the usage and man page of rflash. Please see the bug 2615564 for more information

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@2774 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
jjhua 2009-02-19 08:31:50 +00:00
parent ec5e6f19ec
commit bcbad1bef1
3 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
perl-xCAT/xCAT/PPC.pm
View File

@ -1054,7 +1054,8 @@ sub preprocess_request {
####################
#suport for "rflash", copy the rpm and xml packages from user-spcefied-directory to /install/packages_fw
#####################
if ( $command eq "rflash" ) {
if ( ( $command eq "rflash" ) && (grep(/commit/,@exargs) == 0 && grep(/recover/,@exargs) == 0)) {
# if ( $command eq "rflash" ) {
preprocess_for_rflash($req,$callback, \@exargs);
}
@ -1068,7 +1069,7 @@ sub preprocess_request {
# build each request for each service node
foreach my $snkey (keys %$sn)
{
#print "snkey=$snkey\n";
#$callback->({data=>["The service node $snkey "]});
my $reqcopy = {%$req};
$reqcopy->{'_xcatdest'} = $snkey;
my $hcps1=$sn->{$snkey};

3
perl-xCAT/xCAT/Usage.pm
View File

@ -120,7 +120,8 @@ my %usage = (
[-t tries][-m][-e cmd][-c [timeout[timeout,..]]]",
"rflash" =>
"Usage: rflash [ -h|--help|-v|--version]
rflash noderange -p directory [--activate concurrent | disruptive] [--commit | --recover] [-V|--verbose]"
rflash <noderange> -p directory [--activate concurrent | disruptive][-V|--verbose]
rflash <noderange> [--commit | --recover] [-V|--verbose]"
);
my $vers = xCAT::Utils->Version();
my %version = (

14
xCAT-client/pods/man1/rflash.1.pod
View File

@ -4,17 +4,21 @@ B<rflash> - Performs Licensed Internal Code (LIC) update support for HMC-attache
=head1 B<Synopsis>
B<rflash> [B<-h>|B<--help>][B<-v>|B<--version>]
B<rflash> [B<-h>|B<--help> | B<-v>|B<--version>]
B<rflash> I<noderange> B<-p> I<directory> [B<--activate> B<concurrent>|B<disruptive>][B<--commit>|B<--recover>] [B<-V>|B<--verbose>]
B<rflash> I<noderange> B<-p> I<directory> [B<--activate> B<concurrent>|B<disruptive>] [B<-V>|B<--verbose>]
B<rflash> I<noderange> [B<--commit>|B<--recover>] [B<-V>|B<--verbose>]
=head1 B<Description>
B<rflash> The B<rflash> command initiates Firmware updates on supported xCAT compute nodes. Licensed Internal Code (also known as microcode) updates are performed on supported HMC-attached POWER5 and POWER6 pSeries nodes. The command scans the specified directory structure for Firmware update package files applicable to the given nodes and components. And then it will B<automatically> select the B<latest> version for the upgrade.
B<rflash> The B<rflash> command initiates Firmware updates on supported xCAT nodes. Licensed Internal Code (also known as microcode) updates are performed on supported HMC-attached POWER5 and POWER6 pSeries nodes.
The command scans the specified directory structure for Firmware update package files applicable to the given nodes and components. And then it will B<automatically> select the B<latest> version for the upgrade. The firmware update files include the Microcode update package and associated XML file. They can be downloaded from the IBM Web site: I<http://www14.software.ibm.com/webapp/set2/firmware/gjsn>.
The POWER5 and POWER6 systems contain several components that use Licensed Internal Code. The B<rflash> command supports two of these components: the managed system (also known as the Central Electronics Complex, or CEC) and the power subsystem (also known as the Bulk Power Assembly (BPA) or Bulk Power Controller (BPC)). Some POWER5 managed systems can be attached to a power subsystem. These power subsystems can support multiple managed systems. When the B<rflash> command is invoked, xCAT will determine the managed system or power subsystem associated with that CEC and perform the update.
The B<noderange> can be an CEC or CEC list, a Lpar or Lpar list and a BPA or BPA list. When the I<noderange> is an CEC or CEC list, B<rflash> will upgrade the firmware of the CEC or CECs in the cec list. If I<noderange> is a Lpar or Lpar list, B<rflash> will update Licensed Internal Code (LIC) on HMC-attached POWER5 and POWER6 pSeries nodes. If I<noderange> is a BPA or BPA list, B<rflash> will update Licensed Internal Code (LIC) of the power subsystem on HMC-attached POWER5 and POWER6 pSeries nodes. The I<noderange> can also be the specified node groups. You can specify a comma or space-separated list of node group ranges. See the I<noderange> man page for detailed usage information.
The B<noderange> can be an CEC or CEC list, a Lpar or Lpar list and a BPA or BPA list. But CEC (or Lpar) and BPA B<can't> be used at the same time. When the I<noderange> is an CEC or CEC list, B<rflash> will upgrade the firmware of the CEC or CECs in the cec list. If I<noderange> is a Lpar or Lpar list, B<rflash> will update Licensed Internal Code (LIC) on HMC-attached POWER5 and POWER6 pSeries nodes. If I<noderange> is a BPA or BPA list, B<rflash> will update Licensed Internal Code (LIC) of the power subsystem on HMC-attached POWER5 and POWER6 pSeries nodes. The I<noderange> can also be the specified node groups. You can specify a comma or space-separated list of node group ranges. See the I<noderange> man page for detailed usage information.
The B<rflash> command uses the B<xdsh> command to connect to the HMC controlling the given managed system and perform the updates.
@ -26,6 +30,8 @@ The flash chip of a POWER5 and POWER6 managed system or power subsystem stores f
The B<--commit> flag is used to write the contents of the temporary side of the flash to the permanent side. This flag should be used after updating code and verifying correct system operation. The B<--recover> flag is used to write the permanent side of the flash chip back to the temporary side. This flag should be used to recover from a corrupt flash operation, so that the previously running code can be restored.
B<NOTE:>At present, the B<rflash> command B<doesn't> support B<commit/recover> for BPAs. Because the command "B<licutil>" on HMC doesn't support the "B<commit>" and "B<recover>" operation for the BPA. And "B<rflash>" is dependent on the "B<licutil>" command. So when the B<--commit> or B<--recover> two flags is used, the noderange cannot be a BPA or BPA list in the B<rflash> command. xCAT will pay the attention to the changes all the time.
xCAT recommends that you shutdown your Operating System images and power off your managed systems before applying disruptive updates to managed systems or power subsystems.
Any previously activated code on the affected systems will be automatically accepted into permanent flash by this procedure.