A couple IPMI bugs exist in 2.7.5:
Both of the problems are fixed in the file IPMI.pm that is attached to bug 3156.
For xCAT 2.7.5 with Linux, you should use the xcat-dep tarball from 6/12/2012. The is the xcat-dep tarball that has been tested with xCAT 2.7.5. (The most recent xcat-dep tarball should also work with xCAT 2.7.5, but it hasn't been tested yet.)
For sles11.2 nfs-based statelite deployment on x86, initrd might fail to mount the rootimg and complain the messages below:
Setting up Statelite
mount.nfs: Protocol not supported
Couldn't mount dx360m3n04:/install/netboot/sles11.2/x86_64/compute on /sysroot
Trying again in 1 seconds
the work around can be found in bug 3038
When running mkdsklsnode you may, in certain cases, see the following error:
Error: there is already one directory named "", but the entry in litefile table is set to one file, please check it
Error: Could not complete the statelite setup.
Error: Could not update the SPOT
If you see this error simply re-run the command.
In an AIX HASN environment, if you have more than 8 service nodes, the mkdsklsnode command may create an /etc/exports file entry that is not supported by AIX.
The mkdsklsnode command updates the /etc/exports file on the service nodes with an entry that contains a list of replicas that are used by the the AIX NFSv4 support. Due to an NFS limitation the list of replicas may not exceed 8. If you have existing /etc/exports files that already contain the replication entry then it will not be modified and you DO NOT need to take any further actions. However, if you have removed the /etc/exports file or need to set up a new service node, you must manually check the /etc/xports file to make sure there are no more than 8 replicas listed.
The format of the file is as follows:
Simply remove one or more replicas from the list.( ex. :/email@example.com)
For the rvitals command on system p with option "lcds", if there is any LPAR in the noderange which is defined in the xCAT DB, but doesn't exist on its CEC, the rvitals will not return correct info. You can get more info from bug 3133 and you also can get the e-fix to fix this issue from the attached in the bug 3133 page.