Quote:
| Originally Posted by jmcgrady Notice that eth2.2 is a vlan resident on eth2. It shows up under "Virtual cluster interfaces" but theres only one instance of eth 2 under "Required interfaces". I believe that HA is considering eth2 as a single interface instead of two. Hence the "4 active 5 required" message. |
The output looks normal (and fine) to me. From memory, what I'd say ClusterXL is doing is monitoring the link state of the physical "eth2" interface, whilst at the same time also performing the CCP (UDP 8116) checks and VLAN connectivity checks on eth2.2. Because eth2.2 is a VLAN check only, it prints them on the same line.
Note that if you had "eth2.3" and "eth2.4", etc, they would not appear in the required interfaces list, because as I mentioned in my previous post it only monitors the first VLAN (and it considers if one VLAN is working then they all must be).
Honestly I think your problem is something to do with the VLAN interface not considering itself "up". A good way to test this is to edit the /$FWDIR/conf/discntd.if file and add "eth2.2" to it. If after restarting it does not complain, then you have found your problem. Of course, having said all that I could be wrong! I'd need to bring up my VMWare Cluster test and twiddle with it to see if I can reproduce your symptoms.