The LLT errors that you see are telling you that heartbeats on public NIC is a bad idea - there is so much traffic on e1000g0 that heartbeats are missed.
Maybe there's less traffic on the other cluster's public network, therefore no missed heartbeats.
Maybe go back to basics are re-look your design and consider Symantec's recommendation with regards to Private Network configuration in the Install Guide:
"The private network requires two communication channels to guard against network partitions."
"On each system, use two independent network cards to provide redundancy."
"Do not use the network interface card that is used for the public network"
"In addition to the built-in
public Ethernet controller, VCS requires at least one more Ethernet interface per system.
Symantec recommends two additional interfaces." (for heartbeats/private network)
Although your setup is supported, it is certainly not recommended and far from 'best practice'.
Without I/O fencing in place, you ideally need four NIC's:
2 for MultiNIC
2 for Private Network
I personally do not believe that Low-Pri links is a good idea when MultiNIC is configured.
If I have only three NIC's in each cluster node and no I/O fencing, my config will be as follows:
Choose two independent NIC's for private network (heartbeats)
Config Public network on remaining NIC (no MultiNIC)
IMHO, reliable hearbeat links are the most important aspect of the cluster - you only have to deal with Split Brain once in your life to understand the importance of independent heartbeat links...
Please also read this section in the
VCS User Guide :
Chapter 10: About communications, membership, and data protection in the cluster
About cluster communications
About data protection
About cluster membership and data protection without I/O fencing
Examples of VCS operation without I/O fencing
