Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
56
Issues related to global clusters
LLT known issues
The engine log file receives too many log messages on the
secure site in global cluster environments [1919933]
When the WAC process runs in secure mode on one site, and the other site does
not use secure mode, the engine log file on the secure site gets logs every five
seconds.
Workaround: The two WAC processes in global clusters must always be started in
either secure or non-secure mode. The secure and non-secure WAC connections
will flood the engine log file with the above messages.
Application group attempts to come online on primary site
before fire drill service group goes offline on the secondary
site (2107386)
The application service group comes online on the primary site while the fire drill
service group attempts to go offline at the same time, causing the application group
to fault.
Workaround: Ensure that the fire drill service group is completely offline on the
secondary site before the application service group comes online on the primary
site.
This section covers the known issues related to LLT in this release.
LLT may fail to detect when bonded NICs come up (2604437)
When LLT is configured over a bonded NIC and that bonded NIC is DOWN with
the ifconfig command, LLT marks the corresponding link down. When the bonded
NIC is UP again using the ifconfig command, LLT fails to detect this change and
it doesn't mark the link UP.
Workaround: Close all the ports and restart LLT, then open the ports again.
LLT connections are not formed when a vlan is configured on
a NIC (2484856)
LLT connections are not formed when a vlan is configured on a NIC that is already
used to configure an LLT link.
Workaround: Do not specify the MAC address of a NIC in the llttab file while
configuring LLT if you want to configure a vlan later. If you have already specified