HP XC System Software Release Notes for Version 4.0

Therefore, for Serviceguard clusters that do not include the head node, HP recommends that
you define a quorum server for quorum instead of using a lock LUN.
5.3.2 HP Scalable File Share Mount Problems with Mixed HCAs
NOTE: This note applies only to SFS Version 2.3.
A Scalable File Share (SFS) share might not mount properly if the head node and compute nodes
have different types of HCA cards. For example, a memfull HCA on the head node and a
memfree HCA on the compute nodes, including ConnectX HCAs.
HP does not support a mixture of ConnectX and non-ConnectX HCAs, so this situation should
rarely be encountered.
Follow this procedure to work around the problem before you run the cluster_config utility:
1. Use the text editor of your choice to edit the /etc/modprobe.conf.lustre file.
2. Set the value of the mtu attribute to 2048, as follows:
options lnet networks=o2ib0 mtu=2048
3. Invoke the cluster_config utility and complete the imaging process to propagate this
file to all compute nodes.
After imaging is complete, follow this procedure on the head node to avoid any performance
issues if the head node is installed with memfull cards:
1. On the head node, stop all jobs that are using the SFS share.
2. Stop the SFS service:
# service sfs stop
3. Use the text editor of your choice to edit the /etc/modprobe.conf.lustre file on the
head node.
4. Set the value of the mtu attribute to 4096, as follows:
options lnet networks=o2ib0 mtu=4096
5. Restart the SFS service:
# service sfs start
6. Restart all stopped jobs.
5.4 Notes that Apply after Running the cluster_config Utility
Read the notes in this section after you run the cluster_config utility.
5.4.1 Incorrect Licensing Message Output by the startsys Command
The following licensing error message might appear when you run the startsys command
after you run the cluster_config utility (either during an upgrade or a fresh installation of
Version 4.0):
Could not count licenses. Is the license manager running?
This message appears even when the license manager is up and running.
To work around this issue, restart the license manager and re-run startsys:
[root@n16]# service hptc-lm restart
[root@n16]# startsys --image_and_boot
Sun Dec 7 22:51:58 2008 Enabled nodes: 3 nodes -> n[14-16]
Sun Dec 7 22:51:59 2008 Removing the execution node: n16
Sun Dec 7 22:51:59 2008 Boot hierarchy of specified nodes is: n[14-15]
Sun Dec 7 22:52:04 2008 Initial power test - please wait.
Sun Dec 7 22:52:11 2008 Nodes that will image: 2 nodes -> n[14-15]
5.4 Notes that Apply after Running the cluster_config Utility 21