HyperFabric Release Notes HP-UX 11i v1 and HP-UX 11i v2 (B6257-90101, July 2011)

• CLIC_ATTR_APPL_MAX_MEM_EPTS 9994
• CLIC_ATTR_APPL_MAX_RECV_EPTS 9994
System tunables for the shared memory should be modified based on the attribute values, but
shared memory must be less than 4 GB.
In the Non-Local Failover configuration mode, these values can be set to a maximum of (4997 *
Number of CLIC cards configured). Oracle RAC users must use the Local Failover configuration
mode.
Documentation availability
The documentation for the HyperFabric software versions B.11.11.05.01, B.11.23.03.01 and
B.11.23.04 is available on the HP web site:http://www.hp.com/go/hpux-networking-docs.
The product can be located under the section I/O Cards and Networking Software and the
documents are as follows:
• Installing and Administering HyperFabric (Part Number: B6257-90052)
• HyperFabric Release Notes (Part Number: B6257-90101)
• HyperFabric Configuration Guidelines (Part Number: B6257-90049)
Known problems and workarounds
The known problems and corresponding workarounds for versions B.11.11.05.01, B.11.23.03.01
and B.11.23.04 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.
Known problems and workarounds 5