--- Net Cerebrum <netcerebrum@xxxxxxxxx> wrote: > On 1/29/07, Roger Peña Escobio <orkcu@xxxxxxxxx> > wrote: > > > > > > --- Net Cerebrum <netcerebrum@xxxxxxxxx> wrote: > > > > > I am now dealing with the issue of configuring > the > > > network interfaces. As of > > > now I have configured ethernet bonding on each > of > > > the hosts to achieve > > > network interface redundancy also. However this > > > leads to a lot of network > > > traffic since the same interfaces are being used > for > > > heartbeat / monitoring > > > also. Therefore, I am thinking of using the two > > > ethernet interfaces > > > individually, one interface for monitoring and > the > > > other one for the LAN > > > through which the clients will be able to access > the > > > hosts. They would be > > > connected to separate switches and the fence > devices > > > would also be on the > > > monitoring / control network. So I assume that > the > > > arrangement would be > > > something like: > > > > > > Node A > > > eth0 - 192.168.100.1 > > > eth1 - 172.16.1.101 > > > fence device - 192.168.100.11 > > > > > > Node B > > > eth0 - 192.168.100.2 > > > eth1 - 172.16.1.102 > > > fence device - 192.168.100.12 > > > > > > The interfaces eth0 and fence devices would be > > > connected through a switch, > > > while the other interfaces (eth1) would be on > the > > > LAN where clients would be > > > accessing them. In addition there would be two > more > > > floating / shared IP > > > addresses 172.16.1.201 for the database server > and > > > 172.16.1.202 for the > > > application server which would be defined in the > > > Resources section of > > > Cluster Configuration Tool and would not be > > > mentioned in /etc/hosts (read > > > somewhere in the documentation). > > > > > > Please let me know if these assumptions are > correct. > > > I am just wondering how > > > does the cluster manager figure out which > interfaces > > > to use for heartbeat > > > and monitoring. I haven't seen any such > > > configuration option in the > > > system-config-cluster program. > > I guess it will use the interface with the right > IP to > > reach the nodes ;-) or the one used to reach the > > default router if the nodes are outside any of its > > local networks > > I guess, in your configuration, if the nodes names > are > > bounding to IP 192.168.100.x (through DNS or > > /etc/hosts) then cluster applications will use > eth0 > > for its traffic > > am I wrong? > > > If that's true then I think we need to specify only > the monitoring IPs in > the cluster configuration along with the host names. > What happens to the > other set of static IP addresses which belong to the > interfaces on the LAN > subnet ? Do they get used anywhere in the > configuration ? Any ideas ? you mean yours 172.16.1.x IPs ? the floating IP (the one that is move between the node during relocalization) ? well, I think, again just guessing, that they are not used for cluster internal comunication not its network interfases, but ofcourse, should be monitoread by cluster services. cu roger __________________________________________ RedHat Certified Engineer ( RHCE ) Cisco Certified Network Associate ( CCNA ) ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
