Hi,
Of course. As per the Redhat recommendation you have to put the switch in the middle between two nodes.
Of course. As per the Redhat recommendation you have to put the switch in the middle between two nodes.
Due to this reason only, your second server is rebooting.
Best Regards,
S.Prasath
On 9 September 2014 13:19, Amjad Syed <amjadcsu@xxxxxxxxx> wrote:
Yes, the two are connected crossover cable with bonding. There is not switch in middle.So you mean to say i need to put a switch in middle with crossover cable for cluster communication ?On Tue, Sep 9, 2014 at 10:37 AM, Sivaji Prasath <prasathslt@xxxxxxxxx> wrote:Hi,Is this two connected crossover cable with bonding ? Do you have switch in the middle ?Note: Red Hat does not support use of a crossover cable for cluster communication.On 9 September 2014 12:44, Amjad Syed <amjadcsu@xxxxxxxxx> wrote:Hi,--I have setup a 2 node cluster using RHEL 6.5 .The cluster .conf looks like this<?xml version="1.0"?><cluster config_version="7" name="oracleha"><cman expected_votes="1" two_node="1"/><fencedevices><fencedevice agent= "fence_ipmilan" ipaddr="10.10.63.93" login="ADMIN" name="inspuripmi" passwd="XXXXX/><fencedevice agent = "fence_ilo2" ipaddr="10.10.63.92" login="test" name="hpipmi" passwd="XXXXX"/></fencedevices><fence_daemon post_fail_delay="0" post_join_delay="60"/><clusternodes><clusternode name= "192.168.10.10" nodeid="1" ><fence><method name = "1"><device lanplus = "" name="inspuripmi" action =""></method></fence></clusternode><clusternode name = "192.168.10.11" nodeid="2"><fence><method name = "1"><device lanplus = "" name="hpipmi" action =""></method></fence></clusternode></clusternodes><rm><failoverdomains/><resources/><service autostart="1" exclusive="0" name="IP" recovery="relocate"><ip address="10.10.5.23" monitor_link="on" sleeptime="10"/></service></rm></cluster>The network is as follows:1)Heartbeat (Bonding) between node 1 and node 2 using ethernet cablesThe ip addresses are 192.168.10.11 and 192.168.10.10 for node 1 and node 2.2) IPMI. This is used for fencing and addresses are 10.10.63.93 and 10.10.63.923) External ethernet connected to 10.10.5.x network.If i do fence_node <ipaddress>, then fencing works,However if i physically shutdown active node, the passive node also shutdowns. Even if i do ifdown bond0 (on active node), both node shutdown and have to be physically rebooted.Any thing i am doing wrong ?
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
--
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
- References:
- Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- From: Amjad Syed
- Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- From: Sivaji Prasath
- Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- From: Amjad Syed
- Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- Prev by Date: Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- Next by Date: Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- Previous by thread: Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- Next by thread: Re: Physical shutdown of one node causes both node to crash in active/passive configuration of 2 node RHEL cluster
- Index(es):