HyperFabric Release Notes (B.11.11.04.02)

HyperFabric Release Notes
Known Problems and Workarounds
Chapter 1 7
Known Problems and Workarounds
The known problems and corresponding workarounds for version B.11.11.04.02 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 -c 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 updating the HP-UX 11.0 HyperFabric software from version B.11.00.11 to the
HP-UX 11i v1 release B.11.11.01, some files are not removed from the file system. This
will be fixed in a future release.
WORKAROUND: Before updating to HP-UX 11i v1, uninstall the HP-UX 11.0 version of
HyperFabric.
• 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.