I don't know if it impacts on the cluster config, but I had problems recently with links in my bonding interfaces going down because of some hotplug interference.
The solution was to add HOTPLUG=no to /etc/sysconfig/network
Might be worth a try.
John.
Balaji wrote:
Dear All, Please ignore my previous mail I have using CentOS 4.4 Linux and Kernel Version is 2.6.9-42.EL
I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server)
I have configured Ethernet Channel Bonding in Each Cluster Nodes and Channel Bonding Configuration Details are
- Created bonding devices in "/etc/modprobe.conf" file alias bond0
bonding options bonding miimon=100 mode=1 2) Edit the "/etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1" configuration DEVICE=eth0 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none
DEVICE=eth1 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none 3) Created a network script for the bonding device is "/etc/sysconfig/network-scripts/ifcfg-bond0" DEVICE=bond0 USERCTL=no ONBOOT=yes NETMASK=255.255.255.0 GATEWAY=192.168.13.1 IPADDR=192.168.13.110 4) Reboot the system for the changes to take effect.
After i am rebooted both the server then cluster node becomes simplex and Services are started on both the nodes The cluster output in primary node
Member Status: Quorate
Member Name Status
primary Online, Local, rgmanager secondary Offline
Service Name Owner (Last) State
Service primary started
The cluster output in secondary node
Member Status: Quorate
Member Name Status
primary Offline secondary Online, Local, rgmanager
Service Name Owner (Last) State
Service secondary started
Before Ethernet Channel Bonding cluster services are active in one node and other nodes acts as passive node. But after Ethernet Channel Bonding cluster services are active on both the nodes
I don't know what is the problem and is their any configuration is required in cluster configuration file and cman is working only with eth0 interface
Can some one throw light on this peculiar problem
Regards -S.Balaji
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos