On Fri, 11 Dec 2009 11:36:53 +0000, Christine Caulfield wrote <snip> > > Hmm. I am totally wrong. Very sorry. keyfile IS allowed in cluster3, it > overrides the one assigned in totem. In which case I'm not sure why it's > failing to validate on your system. > according to the validation file (cluster.rng) it should be an attribute of cman, while in my case it was attribute of multicast subelement and is not allowed there > The schema is a bit of a work-in-progress at the moment, which is why it > warns rather than fails if it finds an error. Did it work when you > removed keyfile ? > Yes i know and trying to help with one more config case (hence my email here in the first place). I have replaced it with <totem keyfile=".."> and passed this warning, but still can't pass the validation because of rm ... still looking for the reason. > > I still can't find how do i specify per node interface. There is interface > > allowed only in<totem> section while most of the nodes have (and use) bond0, > > for one of them i need to specify different interface for cluster > > communication. Is per node interface attribute missed from the validation > > schema or is removed completely? > > > > cman always binds to the address of the host given as a node name. see > > http://sources.redhat.com/cluster/wiki/FAQ/CMAN#cman_heartbeat_nic > I have used the answer of "How can I configure my RHEL4 cluster to use multicast rather than broadcast?" few lines below (with V2 initially), so it is safe to just remove this in my conf now and that step was passed. > Chrissie > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster