--- 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? > > The issue which then needs to be resolved is of > assigning hostname aliases > to the shared IP addresses since as per the > developers, the application > manager and the database need to use a hostname and > not an IP address. DNS ? /etc/hosts in each developer computer? cu roger __________________________________________ RedHat Certified Engineer ( RHCE ) Cisco Certified Network Associate ( CCNA ) ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
