Hi Junior,

it is a very bad idea to run 2 (or more) systems with exactly the same 
hostname.

Without knowing your setting: You could provide one A record that points 
to a virtual IP address which is active on your preferred system.

-- 
Best regards,
Hauke

On Wednesday, March 27, 2013 05:29:44 PM Junior wrote:


Hello guys..




This is my first post here.


I have trying to configure two nodes... but is essential that keep the 
hostname of both machines identical.


I have my eth0 with my public IP... eth1 is running a private ip for our 
production system... and I add a new one..


The eth2 is running with the network 192.168.1.0 just for 
corosync/pacemaker. 


my servers are:
app01-a 192.168.1.11
app01-b 192.168.1.12


But is essential the /etc/hostname been the same... app01.foo.bar


I already add in the /etc/hosts the both IP with the hosts... but the 
corosync always get the original /etc/hostname and goes to eth1 


Any idea if is possible to configure or force the corosync to 
goes throw eth2... or maybe something that I can tell him that app01-a 
is the node that needs to been connected?


node app01-a
node app01-b
node app01.foobar.com[1]
property $id="cib-bootstrap-options" \
        dc-
version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \ 
        cluster-infrastructure="openais" \
        expected-quorum-votes="2" \ 
        no-quorum-policy="ignore"


----------------------------------


crm_mon -1
============ 
Last updated: Wed Mar 27 17:23:41 2013
Stack: openais
Current DC: _app01.foobar.com_ - partition with quorum
Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b 
3 Nodes configured, 2 expected votes
0 Resources configured.
============


Node app01-a: UNCLEAN (offline)
Node aoo01-b: UNCLEAN (offline)
Node _app01.foobar.com_: pending 


-------------------------------


resuming... I'm trying to make the corosync use the eth2 and a different 
hostnames that is not from /etc/hostname 




Thanks all


Junior











--------
[1] http://app01.foobar.com
_______________________________________________
discuss mailing list
[email protected]
http://lists.corosync.org/mailman/listinfo/discuss

Reply via email to