thanks again Ian, the key is what you have said "Think of them as "recieve only""
Now all is clear like water ;-) thank you very much for your help Greetings ESG 2009/5/5 Ian Hayes <[email protected]> > On Tue, May 5, 2009 at 12:54 PM, ESGLinux <[email protected]> wrote: > >> Hello, >> >> Thanks for your answer... >> >> 2009/5/5 Ian Hayes <[email protected]> >> >>> >>> >>> All cluster management communication in this cluster is via eth1. I >>> specified host1-management and host2-management as the hostnames in the >>> cluster config to partition off cluster traffic from the interfaces that are >>> actually doing the VIP work. The nodes provide a virtual IP on eth0, and a >>> script service, with the daemon bound to the VIP. For the iLOs and eth1, you >>> could either plug them into a switch on their own non-trunked VLAN, or you >>> can connect eth1 of host1 to the iLO of host 2, and eth1 of host2 to the iLO >>> of host1. Both eth1 and iLOs don't need a gateway since they're on the same >>> subnet. >>> >> >> If I have understand, if I use a dedicated switch, I must to connect IP2, >> IP3, IP5 and IP6 to the same switche and IP1 and IP4 to the service switch, >> isn´t it? >> > > If you're using a dedicated switch for cluster management, yes. Assuming > that IP1 and 4 are your public facing interfaces that will be holding the > service. You can use 2 and 5 for cluster management and fencing via IP3 and > 6. > > Or you can use crossover cables IP2 to IP6, and IP5 to IP3, but you will > have to run your cluster management over eth0, on the same interface that > you have your services bound to. Your choice. > > But you can't reach the iLO interfaces using the other iLOs. Think of them > as "recieve only". It's up to one of the hosts to establish a connection to > them and issue commands. > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster >
-- Linux-cluster mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-cluster
