In my case, what is better: 1. using bonding for eth0 eth1 2. eth0 for public lan, eth1 using cross cable connection as private lan. And two heartbeat network configured in corosync
2010/11/29 Robinson, Eric <[email protected]> > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Mia Lueng > > Sent: Monday, November 29, 2010 6:24 AM > > To: [email protected] > > Subject: [Linux-HA] How to monitor the nic link status > > > > Hi: > > I have configured a cluster with two nodes. Lan setting is > > A > > eth0: 192.168.10.110 > > eth1: 172.16.0.1 > > > > B > > eth0:192.168.10.111 > > eth1: 172.16.0.2 > > > > I have configured a resource ip_0 192.168.10.100 on eth0. > > But when I unplug the eth0 link on A, the resource can not > > be taken over to B and no any log output. > > > > I've checked the /usr/lib/ocf/resource.d/heartbeat/IPaddr2 > > script and found there are no codes for nic link status checking. > > > > How can i monitor the nic link status to protect the virtual > > ip address? > > Thanks. > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > > Why not configure Ethernet bonding and use miimon? > > -- > Eric Robinson > > > > > Disclaimer - November 29, 2010 > This email and any files transmitted with it are confidential and intended > solely for General Linux-HA mailing list. If you are not the named addressee > you should not disseminate, distribute, copy or alter this email. Any views > or opinions presented in this email are solely those of the author and might > not represent those of Physicians' Managed Care or Physician Select > Management. Warning: Although Physicians' Managed Care or Physician Select > Management has taken reasonable precautions to ensure no viruses are present > in this email, the company cannot accept responsibility for any loss or > damage arising from the use of this email or attachments. > This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
