replace the FSPAPI with Direct FSP Management

git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@8995 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
jjhua 2011-03-04 08:56:58 +00:00
parent 7d3d00937e
commit b40421b166

View File

@ -14,9 +14,9 @@ B<mkhwconn> [B<-V>| B<--verbose>] noderange B<-t>
B<mkhwconn> [B<-V>| B<--verbose>] noderange B<-p> hmc [B<-P> passwd]
=head2 PPC (without HMC, using FSPAPI) specific:
=head2 PPC (without HMC, using Direct FSP Management) specific:
B<mkhwconn> noderange B<-t> B<-T tooltype> [B<--port> port_value]
B<mkhwconn> noderange B<-t> [B<-T tooltype>] [B<--port> port_value]
=head1 DESCRIPTION
@ -35,7 +35,7 @@ In any case, before running this command, the FSP and BPA nodes need be defined
Note: If a CEC (FSP) belongs to a frame, which has a BPA installed, this CEC should not be assigned to an HMC individually. Instead, the whole frame (BPA) should be assigned to the HMC.
For PPC (without HMC, using FSPAPI) specific:
For PPC (without HMC, using Direct FSP Management) specific:
It is used to set up connections for FSP and BPA node to Hardware Server on management node (or service node ). It only could be done according to the node definition in xCAT DB. And this command will try to read the user/password from the ppcdirect table firstly. If fails, then read them from passwd table. Commonly , the username is HMC. If using the ppcdirect table, each FSP/BPA and user/password should be stored in ppcdirect table. If using the passwd table, the key should be "fsp" or "bpa", and the related user/password are stored in passwd table.
@ -64,7 +64,7 @@ The password of HMC based FSP/BPA login user(Default user name is 'HMC'). This f
=item B<-T>
The tooltype is used to communicate to the FSP/BPA. The value could be lpar or fnm. The tooltype value lpar is for xCAT and fnm is for CNM.
The tooltype is used to communicate to the FSP/BPA. The value could be lpar or fnm. The tooltype value lpar is for xCAT and fnm is for CNM. The default value is "lpar".
=item B<--port>