Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
57
GAB known issues
the MAC address of a NIC, then delete the MAC address from the llttab file, and
update the file before you restart LLT.
LLT port stats sometimes shows recvcnt larger than recvbytes
(1907228)
With each received packet, LLT increments the following variables:
■
■
recvcnt (increment by one for every packet)
recvbytes (increment by size of packet for every packet)
Both these variables are integers. With constant traffic, recvbytes hits and rolls over
MAX_INT quickly. This can cause the value of recvbytes to be less than the value
of recvcnt.
This does not impact the LLT functionality.
LLT may incorrectly declare port-level connection for nodes in
large cluster configurations [1810217]
When ports get registered and unregistered frequently on the nodes of the cluster,
LLT may declare that a port-level connection exists with another peer node. This
occurs in some corner cases even though a port is not even registered on the peer
node.
Cannot use CPI response files to add nodes to a cluster that
is using LLT over UDP (2869763)
When you run the addnode -responsefile command, if the cluster is using LLT
over UDP, then the /etc/llttab file generated on new nodes is not correct. So,
the procedure fails and you cannot add nodes to a cluster using CPI response files.
Workaround: None
This section covers the known issues related to GAB in this release.
While deinitializing GAB client, "gabdebug -R GabTestDriver"
command logs refcount value 2 (2536373)
After you unregister the port with -nodeinit option, the gabconfig -C command
shows refcount as 1. But when forceful deinit option (gabdebug -R
GabTestDriver) is run to deinitialize GAB client, then a message similar to the
following is logged.