HyperFabric Release Notes HP-UX 11i v1 and HP-UX 11i v2 April 2010

Known Problems and Workarounds
The known problems and corresponding workarounds for versions B.11.11.05.01, B.11.11.05.02,
and B.11.23.03.01 of the HyperFabric software are as follows:
HyperFabric initialization may fail if the STRMSGSZ kernel parameter is set.
WORKAROUND: Set STRMSGSZ to 0 on /stand/system from the command line to unset
the parameter.
In SAM, set STRMSGSZ to 0 (zero) to unset the parameter.
The switch management software in HyperFabric has some problems that may result in the
following symptoms:
— The HyperFabric management daemon (clic_mgmtd) loses connection with other
nodes in the cluster.
— Invalid class messages (that is, class messages that are not related to HyperFabric) get
logged into the /var/adm/clic_log global log file.
WORKAROUND: Disconnect the HyperFabric switch(es) from the Ethernet network, and
leave them disconnected. Then, reconfigure HyperFabric by doing one of the following:
— Use the clic_init -pc command, but do not configure switch management.
— Use SAM (HP-UX 11.0 and 11i v1 only). As mentioned earlier, you cannot configure
switch management within SAM.
HyperFabric will work correctly without switch management configured, but the switches
will not create diagnostic logs.
When you run the clic_probe nodename -c adapter_ID command, if the adapter
specified by adapter_ID is not operational— and another (operational) adapter is installed
in the “source” node (the node you specified the clic_probe command
from)—clic_probe uses the other adapter. However, clic_probe does not notify you
that the adapter you specified is not operational. This will be fixed in a future release.
If you update the HyperFabric software from a version earlier than B.11.00.11 or B.11.11.01
to the current release, the following things happen:
— The files /etc/rc.config.d/clic_global_conf and /etc/rc.config.d/
netconf are moved to the directory /tmp/clic.software_version/ (for example,
/tmp/clic.B.11.00.10).
— The /etc/rc.config.d/clic_global_conf file is deleted.
The result is that HyperFabric cannot find the existing configuration information, because
it has been removed from its normal locations.
WORKAROUND: After the HyperFabric software installation is complete, you must run
clic_init -c to create the global configuration file. When you do this, consider the
following things:
— If you want to keep the existing configuration: You must re-specify the existing
configuration information when you run clic_init -c. To do this, refer to the contents
of the two files that were moved to the /tmp/clic.software_version/ directory (the existing
configuration information is stored in those two files). Then, specify that configuration
information when you run clic_init -c.
— If you do not want to keep the existing configuration (that is, you want to do a new
configuration): Run clic_init -c and specify the configuration information you
prefer.
HP-UX 11i v1 installation issue on systems that have HyperFabric cards. Customers installing
or re-installing HP-UX 11i v1 using the Guided Installation option may encounter a program
loop during network configuration the first time the system reboots. This is not due to a
defective card.
8 HyperFabric Release Notes